Is there a way I can see/monitor the ZWave messages that are going across the network while HA is running? I know I can do so when I start the OZWCP, but I need to see while HA is running.
With the latest update, I am unable to change temps on my thermostat (though I can change the mode from Heat to Cool) and I am unable to unlock/lock my doors. I thought it might be a network key issue, but I am not seeing any errors relating to that when I am in OZWCP.
in the side menu of HA, select configuration > z wave then scroll down and refresh the ozw log. It’s the same log that ozwcp has.
Ahhh, yeah. I forgot about that. Though, I was hoping to be able to narrow it down to the tail end of the log, what you suggested will work. Thank you.
Okay, so my original assessment was completely incorrect, it does appear to be a network key issue:
2017-11-04 20:10:22.852 Always, OpenZwave Version 1.4.2586 Starting Up
2017-11-04 20:10:47.169 Info, Setting Up Provided Network Key for Secure Communications
2017-11-04 20:10:47.169 Warning, Failed - Network Key Not Set
2017-11-04 20:10:47.169 Info, mgr, Added driver for controller /dev/ZStick
2017-11-04 20:10:47.169 Info, Opening controller /dev/ZStick
2017-11-04 20:10:47.169 Info, Trying to open serial port /dev/ZStick (attempt 1)
2017-11-04 20:10:47.170 Info, Serial port /dev/ZStick opened (attempt 1)
The options.xml file does have the network key set. Is there any remedy to this without having to go through and exclude and re-include the locks to the Aeotec controller? It appears to be affecting the thermostat as well because it will not allow me to change the temp from within HA, though it was never added as a secure device. With the controller not seeing a network key set, I understand the locks not working as they should, but the thermostat is a little mysterious.
Anyway, are there any suggestions, or is there anything I can do?
I got the network key issue resolved, I think:
2017-11-05 01:48:07.522 Always, OpenZwave Version 1.4.2586 Starting Up
2017-11-05 01:48:29.766 Info, Setting Up Provided Network Key for Secure Communications
2017-11-05 01:48:29.767 Info, mgr, Added driver for controller /dev/ZStick
2017-11-05 01:48:29.767 Info, Opening controller /dev/ZStick
2017-11-05 01:48:29.767 Info, Trying to open serial port /dev/ZStick (attempt 1)
2017-11-05 01:48:29.767 Info, Serial port /dev/ZStick opened (attempt 1)
2017-11-05 01:48:29.767 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-11-05 01:48:29.767 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-11-05 01:48:29.767 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-11-05 01:48:29.767 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-11-05 01:48:29.767 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
However, my thermostat is still not responding to changes in temp., and my door lock is still not responding to unlock commands:
2017-11-05 02:03:24.136 Info, Node082, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2017-11-05 02:03:24.136 Info, Node082, Value_Lock::Set - Requesting lock to be Unlocked
2017-11-05 02:03:24.136 Detail, Node082, Queuing (Send) DoorLockCmd_Set (Node=82): 0x01, 0x0a, 0x00, 0x13, 0x52, 0x03, 0x62, 0x01, 0x00, 0x25, 0x1b, 0xea
2017-11-05 02:03:24.136 Detail, Node082, Queuing (Send) DoorLockCmd_Get (Node=82): 0x01, 0x09, 0x00, 0x13, 0x52, 0x02, 0x62, 0x02, 0x25, 0x1c, 0xec
2017-11-05 02:03:24.136 Detail,
2017-11-05 02:03:24.136 Info, Node082, Sending (Send) message (Callback ID=0x1b, Expected Reply=0x04) - DoorLockCmd_Set (Node=82): 0x01, 0x0a, 0x00, 0x13, 0x52, 0x03, 0x62, 0x01, 0x00, 0x25, 0x1b, 0xea
2017-11-05 02:03:24.142 Detail, Node082, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-11-05 02:03:24.142 Detail, Node082, ZW_SEND_DATA delivered to Z-Wave stack
2017-11-05 02:03:25.282 Detail, Node082, Received: 0x01, 0x07, 0x00, 0x13, 0x1b, 0x00, 0x00, 0x72, 0x82
2017-11-05 02:03:25.282 Detail, Node082, ZW_SEND_DATA Request with callback ID 0x1b received (expected 0x1b)
2017-11-05 02:03:25.282 Info, Node082, Request RTT 1146 Average Request RTT 1194
2017-11-05 02:03:25.282 Detail, Expected callbackId was received
I am not entirely sure what to look at next, so any suggestions are greatly welcome.
If you didn’t already find it, the network key is set in configuration.yaml now.
However, once setting it, you’ll need to remove any devices that support Secure, and then re-include them with Add Node Secure.
Ironically, I had the key set there. However, upon seeing this issue I moved it back to the options.xml file just in case there was an issue there of some kind.
I just can’t figure out or understand WHY the network key all of a sudden became an issue. I have now moved it back to the configuration.yaml. I was not getting any notices that it had failed to set up the network key once I got the options.xml file set up properly and copied into the HA config directory nor am I now with it in the configuration.yaml file. Though, I really wish I could figure out what happened. I put those locks in HA as soon as they were supported and have not had any issues until now.
Thank you @Tinkerer for your help. Much appreciated.
I have excluded then re-included my door locks and thermostat. The door locks are responding again, however, the thermostat is not. I can try and change the temp from within HA and it does nothing yet I can change the temp. at the thermostat and it updates in HA.
When I restart HA, it looks like it is communicating just fine with the thermostat but when I try to change the temp. setpoint, I see no messages sent to the thermostat.
2017-11-06 07:10:55.294 Info, Node103, Sending (Query) message (Callback ID=0xbb, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=103): 0x01, 0x0a, 0x00, 0x13, 0x67, 0x03, 0x43, 0x02, 0x01, 0x25, 0xbb, 0x5c
2017-11-06 07:10:55.299 Detail, Node103, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-11-06 07:10:55.299 Detail, Node103, ZW_SEND_DATA delivered to Z-Wave stack
2017-11-06 07:10:55.381 Detail, Node103, Received: 0x01, 0x07, 0x00, 0x13, 0xbb, 0x00, 0x00, 0x08, 0x58
2017-11-06 07:10:55.381 Detail, Node103, ZW_SEND_DATA Request with callback ID 0xbb received (expected 0xbb)
2017-11-06 07:10:55.381 Info, Node103, Request RTT 86 Average Request RTT 1271
2017-11-06 07:10:55.381 Detail, Expected callbackId was received
2017-11-06 07:10:55.390 Detail, Node103, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x67, 0x05, 0x43, 0x03, 0x01, 0x09, 0x48, 0x92
2017-11-06 07:10:55.390 Detail,
2017-11-06 07:10:55.390 Info, Node103, Response RTT 96 Average Response RTT 95
2017-11-06 07:10:55.390 Detail, Node103, Initial read of value
2017-11-06 07:10:55.391 Info, Node103, Received thermostat setpoint report: Setpoint Heating 1 = 72F
2017-11-06 07:10:55.391 Detail, Node103, Expected reply and command class was received
2017-11-06 07:10:55.391 Detail, Node103, Message transaction complete
2017-11-06 07:10:55.391 Detail,
2017-11-06 07:10:55.391 Detail, Node103, Removing current message
2017-11-06 07:10:55.391 Detail, Node103, Notification: ValueChanged
2017-11-06 07:10:55.396 Detail,
2017-11-06 07:10:55.396 Info, Node103, Sending (Query) message (Callback ID=0xbc, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=103): 0x01, 0x0a, 0x00, 0x13, 0x67, 0x03, 0x43, 0x02, 0x02, 0x25, 0xbc, 0x58
2017-11-06 07:10:55.400 Detail, Node103, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-11-06 07:10:55.400 Detail, Node103, ZW_SEND_DATA delivered to Z-Wave stack
2017-11-06 07:10:55.416 Detail, Node103, Received: 0x01, 0x07, 0x00, 0x13, 0xbc, 0x00, 0x00, 0x02, 0x55
2017-11-06 07:10:55.416 Detail, Node103, ZW_SEND_DATA Request with callback ID 0xbc received (expected 0xbc)
2017-11-06 07:10:55.417 Info, Node103, Request RTT 20 Average Request RTT 645
2017-11-06 07:10:55.417 Detail, Expected callbackId was received
2017-11-06 07:10:55.426 Detail, Node103, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x67, 0x05, 0x43, 0x03, 0x02, 0x09, 0x4f, 0x96
2017-11-06 07:10:55.426 Detail,
2017-11-06 07:10:55.426 Info, Node103, Response RTT 29 Average Response RTT 62
2017-11-06 07:10:55.426 Detail, Node103, Initial read of value
2017-11-06 07:10:55.426 Info, Node103, Received thermostat setpoint report: Setpoint Cooling 1 = 79F
2017-11-06 07:10:55.426 Detail, Node103, Expected reply and command class was received
2017-11-06 07:10:55.426 Detail, Node103, Message transaction complete