From my view when the extraction process has always been designed to be a one scene/snapshot/diy at a time process. This has always been because of the nature of how the objects are displayed on that page.
That said technically I believe it will extract all of the Tap-To-Runs configured in the group in the Govee home app. It will just display the first or last one it parses. This is assuming that there isn't something with one of the tap-to-run that it can't parse and it errors out. So in theory it should be processing all of the "Tap-To-Run
I have always said to do one at a time so you can see the information easily. With the change to the way this data is managed to now be retained in a file instead of the app data, it should be easy to retrieve the info if you wanted to though.
I think something to remember is we aren't really storing/running the Tap-To-Run. We are just extracting data from it so we can submit the same actions via LAN API. The most important part of that extraction is the command value. Also the process filters out multiple items for the same model number.
With V2 you can now submit scenes through the API. So another option would be to simply not use LAN API, or change the flag to control scenes with the cloud. Then you just need to submit the appropriate values for the scene/snapshot/DIY and it should activate.
I did start looking at the other devices that were included in that tap-to-run, it actually did extract them all (like you said with the devices I think it just reports the last one). It doesn't look like it adds the DIY to devices of a different type that are included in the tap-to-run. I have some strip lights that don't have that DIY attached to it.
I guess I keep thinking of it as a way to call the tap-to-run itself to do all the actions contained in it, like setting brightness and turning on a DIY, but really it is just extracting the DIY part and not the rest (which can be done on the Hubitat side for sure).
Been using the v1 integration for quite awhile and just switched to v2 and just seeing what it is capable of. Appreciate your work!
Govee's Matter supported devices is growing rapidly. Here is the current list from the documentation. So with the Govee RGBW Matter Advanced driver you can enable LAN API to call all of the scenes and such for the device as well. You need the scenes file, but the control is possible.
Device Name
Model Number(s)
Device Type
Driver
Comment
Smart Plug Pro
H5085
Plug
Generic Matter Outlet
Table Lamp 2
H6022
Light Device
Govee RGBW Matter
Wall Sconce
H6039
Light Device
Govee RGBW Matter
Govee Gaming Wall Light
H6063
Light Device
Govee RGBW Matter
Floor Lamp 2
H607C
Light Device
Govee RGBW Matter
.
M1 Led Strip
H61E0
Light Device
Govee RGBW Matter
Govee Strip Light 2 Pro
H61F2, H61F5, H61F6
Light Device
Govee RGBW Matter
Neon Rope Light 2
H61D2-H61D5
Light Device
Govee RGBW Matter
Govee Perm Outdoor Lights Pro
Light Device
Govee RGBW Matter
Govee Perm Outdoor Lights 2
Light Device
Govee RGBW Matter
Neon Rope Light for Wall Lining
H6640-H6641
Light Device
Govee RGBW Matter
.
Govee Christmas Tree Lights 2
H70C4-H70C5-H70C7-H70C9
Light Device
Govee RGBW Matter
Govee Icicle Lights
H70D1-H70D2
Light Device
Govee RGBW Matter
Govee COB
H61E5
Light Device
Govee RGBW Matter
Starry Light Projector
H6093
Light Device
Govee RGBW Matter
Govee Outdoor Triad Flood Lights
H7063
Light Device
Govee RGBW Matter
Outdoor Wall Light
H7075
Light Device
Govee RGBW Matter
Govee Curtain Lights 2
H70B5
Light Device
Govee RGBW Matter
Govee Net Lights
H6811
Light Device
Govee RGBW Matter
Smart Tower Fan Max
H7105
Fan
Govee H7105 Fan(Matter)
Does not support Govee Wind Modes
The one big thing some folks may want to consider when going between the other drivers and Matter for light devices is that Matter calculates color differently. So it will be more accurate for color selection and restoring a color, but this comes at a cost of being able to set the color to a super low level in some cases.
Hi, Govee Integration V2 works on my system. I can choose a color, hue, level, etc..
I can't however figure how to set "snapshot" and "activate DIY".
What string should be input in the field?
You need to open the device and scroll down until you see it's state variables.
If you are using the cloud and have DIY's or Snapshots associated with the device they will be listed there with their corresponding number values that can be used to activate them. Here is a screenshot of how it looks below. It would use use the number values next to the
If you are setup to use scenes and such with LAN API enabled then those values would be there, but you would have to extract them using the given process in the Govee Integration app. I would suggest clicking on the help icon in the app for clarity on how to do that.
If you load the integration app there is a icon with a ? in the upper right corner or the documentation. The link is below. That can be used to see all the details of the integration including supported devices.
Yes looks like it is supported based on the info on the Govee support page. Will there be a specific driver to use? There's only 4 or 5 or drivers listed in the app...
Be warned that just because a device is on that list, it doesn't mean that the integration will find the device and you will then have to use the Govee Manual LAN device that does not do all of the things the other drivers can do. I have the H7052 and the integration has never found them. The Home Assistant integration does not either so it is a Govee shortcoming, not @mavrrick58. His work on this is AWESOME and he has been patient with me trying to get my 3rd device connected.
Most likely it will use the standard Air Purifier driver initially. If you want a device specific driver just send me the data section from the bottom of the device page and the state info so i get all the work mode info.
The only differences i have noticed is the number of speeds and how sleep mode activates. It is possible one of the other drivers will already be good for it.
As far as @stephen_nutt's point. That is generally a issue only on the newest devices that may not have all apis activated. That is based on what has been reported to me. The problem is when it happens there is no telling how long it will be.
Ultimately as long as it is detected I will get you going. The framework for the drivers are complete so it is just finding out what the differences are.
Another user reach out to me in a DM asking about Matter support for the H7124. He indicated he had it working with the regular integration already but was curious about a MATTER driver. If you have a matter code on a sticker on your device can you DM me and I will work on a Matter driver with you if you are interested.
I just located a bug within some of the Light drivers. I have posted a fix that can be downloaded now.
This bug caused a problem if you configured the device to use LAN API for device control, but then wanted to use the cloud API to activate scenes. It was failing to use the cloud api and was continuing to try to submit the command via LAN API.
If I have 3 curtain lights “spliced” together to create one large canvas, how can I control that with the integration? Or is it not possible? Also, is there a way to initiate the “Auto-Play” scenes from the integration too?
Not sure what you mean by auto-play. Is that similar to tap to run? What does your auto-play do?
As far as the spliced curtains go it probably depends on how they are viewed in the APP. Are they all under one device in the Govee Home APP, or are they still seperate?
There is nothing special in the API to account for spliced devices. You may need to try it to find out?
I just installed the Fan H7102. I notice that the oscillator function appears in the device as airdeflecteron_off. When I try to access it rules using the actuator what should I specify as the parameter type etc. in order to turn it on or off? Or should I be doing this another way? Thanks.
So you can pass the parm as either "on" or "off". Lowercase is important.
The other option would be to go to the device page. Scroll down and collect all of the work mode info in the States section and then the data section and send it to me in a DM. Then i should be able to turn around a device specific driver for you fairly quickly. Those drivers allow you to use the fan control options in RM and then have seperate command buttons for osscilation on and osscilation off.
You could also try switching to the driver for the H7106 fan and see if that is 100% functional for you. Most likely the only difference is the number of speeds, and may some of the mode functions like nature or sleep won't work if not supported.
@mavrrick58 my token was expired but i click login and it doesn't change and just says im not logged in. Is there any reason why it would happen and how to i check that the login is correct, i logged in and out the app so i know the details i have are correct (i assume its the same).
