It doesn't seem to be hurting anything I just noticed it in the logs
1 Like
Thanks for the info. Have you seen anny occasion of it actually being a problem, or is it just a warning ?
The attribute size isn't something i can do to much about. It is just the result of number of scenes a Govee device has. I am not suprised some devices would hit that.
@oldcomputerwiz if it isn't causing a problem then i wouldn't worry to much about it for now.
An attribute of over 1024 won’t load on a dashboard, but other than that just the error message from what I’ve seen.
2 Likes
It looks like you turned on the Automatic install of Lan API Devices. And it installed with the Manual LAN API Driver. For some reason in your setup that driver is still missing some preferences. It may need to be repaired.
That said to enable all the functions of your devices, I would suggest disableing the option for the "Automatic install of LAN API devices" in the Govee Device Manager preferencea and set them up from the Govee Integration App. That will enable features not avaliable with the LAN API but can be enabled to use the LAN API for everything it can.
1 Like
Is this in response to something above, or what i sent you i the DM. I should have a dual socket devices in the next few days days to fully vet the Multisocket functions.
1 Like
Has anyone tried to use this smart outlet with nightlight from govee inside of hubitat yet? model H5089
I have one on my doorstep so i should get some time with it over the next few days..
So if it isn't already working there will be a update to support it shortly 
Nice, it looks like a pretty handy device. I already know a place that I can use it in my home.
I had opened a different thread to discuss this concern and it seems that this will be fixed in a future release of the firmware.
So I have had a little bit of time with the device and it seems that the device is about 75% there when it comes to the integration.
The device as it shows in from the API should support turning the whole device on/off, turning the Nightlight on/off, changing color, brightness, and then setting nightlight scenes. There are only 4 scenes by the way.
That sounds pretty good, but at the moment the On/Off for the whole device and the Nightlight don't seem to work.
What I see missing is the option to toggle each of the Outlets individually.
I have opened up a thread on the Govee Community to explain my findings and bring up the lack of the ability to switch the individual outlets on/off as the H5082 can do. We will see where that goes
As far as Hubitat goes this opens up a new need that I have already coded for in my personal setup. Simply put we know need a socket driver with the ability to have a daughter light device. I will be updating the code and publishing it soon enough. This new code will simply enable controlling the Light portion though and as it stands there is no way to turn it off outside of the Govee Home app. Hopefully this gets changed soon. I will keep contacting Govee until something is done.
2 Likes
I have just posted a update to the Govee Integration V2. The changes are as follows
- Update to the Socket Driver as stated in the above post. This update improves support for the H5089 Socket Extender. I also modified the routine to create the secondary outlet controls for multi-socket devices.
- A few changes to the Cloud and LAN Api scenes management routine were made to better support upcoming Light Effects tools. These changes mainly did two things.
a. Now DIY's can also be submitted on the setEffects commands. This makes the ActivateDIY command redundant to some extent. It isn't going anywhere though as is needed for anyone that uses it previously.
b. I removed support for the Hard-Coded low number Scenes(1-23) I created a long time ago. They are still in the code, but will never be activated. This does not effect devices that have Low number scenes in the LAN API Scenes files. This likely has minimal impact to anyone since they were really only used when a user used the nextEffect or previousEffect commands. They were intended for matching with Wiz bulb Scenes. This functionally will be able to be replicated with the Light Effect Tools app that I am working on.
As usual if you have any issues please let me know. I am already running this code in my home.
2 Likes
In case anyone was curious about this, they can now go into HPM and do a search for effects and see the tool package and install it. There is a second tool in the works, but the first one will help with holiday light effects i hope and is why i am making it available now. I will look at creating a similar support thread like this one in the future. This is not Govee Specific and leans on the Hubitat LightEffect Capability. This is why it isn't being baked into the general integration.
1 Like
Woot! Great update!
This is very cool.
2 Likes
I have created a support thread for the new "Light Effects Tools"
[Early Release] Light Effects Tools - 
Custom Apps and Drivers / Custom Apps - Hubitat
If you loaded the new tool yesterday please update to the latest release. I found a bug yesterday that if hit could have very negative impact on the hub. It would only impact you if used a single Interval in the "Light Effects Show" Child app.
I have also released the second tool i mentioned above "Light Effect Grouping" It will basically allow you to create a Scene list across multiple devices. This is what i expect to replace the low number hard coded curated scenes that got disabled in the last release. Those were largely built for me, and anyone that had Wiz bulbs. Now with a few more steps we can simply use this tool to link up as many devices as we want and it will build a scene list that can be used to activate scenes together across multiple devices.
In theory with these new tools allot of stuff could get standardized between Lan API and Cloud API , but that is a much bigger nut to crack if we ever decide to go down that path.
2 Likes
Trying this out as think it's what i need for season effects. However no matter what scene i send for last month it just does the same thing. Logs says it was set but nothing changes, If i do it through the govee app it works though.
Just for clarity is this a problem with the Govee Integration, or the new Light Effects Tools. If it is with the Light Effects tools lets take this to the support thread mentioned in the above post.
If the issue is with the Govee Integration what is the device type and driver it is using. Are the scenes being controlled via cloud or LAN API?
Its got to be the device, because although I was trying it in the new app i then tried it manually in the driver and it did the same.
It's a Curtain_Light H70B1
Im using LAN control but cloud for scenes, I did try local scenes as well but was the same.
Curtain lights and Net lights have issues with there scenes using the LAN API. In the preference leave LAN Control on, but turn off the option for "Local Lan Scene Control". It is a known issue with those devices.
Those two devices are the reason that option exists.
Lastly go back into you Light effects show app and adjust the scene selection as well
Woops after a second look at your settings it is that way. Try turning on debug and sending me the log output when it fails.
You need to verify that the light effects show app selection is valid. Go back into it and verify each scene is selected as expected and then click done or next until you are out of it to make sure the setting are valid to the state of your device configuration.
Lets first make sure you control the scenes fine from the regular device driver though before worrying about the new tool though.
1 Like
will send direct as i think there is personal data in the debug
I recently bought and integrated some of the Govee RBIC Neon Rope Light 2 and I've noticed that I only get some values back when the device is polled, so things like the effectNum/effectName state that are modified outside of the driver never get updated.
Is this a limitation of the API or maybe a driver issue? I see that getDeviceState response does not include the right fields and it appears that retrieveScenes2 only grabs the list of scenes available and not the current state. The only way I see the effect fields updating is when the driver sends the lightScene command to the device and it gets the dynamic_scene value response.
Apologies if this is covered elsewhere in the thread.
Yes it is a API issue.
Yea.. everything you said is spot on about how it works..
The API's called by the "retrieveScenes2" routine just retrieve what is available to call from the new cloud API. Simply put for some reason the Govee APi includes the settings but leaves them blank if they are considered not retrievable. Perhaps that will change at some point, but it isn't the case now. The new api is still under development so it is possible it will change at some point. I think in my integration the code may already be inplace to handle it if it is suddenly being passed
