Hi, I’m new to HA and this forum. I have 11 Govee lights that I want to integrate in HA. But every step I follow from solutions found on the internet or on YouTube, I just can’t get it to work. I have the MQTT broker installed and when I start it I get see this in the log:
I have been trying everything to troubleshoot this and it’s very frustrating. Starting to doubt if I even should have started with HA, but I invested in a Beelink S13 and Aqara M3 and want to continue.
Hopefully someone can explain to me what to do in layman’s terms, because this is all new to me.
Tell us a little about your setup. How do you have HA running? OS? Docker? This will help us understand if you’re using add-ons or containers, which will require different configurations.
I have it running on a Beelink as an OS. User settings is advanced. And I was following this YT video (https://www.youtube.com/watch?v=i2PitlYazu0&t=1s) and all went well till 07:40. It won’t add any devices.
I use HAOS, too. Okay, so you have your Govee API?
I experienced an issue with this add-on a few months ago and in order to get it to work correctly, I had to add the MQTT broker info in the Govee to MQTT Bridge configuration. Worth a try.
Put 127.0.0.1 as the MQTT Broker Hostname
Put 1883 as the port
Add your MQTT user and password credentials. (Most people recommend you setup a separate HA user just for your MQTT broker use-case, myself included)
Even though the Govee to MQTT Bridge settings say Home Assistant will handle the broker info automatically, I think somewhere down the line the Mosquitto Broker had an update and is explicitly checking for the broker details now. Govee to MQTT Bridge wasn’t the only add-on I had that the broker was closing connections on. I had to manually add the broker details to the z2m add-on too.
Also, should you do that and it’s still closing connections, hard reboot your Beelink. You’d be surprised how often a hard reboot will fix glitches in the HA matrix.
" I had to add the MQTT broker info in the Govee to MQTT Bridge configuration." I have no idea where to find that.
The weird thing is that when I try to reconfigure Mosquitto MQTT Broker I see username “homeassistant” and password "password not changed (incl. some other characters). When I put in my MQTT username and pswrd it fails to connect. Also with 127.0.0.1 which it won’t let me go back to core-mosquitto…
The hard reset did get my Sonos back in the Overview
You’ll add the broker info in the Govee to MQTT add-on. On the configuration tab, click the boolean switch that says “Show unused optional configuration options”.
Yes, I did.
I have the feeling that it must be something small that is preventing to integrate the Govee lights, but I can’t figure it out.
I found a post that said that not using the Govee login details helped. Tried it and no result. Tried logging in without MQTT login details, no result. Tried without both logging details, no result.
This is very frustrating, without the Govee lights I cannot do much automation.
I have logged out of the app, used “forgot password” and received an email from Govee. I changed my password and no the error says that it failed for legal reasons and email isn’t registered yet. Which is weird because I receive emails from Govee.
I also tried to sign up a new account at Govee - Haciendo la vida más inteligente | Govee Spain and used another email address. Received confirmation an can log in at the website.
Used email and psswrd in HA and same error.
Am searching now to see how I can bypass that Error 451.
I tried exactly the same thing earlier today (as I wrote before) but it didn’t give any result… but now it works.
But thanks for telling me, otherwise I would not have tried it again.
