Z-Wave Switch Automation Trouble

Brett_C · April 2, 2018, 7:59pm

Hi all,

I have a handful of GE Z-Wave switches that all work swimmingly, but one that I just installed that is giving me trouble only in automations…? I can control the switch from the Hass UI without issue, but when my automation fires to turn the light on when a door opens, the light never turns on. I turned on Debug in the Z-Wave logs and can see the following. Unfortunately I’m not familiar with this level of Z-Wave to be able to tell what the issue might be. Anyone able to provide any thoughts on what might be the problem?

My switch is node 62, and my door contact sensor is node 61.

2018-04-02 15:46:22.187 Info, Node062, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 -     1 - False
2018-04-02 15:46:22.187 Info, Node062, SwitchBinary::Set - Setting node 62 to Off
2018-04-02 15:46:22.187 Detail, Node062, Queuing (Send) SwitchBinaryCmd_Set (Node=62): 0x01, 0x0a, 0x00, 0x13, 0x3e, 0x03, 0x25, 0x01, 0x00, 0x25, 0x8b, 0x51
2018-04-02 15:46:22.187 Detail, Node062, Queuing (Send) SwitchBinaryCmd_Get (Node=62): 0x01, 0x09, 0x00, 0x13, 0x3e, 0x02, 0x25, 0x02, 0x25, 0x8c, 0x57
2018-04-02 15:46:22.189 Detail,
2018-04-02 15:46:22.189 Info, NONCES: 0xd7, 0x64, 0xc8, 0xcc, 0xe9, 0x32, 0x55, 0xc4
2018-04-02 15:46:22.189 Info, NONCES: 0x47, 0x8d, 0x7a, 0xa0, 0x5d, 0x83, 0xf3, 0xea
2018-04-02 15:46:22.190 Info, NONCES: 0xa3, 0xb7, 0x24, 0x9b, 0x04, 0x3e, 0x23, 0xcd
2018-04-02 15:46:22.190 Info, NONCES: 0x28, 0x66, 0x21, 0x1b, 0xff, 0x37, 0x83, 0xd6
2018-04-02 15:46:22.190 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2018-04-02 15:46:22.191 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2018-04-02 15:46:22.192 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2018-04-02 15:46:22.192 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2018-04-02 15:46:22.192 Info, Node061, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x3d, 0x0a, 0x98, 0x80, 0x28, 0x66, 0x21, 0x1b, 0xff, 0x37, 0x83, 0xd6, 0x05, 0x01, 0x3f:
2018-04-02 15:46:22.192 Error, Node061, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-04-02 15:46:22.192 Detail, Node062, Removing current message
2018-04-02 15:46:22.192 Detail,
2018-04-02 15:46:22.192 Info, Node062, Sending (Send) message (Callback ID=0x8b, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=62): 0x01, 0x0a, 0x00, 0x13, 0x3e, 0x03, 0x25, 0x01, 0x00, 0x25, 0x8b, 0x51
2018-04-02 15:46:22.200 Detail, Node062,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-04-02 15:46:22.200 Detail, Node062,   ZW_SEND_DATA delivered to Z-Wave stack
2018-04-02 15:46:22.200 Detail, Node062, CAN received...triggering resend
2018-04-02 15:46:22.200 Detail,
2018-04-02 15:46:22.200 Info, Node062, Sending (Send) message (Attempt 2, Callback ID=0x8d, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=62): 0x01, 0x0a, 0x00, 0x13, 0x3e, 0x03, 0x25, 0x01, 0x00, 0x25, 0x8d, 0x57
2018-04-02 15:46:22.204 Detail, Node062,   Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2018-04-02 15:46:22.204 Error, Node062, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2018-04-02 15:46:22.251 Detail, Node062,   Received: 0x01, 0x05, 0x00, 0x13, 0x8d, 0x00, 0x64
2018-04-02 15:46:22.251 Detail, Node062,   ZW_SEND_DATA Request with callback ID 0x8d received (expected 0x8d)
2018-04-02 15:46:22.251 Info, Node062, Request RTT 51 Average Request RTT 39
2018-04-02 15:46:22.251 Detail,   Expected callbackId was received
2018-04-02 15:46:22.251 Detail,   Expected reply was received
2018-04-02 15:46:22.251 Detail,   Message transaction complete
2018-04-02 15:46:22.251 Detail,
2018-04-02 15:46:22.251 Detail, Node062, Removing current message
2018-04-02 15:46:22.251 Detail,
2018-04-02 15:46:22.252 Info, Node062, Sending (Send) message (Callback ID=0x8c, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=62): 0x01, 0x09, 0x00, 0x13, 0x3e, 0x02, 0x25, 0x02, 0x25, 0x8c, 0x57
2018-04-02 15:46:22.259 Detail, Node062,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-04-02 15:46:22.259 Detail, Node062,   ZW_SEND_DATA delivered to Z-Wave stack
2018-04-02 15:46:22.280 Detail, Node062,   Received: 0x01, 0x05, 0x00, 0x13, 0x8c, 0x00, 0x65
2018-04-02 15:46:22.280 Detail, Node062,   ZW_SEND_DATA Request with callback ID 0x8c received (expected 0x8c)
2018-04-02 15:46:22.280 Info, Node062, Request RTT 28 Average Request RTT 33
2018-04-02 15:46:22.280 Detail,   Expected callbackId was received
2018-04-02 15:46:22.324 Detail, Node062,   Received: 0x01, 0x05, 0x00, 0x13, 0x8c, 0x00, 0x65
2018-04-02 15:46:22.324 Detail, Node062,   ZW_SEND_DATA Request with callback ID 0x8c received (expected 0x00)
2018-04-02 15:46:22.324 Warning, Node062, WARNING: Unexpected Callback ID received
2018-04-02 15:46:22.430 Detail, Node061,   Received: 0x01, 0x1f, 0x00, 0x04, 0x00, 0x3d, 0x19, 0x98, 0x81, 0x42, 0xc1, 0x12, 0x70, 0x11, 0xff, 0x99, 0x1e, 0xe4, 0x39, 0xce, 0x99, 0x73, 0xe8, 0x28, 0x7e, 0xae, 0xbd, 0x6b, 0xff, 0x70, 0x42, 0x10, 0xb3
2018-04-02 15:46:22.431 Info, Raw: 0x98, 0x81, 0x42, 0xc1, 0x12, 0x70, 0x11, 0xff, 0x99, 0x1e, 0xe4, 0x39, 0xce, 0x99, 0x73, 0xe8, 0x28, 0x7e, 0xae, 0xbd, 0x6b, 0xff, 0x70, 0x42, 0x10, 0xb3
2018-04-02 15:46:22.431 Detail, Node061, Decrypted Packet: 0x00, 0x31, 0x05, 0x01, 0x09, 0x4b
2018-04-02 15:46:22.431 Detail,
2018-04-02 15:46:22.431 Info, Node061, Received SensorMultiLevel report from node 61, instance 1, Temperature: value=75F
2018-04-02 15:46:22.431 Detail, Node061, Initial read of value
2018-04-02 15:46:22.431 Detail, Node061, Notification: ValueChanged
2018-04-02 15:46:32.253 Error, Node062, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-04-02 15:46:32.253 Detail, Node062, Removing current message
2018-04-02 15:46:32.253 Detail, Node062, Notification: Notification - TimeOut

Tinkerer · April 2, 2018, 8:31pm

You’ve got communication problems with nodes 61 and 62. I’d suggest you graph your mesh and see if they’re connected by the same node, and only that node.

Brett_C · April 3, 2018, 1:27pm

Thanks @Tinkerer - I generated the graph and it looks like the two aren’t connected to each other. I’ve associated the two devices in a group and now have the contact sensor turning the light on independent from HA. Haven’t had much trouble with it this route, so not sure where the communication problem might actually be, but something does seem odd.

Tinkerer · April 3, 2018, 7:40pm

That’s overall fairly healthy looking. Whatever your problem is, it’s likely not connectivity in the mesh.

Running a Heal Network might help, or it might make no difference Worth a shot though.