Well, got around to playing with the diffuser and the integration. Everything pretty much works as it should. I didn't try setting colors. I am appreciating the timer option that was added for this device. Will be very useful. Thank you, sir for all your work on this.
No problem at all and thank you for the gift again. It really helped drive it out faster. There may still be some order of operations quirks. I think anytime you turn on anything from device fully off state it will return to the last running state. Govee also fixed the brightness command API yesterday so it should be 100% working.
2 Likes
I wonder if they would consider adding the waterless notification to the api as a true or false state. I would love to setup notifications to know when it's out of water via pushover, instead of their app.
I may have to time it to see how many hours it can go before running out and then sending a notification based off a power-on counter variable of sorts.
That would be nice. I wouldn't expect that to change though. They would need to allow a way to retrieve data from the appliance api and then signficantly increase the rate limit.
1 Like
Any way to trigger the snapshots? I can activate them with using ifttt in the rules but that adds more delay and another potential troubleshooting point as well as more maintenance. I'm assuming since IFTTT has the ability to do it, the ability is there....would rather activate the snapshots directly from hubitat.
Does the device in question support Lan control? If it does then you can follow the process to extract the Snapshot to a DIY and then run it from there.
What is the device model you want to do this with?
I just released 1.0.39 which is a significant change to the code. The emphasis for this code drop is to improve the code to be more efficient if possible
This involves a big change to the way the device add process works as well. I have run it several times on my hub to check resource consumption and this new method seems to be a bit friendlier to the hub
If anyone has problems let me know.
That said there are a few thing you may see.
There is a new method to extract the scene list. It will now be mostly in order with the exception of the first 20 or so if present. They will be at the end of the list.
There are now scenes for the new Sconces devices preloaded.
The appliance drivers will now show the command options under the States section. This may help if the value was a 1 or something that was not intuitive. Because of this change they will no longer be populated in the driver data section. They are not being removed though.
1 Like
It does.
It's the outdoor permanent lights.
The snapshots are LED specific, that's why I used them instead of a DIY.
I have certain LEDs come on above my garage doors that open depending which open, instead of a whole string. Some section of my backyard. Very granular control of each individual LED.
How does one extract to a DIY?
I add snapshot to a group and the module won't read them like it reads DIY ones.
Then you certainly can.
First setup the lights to use Lan Control.
Then go into the Govee Home app and setup a tap to run with the Snapshot. Keep track of the group name you create it in .
Once that is done, go in the Govee integration app, go into the Scene Management section and setup your creds. Once the creds are validated click on the button to do the scene extract.
If it is successful you will get a scree displaying the command extracted and its name.
Let me know if you have any issues.
I'll try this again but a few days ago I was trying to read snapshot like I was reading DIYs from a group. It just comes up blank if I add any snapshots to the group. Or even just a single snapshot by itself.
Tried this again just now after your latest update.
Still same as before. If I have a snapshot in the group it just comes back blank when I do the extraction. I remove the snapshot from the group and the other DIY stuff shows back up again.
I reall thought it was validated previously.
I will check what is extracted again and let you know what I find. I still have my test for it in my setup so it was clearly checked before. The key is that a valid command is provided. If it isn't then it will be a no go for now.
If you don't mind me asking what is in the snapshot you are trying to capture? Maybe there is a way for the functionality to be replicated in HE instead of calling it from Govee.
I can't seem to get the scenes to extract, and I think I'm doing things right. Any insight/guidance would be appreciated! Here's pics of my group, the LAN control/token showing as 'valid', and then the results of when I click to extract:
Based on your first screen shots It looks like you added the device to a device group instead of a "Tap To Run"
In the Govee Home app you can create groups of "Tap To Run" automations. That is what the second screen shot allows you to setup. That value is there so you can set a custom grouping to do the Scene extractions for Hubitat. By default it uses Default which is the name of the standard group in the Govee Home Android App.
I would suggest you go into the Govee Home app and scroll down. You should see a section for Tap-To-Run that is probably labled default if you don't already use it. Add a tap to run with the device and scene you want. and save it. Once that is done go back into the Govee Integration app and set that "Govee Home Group" value to "Default". Click done to save it and then run the extraction process again. It should work once that is done.
Sorry for the terminology confusion.
1 Like
Ok so i was kind of right, and kind of wrong. I think very early on Snapshots may have kind of worked. It didn't take long for a issue to occur that made my simplistic extraction process problematic and the fixed would have certainly broken Snapshots.
That said i kind of have it working on my dev hub, but there are some problems. First is that even being able to extract the snapshot command is part of the action. In the simple situation I have checked there were two commands, 1 for brightness and the other for a scene i guess.
So the question is what is it that you are exactly trying to create in a snapshot. If it is simply setting a scene effect or color and brightness level it may just be easier to tell hubitat to submit those commands individually.
What do you normally contain in your snapshots?
Thanks! That worked! To set the scene that was extracted, do I do something like this in RM:
Run Custom Action > (device) Switch > (custom command) setEffect > String
(...I had clicked on 'on', which is why it's highlighted below...)
Or is there some other way I should be setting the scene?
Yea that looks right. Just make sure you select setEffect and pass the Number for the scene you want.
1 Like
I think i realize what you mean by LED Specific. I will think about this and get back with you. Would it be ok if it only captured the led colors chosen and you still needed to set brightness?
Snapshots can involve multiple commands unlike scenes. So they are potentiallya more complicated idea to capture. If you can take care of something like setting brightness then we can capture the command for the individual led's as a single command.
Can you show me a screenshot of your tap to run with the snapshot?
I just found a bug in the latest release that effects how the events are sent to the state of the device. This will impact automations that trigger from govee device status change. Govee devices will still change state, it just may not be reflected properly in the states on right side of the display.
I will work on a update for tomorrow to fix this issue.
This has also been found to only effect appliance devices as regular light devices don't use the same method to update the states on the right side of the device.
1 Like
