reboot_timeout (Optional, Time): The amount of time to wait before rebooting when no WiFi connection exists. Can be disabled by setting this to 0s, but note that the low level IP stack currently seems to have issues with WiFi where a full reboot is required to get the interface back working. Defaults to 15min. Does not apply when in access point mode.
I’m quite unnerved by the way the documentations for reboot_timeout blame the current (when was current?) ESP framework but does not point to any open issue or reproduction steps. Any one knows?
To me, it sounds like if you set the time out to zero and then the board loses it’s wifi connection, even if the wifi connection is restored the boards interface(web server?) will still be unreachable until a restart.
Have you set a board to zero and then dropped it’s wifi connection, to see what happens when the connection is restored?
I have not tried anything as I’m trying to observe what the exact problem is, it appears that:
I set my Beken running ESPHome with reboot_timeout: 0s
Brought down my wifi for 15 mins and up again
The LEDs on ESPHome blinks once every cycle indicating there is a problem
Yet, after a few days, my router page still do not show these devices acquire an IP address
It is hard to tell if the ESPHome did not try or could not get an IP
But it certainly knew something was wrong, probably from the fact it did not receive any incoming connections
Which brings up the questions:
How often does ESPHome try to re-acquire an IP? This feels like the prime suspect since the docs imply the problem was intermittent, but I have been able to consistently reproduce the problem
How often does HA try to connect to ESPHome devices? (Probably less than 15 mins since the default ESPHome tries to reboot itself every 15 mins)
At this stage, I think it might be helpful to eliminate #7 by making the LEDs blink twice every cycle if it has an IP but no connection with HA