-
Notifications
You must be signed in to change notification settings - Fork 57
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
New local API coming soon! #77
Comments
Awesome news if true! Been having so many issues with rate limiting the past week. |
Nevermind, seen someone on the Home Assistant Community has found a URL for it (which should hopefully stay updated as new devices and features get supported): https://app-h5.govee.com/user-manual/wlan-guide |
I just tested the local API with nc and it is super quick. I completely lack any programming knowledge though.Are there any plans or time frame for implementing this in this or any integration? I suppose most users would prefer to use local API where available. |
Subscribed to this one! Would be really useful! |
For all the fuss everyone made about not having local control, you'd think someone would be all over this when Govee finally released it. Local control is the whole goal of HA! Let's go! |
Node Red has a module for local control. the problem I have is that I am new to Home Assistant and still learning. struggling a fair bit with node red |
FWIW, the homebridge-govee plugin has invested in this recently and can even let you configure the IP addresses of hosts to communicate with if they are eg: on an IOT subnet and can't directly be discovered through the multicasting stuff. May be interesting to get inspiration from there. I'm almost at the point where I'm ready to spin up a second homebridge instance with just that plugin and then using homekit controller in hass to talk to that :) |
hubitat has local integration as well, it looks like you only need port 4003, the homebridge integration has the full discovery process, while the habitat asks you to define the IP and then sends commands over 4003. |
A bit hesitant to post this here because it feels a bit off to self-promote in someone else's repo. My take on this integration prefers lan, then ble, then http based control: in other words, it tries to avoid using the cloud interface where possible. It has some different design choices from hacs-govee and its underlying library. It's all-new code so will have new and exciting issues compared to what you're used to; you can find it here: |
This is awesome! I'll try it out soon. Thanks for posting here :) |
Maybe it makes sense to join forces? |
This chat with Govee support was something of a roller coaster. Long story short, even devices listed in supported models aren't necessarily going to be supported depending on hardware version. Extrapolating on my very limited experience (11 and 6 month old devices of the same model), I would say it's safest to assume that only very new devices are going to have local network support. I would bet it really depends a lot on which particular models and not getting a device from an old batch. Personally, I'm running two H6110 LED strips, both with Hardware Version 1.00.02, bought in February and July of 2022. On the bright side, if your device isn't supported, looks like support is willing to remove the rate limits from your API account. So I have that slow, cloud based access going for me now... |
OMG ! You don't get enough recognition, thanks you so much. Found it way too late ! It works amazingly with my H61A0 |
Not a feature request, but some exciting news regarding the future of the Govee API.
Check it out here:
https://app-h5.govee.com/share/community?client=0&postId=93664&t=1652143647014
The text was updated successfully, but these errors were encountered: