Zaptec polling intervals #202
Description
To reduce the polling foot-print on Zaptec cloud, there is a need to implement context dependent poll-intervals.
This is the current proposal based on conversation with Zaptec. See #176 (comment)
| State | Endpoints (GET) |
Poll interval |
|---|---|---|
| Chargers: Charging | chargers/{id}/state |
60 second |
| Chargers: Disconnected/idle | chargers/{id}/state |
10 minute |
| Chargers: Info | charger/{id} |
60 minute |
| Installation: Info | installation/{id} |
10 minute |
| Firmware updates | chargerFirmware/installation/{id} |
1 day |
| Structure | installation, installation/{id}/hierarchy |
|
| Charger commands | chargers/{id}/state |
2, 7, 15 seconds (1) |
| Installation commands | installation/{id} |
2, 7 seconds (2) |
- (1) "Commands" are any action from HA that results in
POSTorPUTsent to Zaptec. This will happen only once. The resulting sequence of polling at intervals is usingGETstate to ensure the local data is updated sufficiently fast for UX and are able to handle latencies on the cloud side. The exact delay values can be fine tuned later. - (2) Installations doesn't have state, so the only end-point to use for polling is `installation/{id}´