API Key/Setup issues

[KyleVenenga]

Cannot setup anymore. I was having issues with my integration being unavailable constantly the last few weeks so I uninstalled and reinstalled. Now my API key won't work on setup at all. Tried on multiple devices, reinstalling again, etc.

[the1legend1]

Same issue here. Uninstalled v0.2.2, installed v0.2.1, same issue.

[ilbagatta]

Same here... :-(
It didn't work, I tried unistalling and now it doesn't accept my API key

[justfly1111]

same here i got a brand new api about 5 minutes ago which doesnt work either sucks but reassuring its not something s pecific to me only having this problem

[Maxtoid]

Same also. - Did Govee change something with their API recently?

[ts]

Same original issue here. Same result as well. I requested another API key from Govee thinking it was my key but the new one results in the same error.

[MaxxKra]

I also had this issue.
To test the API, I integrated it as a sensor in HomeAssistant. After restarting HomeAssistant I was able to reinstall the integration.
The sensor only shows whether the API is successful or not.

• platform: rest
  name: Govee API
  resource: https://developer-api.govee.com/v1/devices
  value_template: "{{ value_json.message}}"
  scan_interval: 60
  headers:
  Govee-API-Key: !secret govee_api_key #Replace the secret with your API
  Accept: application/json

[Gotcha182]

I had the same issue. I was not able to control any of my lights. Downgraded to 0.21 no change and now can’t take any new API codes

[KyleVenenga]

I too used two different API Keys.

I am pretty sure that Govee is changing their API, it recently went limited. However, they are adding a localized API for non-cloud integration which is always exciting!

[vcantrell]

Govee rate-limited their overall calls to 10,000 per 24 hours. Current integrations poll way to frequently so that limit is hit pretty quickly.

Before there was an integration I had written sensors and objects that poll the API every few seconds for a status and that fits well under the rate limit. So just reused that for them Govee lights I actually use and am good to go.

Also using multiple api keys won't work since an account-level rate limit

Hopefully my patch will work till the local API 2.0 comes out. But it's definitely the rate limit cuz it tells you when it'll reset and how many you have left after each API call.

[KyleVenenga]

Govee rate-limited their overall calls to 10,000 per 24 hours. Current integrations poll way to frequently so that limit is hit pretty quickly.

Before there was an integration I had written sensors and objects that pill the API every few seconds for a status and that fits well under the rate limit. So just reused that for them Govee lights I actually use and am good to go.

Also using multiple api keys won't work since an account-level rate limit

Hopefully my patch will work till the local API 2.0 comes out. But it's definitely the rate limit cuz it tells you when it'll reset and how many you have left after each API call.

Do we have any idea on when the local API drops?

[Maxtoid]

Govee rate-limited their overall calls to 10,000 per 24 hours. Current integrations poll way to frequently so that limit is hit pretty quickly.
Before there was an integration I had written sensors and objects that pill the API every few seconds for a status and that fits well under the rate limit. So just reused that for them Govee lights I actually use and am good to go.
Also using multiple api keys won't work since an account-level rate limit
Hopefully my patch will work till the local API 2.0 comes out. But it's definitely the rate limit cuz it tells you when it'll reset and how many you have left after each API call.

Do we have any idea on when the local API drops?

All we get is “soon” lol - But it appears like some of the documentation for it is already coming out so I’d expect fairly decently soon.

[the1legend1]

FYI - I was able to get my setup going again by waiting for a day for the timeout to reset, installing v0.2.1, and setting the polling to 300. It has been working without issue for the last 4 days now. I imagine 300 is high for those wanting to have good control over the state of your lights but for me it's not a big deal. I'm looking forward to their localized API control.

[timothybuchanan]

1. What is the "patch" mentioned above and how would I install it?
2. What version should I run?
3. It won't accept my API key; will that eventually change with timeout reset?
   Thanks.

[tech2mar]

Any news in this topic?

[ts]

I was able to get the integration to start running consistently again after some combination of:

• Remove hacs-govee from HACS/HA
• Wait ~24h+
• Install hacs-govee
• Set the polling interval to something long (I did 600)

It's been working fine for a few weeks now but the response time isn't ideal for complex automations/scenes depending on Govee devices. Really looking forward to the local api.

[tech2mar]

I was able to get the integration to start running consistently again after some combination of:

• Remove hacs-govee from HACS/HA
• Wait ~24h+
• Install hacs-govee
• Set the polling interval to something long (I did 600)

It's been working fine for a few weeks now but the response time isn't ideal for complex automations/scenes depending on Govee devices. Really looking forward to the local api.

Thanks I will try.

[Doom666DE]

Hallo liebe Community,

ich hoffe ich bin hier richtig mit meinem Problem.
Hoffe einer kann mir dabei helfen :)

[hraschan]

Got the same problem, Is there any fix for that problem?