I have Light Show Box H1167. I had it setup a long time ago and then lost it. But I just found it. It was set up in Hubitat, perhaps in V1? But not sure if it was ever working. So I deleted it and then re-added it. No dice. Is this something that can be made to work? Thanks.
As i recall i have had some talks with someone about that device in the past. I believe the determination was that it is a bluetooth only device and as such Hubitat has no way to talk to it.
1 Like
I just published a new update. This just makes offical a few fixes that i have published as users needed them. They are as follows:
- The H712C Air Purifier will no install properly with it's dedicated driver
- I found that the H6056 TV Light Bar and the Y Light Lan Scene File was not setup to be downloaded. The files have been added to properly install
- Re enabled a process to update the API on devices if your API is updated for some reason.
- Several improvements to the Scene extract process. It will now better handle Tap to runs with multiple devices and scenes. The display page has been updated to a display a table of all of the scenes/DIY's/ ect that were processed by the extract process.
Happy Holiday everyone.
1 Like
Happy Thanksgiving and thanks for this awesome integration. I only have 2 Govee light strips and I got them both integrated on the first try without a hitch. The only hard part was getting my devices on WiFi since my hub prioritizes 5Ghz and Govee doesn't support that. Once I figured out how to force 2.4 i was golden. I don't really need all the fancy things this can do but it's nice to know it is there should I change my mind later. For now just on and off and color setting is all I need to light my theater room the way I want in different modes. This integration allows me to do that all from a HE rule and ditch the flaky remote hacking I did with my Harmony hub. Teaching the Harmony hub to send RF signals to Govee worked but not consistently. Thanks so much again. Brilliantly done.
1 Like
Looks like I'm getting stuck on the screen below, not sure why it's hung up.
Added perm lights 2 to Govee app.
Added lights to hub via Matter. Controls fine from app or hub.
Installed integration and selected option to find devices and it's sitting on this screen. Any suggestions? 
That's kind of what I thought. I didn't see the model number in the API listing of devices. Thanks.
1 Like
Can you turn on logging and try again and then send me the logs so I can see exactly where it is getting hung up.
Please make sure you already have the Govee Device manager device already installed as well.
Do you have anything else already installed, or is this your first attempt.
Look what was on my front porch today from Amazon, tree goes up tomorrow, I better get it up and tested before then.
4 Likes
Looks like I have to take the "tedious" method to create the LAN scenes file for the Christmas String Lights 2. Just a heads up this is what was discovered when integrating with Hubitat but the default LAN scenes file name is: GoveeLanScenes_null.json
I assume it's because this is a newer product not yet coded in the app and drivers.
Tried device discovery again this AM and it worked as expected. 
Last night was trying on the phone, this AM on the computer but that shouldn't make any difference...but it's working so all good. 
One question...the lights went into a flowing mode moving between colors across the lights when I first plugged them in. My wife really liked that, but after playing w/various settings in the mobile app I can't get it to do that "startup" scene/mode again. Is there a way to make them do that again.
1 Like
Exactly. To identify the scene file the DevType is needed and that just needed to be updated. You can do a repair on the integration and it should be there now. Once that is done you will want to update the preference value for the file name. Update that to GoveeLanScenes_XMAS_Light.json and save the setting. That should trigger it to refresh everthing and you should get local scenes.
Another thing is that i don't have Xmas String Lights gen 2 so the scene file currently contains entries for Gen1. It may work fine, but there may be some scenes that the Gen2 have that the Gen 1 didn't. If you want everything that is part of the Gen2 you can extract all of the Scenes and send it to me so i can add it to the repo.
1 Like
I just wanted to give a heads up to folks on something I have just found with the help of @thinkfire.
There appears to be a issue with data extraction of some scenes/effects as they use a new undocumented command I haven't seen before. As of now we have only seen this on Curtain light devices so if you are extracting scenes/DIY's that simply won't extract this may be why. I am thinking about a good way to handle this going forward. It effects several aspects of scene management so this may take some time.
As of right now this is only known to impact Curtain Gen2 lights
So I'm kind of lost here on installing this app. I went through the install in HPM, and afterwards there's no Govee integration showing in my app list. If I go back to HPM and check the list of installed apps and drivers, it's there, but I can't actually access the app to do anything or input the API key. Am I missing some step?
Did you click on the add user app button at the top of the Apps tab.
Installing from HPM only makes the app available to install on your hub. Then you need to use the add user app button to actually install the app on your hub.
You could look at my documentation here as well
3 Likes
Some of the best I've seen here.
Just a heads up the file name when I put in:
GoveeLanScenes_XMAS_Light.json
And saved. It doesn't seem to update it properly when you save preferences. Every time I try to set a scene this is logged:
dev:7232024-11-30 01:26:58.631 PMerrorjava.nio.file.NoSuchFileException: GoveeLanScenes_null.json on line 1942 (method setEffect)
That was the previous file name entery. You can see I have the right file name on the panel:
Just tried the "Scene Load" option and it's still referring to the old file name:
dev:7232024-11-30 01:31:38.901 PMerrorjava.nio.file.NoSuchFileException: GoveeLanScenes_null.json on line 1942 (method sceneLoad)
Update
Ok did a repair one more time and also uploaded a copy of the XMAS json as GoveeLanScenes_null.json. Now it's working. I am still going to take the long way tonight and export as suggested to see if there is a difference. So far the scense from the XMAS json seem to match the Christmas Light 2 device.
Yes I see that now, been a while since I've used the HPM and forgot about the add user app step. Thanks!
1 Like
Can you go back to it and confirm it is set to the correct name. Also check for spaces at the end of the file name.
Lastly check the device data at the bottom of the UI and let me know if it shows DevType: XMAS_Light
My guess is that the DevType did not update as it should have. Click on the save button in the preference section and let see if that shows up.
Removed the "null" file from files and replaced the file name again with:
- GoveeLanScenes_XMAS_Light.json
Did a save again checked the device type:
- DevType: XMAS_Light
And now it's loading your published file very strange. The only difference is that I let it rest for a while
1 Like
