Closed S57PNX closed 3 weeks ago
My plan is to stop all WiFi with button for new ultra low sleeping (until packet rx) digirepeater
I just went through the code and I think I can make a minimal change to make autoap run only once, and then only try to connect to wifi evey 15 min. Would this help for now?
I just created merge request #159 to fix this behaviour. While I have been testing this extensively in my lab with different configs, as usual more testing is recommended.
I have been running this fix on two solar digi sites for a week and no problems observed so far. Reducing power consumption from 85mA to 37mA is a nice improvement, it makes my batteries last twice as long.
added a WIFI KILL Switch (on Wifi AP section of webUI config)
this is to kill Wifi and WifiAP completely from restart for pure Remote Digirepeater which should lower power comsumption a lot (as we need for this special cases)
please test it a comment
Digi EcoMode not kills all and uses as low as ~21,5mA for esp32s3+sx1262 and ~24mA for esp32+sx1278 ;)
In #144 we fixed the return from AutoAP mode to Wifi client mode. Unfortunately this uncovered a new issue that was hidden before: when AutoAP stops due to timeout, it correctly tries to connect to Wifi client and after this fails, it will immediately start AutoAP again.
On a site without wifi, this means that AutoAP will be constantly on. It will timeout but restart immediately. This is convenient but wastes electricity on solar systems.
My expectation is that AutoAP is only tried once after reboot - when it times out and there is no wifi present, it should remain off and save power while checking if wifi gets back. If there is no wifi and you need to service the gate, you need to reboot it to get into AutoAP mode.
In my mind the logic should be:
This logic needs another wifi check loop and some refactoring of the code, which is a bit too much for me at this late hour in the evening. Better ideas?