Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Maximum for .sleep

dzairo last edited by

Hi.
What is maximum for sleep function .. is possible to set every hour ?? or more ?? for example every 4 hour ??

regards.
Reply Quote 0
1 Reply Last reply
hek Admin last edited by

The function takes an unsigned long, so the longest you can sleep is 4,294,967,295 milliseconds. That's 1,193 hours or 49.7 days.
Reply Quote 3
1 Reply Last reply
dzairo last edited by

oh it's really long ..
thanks.
Reply Quote 0
1 Reply Last reply

3
Posts

1551
Views

Log in to reply

Suggested Topics

not understanding Smart Sleep
Development • sleep smartsleep api • • Stef9998

6

0
Votes

6
Posts

121
Views

@Stef9998 said in not understanding Smart Sleep: @rejoe2 I'm in the process of configuring an OpenHab instance, and the binding should support smart sleep Don't know about OH's abilities, I "just" did the FHEM implementation of that feature . That I don't understand. Why should the controller have queued messages when the node is sending the second type (going to sleep). The controller knows the node is awake (cause of first/awake message), so why should it start to queue them? It should just send them, and then when the controller knows, that a node will be asleep (second message) start queueing. The user or some automatics could create some message to be sent out at any point in time. But sending out any message only makes sense when the controller knows the node is actually listening - these are sparse blinks in time, so most of the time a message will be queued first (or let's call it retained to stick to mqtt conventions). Then the controller has to wait for a signal from the node side, but as described earlier, this should not be the "awake" message (meaning a sensor can deliver some values and so on), but the "will go to sleep" one (meaning: "I will stop talking now, but continue to listen for 500 ms now"). Hope the fog is clearing now...
Testing a sensor with sleep
Development • sleep mega • • CrankyCoder

7

0
Votes

7
Posts

2165
Views

Ok I got it to work. I misunderstood how the interrupts worked. Got it now. The culprit was the if statement detecting if the state changed. Since the state was being maintained while sleep, it wasn't firing when I pushed the button. Thanks for everyones help!!
DS18B20 Sketch from Examples doesn't brings Node to sleep.
Troubleshooting • ds18b20 sleep sleeping • • Floca

7

0
Votes

7
Posts

2556
Views

@Floca Your node is defined as repeater, and repeaters do not sleep by definition: See log: 65890 !MCO:SLP:REP To disable repeater mode, comment this line (writing "Disabled" won't work): #define MY_REPEATER_FEATURE Disabled
Arduino Leonardo serial port and MySensors sleep
Troubleshooting • sleep leonardo • • doctor64

4

0
Votes

4
Posts

3442
Views

@hek Accordingly to LowPower library documentation, library support Atmega32U4 processor, so should work on Leonardo. Look's like i need to investigate deeper.
Node with Interrupt, sleep and batteries
Troubleshooting • interrupt sleep • • sundberg84

16

0
Votes

16
Posts

10905
Views

Yea, now I understand how to use that!! I will do that, thats probably the best... will try! Thanks alot everybody involved! @martinhjelmare @AWI @Yveaux
Radio does not go to sleep
Troubleshooting • radio sleep • • A Former User

6

0
Votes

6
Posts

2187
Views

@hek Just a hunch, could it be the radio that somehow is stuck in receive mode, and not going to sleep? If I remember correctly from the datasheet, it almost uses the same current in both transmit and receive mode (~14mA) / Thomas

0
Online

11.4k
Users

11.1k
Topics

112.7k
Posts

Copyright 2019 Sensnology | Forum Guidelines | Privacy Policy | Terms of Service

1 / 1