On my Christmas Tree Lights 2, all of the scenes with "-B" at the end were the ones that did the Shape Mapping that I could originally only activate with the app; not your integration or directly to the API. I wonder if just related or a coincidence; probably the later. The Shape Mapping works now though using your integration and direct method.
I'm encountering something odd with the H6168 RGBIC TV Strip. When using setColor, the desired settings take effect. Then anywhere from 1 to 15 minutes later, the switch attribute changes to off. (However, the lights remain on with the current settings.) I'm using LAN settings.
Another note, likely unrelated, is that the hue and saturation attributes occasionally change by 1 from their instructed settings. Not a big deal.
Star Light Projector Values:
Cap Types
["devices.capabilities.on_off","devices.capabilities.range","devices.capabilities.dynamic_scene","devices.capabilities.dynamic_scene","devices.capabilities.dynamic_scene"]
Commands
["powerSwitch","brightness","lightScene","diyScene","snapshot"]
Govee early on had occasions where they would have many variations of the same scene but only show one by default. So as an example if i prefer Halloween-D on my H6172 Outdoor LED strip it won't be available with the new method. For LED Strip devices there were a ton of scenes extracted that were the extra versions, they just won't be available with the new method. I am not sure how much of a issue that is, but I wanted to inform users first. The big issue i am trying to fix with this method is to allow users to pull in new scenes as they are made available on devices by Govee. Many new devices add scenes over time. I have a feeling users with older devices like the LED Strips i mentioned above will find some scenes are missing.
@AEBogdan I will work on a new device specific driver tomorrow. The integration did map you with the best existing driver, but it seems that though your device doesn't have any color controls through the API, it does have the ability to do scenes. That driver is extremely limited because it is literally just for a White light only device even without CT. The only other device i know of that uses this was a Outdoor String light device.
@mavrrick58 Soo.. I was trying to figure out what was going on with my Govee lights and it appears that everyone has got similar issues, so I'll just leave that be for the moment, however, I have a question.. kinda feel dumb asking but I'm curious.. Under the Driver Code section I find, which appears to me, multiple drivers listed for the same driver. I could be wrong and am totally missing what (or why) these are there, but I thought i'd ask cause I can't really find anywhere that anyone has had a similar question. See below for the screen shots
As always thanks for your dedication to your mastery of the integration.. Honestly, if I were in your shoes, I would have already been running, screaming naked through the streets of my town like a crazy man, so kudos to you for keeping your sanity lol..
What is the problem you are having with your lights?
The different light drivers are for features related to your device that it may or may not have. Here is a breakdown in the documentation document that explains it.
Basically, this occurs because I had a few occasions in V1 of the integration where I had to explain why something didn't work on a device that had limited functions. The drivers in V1 enabled all functions no matter what your device could do. Prior to the new APi I couldn't identify what features a device actually had enabled in the API, but the new API does. This is why it is best to leave the driver alone when you install something. The integration looks at what features the device has and selects the correct driver for you. To do that though you need all of those drivers. Occasionally we run into a combination of features i didn't plan for so i have to expand the list. That rarely happens now though.
1 Like
The new "Star Projector" device is working well. You can turn it on and off and set the master brightness and a timer.
All scenes listed in the app were retrieved. I created a DIY scene and it was retrieved as well. I was able to enter a scene number into the SET EFFECT field and trigger a scene and also use the DIY Number to activate a DIY scene.
Additional App Features Not Included:
- Defining an on-the-fly effect instead of using Scenes or DIY.
- Turning on/off Music Detection (Start/Stop Pickup).
1 Like
The "Star Projector" does everything I need, so those last two features are just from observation. Thanks!
1 Like
Thank you for the update. I will include it in the next release.
1 Like
I just released another update to the code.
Now when you go to the "Lan API Scene Management Menu" a new button is available. It will allow you to retrieve and create the Scene files for all of your devices at once. This should make it easier and faster to use for your devices if you have several like me.
I have also done some code cleanup and tweaking to the new Scene Extraction process to help it handle device types that were previously providing incorrect data.
I added the new H6093 driver to the integration. Thank you AEBogdan for testing before hand.
2 Likes
Oh man can't wait to try out have to dig out the Christmas Tree string since I don't want to mess with the current TV bars and other lights.
Belated Merry Christmas. I have been offline for awhile. I just wanted to check to see if there was any thoughts on this or if the developer site had responded to your query.
This new process builds a new file to be used. So you can pick a device, run the extract process, and then just change devices over one at a time. It will still default to the old files unless you intentionally change the file name in the preferences.
Unfortunately no. It seems this is more widespreed then i knew initially, There are other reports of users having issues with DIY's showing up on random devices. There has to be a API problem. Hopefully they are working on it.
I was going to reset one of my lights before returning it and am finding different suggestions:
- Hold the power button while pressing the recessed button w/a pin 4 times, lights will blink
- Hold the power button until the lights blink
Which is the right way to do it?
It depends on the device. Though i would be curious what they think is a recessed button. They could be mistaking the mic for a pinhole button.
Oops - that was my bad, I was voice typing and got some "creative" interpretations of what I was saying that I didn't edit properly. Should have said "middle" button, and it looks like that only refers to devices w/multi-button controllers.
I expect that the long press on the power button will will do it...found that mentioned several times for single-button controllers.
1 Like
I had an error when doing the Standard Device setup for my Curtain Lights and similarly the Gaming Wall Light.
The error I get is
Device Curtain Lights was selected for install but driver Govee v2 Color Lights Driver is not installed. Please correct and try again
When I check the drivers installed I have "Govee v2 Color Lights 2 Driver" instead of "Govee v2 Color Lights Driver". I installed using HPM.
Anyone know how to resolve this error?
Go into HPM and click Modify, then select Govee Integration v2, Next, then check the box next to Govee v2 Color Lights Driver in the list of drivers.
1 Like
Thanks, that resolved it. I should have realised to try that. Also I was expecting my Curtain Lights 2 to need to use the Color Light 2 Driver, but it seems to work fine with the Color Lights Driver.
The driver used is determined by the features it supports. That is why there are so many different drivers for Lights. If it uses a different driver then the functions it supports are different.
There is talk about a feature being added that may change that, but for now that is the case.
1 Like
