ESP8266 Community Forum

- Mon Jun 05, 2017 10:47 am #66758

For a specific application where you need to wake-up only few times per day and you want to conserve power the hardware RTC solution remains the most stable and power efficent.

for a specific application maybe but surely not in general.
so be more specific on you application ....

They are some application's where nothing can beat a true RTC configuration.
If you think that in the case when you need to wake up and check/send some data few times per day, 24/7, your total power consumption is more for a hardware RTC implentation than for software "RTC" with the entire process of wake-up ESP8266 every hour-and-something for evaluation and go to sleep again,etc I will be definitely not the one to try to convince you that you are wrong. Same for the long run reliability factor point of view.

ESP8266 MPDMv4 AC MAINS Dimmer Home: http://esp8266-projects.com/2016/04/mpdmv4-mains-dimmerswitch-html/
Available on Tindie: https://www.tindie.com/products/nEXT_EVO1/universal-ac-mains-dimmer-mpdmv41/

- Tue Jun 06, 2017 4:05 am #66794 There is a library to help with waking up just once a day, here. You can look in the code for that for an example of how to use an RTC memory counter to do the multiple 71 minute sleeps.

- Sun Jun 11, 2017 4:49 am #67010 With the sdk 2.1.0 the deep_sleep parameter is changed from uint32 to uint64.
This should alleviate some deep_sleep trouble, still leaving the gpio16/rst blemish / burden.

- Sun Jun 11, 2017 5:12 am #67011

With the sdk 2.1.0 the deep_sleep parameter is changed from uint32 to uint64.
This should alleviate some deep_sleep trouble, still leaving the gpio16/rst blemish / burden.

However unfortunately the unit64 sleeps don't seem to work very well. See here. Would love it if someone else could give it a go and confirm or disprove those results.