-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT No Longer Connects after upgrade to v5.1.0_modified #829
Comments
I tried reverting back to 5.0.2 but the problem still persists, so it may not be due to the upgrade after all. But the MQTT broker is clearly working as I can connect to and see the charge power state updates coming through just fine. Nothing has changed aside from me doing that upgrade. This just suddenly stopped working (again). |
may be the MQTT problem is relate to the bug see "Let's Encrypt CA is out of date" #806 if yes the workaround is to accept self-signed certificates |
I do not have SSL enabled on my MQTT broker as it runs on my local network. This issue eventually just went away on it's own. Several days later the EVSE finally successfully connected to the MQTT broker. |
I think I also just experienced this. Pressing the 'Restart' button OpenEVSE Wifi in the Firmware settings fixed it. |
I am running v5.1.2 and this issue still persists. My observation is that is openevse get disconnected from the broker for example there is transient loss of Wifi signal then it will not reconnect. The only way I have found to make it reconnect is to restart the Openevse Wifi module. I ran for many years on v4 and never experienced this. |
OpenEVSE is refusing to connect to my MQTT broker even after powering down and restarting the unit:
And yet I can connect from my local PC on the same network just fine:
I have tried disabling and re-enabling MQTT and self production, restarting the unit, etc. Nothing seems to work.
The text was updated successfully, but these errors were encountered: