I am currently considering to add my first Govee components to my Hubitat System, which I use already for Z-Wave and Kasa components. I downloaded in preparation already the Govee Integration App mentioned here.
I want to add multiple (10) H5054 Water Leak sensors. It seems they are not on the list API enabled components and I checked with Govee it is also not planned to do.
Now my question, does it mean they will not work at all via the integration to Hubitat or only limited ? The water sensor has of cause very limited functionality and I would like that I get the signal of water leak or water dropping for the individual component into Hubitat.
I can not try it, as I would buy the gateway and water sensors only after there is a chance it will work.
We can only connect to devices that are enabled through the API. This is completely in Govee's court. If they make them available through the API just let me know and I will work on getting a driver setup for them. My only suggestion would be to hound Govee to add them. Currently the API is only good for Lights, Switches, Plugs and Appliance devices.
You may want to look at using Alexa as a middle man. Basically the idea would be to have a alexa routine that would then flip a virtual switch in Hubitat to let Hubitat know the state. It isn't the best solution, but until Govee enables their sensor devices to use the api there really isn't any other option.
What is the device and what command did you use that used the cloud.
The cloud is never fully eliminated as device status is still retrieved via the cloud. This is a current limitation of Hubitat. All other commands should be over the LAN API if the switch is turned on.
@user4784 Did you manage to figure out what is happening with your Lan Control? It shouldn't be able to use the Cloud once the Lan Control option is switched except for Devices Status lookup.
To everyone else Govee is doing system maintenance on there cloud system tomorrow I just saw this in their Govee Home app. Looks like they will be doing system maintenance tomorrow morning and we may have an outage for 1 hour. If it goes much beyond the time window shown in the screen shot below you may need to reach out to Govee support to start a ticket. Hopefully this means we have some updates to the GoveAPI coming.
You have allot of references of "cloud already in retry state. Aborting call" and i see a few occasions of error status 429. Thise indicate you are hitting rate limits. Please remember we can only make up to 10 calls to the API in one min. Some actions take multiple calls. So that may be reduced to five. In those cases.
You also have several references to "unauthorized" and that makes me wonder if there is a issue with your token.
How many devices do you have? Do they just work for a short time and then fail. Or are they just not working at all. What do you have your soft poll value at? What are you trying to do when this happens?
My first suggestion would be to determine if you can use the Lan API instead to significantly reduce your use of the Cloud API. With the LAN API it seems you can send commands about as fast as every two seconds.
The unauthorized error is strange as i think that points to a issue with the token. Maybe request a new one?
Yes great help, thanks a lot, but I tried with new API, but I couldn't solve it yet, i'm waiting for the weekend to finish investigating and will try the LAN API thing, i have 16 active lightstrip.. even with heavy testing not using 30% of the 10k API limit, but i still have the problem
The numbers I provide in the Integration app are for the total 10k per day, but do not address rate limits on each individual device. That space is important to understand how your polling settings are potentially impacting your daily rate limits.
What are the model numbers of your strips. My Outside LED strips are H6152 for instance. If you don't know you can get this from the data section when looking at the Device in the HE UI. If your devices support LAN API control that is the way to go. Make sure you follow the steps to verify your device supports it though. Make sure you set it up properly though and I would setup each device with a DHCP reservation on your router so the ip doesn't change.
If you look at the page for the device you can see the rate limit as it is circled below. The state values don't update immediately though so you would need to refresh the device page to see the most recent value if you have been pushing on buttons in the UI.
When trying to install the Govee API Integration app on my C8 the following error appears:
No signature of method: Script1.definition() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:Govee Integration , namespace:Mavrrick, author:CRAIG KING, ...]] on line 16
The solution is not apparent to me. All of the other APIs installed properly. How should I proceed?
That is interesting. That is like a header for each of the pieces of the application and it never changes at this point. I will take a look.
Has anyone else seen this?
So just so I am aware how did you install the Govee Integration?
What is your current firmware on your C8 hub?
Do you have any similar problems with other apps? The part you called out is standard declaration all apps have to do. It is strange that it would call that out.
Can you provide clarity on exactly when that error occurred. Was it right after you clicked on it in the list of user apps, or where you at some part of the setup?
If so what part were you setting up?
I am still testing but it seems that it worked fine when I did it on my C8 hub. I am did a repair through HPM now to be 100% sure I have the latest copy of code from the repository.
Can you show me a few errors that occurred before and below the error you linked above.
I have managed to resolve it thank you @mavrrick58 I've tried changing API key further that didn't work, and actually put all lights to cloudAPI status to Retry
so I removed the entire Govee app from HE, and installed again with the new API key, which worked smoothly, but further more I did your suggestion for Local LAN API, and man that is so quick so smooth, it take some time to identify each light MAC from Govee android app >> reserve IPs at the router >> Activate LAN Control (from Govee android app) >> then back to HE govee device(s) one by one to update the IP of each light..
Thanks for the update and the info. I will check about fixing the issue with changing the API key. What you said about everything having their cloudAPI going into retry state makes sense after thinking about it. Sorry about that. I will need to think about a way to fix that if anyone else needs to update their API.
I am glad to hear otherwise you got it working though. I have ideas on how to make LAN setup easier, but I need Hubitat to do a few things first. The good news is that should be a one time thing hopefully.
Just FYI everyone. It looks like the Govee Cloud API is having some kind of issue now and for about the last 2 hours. Looks to be a server issue with error code 500. Hopefully they will get it fixed soon, but until then Cloud API calls may not work and the Polling will generate errors.
Devices that are setup using the LAN API should be working fine. You just won't get status updates if you make change from the Govee app
Question, do you know if the TV backlight strips will ever get a local LAN API? Those are really the only devices I use aside from some power plugs I use for powering off the hubitat hubs when needed...
I don't get any inside information unfortunately. So I get the same info everyone gets from their app and community.
That said I don't see why they wouldn't, but if you already have the kit and they are older i wouldn't expect to get the LAN API. I just checked the LAN APi spreadsheet I was maintaining and there are two devices already on it that are for TV Backlighting. Those two devices are the Neon rope kit for TV Backlighting and then light bars for behind the TV. I hope that changes soon though as i am looking at replacing one of my TV's and would like to upgrade my current H6199 (very old) kit to a new one with dual cameras.
I just updated the first post and my LAN API Sheet. It looks like Goove has further trimmed down the list of supported devices. Looks like it effects older devices that were partially supported. Just be aware that list is update to match what is currently in the app and documented. The devices that have been removed are still in the sheet just hidden so you will need to unhid rows if you want to see what has changed
