Your new topic does not fit any of the above??? Check first. Then post here. Thanks.

Moderator: igrr

User avatar
By schufti
#42805 hmm, not really confusing (at least for your case). I read it, that in light sleep (and everything deeper) CPU clock is off. Meaning that your concept with detecting your "events" by checking gpio state in loop() will not work at all ... (concept flawed by design I would say)

AND: don't forget: it's no ultra-low-power µC that runs off a lemon, clocked by a watch crystal. It is a high performance rtos capable "system" even providing wifi and network stack clocked with 80MHz. And by design the power is either on or off; no gears, throttle or handbreak.
User avatar
By PaulRB
#42810 That's my point about the documentation. Its ambiguously worded. You read it one way, i read it another. We both read what we wanted or expected to see. Writing technical documentation is not easy, and if English is not your first language...

Clearly the engineers built power saving features into the chip. What they exposed to us as users so far may be less than the chip is capable of because they could never forsee all the applications we might dream up. As for all-or-nothing cpu speed, that's normal. You achieve low power in ATtiny cpus in the same way. Suspend the processor and wake on timer or external event. Its like PWM-ing an led. Its always full on or off but the effect is variable brightness.

Sounds like your advice is "forget it/flogging a dead horse". I am prepared that you may well be right. Hence plan B i mentioned. But it would be considerably simpler if i can get the whole low-power thing to work on the esp.