Let's Control It

FYI :
The wifi was a little bit unstable with ESPEasy_mega-20190225.( 2 meters away from the wifi router)
I had decided to upgrade the Sonoff Basic from ESPEasy_mega-20190225 to ESPEasy_mega-20190305 to have the new wifi feature cpu eco mode.
After that, I only got one answer every 7 pings, so I was unable to http it.

So I have done a roll back.
To be honest, I cannot know if it was a wifi issue or a CPU issue, or something else, but it was not responding to the ping .

I have too many disconnections issues with ESPEasy_mega-20190225. But it looks like the pings awake it.
When I run a continous ping, I don't see any disconnection.
Is there a feature which make it sleep when there is no activity ? ( I have not set any rule, device or whatever, not even ntp).
It has not rebooted.
It seems to asleep as soon as the ping stops.
Any advice on an hidden option or another ESPEasy verison to use instead ?
Thanks
Gilles

I have seen the ping to do magic too.
See also my discussion here: https://github.com/esp8266/Arduino/issu ... -468961124

I am thinking of adding some kind of ping like activity to ESPeasy too.
For example when the nodes do send p2p traffic to eachother, these packets seem to get lost too and it is very easy to see it happen.

So maybe hosts sending out a p2p packet could also send some ping first to make sure the other end is "awake".
The first ping to a "sleeping" host may take a few 100 msec, but they will be answered. (as long as the sleeping host is sending out Gratuitous ARP packets)
So there should be something better or else the response may appear slow when for example switching off/on a light.

But I am fully aware of these issues and working very hard to get to know what is causing this.
Last night, I also upgraded a few of my nodes to SDK2.2.2 and this issue is still present.

I am convinced this is also causing lots of the HW watchdog resets and maybe also some reboots with "Exception" as reboot reason.
These crashes almost always happen while trying to send data to some host.
There is simply something wrong in the core libraries or SDK related to keeping track of the current state of the network connection.

Hello:

Regarding the ECO mode I'm also experiencing wifi disconnections. Currently I have a wemos with mega-20190305: 305 disconnections (beacon timeout) until I disabled ECO mode and now it has remained connected for 7 hours.

The delay() is having a side effect with core 2.4.2.

I have never been able to http the sonoff once upgraded to MEGA-20190305.
If I have some time, I will give it a second try.
BTW, I had used the bin file : ESP_Easy_mega-20190305_normal_ESP8266_1M.bin
Would you recommend me to use :
ESP_Easy_mega-20190305_normal_core_242_ESP8266_1M.bin
or
ESP_Easy_mega-20190305_normal_core_241_ESP8266_1M.bin

I will use the sonoff in a basic way with some basic rules and notifications. I don't use openhab or Domotiz or anything else (yet)

Thanks