As a z-wave beginner, I would appreciate much the help from anyone to improve performace.
The network works well and generally responds inmediatly, but once in a while some nodes won’t respond or take a few seconds to respond. I believe this is due to network traffic and evidence might be the log file (shown below). How can I fix this? I thought it was polling, but I do not have any configuration for de devices, so polling should be disabled.
Here is my z-wave config:
zwave:
usb_path: /dev/ttyACM0
network_key: "0x1d, ..."
polling_interval: 60000
debug: true
I have a 30 node network, they are all wired in wall switches:
- Controller: AEON Labs ZW090 Z-Stick Gen5 US
- Light switch: AEON Labs ZW139 Nano Switch (13 nodes)
- Light switch: AEON Labs ZW132 Dual Nano Switch (3 nodes)
- Light switch: AEON Labs ZW116 Nano Switch (5 nodes)
- Light switch: Vision Security ZL7431 In-Wall Switch Single Relay (8 nodes)
And the log is constantly showing messages sent from all nodes, any time I enter the log I will see something like this from different nodes:
2019-04-18 13:41:13.470 Info, Node019, Sending (Send) message (Callback ID=0xaf, Expected Reply=0x04) - ClockCmd_Get (Node=19): 0x01, 0x09, 0x00, 0x13, 0x13, 0x02, 0x81, 0x05, 0x25, 0xaf, 0xfa
2019-04-18 13:41:13.477 Detail, Node019, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-04-18 13:41:13.477 Detail, Node019, ZW_SEND_DATA delivered to Z-Wave stack
2019-04-18 13:41:13.617 Detail, Node019, Received: 0x01, 0x07, 0x00, 0x13, 0xaf, 0x00, 0x00, 0x0f, 0x4b
2019-04-18 13:41:13.618 Detail, Node019, ZW_SEND_DATA Request with callback ID 0xaf received (expected 0xaf)
2019-04-18 13:41:13.618 Info, Node019, Request RTT 148 Average Request RTT 152
2019-04-18 13:41:13.618 Detail, Expected callbackId was received
2019-04-18 13:41:13.741 Detail, Node019, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x13, 0x04, 0x81, 0x06, 0x11, 0x2d, 0x5d
2019-04-18 13:41:13.741 Detail,
2019-04-18 13:41:13.741 Info, Node019, Response RTT 271 Average Response RTT 282
2019-04-18 13:41:13.741 Info, Node019, Received Clock report: Invalid 17:45
2019-04-18 13:41:13.741 Detail, Node019, Refreshed Value: old value=17, new value=17, type=byte
2019-04-18 13:41:13.741 Detail, Node019, Changes to this value are not verified
2019-04-18 13:41:13.742 Detail, Node019, Refreshed Value: old value=43, new value=45, type=byte
2019-04-18 13:41:13.742 Detail, Node019, Changes to this value are not verified
2019-04-18 13:41:13.742 Detail, Node019, Expected reply and command class was received
2019-04-18 13:41:13.742 Detail, Node019, Message transaction complete
2019-04-18 13:41:13.742 Detail,
2019-04-18 13:41:13.742 Detail, Node019, Removing current message
2019-04-18 13:41:13.742 Detail, Node019, Notification: ValueChanged
2019-04-18 13:41:13.770 Warning, Exception: Manager.cpp:2499 - 102 - ValueID passed to GetValueFloatPrecision is not a Decimal Value
2019-04-18 13:41:13.770 Warning, Exception: Manager.cpp:2499 - 102 - ValueID passed to GetValueFloatPrecision is not a Decimal Value
2019-04-18 13:41:13.793 Detail, Node019, Notification: ValueChanged
2019-04-18 13:41:13.810 Warning, Exception: Manager.cpp:2499 - 102 - ValueID passed to GetValueFloatPrecision is not a Decimal Value
2019-04-18 13:41:13.810 Warning, Exception: Manager.cpp:2499 - 102 - ValueID passed to GetValueFloatPrecision is not a Decimal Value