-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Tap-to-Run not showing in scenes #373
Comments
A new section on the dashboard appeared for me, called "Govee To MQTT" which had buttons for my tap to run scenes labeled starting "One-Click: Default:" this was a separate section to where my light appeared. |
Ok, maybe I should double check the api key username and password. I see details documented here but I don't see where to actually enter that info in HA: https://github.com/wez/govee2mqtt/blob/main/docs/CONFIG.md Is in the GUI or is there a certain yaml file to edit? |
In home assistant, go to Settings -> Add-Ons -> Govee to MQTT Bridge, click configuration at the top, then the "Show unused optional configuration options" slider. |
It just listed the MQTT Broker info - which is says is not needed as it's handled by HA. My api key is in there - and clicking on devices shows both platform api and AWS iot API as sources for various devices. My log is attached. |
Govee Device SKU
H7065
Govee2MQTT Version
2025.01.04-2c39a50f
Describe the issue
I added a tap-to-run for 2 RBC spotlights, purged cache, and restarted HA. I suspect it's not updating as I still see an old device in HA, so it doesn't appear to be updating. Once of the previous recommendations was to reload mqtt config, but I can't find how to do that.
Startup Diagnostics
not using docker
Additional Logs
No response
Home Assistant Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: