Battery drain during sleep mode about espeasy HOT 16 CLOSED

that is indeed very bad. this is with 2.0.0-dev7?

from espeasy.

I do not think there was any change between the last release and 2.0.0-dev7 regarding the "connect" routine. But I will give it a try to be sure with one of my sensors.

from espeasy.

I confirm, no change with the latest version.

from espeasy.

Yep all i needed to know that it was 2.0.0-dev7 or newer. I'll look into it and fix it. (going to use deep sleep on battery's myself as well)

from espeasy.

Any news on the battery drain in sleep mode when router is not reachable ?

from espeasy.

still didnt get to it:(

from espeasy.

working on the wifi stuff right now (making it more efficient and fixing issues)

from espeasy.

there where various issues with it. it also was trying to connect to SSID2, even though it wasnt defined. this resulted in 6 connection attempts, which takes ages.

now it will only do one connection attempts on the main SSID, and another one on SSID2 if its defined.

also serial logging is much more clear now.

try it and let me know if you have any issues. :)

from espeasy.

Thank you ! Could you please give some details on how the ESPEasy should behave now. I my case, It tried to connect until battery was gone if there was no Router in view. If we use sleep mode, I would understand it would try again after the sleep time, means if if my router is switched off during the night, the ESPEasy would still have tried during the night, bot not non-stop. Maybe I can follow your changes, I guess you modified Espeasy.ino and wifi.ino!

from espeasy.

As far as i could see it would try to connect 6 times, almost taking a minute in total.

New behaivior: Try to connect 1 time (and 1 time to ssid2 if its defined), do stuff (even if connection fails), sleep again.

I didnt test with any controllers and timeouts for that, so i will test that as well now.

from espeasy.

from espeasy.

I tested with one sysinfo device to http domoticz, while using a non-existing SSID:

INIT : Booting version: 
FS   : Mounting...
FS   : Mount successful, used 72288 bytes of 957314
INIT : Free RAM:25592
INIT : I2C
INIT : SPI not enabled
WIFI : AP Mode disabled
IP   : Static IP :192.168.13.92
WIFI : Connecting blah attempt #1
WIFI : Could not connect to AP!
WIFI : AP Mode enabled, reachable on 192.168.4.1
INIT : Rebooted from deepsleep #37
WD   : Uptime 0 ConnectFailures 0 FreeMem 20320
SYS  : 0.00
HTTP : connection failed
SLEEP: Entering deep sleep...
EVENT: System#Sleep

This took almost 20 seconds. So if your sleep delay is 60 seconds, it will have a dutycycle of 25%.

Now here's what we could do: If it cant connect, just go back to deepsleep immeadeatly without doing anything. I'll think i add an option for this. We should also make controllers smart so that they dont try to connect when there's no connection.

from espeasy.

ok, I usually use sleep time of 10 minutes (600secs). An option "goto deep sleep if connection fails" would be a good solution!

from espeasy.

Ok added a new option for this. will document it on wiki.

from espeasy.

from espeasy.

i'm using Ubuntu 16.04.2 LTS, with platformio.

from espeasy.