Toit
#surviving a power outage
Thread channel in help
RobvanLopik 11/09/2025 11:20 AM
After a power outage the ESP32 comes up faster than the WiFi router, so jaguar tends to fail. What is the easiest way to overcome this problem? Using a watchdog? And if so, which of the two, the built-in or the package?
milkmansson 11/09/2025 11:30 AM@RobvanLopik On all mine, jag just keeps trying, each attempt is like three times in succession. Then it has a 5sec stand down and does it again, continually. Could the failure be elsewhere? What do you see in the monitor?(edited)
RobvanLopik 11/09/2025 12:54 PM
Sorry, t didn't look at this project for 6 months so I did not remember well what was wrong. Looking at the code again I supppose the problem is caused by the MQTT broker (on a Raspberry Pi Zero 2) comes up much later still .
floitsch 11/10/2025 09:23 AMUse live reloading over WiFI to turbo-charge developing for your ESP32. - toitlang/jaguar 
You can delay Jaguar by using
If you then install a container that just doesn't do anything for 10s, Jaguar will wait for it, and then only try to connect to the WiFi.
However, Jaguar still runs all other containers. So if you primary container is the one crashing (which seems to be likely), then you need to deal with that in your container.
Two things come to mind:
- protect your own@milkmansson commented above). Your own program would need one too.
- protect accesses to servers. You already mentioned the MQTT broker, so that one should probably be guarded somehow. It depends a bit on which MQTT client you use. The default one reconnects automatically, but still needs a
-D jag.wifi=falseIf you then install a container that just doesn't do anything for 10s, Jaguar will wait for it, and then only try to connect to the WiFi.
However, Jaguar still runs all other containers. So if you primary container is the one crashing (which seems to be likely), then you need to deal with that in your container.
Two things come to mind:
- protect your own
net.open- protect accesses to servers. You already mentioned the MQTT broker, so that one should probably be guarded somehow. It depends a bit on which MQTT client you use. The default one reconnects automatically, but still needs a
catchconnect4 messages in total