DOH...brain should have engaged.
Looks like we're in business...set the JSON file in Preferences, Save & Exit, and re-opened and did a Scene Load/Refresh.
1 Like
I’m finding that my DIY list is no longer matching what’s in the app for one of my devices. I pressed the « Refresh Device List, DIY, and Snapshots » button a few times, but they don’t seem to get refreshed…
I tried turning on all logging before hand, but nothing appears in the logs until I press done… expected?
Any suggestions?
Pressing the Device Refesh button should only impact the Snapshots. For DIY and Scenes you should probably just click on the scene load command on the device page. Are you setup to use the LAN or Cloud API.
For the logging turn on debug logging on the device and then click on the save and close button. It ahould load the scenes again and it will come up in the logs.
Hmmm… Not seeing a scene load command - maybe I need to change the driver?
I’m using the LAN API - Enable LAN control is enabled.
You shouldn't need to ever change your driver. The integration picks the right one for you.
There are two options in the preferences to be comcerned about. They are in the image below
The top option turns on LAN AP for the device in general. The second determines if scenes are controlled via LAN API or Cloud API.
If both are on the. The LAN API is being used for both. That means the scene files are stored on the hub and itself with extracted data. If you are missing things from your DIY List in the App you just to extract them.
1 Like
That means you are running older code. Make sure HPM is running a most recent version. Then upgrade the integration if possible. If not you may want to unmatch and the rematch the integration in HPM. Then repair it.
Ok, I’ll do a manual update and un-match/re-match. I did do a check and it told me I had the latest, then checked to see the versions:
I've found doing an HPM Repair of the app/driver to be reliable "fixer" in cases like this...
Indeed! Unfortunately, I just did a repair and nothing changed… 
The version numbers were exactly the same before and after the repair.
Will try unmatch and rematch next.
2 Likes
Okay, un-matching and re-matching worked. Now I have those new options. Unfortunately, I’m also getting a bunch of errors, and not the new DIY scenes yet…
and when doing a Scene Load command, I get:
Initialize / Refresh did seem to allow me to do a Scene Load command, but now I get a lot of info with all logging, plus the following errors:
And when I run it again, I get the « switch » error again… Very odd…
Doing some more investigation… It seems the device ID doesn’t match the MAC address… should it? (I can’t seem to control power on/off anymore either… via the device…)
The off command results in:
However, if I disable LAN control in the Hubitat device’s screen, then the on/off commands work. (Still no DIY scene update unfortunately though….)
FYI - I do have LAN Control enabled on the device via the Govee app:
May need to continue looking at this on Saturday… (Halloween party tomorrow night…) 
Update: I might have been looking in the wrong spot! I now see my DIY scenes, So the only issue now is why doesn’t LAN control work…
Go into the govee decice manager device. Go to the preferences tab and click on "save and close"
I have a few concerns based on the screenshots. The first and most important one is based on those preferences you are running very old code. The ability to determine how to control scenes has been around a while.
The next concern is a new version was released when hubitat released 2.4.1.x firmware that made significant changes to LAN API and how it works. My first comment above is a important step to ensure any needed settings are initialize with the Govee Device Manager
I also just thought about one big change that took place with that update as well. Simply put if your devices were not children of the Govee Device Manager, they willl need to be recreated so they do reside under Govee Device Manager. Alot Of Lan API functionality goes through a multicast socket that the Govee Device Manager manages. The easiest way to recreate the device would be to open up the old one and change the DNI by adding _old to it. Then simply go into the integration app and click done. It will create new devices for all of them you updated. Then just update each associated app/rule to the new device.
1 Like
Ok, thanks! On my list for the weekend. 
Ok, I can confirm that my devices were indeed not children of the Govee Device Manager. I did go ahead and re-create them and now can control them even when they are setup to use LAN, so that’s good!
I also ran an « All Scene Reload » command from the Govee Device Manager, but unfortunately am not yet seeing the DIY or any other scene numbers from either the parent or the children… Should those appear under State Variables like before?
Can you show me what the preferences page looks like and the click on the save and close button.
Yes, for sure!
For the parent/device manager:
For one of the children:
Please let me know if there’s anything else that would help!
Am I correct in believing that it's the Govee lights on this dashboard that's generating the warnings?
Could very well be. The lightEffects attribute could get pretty large on some devices. Some devices have 130+ scenes.
What happens if you click on the Warn log level icon on those messages. Does it take you to tbe dashboard generating the error.
Is it impacting anything other then generating that message.
Looks like i need to check with Hubitat support as to the impact of that. I believe i am using the attribute as intended so i will need clarity from them as to impact and next steps if something needs to be adjusted.
This is a shame to as i have some stuff i am working on that will extend the use of that attribute for our benifit.
I’ve run into that error over years, and generally have a size check on any attribute that I am constructing that may grow larger than 1024 bytes.
1 Like
