@d-alvrzx the ESP32 has various sleep modes with various possibilities for wake up sources. The lowest power modes are indeed quite limited by design. IIRC the Pycom firmware uses ext1 wake up. You’ll find details of the different wake up sources of the ESP32 in the ESP IDF docs: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/sleep_modes.html

Dear @martijnthe, we have been able to successfully get the boot time of our Terkin-Datalogger [1] from about 25 seconds down to about 3 seconds by freezing the modules like outlined by @robert-hh. The code base including all third-party modules is around 10 kLOC and we have released the result as builds called Annapurna [2]. With kind regards, Andreas. [1] https://github.com/hiveeyes/terkin-datalogger [2] https://community.hiveeyes.org/t/annapurna-firmware-for-pycom-esp32/2754

You have to look at machine.deepsleep link text For example with machine.deepsleep(60000) the LoPy will sleep for 60 seconds (better to say about 60 seconds).

@akshayjames I think the problem is the button on the Pysense goes low when pressed, not high, so you want to wake up on low.

Solved: just needed to increase the timeout to 2 seconds before setting machine.pin_deepsleep_wakeup(['P3'],machine.WAKEUP_ALL_LOW, True) and then going into deepsleep