Yea, that is what i was in reference to.
1 Like
I'm still a little lost. Do I just need to swap the Type?
Or actually "Remove" the device and resync/refresh the devices from the main app page for it to be added again? And does this need to be done ONLY if the devices are LAN enabled? I have the H605C and I don't think this one has LAN control.
For the time being don't worry about converting the legacy devices to devices under the Govee Device manager. I want to address the bug i have found before anyone moves forward with this. I have found a bug that i need to resolve first. Your devices should continue to work fine outside of the Govee Device manager for a good while. Hopefully the next post I make will be with a fix for the bug i found.
I have uploaded a updated bundle package for the Govee v2 Integration. If you have been holding off on upgrading it should be good now. I am going to update the version so it will download the new version.
If you want to start to migrate your devices under the "Govee Device manager" you can follow these steps.
- Go to the device page for the device you want to migrate.
- Scroll down tot he device information section. put a # in front of the name in the Device Label field. Click on the "Edit" link next to the "Deveice Network ID" Field and click on close when the pop up appears. Now put a # at the end of the Device Network ID that is present.
- Click on the "Save Device" button.
- Now open the Govee Integration app and immediately click the "Done" button in the lower right corner.
At this point on the devices page you should have a new device created as a child under the "Govee Device Manager" device as shown below.
Now go back to the original device and select it. Scroll down to the device details section. There will be a "In Use By" section with a list of the rules/apps that the device is connected to. Now click on each one and update the app to use the new device with out the # in front. Once all rules/apps have been update and nothing is listed under the "In Use By" section you can click on the "Remove Device" button to remove the old device.
What happens if you don't see the new device manager after this step? And yes, I updated the app via HPM before I followed the above steps
EDIT: I completely removed the device and v2 of the app, I no longer have the v1 app. Reinstalled and I still see a single device and no manager.
FWIW: After the reinstall, my API key was populated when I opened the app. As if there was a config file that was not removed during the uninstall.
I added a new Govee product yesterday. It's an H6167 I'm using as an accent light in my office. I changed it to local LAN control. It works, but now I can't get to the Effects. They are blank. And while all 5 Govee devices work, the count is now null. I've tried a repair on the integration (through HPM). Anything else I should do? And should I switch back to cloud control to be able to access the effects?
I suspect if you turned on debug logging for the H6167 and then click on the "Initialize" button you will get a message saying that the device is "Unknown". That device hasn't beed added to the code to identify a proper device type.
That said it does look like a RGBIC Strip based on what I can find from the Govee App.
Can you tell if it has the same basic scenes as a regular RGBIC strip? If it doesn't we may need to extract those values and then add them into the Lan Scenes library code.
If it does that is easy enough to fix
It is an RGBIC strip BTW.
Can you look at the device and tell me what driver it is using?
When you turn on "Local Lan Control" did you go back into the device and specify the IP address. Those messages look like they are pointing to it still using cloud commands.
Ugh. Yes, I turned LAN control back off to try to get the effects back. Here's the driver:
You're right. Here's the logs with LAN turned back on.
Can you please try this for me.
- In the Hubitat UI expand the " Developer tools" Section. Then select the "Libraries Code" sub menu. This should display something like what is below.
- Click on the item labled "Govee_LAN_API" and click to display the code in that library file.
- Now scroll down to line 280 and you should see the section for the method "def getDevType()". This is the method that identifies based on the device model what device type to tag the device with.
- Between line 283 and line 313 add the below text on it's own line. My update is below
case "H6167":
Then just click on the Save button in the upper right corner.
Once this is saved, go back to the device and click on the initialization button. It should match up and add the device tag of RGBIC_Strip to it. At that point the process to retrieve the scenes should work to pull in the scenes that are associated with that device type. Refresh your screen to hopefully see the scenes associated. At that point I would suggest you go ahead and try a few of the scenes to see if they work. If they don't we may need to extract the scenes for that specific device and add them in under their own device type. Let me know how the live logging looks. It appears this is another possible condition i need to code for when a valid device type isn't present.
1 Like
If you want you can just do a repair through HPM to get the updated library file with your device included and i fixed the count number in the UI as well.
After it is updated go the devices you use for scenes and press the Initialize button to refresh the scenes in memory.
Being lazy I did a repair and everything is back. The scenes are there. The count is now 7.
Not sure what a Govee v2 device manager is, but everything seems dandy. And yes, the scenes even work. Thanks @mavrrick58 !
1 Like
The Govee Device manager is basically a management device. Simply put it will do allot of management for all of the Gove Devices under it. I may also add additional management functions to that device as time goes on.
This largely was built because of the struggles with MQTT messages from the new Govee MQTT API. Simply put Govee doesn't give a way to link directly to a single device. After doing some testing it was clear that having a parent device to mange data for Integration was better then the way it was going. Performance wise it is very significant for the devices.
Doesn't work on app child devices however what you can do is clone a rule or app or export it and reimport it selecting the new device. 
2 Likes
Is the H617A1D1 rgb strip supported??
Thank you, that worked and saved me a lot of trouble.
Migrated all devices and used clone to fix all my rules.
2 Likes
It isn't on the supported devices list for the new API, but that doesn't mean it won't be.
Do you already have the H617A strip?
If so i can add that strip to the integration. Are you planning to use it with LAN API. The model isn't added for the standard scenes when setup for LAN API, but i will look at adding it shortly.
The strip will be here tomorrow. I dont know if it supports the LAN API yet. Can give better info tomorrow.
1 Like
