[Bug]: ESP32 "Light Sleep" doesn't work if device is in the CLIENT role

[dm5tt]

Category

Other

Hardware

Heltec V3

Firmware Version

2.5.x

Description

If the device is set as CLIENT with power saving activated it stays awake the entire time.

How to reproduce

1. Set "CLIENT" role
2. Set "Minimum Wake Interval" to 1s
3. Look at the console

It stays awake the entire time:

DEBUG | ??:??:?? 662 [Power] Battery: usbPower=0, isCharging=0, batMv=4122, batPct=95
DEBUG | ??:??:?? 682 [Power] Battery: usbPower=0, isCharging=0, batMv=4122, batPct=95
DEBUG | ??:??:?? 702 [Power] Battery: usbPower=0, isCharging=0, batMv=4122, batPct=95
DEBUG | ??:??:?? 722 [Power] Battery: usbPower=0, isCharging=0, batMv=4122, batPct=95

Compared to the ROUTER role:

INFO  | ??:??:?? 1 [RangeTestModule] Range Test Module - Disabled
DEBUG | ??:??:?? 4 [PowerFSM] Enter state: ON
INFO  | ??:??:?? 7 [PowerFSM] lsEnter begin, ls_secs=86400
INFO  | ??:??:?? 7 [PowerFSM] lsEnter end
INFO  | ??:??:?? 7 [PowerFSM] setup LORA_DIO1 (GPIO03) with wakeup by gpio interrupt
INFO  | ??:??:?? 37 [PowerFSM] Exit light sleep cause: 4
INFO  | ??:??:?? 37 [PowerFSM] setup LORA_DIO1 (GPIO03) with wakeup by gpio interrupt
INFO  | ??:??:?? 37 [PowerFSM] Exit light sleep cause: 4
INFO  | ??:??:?? 37 [PowerFSM] sleeping, flash led!
(...)

[thebentern]

screen_on_secs and wait_bluetooth_secs also delay Light Sleep

[dm5tt]

Can confirm. Reducing both to 1s fixed the issue. Device now properly sleeps in "CLIENT" role.

Thanks for super fast help.

[thebentern]

No worries. The power FSM is a complex beast. Router mode cuts through some of the states adding to confusion. One of these days we'll do some cleanup and consolidation.

[dongdigua]

firmware/src/mesh/PhoneAPI.cpp

Line 278 in 29893e0

fromRadioScratch.config.payload_variant.power.ls_secs = default_ls_secs;

is this line ignoring my setting???

whatever value I set, it's always 300 on CLIENT