You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DeepSleep Wakeup rule is not working with Timers correctly when setting Rule1 5 (wakeup ONCE and then STAY ON).
My goal is to run an ESP32-CAM module using a solar panel/battery as a power source, so I need the ESP32-CAM to go to into DeepSleep at sunset to conserve battery power at night, and then come out of DeepSleep at Sunrise... I need this to happen every day.
When setting Rule1 Wakeup, then setting Rule1 5, then setting a Timer to wakeup the device from DeepSleep ONCE and NOT go back to sleep... this fails... instead of staying awake, the device goes back into DeepSleep Countdown immediately after waking up.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Steps to reproduce the behavior:
I followed the Documentation exactly...
I set "Rule1 Wakeup"
Then I set "Rule1 5" which is supposed to wake up the device from deepsleep oon the next wakeup event and then STAY ON and NOT go back into DeepSleep mode unless specifically commanded to do so again.
EXPECTED BEHAVIOUR
I expected this to behave like it is described in the Documentation...
When setting "Rule1 Wakeup" to mode ONCE by setting "Rule1 5" and then having a timer wake the device from DeepSleep the device is supposed to stay ON and NOT go back into DeepSleep immediately after waking up.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
Here is my Timer setting that I used to wake the device from DeepSleep at a specific time... the device does wake up at the set time, but then immediately goes back into DeepSleep Countdown instead of staying awake like it is supposed to.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered:
PROBLEM DESCRIPTION
DeepSleep Wakeup rule is not working with Timers correctly when setting Rule1 5 (wakeup ONCE and then STAY ON).
My goal is to run an ESP32-CAM module using a solar panel/battery as a power source, so I need the ESP32-CAM to go to into DeepSleep at sunset to conserve battery power at night, and then come out of DeepSleep at Sunrise... I need this to happen every day.
When setting Rule1 Wakeup, then setting Rule1 5, then setting a Timer to wakeup the device from DeepSleep ONCE and NOT go back to sleep... this fails... instead of staying awake, the device goes back into DeepSleep Countdown immediately after waking up.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
I followed the Documentation exactly...
I set "Rule1 Wakeup"
Then I set "Rule1 5" which is supposed to wake up the device from deepsleep oon the next wakeup event and then STAY ON and NOT go back into DeepSleep mode unless specifically commanded to do so again.
EXPECTED BEHAVIOUR
I expected this to behave like it is described in the Documentation...
When setting "Rule1 Wakeup" to mode ONCE by setting "Rule1 5" and then having a timer wake the device from DeepSleep the device is supposed to stay ON and NOT go back into DeepSleep immediately after waking up.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
Here is my Timer setting that I used to wake the device from DeepSleep at a specific time... the device does wake up at the set time, but then immediately goes back into DeepSleep Countdown instead of staying awake like it is supposed to.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: