Zooz ZST10 700 Stick repeating messages

Configuration Z-Wave
1

I am having an odd problem with a Zooz ZST10 700 Stick which is seeming repeating messages multiple times. I don’t believe that it is the end devices because it happens somewhat randomly to devices, meaning that it is not the same device each time which has repeating messages.

Here is an example of what I see in the debug tab of zwavejs2mqtt:

2021-05-03 03:32:45.664 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:45.845 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:46.201 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:46.451 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:46.772 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:47.361 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:47.947 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:48.348 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:48.625 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.178 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.239 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.282 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.374 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.403 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.431 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.511 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.588 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.651 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:49.675 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:50.024 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:50.432 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:50.457 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:50.836 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87
2021-05-03 03:32:51.283 INFO ZWAVE: Node 10: value updated: 50-0-value-66049 5.87 => 5.87

This also can happen when I’m switching off a dimmer, note that in this example the message that was repeated many times was the light level is 39. So home assistant saw the light go off, but then the last message received a was duplicate spam of 39, meaning it now thinks the light is back on.


2021-05-03T03:04:55.383Z DRIVER » [Node 009] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ route:            0, 0, 0, 0
                                  │ callback id:      27
                                  └─[SupervisionCCGet]
                                    │ session id:      10
                                    │ request updates: true
                                    └─[MultilevelSwitchCCSet]
                                        target value: 0
2021-05-03T03:04:55.390Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2021-05-03T03:04:55.427Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:     27
                                    transmit status: OK
2021-05-03T03:04:55.530Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[SupervisionCCReport]
                                      session id:          10
                                      more updates follow: false
                                      status:              Success
                                      duration:            [Duration: 0 seconds]
2021-05-03T03:04:55.599Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[SupervisionCCReport]
                                      session id:          10
                                      more updates follow: false
                                      status:              Success
                                      duration:            [Duration: 0 seconds]
2021-05-03T03:04:55.665Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[SupervisionCCReport]
                                      session id:          10
                                      more updates follow: false
                                      status:              Success
                                      duration:            [Duration: 0 seconds]
2021-05-03T03:04:55.738Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 98
2021-05-03T03:04:55.837Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 98
2021-05-03T03:04:55.916Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 98
2021-05-03T03:04:55.974Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 60
2021-05-03T03:04:56.070Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 60
2021-05-03T03:04:56.116Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 50
2021-05-03T03:04:56.211Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 50
2021-05-03T03:04:56.271Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:56.723Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:56.735Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:56.775Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:56.865Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:57.709Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:57.771Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:57.824Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:58.078Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:58.434Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:58.449Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 0
2021-05-03T03:04:58.470Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[MultilevelSwitchCCReport]
                                      current value: 0
2021-05-03T03:04:58.504Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:58.981Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:59.002Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:59.448Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39
2021-05-03T03:04:59.857Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                  └─[BasicCCReport]
                                      current value: 39

Just looking to see if anyone has seen this on a Z-wave network before? Or if there are any suggestions? If I shutdown the server/unplug the stick it starts working fine for awhile, but then eventually will start repeating messages again.

Matt

1 Like
2

I have the exact same issue. Also using the same zwave stick. Have you found a fix?

3

I did not exactly find a solution. But I did reduce the problem a bit. I had a pretty large number of devices on my network, so I split the network in two. I run one stick on a pi in my garage and another stick inside the house on vm server. That seemed to help.

I also went around and updated the firmware of many of my devices. Still see this occasionally but not all the time.

Final thing I did was build Zniffer to monitor the zwave network directly, but didn’t get to far in that.