@mavrrick58 thank you for the quick reply. I missed the previous post, I can enable LAN access.
Thanks
Garry
Yea.. it isn't the perfect solution as the LAN only driver has it's limits, but it is something to get you working for now until they get it fully added. Hopefully it won't take to long.
Welcome to the club! Misery loves company! 
I am sorry for your pain but it does seem to eliminate that it was something in my system causing the problem so I can check off one more thing of what the problem ISN'T.
Ok, new question. I can control the curtain lights for on and off and built in scenes, but what about DIY scenes. Any idea how to pull them into hubitat?
Are you using LAN API or Cloud API for the Curatain lights. in the past for the curtain lights, have tried to avoid LAN API for scenes and DIY's as it has had very mixed results. I would suggest you make sure you are using the cloud for scenes, diy, and snapshots for that device.
Check your preferences and if you have Lan control enabled also make sure you have the option to usw the cloud for scenes and such turned on.
Any idea what the Aid Whitelist is or what they are suggesting I should feel free to do now? This integration nor Home Assistant's find the H7052 still.
The only whitelist i am aware of is related to rate limit. Basically it would give you unlimited calls instead of the 10k limit. The rate limit is also very hard to see with the new integration so not sure how to validate that.
So I am not sure what the Aid Whitelist will do.
Have you tried setting up the H7052 as a LAN only device until they add it to the cloud API.
If I add to the LAN integration, I get this here:
There are errors in logs when adding:
However the device does show up but it never updates when the actual device turns on and off. If I hit refresh, this error shows up in the logs:
I noticed that the DNI is assigned based on the IP address. If I've added the device that was given that DNI then delete it and then that DNI is trying to be used again, could that cause an issue?
I will look into that error, but if the device created then it likely isn't a issue. This may be something i need to look at addressing as it was likely introduced with the recent rework of the Manual Lan Driver. I think this is related to scenes based on the errors, and that kind of makes sense as I believe the Lan Only devices use a different naming for the files they use. I am working on adding some info on this into my documentation for the Govee Integration app now.
It should update when changed within Hubitat. Is that not happening? The status of devices that are LAN only are only updated by changes initiated from within hubitat. There is a limitation on Hubitat that prevents me from creating the UDP Listener that the API supports. So that driver will change states when they are changed from within Hubitat, but will not retrieve states from anywhere. If this ever changes I will add in the ability to retrieve the state from that listener.
I really should remove the option for running a refresh. That is oversight on my part.
As long as the previous device was deleted, the DNI is free to reuse.
I am going to quit messing with it, enjoy the 2 devices that work, and wait for good news from Govee. Automation is a "luxury" for their devices, not required. If this was a light switch, then totally different situation.
2 Likes
Is it possible to control the H5082 dual outlet individually? I can do it via the Grovee app, but via the integration, both outlets are controlled as one, either both on, or both off.
I dont have one of these devices so i can't say if it is possible or not. Can you navigate to the App section on the hub and click on the gear to the left of the Govee Integration app. This will display all of the values used by the app. Then scroll down and find the Application State goveeAppAPI. Copy the entire value field for it and send it to me in a DM.
That will allow me to find and review all the data provided by the API for the device. If there is information there that looks like it is supported then i can create a driver based on that provided data.
It will require a new driver most likely.
Thanks @mavrrick58. I sent you a DM. Here is what it looks like in the Govee App.
I just replied to the DM. The quick answer is that it doesn't appear to have a way to control the outlets individually through the API. Sorry 
Thanks for checking. Hopefully the API will be updated in the future to include the necessary info.
I am not sure if anyone is interested but It looks like Govee has released a new version of their Aura Table Lamp called Table Lamp 2. It seems to include some additional lighting in the base like the new Floor Lamp 2 Pro. It is RGBICWW and puts out 500lm of light from 2700-6500k CT
If you go and purchase it currently there is a 30% discount with code TL30.
I have one on order so we will see how it integrates. It also appears to be another Matter supported device.
I just posted a small update to include the Documentation I have been working on in the app. Now you have a ? in the upper right corner with a link to the document.
It is over 50 Pages already and covers allot about everything that this stuff can do. I hope it helps everyone make things easier. If there are any problems that folks are having that are not documented please let me know and I will try to add something to it.
3 Likes
How do you know which devices are supported by the V2 intergration? I just added the H7105 42'' Smart Tower Fan 2 Max, but cannot get the V2 app to see it. It shows up in my Govee app, but when I do a Device Refresh, in the V2 app, the new tower fan does not show up.
Please Update the app to the latest release. When you Open the app you should have a new 
icon in the top right of the UI. When you click on that it will load the documentation listed. In that document one of the first things covered is how to look up supported devices.
That said I already know your device is not listed unfortunately. I would suggest you reach out to Govee and see if they will add support. This is a brand new fan.
That device does support Matter though. Have you tried adding it as a Matter device to see if it works?
I tried Matter for some SwitchBot devices and it drove me crazy so I turned it off. I'll give it a shot with this smart fan to see if things work any better.
