-
Notifications
You must be signed in to change notification settings - Fork 23
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
Integration doesn't work for too long #112
Comments
And yes, after poking a bit, if i reload home assistant, it says that the integration isn't working and i need to relogin again with the credentials. So something is a miss with the usage of refresh token? 🤔 |
Well we have the refresh token to get new access token, but the integration isnt fetching it. |
Try the beta version 1.2.2. I have changed how to save the updated token in that release. I can promote it to a non-beta if it works better. |
Same issue with 1.2.2 |
I've have the same issue, updated to 1.2.2 now and will know tomorrow if it works for me 🤞 |
I just release 1.2.3 as a public version. Try it out and let me know how it works! |
Still a problem here. Can provide logs later. |
I'm on the 1.2.2 beta and it didn't disconnect the same way as before, I've got new data coming in over 12 hours later. |
1.2.2 failed after 2 days. 429 = Too many requests |
Yes. Same problem for me. |
Same here. On 1.2.3. I am seeing log error related to exceptions for FanEntityFeature.TURN_OFF 'FanEntityFeature' has no attribute 'TURN_OFF' |
Error 429 can be avoided by increasing the update interval. It can be changed by configuring the integration. Please add logs with the FanEntityFeature not found. |
Adding the section, removed some API info (keys and ID's),
|
What version of Home Assistant are you running? The feature should be available since a while back |
Core Supervisor Operating System Frontend I'll try updating to latest. The reason its a little old is because we saw docker issues after the core updates in 2024.7. |
Seems to be working again after update to 2024.8 core. Thanks! |
The flag was added in this PR home-assistant/core#121447 which was included in HA 2024.08 If it's an issue to upgrade, I can remove it and disable the backward compatibility flag mentioned in the PR. But I rather go forward than backwards 😊 |
Nah, I'm happy as the core update didn't break anything but for the future maybe don't expect users to patch every month 😉 |
Hello, I've got the same problems as @olanystrom and @andrecunha-sb. Is there any workaround for this? |
See my message here #112 (comment) In the next update I will force the interval to be higher by default |
Thank you for the information. I wasn't aware that you're going to apply this globally. |
300s instead of 30 works great for my 4 devices. |
@andrebcunha Thank you, I'll check that out. |
60s seems to work here! |
There is a limit of 5000 API calls per day, so technically we should be able to set the rate to 18s |
I think the integration has problems with the refresh token handling stuff. If i add the integration, everything works fine, and then about 12h later it breaks and i get this error:
The text was updated successfully, but these errors were encountered: