-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
PATCH calls to AC Infinity API cause subsiquent requests to API to fail or timeout for a period of time. #39
Comments
I deleted the entire integration and then re-downloaded it and installed it but I'm still getting the same error message. I have the update set to 30 seconds and when I change modes there's a long pause and then the mode changes and then the error message appears or the error message appears and then the mode changes. |
The same error is happening when I try to change other things besides the mode such as ON SPEED and OFF SPEED. I haven't tested everything but so far it seems to be happening with everything I try to change. |
looks like your requests to the API are timing out. I've noticed during development that the occasional request to the API would time out after an update operation, so I threw in some retry logic. As I can see from the logs, it attempts to make the call 3 times before giving up. Not sure why its happening more frequently for you... but that's the dangers of using a non-public API I guess :( It's essentially a black box, so how to "properly" call it has to be reverse engineered and any errors that occur are essentially invisible. I'll convert this into a bug to investigate why patch (update) calls to the API cause it to hang on subsequent calls. One thing you can try is remove and re-add your Controller 69 from the AC Infinity app. See if that doesn't clear any bad data on their end that may be causing issues. |
I'll try that to see what happens. And I don't know if it matters but the App itself is lagging when changing modes and settings. I get an error that says to try again at a later time but then the error clears and the change goes through. |
@dalinicus deleting the device from the app and the integration and adding it back worked. I'm no longer getting the error. Thanks. |
I am having the same issue - when it stops responding, if I control it from the AC Infinity app.. it will start to work again after a reload.. but it keeps happening… I will try to delete it from the app and re-add it |
Would you mind providing what device modes your using, and what settings your frequently changing? It would help me debug; I can throw a traffic spy on my phone and see if the app is sending values that the integration is missing. Some of them (like temperature in auto mode) requires multiple values be to changed for it to work properly, and I could have missed it. |
@dalinicus I am mainly updating the 'mode' (on or off) and the 'on fan speed' from HA. See also #47 |
Nothing really new to add, just to say i'm also getting this. For me, it's the changing of the fan on power value that does it. It still seems to update in the log when i change the speed in the app. However, this last time I've not been changing any settings for the last week or so & its still started to do it. Like zpriddy above, the app itself seems to play up when this is happening & removing & adding it seems to sort it. It seems like it could be AC app issue? there's plenty of posts about problems with it elsewhere. Also thanks for making this integration, really makes it easier to manage everything |
@bert-the-dog it might be an AC app issue. It occasionally happens to me too. I can't really narrow it down to what exactly it is. AC should be coming out with a new version of the app sometime soon because the current version of the app doesn't handle all of the features of the new fan. And FYI if you have an old fan they'll swap it out for the new version which has some major improvements. |
When changing modes I started having the following error message appear at the bottom of the screen...
This is what the log says...
The text was updated successfully, but these errors were encountered: