Closed Tockerz closed 3 years ago
@Tockerz couple of questions:
How long from when you make the change does it show unavailable? I'm expecting this to be about 5 seconds.
Which system do you have (MyAir 5, e-zone, e10zone)?
I have updated the problem - yes about 5-10 seconds is normal but sometimes longer. I am using standard eZone.
So the python library only tries 6 times with 1 second between each try, which means your system is taking longer than 5 seconds to make the change. I will raise a PR to either increase the number of retries, or use a linear back off so that it doesn't show unavailable for 15 seconds
One more test you can do for me to ensure we get this fixed. Make a change using the e-zone app, then repetitively hit ipaddress:2025/getSystemData with your browser and time how long it takes from making the change until it shows more than "{}"
One more test you can do for me to ensure we get this fixed. Make a change using the e-zone app, then repetitively hit ipaddress:2025/getSystemData with your browser and time how long it takes from making the change until it shows more than "{}"
Yeah 5-7 seconds to return data after sending a change.
advantage_air documentation advantage_air source (message by IssueLinks)
The problem
When inputing Advantage Air integration power, mode, temp, or covers change, the integration goes temporarily "N/A" or "unavailable" and reconnects after 5 - 20 seconds. ## EnvironmentProblem-relevant
configuration.yaml
Traceback/Error logs
Additional information