Wenzhou TZ37 causing long delays

Willew · April 22, 2018, 6:00pm

I have Zwave.me USB stick and now the first zwave switch (TKB TZ37, double relay wall switch) in the test bed. If everything works fine, I will start to replace my legacy switches with these.

When I turn on the switch in Hass, the desired relay is turned on. If I immediately after this turn on the 2nd relay in the switch from Hass, this will happen only after few seconds. In the log I can see a timeout message exactly after 10 seconds after the first message. The 2nd command is sent only after the first one has timed out. But I cannot identify what is the request getting no response.

With one switch this is not a major problem but I am afraid this will cause problems if I have 10-15 switches. Any ideas?

2018-04-22 20:43:15.232 Info, Node005, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 3 - True
2018-04-22 20:43:15.232 Info, Node005, SwitchBinary::Set - Setting node 5 to On
2018-04-22 20:43:15.232 Detail, Node005, Queuing (Send) MultiChannel Encapsulated (instance=3): SwitchBinaryCmd_Set (Node=5): 0x01, 0x0e, 0x00, 0x13, 0x05, 0x07, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x01, 0xff, 0x25, 0x23, 0x53
2018-04-22 20:43:15.233 Detail, Node005, Queuing (Send) MultiChannel Encapsulated (instance=3): SwitchBinaryCmd_Get (Node=5): 0x01, 0x0d, 0x00, 0x13, 0x05, 0x06, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x02, 0x25, 0x24, 0xaa
2018-04-22 20:43:15.233 Detail,
2018-04-22 20:43:15.233 Info, Node005, Sending (Send) message (Callback ID=0x23, Expected Reply=0x13) - MultiChannel Encapsulated (instance=3): SwitchBinaryCmd_Set (Node=5): 0x01, 0x0e, 0x00, 0x13, 0x05, 0x07, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x01, 0xff, 0x25, 0x23, 0x53
2018-04-22 20:43:15.242 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-04-22 20:43:15.242 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2018-04-22 20:43:15.258 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x23, 0x00, 0x00, 0x02, 0xca
2018-04-22 20:43:15.259 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x23 received (expected 0x23)
2018-04-22 20:43:15.260 Info, Node005, Request RTT 26 Average Request RTT 38
2018-04-22 20:43:15.260 Detail,   Expected callbackId was received
2018-04-22 20:43:15.260 Detail,   Expected reply was received
2018-04-22 20:43:15.260 Detail,   Message transaction complete
2018-04-22 20:43:15.260 Detail,
2018-04-22 20:43:15.260 Detail, Node005, Removing current message
2018-04-22 20:43:15.260 Detail,
2018-04-22 20:43:15.260 Info, Node005, Sending (Send) message (Callback ID=0x24, Expected Reply=0x04) - MultiChannel Encapsulated (instance=3): SwitchBinaryCmd_Get (Node=5): 0x01, 0x0d, 0x00, 0x13, 0x05, 0x06, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x02, 0x25, 0x24, 0xaa
2018-04-22 20:43:15.276 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-04-22 20:43:15.276 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2018-04-22 20:43:15.280 Detail, Node005,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x20, 0x03, 0xff, 0x28
2018-04-22 20:43:15.294 Detail,
2018-04-22 20:43:15.294 Info, Node005, Response RTT 33 Average Response RTT 55
2018-04-22 20:43:15.294 Info, Node005, Received Basic report from node 5: level=255
2018-04-22 20:43:15.295 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x25, 0xc5
2018-04-22 20:43:15.340 Detail, Node005,   Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x05, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x03, 0xff, 0x40
2018-04-22 20:43:15.342 Detail,
2018-04-22 20:43:15.342 Info, Node005, Response RTT 81 Average Response RTT 68
2018-04-22 20:43:15.342 Info, Node005, Received a MultiChannelEncap from node 5, endpoint 1 for Command Class COMMAND_CLASS_SWITCH_BINARY
2018-04-22 20:43:15.342 Info, Node005, Received SwitchBinary report from node 5: level=On
2018-04-22 20:43:15.342 Detail, Node005, Refreshed Value: old value=true, new value=true, type=bool
2018-04-22 20:43:15.342 Detail, Node005, Changes to this value are not verified
2018-04-22 20:43:15.343 Detail, Node005, Notification: ValueChanged
2018-04-22 20:43:15.363 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x24, 0x00, 0x00, 0x09, 0xc6
2018-04-22 20:43:15.364 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x24 received (expected 0x24)
2018-04-22 20:43:15.364 Info, Node005, Request RTT 103 Average Request RTT 70
2018-04-22 20:43:15.364 Detail,   Expected callbackId was received
2018-04-22 20:43:15.371 Detail, Node005,   Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x05, 0x07, 0x60, 0x0d, 0x02, 0x02, 0x25, 0x03, 0xff, 0x40
2018-04-22 20:43:15.372 Detail,
2018-04-22 20:43:15.372 Info, Node005, Response RTT 111 Average Response RTT 89
2018-04-22 20:43:15.372 Info, Node005, Received a MultiChannelEncap from node 5, endpoint 2 for Command Class COMMAND_CLASS_SWITCH_BINARY
2018-04-22 20:43:15.372 Info, Node005, Received SwitchBinary report from node 5: level=On
2018-04-22 20:43:15.372 Detail, Node005, Refreshed Value: old value=false, new value=true, type=bool
2018-04-22 20:43:15.372 Detail, Node005, Changes to this value are not verified
2018-04-22 20:43:15.373 Detail, Node005,   Expected reply and command class was received
2018-04-22 20:43:15.373 Detail, Node005,   Message transaction complete
2018-04-22 20:43:15.373 Detail,
2018-04-22 20:43:15.373 Detail, Node005, Removing current message
2018-04-22 20:43:15.373 Detail, Node005, Notification: ValueChanged
2018-04-22 20:43:15.401 Detail,
2018-04-22 20:43:15.401 Info, Node005, Sending (Send) message (Callback ID=0x25, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x25, 0xc5
2018-04-22 20:43:15.409 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-04-22 20:43:15.416 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2018-04-22 20:43:15.426 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x25, 0x00, 0x00, 0x02, 0xcc
2018-04-22 20:43:15.426 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x25 received (expected 0x25)
2018-04-22 20:43:15.426 Info, Node005, Request RTT 24 Average Request RTT 47
2018-04-22 20:43:15.426 Detail,   Expected callbackId was received
2018-04-22 20:43:25.403 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-04-22 20:43:25.403 Detail, Node005, Removing current message
2018-04-22 20:43:25.403 Detail, Node005, Notification: Notification - TimeOut

Willew · April 23, 2018, 5:16pm

After some analysis looks like Wenzhou devices do not support requesting the status for a switch (SwitchBinaryCmd_Get), evidence being openzwave log analyzer and this post. Still would like to find a solution, anyone?

blinkenlight · April 23, 2018, 6:27pm

I’m not really sure what to make of this: on the one hand, I have definitely seen devices that were capable of sending or accepting BASIC_SET commands but not willing to reply to queries of the same; on the other hand, that’s the only command class I’ve seen this sort of thing with, with any device implementing a SWITCH_BINARY class I would expect it to reply as well. Then again, It could just happen the TZ37 really won’t do that. If that’s the case, I’m not sure if there is a solution at all, although you might want to try “cutomizing” your switch state to “assumed_state = true” (see https://www.home-assistant.io/docs/configuration/customizing-devices/). I have no idea whether that is an UI-only thing or will actually prevent any attempts to send GET queries on a z-wave level…

Willew · April 24, 2018, 7:28pm

Tried and did not help.

Based on the other post this problem seems to be a feature in Wenzhou switches.

Others having Wenzhou switches without this problem?
I have not found any other switches with relays having CE certificate, are there (event having neutral required)?