Repository navigation
How Data Updates
The integration holds one WebSocket connection to the charger and subscribes to property changes. Nothing is polled.
The charger can push the same property many times a second, and every push writes entity state and a recorder row. Update interval (Settings → Devices & Services → Fronius Wattpilot → Configure, default 5 seconds) caps that to at most one update per entity per interval; 0 forwards every change immediately. It is not a polling interval.
Availability is never delayed by it: a recovery is signalled with the first push after the charger's readings are in, together with those readings.
When the connection drops and is still down at the next check (every 30 seconds), every entity goes unavailable, the drop is logged once, and the client reconnects on its own, at growing intervals of up to five minutes. Entities come back as soon as the charger has sent its current readings. A reconnect between two checks goes unnoticed. No restart is needed.
Changing a switch, number, select, button or time writes the property to the charger and waits for the charger to acknowledge it. A write the charger refuses or does not answer is reported as an error instead of looking successful. The one exception is Restart charger: the charger reboots without answering, so nothing is waited for.