You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there @Galorhallen, mind taking a look at this issue as it has been labeled with an integration (govee_light_local) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of govee_light_local can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign govee_light_local Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
So far I have installed a Light Strip from Govee. Everything is working well so far, but there is one problem:
Every time Home Assistant is restarted/reloaded, the error “Setup error” is displayed in the Govee Local Integration. Even after several reloads.
To solve the problem, the Light Strip must be briefly disconnected from the power supply. It will then work again without any problems.
What version of Home Assistant Core has the issue?
core-2024.11.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Govee lights local
Link to integration documentation on our website
https://www.home-assistant.io/integrations/govee_light_local
Diagnostics information
home-assistant_govee_light_local_2024-11-24T12-50-25.789Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: