Update: So I unpaired the deadbolt. Not sure if I did it properly though. I then repaired the deadbolt through the Dashboard and the lock now works through hassio. Looks like you do need to remove the spaces in the network key.
So I’ve been slowly assembling everything into my hassio for the first time ever. I have my caseta lights, sonos and thermostat setup now. I received my HUSBZB today and got it setup in hass.io. I then made my own z wave network key, leaving spaces between the numbers (0x01, 0x10, etc.) I then paired my deadbolt and it shows up in the dashboard but when I select it to lock it goes back to unlock after a couple of seconds. I then read you need to remove the spaces which I did. then restarted hass.io but nothing changes.
Here’s some logs.
config.yaml
zwave:
usb_path: /dev/ttyUSB0
network_key: “0x01,0x06,0x11,0x07,0x07,0x02,0x11,0x08,0x08,0x05,0x04,0x06,0x11,0x10,0x02,0x01”
new_entity_ids: true
zha:
usb_path: /dev/ttyUSB1
database_path: /config/zigbee.db
(I edited the network key for this post but kept the same format)
Here’s the options ozw log
2017-12-14 17:50:18.716 Info, Node002, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2017-12-14 17:50:18.717 Info, Node002, Value_Lock::Set - Requesting lock to be Locked
2017-12-14 17:50:18.717 Detail, Node002, Queuing (Send) DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x14, 0x4a
2017-12-14 17:50:18.717 Detail, Node002, Queuing (Send) DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x15, 0xb5
2017-12-14 17:50:18.717 Detail,
2017-12-14 17:50:18.717 Info, Node002, Sending (Send) message (Callback ID=0x14, Expected Reply=0x04) - DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x14, 0x4a
2017-12-14 17:50:18.724 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-14 17:50:18.724 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2017-12-14 17:50:19.996 Detail, Node002, Received: 0x01, 0x05, 0x00, 0x13, 0x14, 0x00, 0xfd
2017-12-14 17:50:19.996 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x14 received (expected 0x14)
2017-12-14 17:50:19.996 Info, Node002, Request RTT 1278 Average Request RTT 1271
2017-12-14 17:50:19.996 Detail, Expected callbackId was received
2017-12-14 17:50:28.718 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-14 17:50:28.718 Detail, Node002, Removing current message
2017-12-14 17:50:28.719 Detail, Node002, Notification: Notification - TimeOut
2017-12-14 17:50:28.722 Detail,
2017-12-14 17:50:28.723 Info, Node002, Sending (Send) message (Callback ID=0x15, Expected Reply=0x04) - DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x15, 0xb5
2017-12-14 17:50:28.729 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-14 17:50:28.729 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2017-12-14 17:50:29.956 Detail, Node002, Received: 0x01, 0x05, 0x00, 0x13, 0x15, 0x00, 0xfc
2017-12-14 17:50:29.956 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x15 received (expected 0x15)
2017-12-14 17:50:29.956 Info, Node002, Request RTT 1233 Average Request RTT 1252
2017-12-14 17:50:29.956 Detail, Expected callbackId was received
2017-12-14 17:50:38.724 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-14 17:50:38.724 Detail, Node002, Removing current message
2017-12-14 17:50:38.724 Detail, Node002, Notification: Notification - TimeOut
Do I need to remove then repair the deadbolt for this to work or is there something else I’m missing?
Thanks,
Travis