home-assistant.io
home-assistant.io copied to clipboard
Unable to find / use when
Feedback
-
I was unable to find
govee lights local
when I had thehacs-govee
integration installed - https://github.com/LaggAt/hacs-govee -
After removing
hacs-govee
, I finally was able to findgovee lights local
in the integration list, but I was presented with an error when trying to add it:Unknown error occurred
. So I went and disabled myGovee to MQTT Bridge
add-on, and then it let me addgovee lights local
. - https://github.com/wez/govee2mqtt
My question is, is this intentional that we must remove all of these things before we can use this official integration? Some of these other integrations have way better features, like govee2mqtt can control the segments of my lights.
URL
https://www.home-assistant.io/integrations/govee_light_local/
Version
2024.2.1
Additional information
https://github.com/LaggAt/hacs-govee https://github.com/wez/govee2mqtt
Hey there @galorhallen, mind taking a look at this feedback 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 feedback. -
@home-assistant rename Awesome new title
Renames the feedback. -
@home-assistant reopen
Reopen the feedback. -
@home-assistant unassign govee_light_local
Removes the current integration label and assignees on the feedback, add the integration domain after the command. -
@home-assistant add-label needs-more-information
Add a label (needs-more-information) to the feedback. -
@home-assistant remove-label needs-more-information
Remove a label (needs-more-information) on the feedback.
Hi @talormanda ,
I was unable to find govee lights local when I had the hacs-govee integration installed
This has been addressed here https://github.com/home-assistant/core/issues/109921. The issue is not strictly related to Govee Light local.
After removing hacs-govee, I finally was able to find govee lights local in the integration list, but I was presented with an error when trying to add it: Unknown error occurred. So I went and disabled my Govee to MQTT Bridge add-on, and then it let me add govee lights local. - https://github.com/wez/govee2mqtt
Both integrations require to bind to port 4002 to receive status update from Govee lights, that's how the Govee protocol works and the port can't be changed.
My question is, is this intentional
If by intentional you mean to prevent the use of another integration (HACS or not) the answer is obviously no. Usually only one software can bind to a specific port on a specific protocol, in this case UDP port 4002 (There are exceptions to this, but this is not the case).
Hi @talormanda ,
I was unable to find govee lights local when I had the hacs-govee integration installed
This has been addressed here home-assistant/core#109921. The issue is not strictly related to Govee Light local.
After removing hacs-govee, I finally was able to find govee lights local in the integration list, but I was presented with an error when trying to add it: Unknown error occurred. So I went and disabled my Govee to MQTT Bridge add-on, and then it let me add govee lights local. - https://github.com/wez/govee2mqtt
Both integrations require to bind to port 4002 to receive status update from Govee lights, that's how the Govee protocol works and the port can't be changed.
My question is, is this intentional
If by intentional you mean to prevent the use of another integration (HACS or not) the answer is obviously no. Usually only one software can bind to a specific port on a specific protocol, in this case UDP port 4002 (There are exceptions to this, but this is not the case).
Thanks for the detailed answer. Is it possible we could get something like this added to the official documentation so users are aware that adding third party add-ons for govee will cause problems like the one I am facing? Might save you some time / posts on this github page.
Is it possible we could get something like this added to the official documentation so users are aware that adding third party add-ons for govee will cause problems like the one I am facing?
It make sense
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.