-
Notifications
You must be signed in to change notification settings - Fork 52
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
403 error when trying to add integration #222
Comments
Having the same here - very occasionally will see a sensor display - same errors as above |
same for me |
Same here. Even increasing the interval to 90s does not help. I have registered two accounts. |
Hi same problem for me.
|
I’ve had the integration working for a long time, but am now seeing 403 error too. |
Me too. Here are the logs I’ve got.
|
Related to issues mitch-dc#211, mitch-dc#215 and mitch-dc#222 insofar as reducing the polling frequency reportedly avoids WeConnect API errors (e.g. 403, 429) when the servers are busy (API call rate limiting / throttling).
Same here. Lots of 403 errors since yesterday, and trying to set up the integration from scratch didn't help either:
|
Version of the custom_component
v0.1.8
Installation method (hacs / manual)
HACS
Installation method of hass (venv, docker, hassio,...)
docker
Configuration
N/A, added via integration
Describe the bug
When trying to add the integration, it takes a couple of minutes and the logs subsequently show a 403 error. All added entities are "unavailable" and lots of them are missing (SoC etc).
I do also have the Cupra WeConnect integration installed for my other half's car, not sure if that's conflicting?
I have tried removing the integration, reinstalling it, restarting HA (also between removing and reinstalling) but to no avail. Anyone else have any idea how to fix this?
Debug log
The text was updated successfully, but these errors were encountered: