This is a concern, not a compliment.
I've been using z-wave for well over a decade and although i class myself as no expert have learnt enough to get an efficient system running.
This week i installed my first zigbee device and assume its similar in many ways to z-wave.
The device is a battery operated radiator TRV. This is running in my HE alongside 20 z-wave devices.
My understanding is that (based on my z-wave knowledge) sending updates to this device works on a polling system. However, when i issue a setpoint change the device receives and executes this command immediately, which is great but i fear this "live" communication will be at the expense of the battery life. I have the polling set to 30min intervals so would expect the device to only update as such.
Is this normal or acceptable? thanks
Z-wave battery devices generally fall into two groups. Sensors, which only wake on an interval (usually 12 hours) to take configurations, they send sensor readings at any time as configured. Or FLIRS devices which can accept commands and wake every 60 seconds. The only "polling" done with zwave is typically for older non-plus mains powered devices AFAIK.
Zigbee battery devices are different, I am not sure how they work exactly but the few sensors I have seem to be always awake, I can send them configurations or refresh and they respond fairly quick. Not sure if there is a difference in Zigbee sensors vs devices that take commands like your TRV controller.
Here is better info on Zigbee devices: Discussion about battery-powered z-wave/zigbee devices - #21 by hubitrep
The ZIgbee battery-powered TRV's are actuators, they listen for incoming Zigbee commands. To save the battery, their radio is turned off most of the time, but the firmware is made to turn it on periodically, typically once for a short time period every second.
Many Zigbee blinds controllers and Zigbee locks have a similar battery-saving behaviour, that's why these devices do not react to the open/close commands immediately, but after some delay.
No, the TRV instantly sends updates to the hub when an attribute changes (the measured temperature as an example).
The TRV automatically reports back the heating setpoint to the hub immediately after accepting the command. There is no need for additional 'poll' commands.
This is a custom driver feature, that you can turn off
As stated in the preference description, one possible reason for the polling could be to produce a better looking graphs :
It may be a good idea this polling option to default to 'disabled', typically it is not needed.
This one of yours?
