Closed simonetolomelli closed 10 months ago
Fixed in v0.4.0
I've installed v0.5.0 and it seems that this bug is happening again
[03/01/2024, 20:07:17] [AirZone] Error in getDeviceStatus. Error [03/01/2024, 20:07:17] [AirZone] [Fetch] Error calling to AirzoneCloud. Status: 429 Too Many Requests [03/01/2024, 20:07:17] [AirZone] Error in getDeviceStatus. Error [03/01/2024, 20:07:21] [AirZone] [Fetch] Error calling to AirzoneCloud. Status: 429 Too Many Requests [03/01/2024, 20:07:21] [AirZone] Error in getDeviceStatus. Error [03/01/2024, 20:07:21] [AirZone] [Fetch] Error calling to AirzoneCloud. Status: 429 Too Many Requests [03/01/2024, 20:07:21] [AirZone] Error in getDeviceStatus. Error [03/01/2024, 20:07:21] [AirZone] [Fetch] Error calling to AirzoneCloud. Status: 429 Too Many Requests [03/01/2024, 20:07:21] [AirZone] Error in getDeviceStatus. Error [03/01/2024, 20:07:22] [AirZone] [Fetch] Error calling to AirzoneCloud. Status: 429 Too Many Requests [03/01/2024, 20:07:22] [AirZone] Error in getDeviceStatus. Error
Same here
Same for me with v0.5.0
Fixed in v0.4.0
Looks like it is not. Could be depending on the recent (and mandatory) AZC firmware update?
Same for me with v0.5.0
Same for me with plugin v0.5.0 [1/28/2024, 9:31:27 PM] [AirzoneCloud] [Fetch] Error calling to AirzoneCloud. Status: 429 Too Many Requests [1/28/2024, 9:31:27 PM] [AirzoneCloud] Error in getDeviceStatus. Error
The plugin makes too many requests per second for each thermostat I have installed in every room. To the point that AirZone Cloud API service locked me out for quite sometime this morning which was very disruptive for the apartment heating.
see the attached log.