-
Notifications
You must be signed in to change notification settings - Fork 18
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
Bug: mqtt connection loop in v2.1.0 #171
Comments
Could you please enable extended logging and then paste the logs here? |
I'm getting this loop randomly too. Using Mosquitto docker image as a broker
I don't know. I guess the default one When I restarted the agent to enable extendes logs, MQTT took a while to connect and then failed. Right after failing, it connected Logs from the start until it connected successfully (i guess)
After this, I've been waiting for the conection failed notification and it didn't poped up, but I've found this logs which might be helpful Logs
If/when it fails I will post logs here |
It happened
|
Thank you for pitching and and providing the logs! Some additional questions if I may:
|
i use the home assistant mosquitto broker addon with username+password, without certificates |
username + password too and without certificates I updated from the legacy app to this one recently, but I remember updating to 2.1.0 after. I don't recall receiving this notifications before the update (but there is a chance I'm confused sorry) |
Looking at the logs right now I can see 532 occurrences of Here it is all different occurrences with the stack traces for the error you mentioned
|
Ok so, I still wasn't able to fully replicate this, by this I mean the exception regarding disposed object. But before I elaborate: to have any kind o test bed - MQTT status cycling between "running" and "connecting" - I had to run two instances of HASS.Agent that had the same MQTT settings (client id). Now going back to what I tried to do, there is a test build available here - https://github.com/amadeo-alex/HASS.Agent/releases/tag/2.1.1-beta2-mqttdisposed - with the changes I mentioned at the beginning. |
The day after reporting the problem it stopped giving the notification errors (i guess) Didn't made any upgrades to any related container, but I had some manual restarts last weeks, maybe it helped making connections more stable. Now thats stable, can't reproduce it neither test the version you published 😕 |
I had the same problem. I have two Windows 11 users. I have disabled "Automatic Sign-in after Update" in Settings/User and my loop was gone. |
Describe the bug
after updating to v2.1.0 the MQTT tries to connect, connects successfully for like 1sec and tries to reconnect over and over again
To Reproduce
Steps to reproduce the behavior:
Expected behavior
mqtt should connect and stay connected
Screenshots
homescreen mqtt going from "running" to "connecting" quickly
Misc info (please complete the following information):
winver.exe
output): 24H2 Build 26100.1591Please check what's applicable (multiple answers possible):
Additional context
after a while it connected for 2 whole minutes and started looping again
Logs
The text was updated successfully, but these errors were encountered: