I think I may have found the issue, though I don't like it. I suspect if you go into the devices and look at the state variables for it you will still see a Diy Scene Options value with your DIY's listed next to it. That should have been removed and then changed to diy Effects as shown below.
When I started to test this myself I found that it wasn't right on my prod hub either and I couldn't find out why. I re ran the process multiple times to update the scenes and it just wasn't applying like the updated code libraries were not being applied. I fixed this by simply opening the driver code itself and clicking on save. That seems to have triggered the driver to recompile and collect the new code. The next attempt to update the DIY effects/scenes worked as expected and I got what you see above.
Please go ahead and try the same open under the developer page open the driver and just click on save. Then go back to the devices and click on "Scene Load" command and hopefully you will have the DIY Effects state variable to remove the error.
Hi @mavrrick58. I update via HPM, and I'm still having the same issue. I initialized the device, enabled LAN Scene Control, changed the file name to GoveeLanScenes_Lyra_Pro.json, and clicked "SceneLoad". The same limited number of scenes appear (exact same log as I posted earlier). Do I need to delete the devices and create them anew? Thanks.
Can you try the same steps as i provided for @danabw.
Please go ahead and try the same open under the developer page open the driver and just click on save. Then go back to the devices and click on "Scene Load" command and hopefully you will have the DIY Effects state variable to remove the error.
+100 points for your patience and -100 points for my idiocy It worked perfectly, as you explained clearly above and I missed in my food-coma post-holiday haze.
I noticed some oddities in the scenes file though. They Lyra Pro has some names/scenes in duplicate (e.g. Forest), and it's missing others (e.g. Fire) that I thought were there before.
Thanks again for your work/help. Because of your work, I went from 0 Govee lights to 6 in under 2 weeks.
There may be duplicates between 1-21. This is totally self serving, but it was actually done to match Wiz Bulbs so if you have Wiz Bulbs and Govee lights configured fully local API ,there is a decent chance scenes will kind of match up and provide nice matching effects when using the Next and previous effect buttons.
I can take another pass at what is missing. It isn't uncommon for Govee to add scenes to Devices as time passes. I am sure that as time has passed some of the lists I have created previously are no longer 100%. It also doesn't take to long looking at the app to see there are some gaps with the Lyra Pro lamp. Try out a few of the ones that are there and see how well it really matches up. If not it may be needed to create a new list specific to the Floor Lamp 2 model you have. Keep me informed.
Something you may also want to consider is the Floor Lamp 2 is capable of Matter. If you really want it to be 100% local you could use that and eliminate the cloud completely even for status updates. YMMV though with matter so make sure matter is working reliable for you. My Govee matter drivers still enable scene control with LAN API so you wouldn't loose that ability.
Ah, OK. I have been doing a lot of testing. Hmm...I'll take a look at my rule and see if I'm making unnecessary calls. I think you said I had a 10K limit/24 hours.
Assuming things reset at midnight, I'll be able to confirm tomorrow AM that it's a rate limit issue.
Yep. The rate limit is one of those things they kind of screwed up big time with their new APi. I use to be able to keep track of it in the Smartapp, the new app broke that as it isn't include in the response anymore.
Thanks for your time on this. At this point, I notice only one cloud scene (Fire) that is missing from the Lyra Pro JSON. Of course, it's one that I already automated I tried a custom file with the various "Fire" configs from the other JSONs, but none of them are the same. Not a big deal at all.
Now for more fun. I just received a Table Lamp 2. When I enabled LAN Scene Control, it did not locate a file. I chose an existing file (Cylinder) that looked pretty close, but the scenes didn't load. The logs reveal two recurring errors: getDevType(): unknown device Type H6022; null on line 1652.
Woops that makes sense. Ironically I have that file already extracted for the Matter driver with that device. Give me a little bit and I will add it all to the integration and get it setup for you to download.
Go ahead and perform a repair from HPM. I update the library code to properly recognize the H6022 light. I also added the scene file so that will download with the repair.
Worked smoothly. Thanks for the fast turnaround! Now this is odd. The LAN scenes for Lamp 2 and Table Lamp 2 have the same issue: they both are missing the scene "Fire". All the others appear to be there. Pretty bizarre.
Unfortunately, that is right in that it doesn't provide humidity. That device was the second humidifier they made, and it seems some of the functions are linked together. The RGB is also not controllable.
I have that humidifier, and it works well for me, but does have a few quirks like that. You also can't control the UVC sanitizer lamp outside of the Gove Home App.
The good news is the built-on sensor does work pretty well to automate the device itself. I just set mine to 45 and leave it on auto.
Hello - I just set your integration with a new RGBIC light strip. I installed it via HPM and included all the V2 color light drivers. I applied for an API key and got it, and added to the integration (V2). No device appears in the dropdown for adding devices. I've closed and opened the app and hit refresh a bunch of times over about an hour, but nothing appears in the dropdown. What is odd is that on the app screen I see this:
Current Integrated Device Information
There are 2 devices integrated
Your current integrated devices are [Govee v2 Device Manager]
When I go to the device manager in devices, it doesn't seem to have any child devices - or anything indicating the actual light strip.
Not sure what the problem is. I confirmed in the Govee Home app that the device is setup and visible with the associated account.
What is the model number for the device you are trying to add.
Once the integration is installed and you have the API key loaded you need to click on the option for "standard Device Setup". If your device does not appear there you can try to force it by clicking on the refresh button. If the device still doesn't appear there may be aomething in the Govee aide delaying your account feom being updated, or your device doesn't support the Govee Cloud API.
By providing your device Model number i can check if it supports the cloud API and possibly provide alternatives. By chance does the device support Local LAN control(LAN API)?
Do you see any errors in the Live Logging on Hubitat. That can also shed some light on what is happening.
I'm noticing an odd behavior with the setColor command for the Floor Lamp 2 and Table Lamp 2. For both devices, setColor (whether executed on the Device page or programmatically) always sets the Level to 100, regardless of the input. (setColor sets the Hue and Saturation values correctly. As well, the setLevel command correctly sets the Level. However, setColor cannot do it in one step.)
It worked perfectly, as you explained clearly above and I missed in my food-coma post-holiday haze.
