The Local API Status tab is a nice addition. Is local discovery of lights available on the Self Host Server version of Homey? My Homey Pro discovers local lights just fine, but I’ve yet to see them on SHS.
SHS is primarily a very different layers of infrastructure. If it is supported depends on how you setup the infrastructure. And I can not help with that. What it needs is the broadcasts over udp needs to be able to reach the port of the SHS and vice versa. I know I could not get it to work even in Homey development docker images.
1 Like
Hello, I am new to the platform. How do I install the test version? The installed version is v2.15.2.
I have tested with Wi-Fi and with the official Homey LAN adapter, and in both cases, I get the same result: it doesn’t find the device.
My native language is not English, sorry if I’m not expressing myself correctly.
Thanks
Now i have the test version but not detect any device with local API
Result of API test:
{
“code”: 200,
“message”: “success”,
“data”: [
{
“sku”: “H6076”,
“device”: “35:D1:D6:50:84:86:6F:71”,
“deviceName”: “Floor Lamp Basic”,
“type”: “devices.types.light”,
“capabilities”: [
{
“type”: “devices.capabilities.on_off”,
“instance”: “powerSwitch”,
“parameters”: {
“dataType”: “ENUM”,
“options”: [
{
“name”: “on”,
“value”: 1
},
{
“name”: “off”,
“value”: 0
}
]
}
},
{
“type”: “devices.capabilities.toggle”,
“instance”: “gradientToggle”,
“parameters”: {
“dataType”: “ENUM”,
“options”: [
{
“name”: “on”,
“value”: 1
},
{
“name”: “off”,
“value”: 0
}
]
}
},
{
“type”: “devices.capabilities.range”,
“instance”: “brightness”,
“parameters”: {
“unit”: “unit.percent”,
“dataType”: “INTEGER”,
“range”: {
“min”: 1,
“max”: 100,
“precision”: 1
}
}
},
{
“type”: “devices.capabilities.segment_color_setting”,
“instance”: “segmentedBrightness”,
“parameters”: {
“dataType”: “STRUCT”,
“fields”: [
{
“fieldName”: “segment”,
“size”: {
“min”: 1,
“max”: 7
},
“dataType”: “Array”,
“elementRange”: {
“min”: 0,
“max”: 14
},
“elementType”: “INTEGER”,
“required”: true
},
{
“fieldName”: “brightness”,
“dataType”: “INTEGER”,
“range”: {
“min”: 0,
“max”: 100,
“precision”: 1
},
“required”: true
}
]
}
},
{
“type”: “devices.capabilities.segment_color_setting”,
“instance”: “segmentedColorRgb”,
“parameters”: {
“dataType”: “STRUCT”,
“fields”: [
{
“fieldName”: “segment”,
“size”: {
“min”: 1,
“max”: 7
},
“dataType”: “Array”,
“elementRange”: {
“min”: 0,
“max”: 14
},
“elementType”: “INTEGER”,
“required”: true
},
{
“fieldName”: “rgb”,
“dataType”: “INTEGER”,
“range”: {
“min”: 0,
“max”: 16777215,
“precision”: 1
},
“required”: true
}
]
}
},
{
“type”: “devices.capabilities.color_setting”,
“instance”: “colorRgb”,
“parameters”: {
“dataType”: “INTEGER”,
“range”: {
“min”: 0,
“max”: 16777215,
“precision”: 1
}
}
},
{
“type”: “devices.capabilities.color_setting”,
“instance”: “colorTemperatureK”,
“parameters”: {
“dataType”: “INTEGER”,
“range”: {
“min”: 2200,
“max”: 6500,
“precision”: 1
}
}
},
{
“type”: “devices.capabilities.dynamic_scene”,
“instance”: “lightScene”,
“parameters”: {
“dataType”: “ENUM”,
“options”:
}
},
{
“type”: “devices.capabilities.music_setting”,
“instance”: “musicMode”,
“parameters”: {
“dataType”: “STRUCT”,
“fields”: [
{
“fieldName”: “musicMode”,
“dataType”: “ENUM”,
“options”: [
{
“name”: “Energic”,
“value”: 0
},
{
“name”: “Dynamic”,
“value”: 1
},
{
“name”: “Calm”,
“value”: 2
},
{
“name”: “Bounce”,
“value”: 3
},
{
“name”: “Hopping”,
“value”: 4
},
{
“name”: “Strike”,
“value”: 5
},
{
“name”: “Vibrate”,
“value”: 6
},
{
“name”: “Skittles”,
“value”: 7
},
{
“name”: “Torch”,
“value”: 8
},
{
“name”: “CandyCrush”,
“value”: 9
},
{
“name”: “Fusion”,
“value”: 10
},
{
“name”: “Luminous”,
“value”: 11
},
{
“name”: “Separation”,
“value”: 12
}
],
“required”: true
},
{
“unit”: “unit.percent”,
“fieldName”: “sensitivity”,
“dataType”: “INTEGER”,
“range”: {
“min”: 0,
“max”: 100,
“precision”: 1
},
“required”: true
},
{
“fieldName”: “autoColor”,
“dataType”: “ENUM”,
“options”: [
{
“name”: “on”,
“value”: 1
},
{
“name”: “off”,
“value”: 0
}
],
“required”: false
},
{
“fieldName”: “rgb”,
“dataType”: “INTEGER”,
“range”: {
“min”: 0,
“max”: 16777215,
“precision”: 1
},
“required”: false
}
]
}
},
{
“type”: “devices.capabilities.dynamic_scene”,
“instance”: “diyScene”,
“parameters”: {
“dataType”: “ENUM”,
“options”:
}
},
{
“type”: “devices.capabilities.dynamic_scene”,
“instance”: “snapshot”,
“parameters”: {
“dataType”: “ENUM”,
“options”:
}
},
{
“type”: “devices.capabilities.toggle”,
“instance”: “dreamViewToggle”,
“parameters”: {
“dataType”: “ENUM”,
“options”: [
{
“name”: “on”,
“value”: 1
},
{
“name”: “off”,
“value”: 0
}
]
}
}
]
}
]
}
Then it must be a udp broadcast issue not reaching the Homey on the adapter the local api host is listening on. Since that is a pure infrastructure issue in combination with my local range broadcasts it is impossible for me to debug.
I will try to create an option to allow for global vs local scoped broadcasts.
If there’s anything I can help with, please don’t hesitate to ask.
Thank you very much for everything.
I reworked the library I am using to try to solve this issue. Can you install the latest test version?
It uses my reworked library to bind better in case of multiple connections and multicast scenarios.
Chnaged waiting times to give Govee devices a bit more time to respond.
New: Added a BLE temp sensor driver for thermometers that only support BLE.
for you the new test version is also worth a try
1 Like
Can you try with the latest test version?
Everyone else: It improves stability but it also adds: DreamViewScenes are now supported.
It works on app level, you can use flow cards to activate one of your dreamviewscenes or use the new widget to activate them.
I just noticed that my local API doesn’t work on the Govee H6159, I then removed itand used the Cloud instead. I can turn on and off the led strip but I can’t change the color. I have tried to change it with a flow and manualy by clicking on the different colors in Homey. If I use the Govee app on my phone I can change color and it will show in Homey which color that has been picked.
Since the update in January, my local API interface no longer works for any of my four outdoorlamps. After adding them, the lamps lose connection after about 15 minutes. Can you help me?
And they don’t reconnect at all anymore?
Because it’s new I mark them as offline if they don’t respond for a long time but if they do again I mark them back online. It’s just the status, the lamp can still be controlled often. The method of detecting is a bit difficult because how slow they respond to request of they are still there polls.
If it’s a real disconnect please describe what you experience.
Hey, here’s a post I wrote in the German forum where I also asked for help:
Hi everyone, for the past few weeks I’ve been having a problem where my Govee lights are no longer accessible via the local API.
If I restart the devices and delete them from Homey, I can add them back. But after about 15 minutes, they disappear again and are no longer reachable.
The following error message then appears:
Could not locate device with id [0C:C7:6B:06:06:35:28:FF]
I’ve already deleted all the lights in the Govee app and added them again. The local API is enabled for every device. I’ve also restarted Homey several times.
Does anyone have any ideas?
The problem just suddenly appeared; everything worked perfectly for months before. I suspect it might be related to an app update. In January, the following update was released: “Improved handling of local UDP port unavailable cases,” and the problems started after that.
Best regards
What version are you now on?
Also please send me a diagnostic report after they dissappear. I don’t see how they can become unavailable after they have been found. I need to check that.
cc20c17e-ae57-440d-8ac4-703a0b9bfd61
I used the newest version of the app
The Local API is working again after the latest app version. Thank you very much.
Has anyone automated Govee DreamView (esp. TV Backlight 3 / camera mode) via Homey or API?
Text:
Hi all!
I’m trying to automate Govee DreamView with Homey (cloud API), especially the TV Backlight 3 camera mode, but it seems like it’s only available via the official Govee app.
I’ve seen that Homey’s Govee app can show DreamView scenes in flows, but I can’t trigger the camera/film mode automatically.
So far I read one workaround with Govee strips (T1) where:
-
the device is turned on via API
-
and a Govee in-app automation then switches it to DreamView movie mode
but that still needs internal automations.
Questions:
-
Has someone successfully automated TV Backlight 3’s camera/film mode via Homey flows or API?
-
If so, which API calls or app automations did you use?
-
Any examples of flows or Homey apps supporting this?
Thanks! 
If those would be available I would implement them directly. So if anyone found a way post here then I’ll make it part of the official app.
1 Like
Hi Kaoh,
thanks a lot for the app first of all — I really love it, great work
And thanks for the clarification. That confirms what I suspected: the Film / camera DreamView mode isn’t exposed via the API and therefore can’t be selected natively in Homey flows.
I’ve put together a workaround that I’m going to test this weekend. It’s not perfect, but it’s fully automated and works within the current limitations:
Idea / Use case
-
The TV Backlight 3 (T3 Lite) should always run as basic backlight when the TV is on.
-
When a specific trigger happens (e.g. VLC Player starts), additional lights should be added into extended DreamView (movie/camera mode).
-
When the trigger ends, DreamView must be explicitly disabled again, otherwise the T3 automatically re-captures the lights the next time it turns on.
Workaround
-
Use a “dummy” Govee device (e.g. a GU10 spot), placed somewhere invisible (cabinet, storage, etc.).
-
Control this GU10 via Homey (switch on/off, via Matter or plug).
-
Inside the Govee app, create internal automations:
-
If GU10 turns ON → activate extended DreamView (movie/camera mode)
-
If GU10 turns OFF → deactivate extended DreamView
-
-
Homey only controls the GU10, Govee automations do the DreamView switching.
This way:
-
Homey stays the automation brain
-
Fully automatic based on automatic triggers (media player, scene, etc.)
Obviously not optimal, but it works reliably with today’s API limits.
I really hope Govee opens the DreamView camera/film controls in the API at some point — if that happens, native Homey integration would be amazing.
Thanks again for the app and for being open to implementing this if a real API solution ever shows up!
Best regards
El_Capitan
1 Like
