-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device going to sleep forever #191
Comments
Hi Stefan,
Shouldn't the log entry level after the sanity check:
be of LOG_LEVEL_ERROR? Currently it is of LOG_LEVEL_DEBUG_MORE:
As I understand this is the current plausability check, which unfortunately would allow the 1 second sleeping time:
Wouldn't it make sense to introduce a MinSleepIntervall of maybe 3 seconds which assures that the device can goto sleep and gets woken up again. If so, I would suggest:
|
Added new 5sec minimum deepsleep time.
I added some comments to make it more understandable what we are doing here and why. I added your suggestion about the minimum sleep interval. I was able to send the device to death (infinite sleep) without. Thanks for bringing this up. |
With the latest fix it now also does not wakeup more often than requested. |
BUG DESCRIPTION
It seems that under some conditions the sleep timer is set for a too short sleeping pause. As a result the device goes asleep and misses the wake up time. As a consequence it will probably never wake up again.
REQUESTED INFORMATION
status 0
/ Syslog Info :TO REPRODUCE
I don't know, this happened the first time - device is not reachable anymore and more than 4000km away :-(
EXPECTED BEHAVIOUR
Should wake up after 5 minutes
ADDITIONAL CONTEXT
I think the problem is shown in these two lines:
Current time (Epoch) is: 1569067799 - GMT: Saturday, September 21, 2019 12:09:59 PM
Update Timer (Epoch) is: 1569067800 - GMT: Saturday, September 21, 2019 12:10:00 PM
It shows that there is one second time for the device to fall asleep and wake up again. I think it went the second asleep, when it should wake up again and is now sleeping forever.
In my opinion there should at least be a plausibility check for the size of the next sleeping window (Epoch-Time minus Update-Timer > 5 seconds).
The text was updated successfully, but these errors were encountered: