Is this waking it by means of an internal timer, receipt of a WiFi command
or an external event from something like an RTC interrupt?

I need to do the RTC method in the near future, the WiFi method would mean
I could have one central RTC and use a broadcast to get data back from
outlying sensors (maybe) - not so sure about internal timers...

Presumably waking from deep sleep isn't possible with an ESP-01 as GPIO16
doesn't appear?Are they connected on the board?

I haven't investigated sleeping ESPs yet - I still have upload issues...

On 28 April 2015 at 01:00, Ivan Grokhotkov notifications@github.com wrote:

Merged #135 #135.

—
Reply to this email directly or view it on GitHub
#135 (comment).

ESP-01, get out some really tiny wires, connect right to the chip, and good luck. :-)

I was able to do this successfully with an ESP-12. When you deepSleep, the ESP8266 goes to sleep until an internal timer brings GPIO16 low. Tying this to RST allows it to reboot the ESP8266. (No state is stored, so, see my other request to bring forward the RTC storage, which is stored across a .deepSleep reboot. Another alternative: Store in EEPROM/SPI flash.)

I believe there are other sleeping ways to wake on WiFi/other GPIO interrupt, but they use about 3x as much power. (Also, I don't know what command does this from the ESP8266 SDK, it might not even be easily exposed.) If you want to use the .deepSleep method as a single external interrupt, you could probably .deepSleep (for nearly forever?) then bring RST low to "bring it out of deep sleep" / reboot.

I'm in my 60s, my hands are no longer steady and I have cataracts - I can
barely solder 0.1"headers on stripboard now - not an option!!!

GPIO16 is brought out to the header pins on the Olimex module - that may be
helpful to someone...

Knocking Reset low to reboot was what I was thinking for an RTC Interrupt
(once I can understand how to eliminate the bootloader 'rubbish' on the
serial lines (I've read the posts, but I'm not there yet) and discovered
how to reduce the connect time.

Wake on WiFi would be good, but the power consumption (I've seen 48mA
quoted somewhere) would be a significant issue.

Thanks

On 28 April 2015 at 19:23, linagee notifications@github.com wrote:

ESP-01, get out some really tiny wires, connect right to the chip, and
good luck. :-)

I was able to do this successfully with an ESP-12. When you deepSleep, the
ESP8266 goes to sleep until an internal timer brings GPIO16 low. Tying this
to RST allows it to reboot the ESP8266. (No state is stored, so, see my
other request to bring forward the RTC storage, which is stored across a
.deepSleep reboot. Another alternative: Store in EEPROM/SPI flash.)

I believe there are other sleeping ways to wake on WiFi/other GPIO
interrupt, but they use about 3x as much power. (Also, I don't know what
command does this from the ESP8266 SDK, it might not even be easily
exposed.) If you want to use the .deepSleep method as a single external
interrupt, you could probably .deepSleep (for nearly forever?) then bring
RST low to "bring it out of deep sleep" / reboot.

—
Reply to this email directly or view it on GitHub
#135 (comment).