Replies: 4 comments
-
|
I believe this should happen by default as the autoconnect uses the defaults to reconnect automatically, however this bug might be relevant - tzapu/WiFiManager#1752 This being said, I cannot replicate at the moment - my devices seem to reconnect after a while - how long are you waiting? |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that this does not happen with my ESPGeiger 0.6.2. If I pull the power or reboot my access point, the ESPGeiger simply reconnects itself when the access point is available again. That said, I have never rebooted the ESPGeiger when the WiFi hasn't been available. If I did reboot the ESPGeiger when the WiFi was not available, then I would expect the ESPGeiger to drop to it's default 'WiFi Manager' standalone AP (like before it is connected to an AP and you connect to the ESP itself for initial config) and I would assume it would just hang there as it is waiting for input, as opposed to looking for the WiFi. I'm not sure if this is what you are experiencing, tinovator. FWIW I am using all Ubiquity networking gear. USG-3P router, UAP-AC-Lite and UAP-AC-Pro access points, along with HP network switches. |
Beta Was this translation helpful? Give feedback.
-
|
This could be it, this would likely be during startup if the wifi isn't available - I can set a timeout on the configuration portal so that we can handle such instances and retry connection periodically/work offline. |
Beta Was this translation helpful? Give feedback.
-
|
The latest releases hopefully have fixes for this. Let me know if you have any feedback! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
HI, not sure if this is intended or not but I stumble across potential for improvement.
Uppon initial booting ESP32 connects to WiFi and everything is OK.
If WiFi becomes unavailable ESP32 will not automatically reconnect to saved WiFi when it becomes available again.
Device has to be powered off and on again for connection process to be run again.
Is that something that can be fixed/implemented?
Since my Geiger is on a remote location if I lose power for AP it will not submit data again until I power-cycle it.
Beta Was this translation helpful? Give feedback.
All reactions