Just found this issue on GitHub: https://github.com/letscontrolit/ESPEasy/issues/3072 that talks about a similar problem. Disabling syslogging appears to resolve my problem.
Johan

FWIW: like before, there is no problem when using the old WRT54G router: 15748 : Info : EVENT: System#Sleep 15763 : Info : SLEEP: Powering down to deepsleep... enter deep sleepsll|l|lc|sccnnlggcpl{lrlpglcg|sbogld`gd`gsol{gdld`'bl`rolphU69 : Info : INIT : Booting version: (ESP82xx Core 9632e868, NONO...

ABove was using the "normal_4M1M" firmware. I also tried the "Test_beta" of the same, but with the same result.
Johan

No joy, I'm afraid. Again, there's no problem on a cold boot, but on warm boot the board goes in an endless loop. Here's a part of the serial log: : Info : FS : Mount successful, used 76304 bytes of 957314 499 : Info : CRC : program checksum ...OK 508 : Info : CRC : SecuritySettings CRC ...OK 621 : ...

Hi. I tried fixed vs auto channels before and that didn't help. I have one new development though. I had an old Linksys WRT54G lying around and decided to give that a try. And behold: with this router, everything works perfectly. No changes to the D1 mini, apart from the change in access point. So t...

dampa wrote: ↑03 Apr 2020, 09:39 How about setting the IP address in the router based on the MAC address of the D1 and increasing the wake time?

That is the way it's set. IP is received correctly.
Increasing the wake time is ignored by the D1. It ALWAYS sleeps at 12.some seconds...

Well, the logs show that the IP address is received correctly every time. I also just noticed that the webserver appears to be up - at least, it threw me the login window before going back to sleep. Still ignores the awake time I set to 20 sec. It's just that outgoing messages are not going anywhere...

@JohanE - Do you have Config->Sleep mode->Sleep on connection failure checked off? It was checked on, but checking it off makes no difference. I also tried various various settings of the times there, but always the same result. I did do some more testing, after flashing the latest Mega firmware (E...

OK, that solves that. Still, it remains that I can't use rules, old or new engine. I had it running for two days without the rules and it sleeps, wakes up, connects, sends data and sleeps again flawlessly. Now, I went back in and the ONLY thing I changed was to put the check in the box to switch &qu...

EVENT: System#NoSleep=30 This will only be logged the first time (since cold boot) the node will go to deep sleep. Well, then how do you explain it's occurrence in the second and third logs in post #3? These are "wake from deep sleep", and the event appears there, at t=694 in the second l...

Following up on my own conclusion from previous post, I decided to try by switching off the rules option and use the built-in reporting to Domoticz. Remarkably, that solves the problem! I do still see the occasional "Connection failed" error, but the WiFi appears to be connecting reliably....

Thanks for your reply. I had tried before with reversing the two APs, but to no avail. I tried your suggestion, with only the closest AP in the settings and the behaviour is exactly the same, only now trying several times to access the one AP and eventually getting to a stable result. See log below....

Hi all, I just posted my first message in the software forum, but some introduction about myself. I am from the Netherlands and have a Domoticz system that I use to control some things in my house. I'm now starting to extend by using sensors on D1 mini boards, using ESP Easy. I like the software so ...

Hello everyone, I've been experimenting with ESP Easy for a while on D1 mini boards. Mostly successful, but I thought I was having problems with recovery from deep sleep. However, after some experimenting and logging, it turns out the board does wake up reliably, but it does not reconnect to wifi. I...