Just a note the scenes in the app for "mapped" devices have the "M" underneath them. Also these scenes are created dynamically as how the app mapped the light string against the tree. My Christmas Stripe B will be different code than your Christmas Stripe B if you extract the scene.
I found some really tacky lighting scenes in their library and just to make the wife mad, I selected one on the tree right before we I turned it off the other day and when she turned on the tree, I just heard a loud yell "Noooooo."
I had the same question a month ago with my TV Bar Lights and there are limitations on what Room Lighting can do with the RGB Govee Devices. I found I can set the RGB Value and Levels in the room lighting apps, but you can't get to custom attributes that deal with segmentation and other advanced features in the Govee Integration. With that in mind I am using Rule Machine for anything that requires the more complex setting like segmentation or custom scene loads. You may want to open a thread in Room Lighting let's see how far it gets.
Mine are arriving tonight...which driver did you install for the X-masLights 2? I mean, did you install the "Govee Integration v2" or "Govee Matter Drivers" ??
My Echos and Google Home are on a IoT VLAN so blocked from my Hubitat. I wasn't able to easily get Matter working with a plug previously. Since I don't need Matter, I haven't put in much effort with it.
My Christmas Lights 2 don't work when entering any of the numbers for Scenes ending in "B" which I believe are the ones that use on Shape Mapping. I have done the Shape Mapping and then re-done and still no luck.
So far, the simmarly-named scene without the "B" works and my DIY Scenes work. If I select a "B" scene in the native app, it works. It's just not working from the HE Integration and there are no errors in logs.
Anyone else having issues with the "B" scenes that use the Shape Mapping?
I use Node Red for automations and I am getting this error when using a Command Node and passing the SetEffect number. Not sure what it means or if it matters. The command still works as long as not using a "B" scene as mentioned in previous post.
""The device (1011) sends an event (effectNum) with non-official dataType (INTEGER). The default behaviour is to leave the attribute value (14099) as string. It may result in a difference when getting attribute value with input vs event (e.g., json vs string). You should report back this issue to the device driver maintainer. Supported dataType: https://docs.hubitat.com/index.php?title=Attribute_Object"
Device 1011 is my Christmas Lights 2.
I have noticed this before but don't think I shared it already. If I did, getting old is my excuse.
I've read as much as I think possible, and I'm new with the Govee app so bear with me, but can't seem to get a grasp on how to use this app to import/extract a "Same-Model Group Control" scene/setup.
It appears we can only pull in a Tap-to-Run?
The issue is I have 3 porch poles wrapped with the string lights v2 and in the app I can create a group and apply a scene and they're all in sync. I don't want to use Dreamview scenes/music, I want to use the built in or DIY scenes applied to this "Group." When I put the devices in a Tap-to-Run, they're not all in sync.
Unfortunately the grouping tools in the Govee Home App are not something i can interact with from Hubitat. Govee provides no way to interact with that grouping functionality from their API.
The Dreamview toggle on the devices in Hubitat is for Music or Movie dreamview. Not for regular scenes and such. The way to group devices from Hubitat is to setup rules in Hubitat that simply control multiple devices at once.
I am still exploring how those B scenes work. I had a busy work week, so I am behind on the extract and testing myself. I need to turn on my firewall logging for the Govee devices to see if there is a round trip needed to make mapped scenes work. As of right now I am just setting one mapped scene and sticking with it. When the lights are turned on they are on that scene.
Before I realized it wasn't working, I set up a automation in node-red to change scenes every 15 minutes. It was when I noticed that lights were off or in weird patterns that I discovered that it doesn't like the "B" scenes.
What would the JSON format be for a command sent to Govee API if Scene is 12345?
Since I am not getting an error message when sending an Efffect number for the Shape Mapping automations in Hubitat, I am wondering if I would get a message by sending the API request directly outside of Hubitat.
I found a way to get list of devices so I could get the Device ID. Unfortunately, the result is only 2 of my 7 devices and Christmas Lights 2 is not one of them.
EDIT:
To add another data point, I added the Govee Home Integration and Alexa can also only set my scenes that are not Shape Mapped also so it's something wrong with the device. DARN!!!
I setup 3 devices in RM using a simple 14100 (Christmas) Dreamview and unfortunately, they don't sync to each other like they do from the app. Seems they're not all "started" at the same time. Tried putting them in a group just for the on/off part of it, but that doesn't help.
Thank you. With the help of ChatGPT, I was able to figure out what to put where in the POST request using POSTMAN. Unfortunately, that method also won't start the Shape-mapped scenes so there must be something weird going on if neither your integration, Amazon Alexa skill, and direct to their API isn't working. The POST would respond with "Success" even when sending a request for shape-mapped scene so no clues. Shape-Mapping is a Beta feature so I guess that should be expected that it is not working 100%. That's a shame.
The POST in POSTMAN would successfully set the standard scenes just fine like your integration and Amazon Echo Skill does.
I posted on the Govee Community Forum to see if anyone else is having similar issue.
Is there a trick to using the matter drivers? I initially had my Floor Lamp 2 hooked up with some other random driver from the V2 integration. It was working except I was having major issues with Room Lighting transitions - basically the lights just kept cycling colors until the transition period was complete.
Then I saw there was a separate matter driver, so I downloaded that in HPM and changed my device driver. Now it's not working at all, can't do any commands at all, logs are just showing a bunch of errors. The integration "device" shows disconnected. I tried repairing both the integration and the driver but still no luck. Is there any trick to using the matter driver?
Having some issues with the DIY scene extractions. I see that there are some issues with the Gen 2 curtain, but I have the Gen1 curtain.
I am running Govee Integration V2 and updated to the latest.
I initially ran V1 and updated to V2 a couple of months ago. I initially used LAN control and that defaulted to LAN scene extraction as I understand it.
I since have changed the curtain to: Enable Local LAN Control "Enabled" and Enable Local LAN Scene Control "disabled".
I "Initialized" the device and then "sceneLoad" the device. It appears that all the predefined scenes have been defined, but there is an issue with the diySceneOptions.
Unfortunately, I have two groups defined with diyScenes in each group. The first group "default" contains 37 diyScenes. The second group "tedit" contains 41 diyScenes.
I don't recall how or why I defined the two groups.
In any case, after I do the Cloud extractions. I get all of the 37 diyScense from the "default" group and I get 3 diyScenes from the "tedit group". So a total of 40.
So I am confused as to why I only got 3 from the second group but wasn't sure if there was a sizing issue or just confusion due to the two groups.
I cycle through the many scenes using the Govee APP but was hoping to come up with something better using Hubitat to cycle the curtain scenes.
I am not sure what this means. Scenic Dreamview is not something i can access through the new Cloud API. I am not suprised with your results though unfortunately. Each device needs to be controlled independently. The only way around this would be for Govee to change there API to allow a way to activate and deactivate Scenic Dreamview Groups.
It has to be something with how it is activated. It must require more then the command we can submit via thr LAN API. They may need to add new commands or something to the current Cloud API to enable it. The Dreamview command was added to the API. Could you dm me your list of commands in the data section on that device just so we can be sure a new command wasn't added to support it.
As MATTER is a whole new method of connecting you will need to add the device again using the Matter device add method.
Yes the same recommendation applies though. Use the cloud for scene and DIY scene control. Once that is done you do not need to worry about extracting scenes as you will get the scene data from the Cloud API. The DIY's presented should be the DIY's avaliable from the DIY scene selection on the device from the Gove Home App. Unfortunately we found on the Curtain Light G2 it doesn't seem to be getting populated. Snapshots were though so those can be used as a secondary option.
