Hello,
thanks for that quick answer.
Unfortunately its quite hard to reproduce those events. In my lab enviroment I cannot replicate those events. Those occur only in the field and from there the logging for the ESP is turned off / not reachable.
I tried to download a troubleshoot log last time but for some reason it didnt work, I will try that next time.
As said: These errors occur very rarely and on different systems.
The error modes are also quite different, sometimes all ESP32s cannot connect, sometimes just one. I suspect different reasons for these 2 behaviours.
For more background info:
The ESP32s power supplies are switched via the output port of the RUT240. Toggling the output pin via webUI(so power cycling the ESPs) doesnt solve the issue. There are up to 8 ESPs connected to one router. So I think the problem lies somewhere in the router.
I'm very curious about the "daemon.info unhandler[2363]: modem_init[3]" message, since it was interleaved with the connection attempts of one ESP32 - can you give me a pointer what this error means?
Sorry, that I cannot provide further information from the router logs, I will try that next time.
Best regards
Dennis