-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
H610A: Support for scenes over IoT API #7
Comments
I'll take a look. As it happens, I also have an H610A but I didn't notice this because I replaced it with a more beefy home made strip(!) and it's been sitting in the corner. I do have some logic to read the "one click shortcuts", but it is a bit murky to try to reverse engineer most of those. I also recently did some reverse engineering around scenes and getting things to work via the LAN API: egold555/Govee-Reverse-Engineering#11 I'm not sure that it works for 100% of all scenes, but it might be enough to satisfy you. |
I can actually pull DIY scenes and the built-in dynamic scenes for the device via the official API ( |
At the time of writing, the platform API doesn't return correct information for this device, and refuses to control it appropriately. This commit adds the concept of a quirks database that can be used to override the metadata and try to arrive at a better outcome. This is sufficient to regain color and brightness control over this device. For scenes, this commit attempts to use the fruits of some reverse engineering to compute a scene code to send via an undocumented part of the LAN API. In practice, this is most reliable with scene codes that fit in a single byte; the others likely need to get routed via the IoT MQTT connection. That can be examined in a follow up commit. refs: #7
I just pushed some basic improvements for this device; you can now control the color and brightness. I'll need to do some more digging to see about enabling things like the one-click shortcuts. |
Add a bit of summarized output at the end. refs: #7
I just pushed a version that now adds a home assistant scene for each One Click you have defined in the app. |
Thank you! It works perfectly 🎉 I can finally get rid of my homebridge server I was running just for this functionality 😄 . Hopefully the official API and/or LAN API get support for this at some point, but this is an excellent workaround. |
would it be possible to have the one-click scenes show up as effects under the relevant devices as well? Don't worry about it if it's complicated! |
it's a bit awkward to add to the effects list for a couple of reasons:
What may be a bit easier to fit in is adding a button for each scene the device belongs to, which would show up similarly to how the scenes show up in the I wonder if I can make this automatically happen without adding additional entities; if there is some way to associate the scene entity with the device(s) that belong to it, then the default behavior of showing the scenes in the UI should kick in. Again, this is visible with the |
My goal was to be able to add the govee scene as part of a larger HA scene (e.g. have a HA scene that triggers a govee scene/one-click and also applies other settings for other devices). Some kind of button or switch might work for that.. |
you could create a home assistant script that triggers both the home assistant scene that you create and the one click scene(s) |
Looks like they fixed the platform API for my H610A, so the quirks may no longer be needed for it! |
Confirmed: I can set all the scenes for mine here with that quirk override removed |
So remove the quirk that avoids it refs: #7 (comment)
@rygwdn latest version removes the quirk, enjoy! |
Would it be possible to support getting and activating scenes or "one click shortcuts" over the IoT API, and force the addon to use that API rather than the official one for certain devices? I have an H610A which doesn't report any functionality other than on/off from the official API despite being full RGBIC (reported to Govee here without much luck). The scenes can be activated with homebridge-govee with some manual setup, so I believe it's possible over the IoT API.
Thanks for the awesome work on this!
The text was updated successfully, but these errors were encountered: