I also don’t know, but matter is 100% Govee and Homey. I can not help with those devices
Hi, I’m new to the Homey ecosystem and after trying everything, I still can’t add my Govee H6076 lamp using the Local API mode. I’m not sure if I’m following the correct steps.
Both my Homey Pro and the lamp are on the same Wi-Fi network.
In the Govee app, I enable LAN Control.
In Homey, I select “Add new device”, choose the Govee app, then “Local API devices”, and press Connect — but after waiting a few seconds I always get the same result: it doesn’t find anything.
I have reset both devices multiple times, reconfigured the Wi-Fi on the Govee lamp, and I always get the same result: nothing is found.
To check if the issue was with my network or the lamp, I installed a Home Assistant instance in my Proxmox. I added the Govee integration, selected “Add Local API device”, and it found the lamp on the first attempt.
What am I doing wrong in Homey?
I use the official documented broadcast system for discovery, so they should answer. But if I don’t get responses it’s hard to debug why not.
There is one problem that is more common is that hat I need a very specific port to receive messages on. Other local api systems sometimes use the same port, that can mean the port is in use on your Homey and that’s why I don’t receive those messages. I know the Yamaha app uses the same port but others might also.
You can try by disabling all other Homey apps during add. Also sometimes the devices take a couple of minutes to announce themselves. So after starting the govee Homey app, let it sit for 5 minutes and then try to add them. I remember all discovered devices in that period
1 Like
“I have uninstalled all the apps and only kept the Govee one. I have restarted the Homey Pro and the lamp, but it still doesn’t detect the lamp when I try to add it using the local API option.
Is there anything else I can do?
Thanks!”
Not sure, like I said if I don’t receive the broadcasts it’s hard to identify them. Some wifi ap’s don’t route broadcasts between ap’s or towards the utp, vlans block them etc etc.
I do see a new incline in lacal api complains while this has been silent for years. So it looks like govee might have changed something. I’ll go an check if they documented that this time.
Hi, did any of you guys manage to successfully add H60B2 via Local API? (Or even matter)
Tried it a couple of times, reset the device a couple times and even restarted homey 2023 pro with no luck.
I’d appreciate any tips.
Thanks
Oke. Now everything is not responding. Al my gove lights say fetch failed and all my innr sockets just do not respond. What can i do?
Sounds like you have a bigger Homey issue going on, the innr devices are not part of this app.
I would contact Homey support.
1 Like
Hello. I installed the Govee LED strip add-on for my Homey Self Hosted Server, but after installing it, I get a message that the add-on has stopped working. Out of curiosity, I installed the same add-on on Homey Cloud and it works.
Thanks for sharing,
there is a Topic for the Govee integration,
[APP] Govee - Making your life smarter - #679 by Kaoh
In the Appstore you can find the Support link for Govee to report it.
Closed and moved to Central topic.
Hi,
I just installed my new Govee H60A4 ceiling light and I installed it as a local API device. Everything works fine, but I have one question. Is it normal that the UI for switching scenes look like this? It’s just like the brightness slider, only difference is, it switches scenes, while you slide. But you have no idea what scene will be activated. You can just choose from 0 to 100 percent.
So, my question: Did I do something wrong? I have activated both of the checkboxes for the additional cloud features in the device’s settings.
Unfortunately that is the way it works.
Well.. that’s not good. I wonder why it is, though, because it’s definitely possible to get the scene names from the Govee API. The flow card to switch to a scene has them all there to select from.
I mean, I don’t switch scenes manually that often, but it would be nice to have the option at least.
1 Like
It’s because the scenes are undocumented and unique per light types. That means I need to build them dynamically from the Api and Homey doesn’t have a selection control that works dynamically. So it was either this or no control from the Ui.
1 Like
Ok, thanks for the answer. Other than that, the app is working great so far.
Small new years update:
New version has improved error handling on the local api service.
- It should no longer crash the app if the local UDP port is unavailable.
- Discovery process is tweaked, should find states and discover devices faster.
- New local API status tab in the app settings page, shows the dicovered devices and if the local API could be started (including the reason why not), also allows for a forced discovery from there.
For the cloud api I also added a test tab, this allows you to validate you can retrieve the devices you expect (in case you are unsure if the device is supported for example) and it gives raw info back.
If you see a device there that you can not add in Homey due to being a different type for example, you can send me that raw info so I can implement it. If its not there, it is not supported 
You can use the test version now, or wait for the update by Homey.
I am still testing my Govee light in local API mode. I’ve set up a TP-Link router specifically for testing, and I’ve connected the Homey Pro to port 1, my Raspberry Pi with Home Assistant to port 2, and the Govee lamp to the Wi-Fi network generated by the router.
With the cloud API, Homey detects my lamp perfectly.
When I try to set up the lamp with the local API, it still doesn’t detect it. I go to Home Assistant, start the local device detection, and the integration detects the lamp perfectly.
In conclusion, there seems to be some kind of error in device detection with the local API. In the same isolated environment, Homey doesn’t detect anything, but Home Assistant does.
If you need any logs, let me know and I’ll send them to you. It’s very strange that it doesn’t work only with Homey.
Thanks.
Report
d1f75a80-9797-414c-a9ad-6a6e125da613
Is your Homey pro also connected to the wifi? A difference in my implementation vs the Home Assistant one is that I bind to one adapter and not all. I also use local broadcast targets vs global ones. But if your lan is in the same subnet that should work. I do this because other routers block global broadcasts as security measure.
Udp broadcasts are a troublesome technique unfortunately. Since it’s clear it works for your HA your router doesn’t block those, but others do.
Check also my email about the test version.
