You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So now, I get to find a more graceful way (e.g. a hack) to recover from this because even if the newer core is better, it exhibits quite a bit more instability.
Thankfully, this results in a controlled restart (under Keg cop control) so it's not horrible. The worst part of it is that the compressor lockout may cause a kegerator to be off while that timeout runs out.
The text was updated successfully, but these errors were encountered:
Did you actually fire up wireshark and see the same deauth frame coming through? I ask, as that's something I was experiencing personally earlier, but have not been experiencing since more recent versions of esp-idf (via more recent Arduino framework releases) have been available
"Good enough" for now. There is a compile-time define for TRY_WIFI_RECONNECT in wifihandler.cpp if I want to try again. Right now it reboots on WiFi failure.
On occasion, the WiFi connection will disconnect and fail to reconnect:
This seems to be the same as Wifi connection fails - only works after router reboot #8412 in the ESP8266 core for Arduino, and is explained REALLY well in ESP32 STA deauth frame causing reconnect issues (IDFGH-6544) #8192. The tracing tablatronix did here almost mirrors what I saw.
So now, I get to find a more graceful way (e.g. a hack) to recover from this because even if the newer core is better, it exhibits quite a bit more instability.
Thankfully, this results in a controlled restart (under Keg cop control) so it's not horrible. The worst part of it is that the compressor lockout may cause a kegerator to be off while that timeout runs out.
The text was updated successfully, but these errors were encountered: