I have a reasonably large (~100 node) ZWave network, mainly comprising dimmers, mains switches and USB-powered Aeotec MultiSensor 6 units:
On occasion the sensors fail to report a motion start or finish event. This creates a practical issue as these motion events control automatic lighting.
I have configured all devices to minimise unnecessary communications, such as only sending values as needed, setting unsolicited reporting intervals to low values (eg hourly) etc.
All ZWave things are configured for 86,400 second polling, as I do not need openHAB to poll them. Despite this, the debug log shows 84 unique devices over the past hour were polled a total of 227 times. While thatās only an average of one poll every 15 seconds, unfortunately the polling tends to concentrate. For example here we see 17 devices seemingly polled in the same second (these are window controllers):
2022-05-22 16:03:32.689 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 76: Polling...
2022-05-22 16:03:32.709 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 75: Polling...
2022-05-22 16:03:32.715 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 66: Polling...
2022-05-22 16:03:32.722 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 67: Polling...
2022-05-22 16:03:32.734 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Polling...
2022-05-22 16:03:32.743 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 47: Polling...
2022-05-22 16:03:32.748 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 72: Polling...
2022-05-22 16:03:32.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 122: Polling...
2022-05-22 16:03:32.761 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 71: Polling...
2022-05-22 16:03:32.766 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Polling...
2022-05-22 16:03:32.790 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 74: Polling...
2022-05-22 16:03:32.791 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 57: Polling...
2022-05-22 16:03:32.794 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 78: Polling...
2022-05-22 16:03:32.794 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 73: Polling...
2022-05-22 16:03:32.797 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Polling...
2022-05-22 16:03:32.807 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 69: Polling...
2022-05-22 16:03:32.815 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 68: Polling...
More generally a 60 minute log when nothing is really happening in the house shows 2,065 ZWave receive events (grep "payload" openhab.log|grep Received|wc -l
). That is one event every 1.74 seconds.
Any suggestions? It would appear preferable that polling happens as configured in the thing (ie 86,400 seconds, not 1,800), and polling has a network-wide rate limit (eg no more often than once every 5 - 10 seconds) so that devices wishing to send data have a reasonable chance to do so. Or is this really the responsibility of the MultiSensors to queue up their motion events and deliver it when they can, even if the network is flooded for a prolonged period? Or should I just split the ZWave network into 3 different zones (I had it configured this way in the past, but merged it into one to reduce failure modes)? Or donāt worry about it and solve it with software (eg make bigger lighting zones and require consensus of a few sensors to determine a zoneās likely presence state)?