LaggAt / hacs-govee

A HACS repository for Govee light integration
MIT License
270 stars 63 forks source link

Can't Connect to API #160

Open RichardKeschinger opened 8 months ago

RichardKeschinger commented 8 months ago

I am seeing this on different threads/issues but i haven't found a viable solution yet.

i get this everytime i try to change the current API. is the only solution to wait?

"Cannot connect. Is the API-Key correct and the internet connection working?"

CrasyHarry commented 8 months ago

same problem here... :-( cant set up the integration...

"Cannot connect. Is the API-Key correct and the internet connection working?"

RichardKeschinger commented 8 months ago

same problem here... :-(

cant set up the integration...

"Cannot connect. Is the API-Key correct and the internet connection working?"

I had to use different integration

CrasyHarry commented 8 months ago

today it works. I don't know why it didn't work yesterday, but I waited 24 hours and now I was able to set up the integration..

RichardKeschinger commented 8 months ago

Yea it's gonna happen everytime you hit that poll limit or whatever

funnymataleao commented 8 months ago

Same issue here. How to fix it?

RichardKeschinger commented 8 months ago

Same issue here. How to fix it?

Govee to MQTT

alanrenouf commented 8 months ago

Same issue here

alanrenouf commented 8 months ago

Same issue here. How to fix it?

Govee to MQTT

Got a good guide?

RichardKeschinger commented 8 months ago

Same issue here. How to fix it?

Govee to MQTT

Got a good guide?

YouTube will help you well

dc7707 commented 8 months ago

FWIWI am getting:

Traceback (most recent call last): File "/config/custom_components/govee/config_flow.py", line 66, in async_step_user user_input = await validate_api_key(self.hass, user_input) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/govee/config_flow.py", line 32, in validate_api_key raise CannotConnect(error) custom_components.govee.config_flow.CannotConnect: API: API-Error 429: {"message":"rate limited! the limit is 10000 requests every 24 hours. X-RateLimit-Reset in Http Response Header shows the reset time."}

The funny thing here is I can fire up a quick python script and make api calls successfully without getting any limit reach or errors at all. Could there be a bug in the validation?

Edit: I suspect the api url changed at some point and they dropped the old one. The one in current documentation is: https://openapi.api.govee.com/router/api In various pieces of the code here it is: https://developer-api.govee.com

Reference: https://developer.govee.com/reference/get-devices-status

I'm unfortunately not familiar enough with the code base here to implement and test a fix myself.

nekrosoft13 commented 7 months ago

Same issue here. How to fix it?

Govee to MQTT

Got a good guide?

YouTube will help you well

any actual guides to follow? instead of youtube?

rhino53150 commented 5 months ago

Same issue here. How to fix it?

Govee to MQTT

Got a good guide?

YouTube will help you well

any actual guides to follow? instead of youtube?

Govee to MQTT is broke also. Will only work if you have Local API available on your devices. The IOT mode doesn't work.

emn83 commented 3 months ago

Today it suddenly doesn't connect, changed API and neither, uninstalled and installed again and nothing

ktiedt commented 2 months ago

Same problem here, have updated everything and reinstalled the Govee integration to no avail

Noack1978 commented 2 months ago

I have the same problem. A new api-key is not accepted

1975felix commented 2 months ago

I have same problem. Request new api but not accepted

Blankf commented 2 months ago

same here, getting 500s now, and new api-key is not accepted