Open ctml91 opened 3 months ago
I experience the same, but I've only noticed it when restarting HA in general. After HA boots, the devices remain unavailable, until I restart the Govee Add-on
I noticed that there was a recent update to the mqtt broker addon to increase the number of messages that it can handle, I suspect that updating that will improve your experience with this issue.
I have the exact same issue where every time I restart home assistant, my Govee light will be unavailable until I restart the Govee to MQTT Bridge plugin. I'm using the most current version of Mosquitto broker (6.4.1) and still having this issue.
same issue here
Same issue here, need to restart the bridge after every home assistant reboot.
Edit: I created an automation in nodered to restart the govee addon a few minutes after HA has started as a work around.
Govee Device SKU
H6159, H7060
Govee2MQTT Version
2024.04.29-30cf7732
Describe the issue
Randomly devices disappear and stop updating from Govee2Mqtt. In HA the devices appear as unavailable (2 x H6159, 2 x H7060), restarting Govee2Mqtt alone fixes the issue and the devices then appear as available from HA.
One theory I have is my flood lights which are on a separate smart switch (because it's on an extension cord shared with some other dumb devices that need on/off functionality) gets turned off from the external switch then perhaps G2M doesn't handle an existing Govee device dropping from network and it breaks mqtt functionality for all devices that are still on the network?
Before the restart of G2M, container logs show requesting updates but nothing is propagated to HA.
Startup Diagnostics
This is as far back as the logs show. Since restart fixes, logs after restart are not as useful.
Additional Logs
After Restart of G2M (this happened when all devices were online during day)
Home Assistant Logs
No response
Anything else?
No response