Hey guys, I’m looking for a smart lock for my front door that can integrate easily into HA. Would you recommend this one? Does it work well and consistently? Our kids are constantly coming in and out of the front door and some nights the door is left unlocked all night by accident. I currently have HA send my phones a notification if the garage doors are open at 10PM to remind me to close them and I’d love to do the same for the front door if it’s unlocked. Can you also view a history log of when the front door is locked and unlocked?
Thanks!
Yes
Yes
Yes
I use this lock works great, as long as you have a zwave USB stick you can do exactly what you’d like with it.
Good day, my first post (or reply) 
First of all, thank you for this forum, its helping me tremendously. I too have a Kwikset smart lock however it model 914 (came with the new house). I install the above configuration yet I’m seeing the following…
if there is any help anyone can give I appreciate it!
Cheers, David
Make today your best-est day ever!
Did you set a network key in your zwave configuration?
Post the first 5 lines of your OZW_Log.txt file.
2019-01-25 09:55:58.402 Always, OpenZwave Version 1.4.3322 Starting Up
2019-01-25 09:55:59.660 Info, Setting Up Provided Network Key for Secure Communications
2019-01-25 09:55:59.661 Warning, Failed - Network Key Not Set
2019-01-25 09:55:59.661 Info, mgr, Added driver for controller /dev/ttyACM0
2019-01-25 09:55:59.662 Info, Opening controller /dev/ttyACM0
Bingo! go figure. This is why forums are so great, people like you!
Now to fix it! I’ll do some research, unless you have your wonderful hints 
Thanks SOOO much!
Cheers, David
Make TODAY your best-est day ever!
I think this is now done via the Configuration -> Integrations menu on the left side of HA now, under Zwave
OR
Check here:
under the “Network Key” section.
Once again, thank you!
Update: I cannot get status from the lock 
I tried to unlock it via Hassio and the log file responds with the additional addition lines:
2019-01-25 15:41:37.287 Info, Node002, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2019-01-25 15:41:37.287 Info, Node002, Value_Lock::Set - Requesting lock to be Locked
2019-01-25 15:41:37.287 Detail, Node002, Queuing (Send) DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x0e, 0x50
2019-01-25 15:41:37.287 Detail, Node002, Queuing (Send) DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x0f, 0xaf
2019-01-25 15:41:37.288 Detail,
2019-01-25 15:41:37.288 Info, Node002, Sending (Send) message (Callback ID=0x0e, Expected Reply=0x04) - DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x0e, 0x50
2019-01-25 15:41:37.296 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-01-25 15:41:37.300 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2019-01-25 15:41:38.574 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x0e, 0x00, 0x00, 0x80, 0x65
2019-01-25 15:41:38.574 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x0e received (expected 0x0e)
2019-01-25 15:41:38.575 Info, Node002, Request RTT 1286 Average Request RTT 1351
2019-01-25 15:41:38.575 Detail, Expected callbackId was received
2019-01-25 15:41:47.289 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-01-25 15:41:47.289 Detail, Node002, Removing current message
2019-01-25 15:41:47.289 Detail, Node002, Notification: Notification - TimeOut
2019-01-25 15:41:47.294 Detail,
2019-01-25 15:41:47.295 Info, Node002, Sending (Send) message (Callback ID=0x0f, Expected Reply=0x04) - DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x0f, 0xaf
2019-01-25 15:41:47.303 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-01-25 15:41:47.303 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2019-01-25 15:41:49.731 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x0f, 0x00, 0x00, 0xf4, 0x10
2019-01-25 15:41:49.731 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x0f received (expected 0x0f)
2019-01-25 15:41:49.731 Info, Node002, Request RTT 2436 Average Request RTT 1893
2019-01-25 15:41:49.731 Detail, Expected callbackId was received
2019-01-25 15:41:57.296 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-01-25 15:41:57.296 Detail, Node002, Removing current message
2019-01-25 15:41:57.296 Detail, Node002, Notification: Notification - TimeOut
Just being curious, if I install a network key, does the lock need to be reconfigured?
Many thanks :}
after adding a network key, you will most likely need to remove/exclude the node, then you absolutely must use the secure include option to add it back into the network. A lock is considered a security device and will only communicate and respond to certain function commands if it is included via secure inclusion.
I DO appreciate ALL your help… however I must seek help once again…
when I ‘lock’ the lock via hassio this is what come in the OZW log
2019-01-25 19:33:38.014 Info, Node002, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2019-01-25 19:33:38.015 Info, Node002, Value_Lock::Set - Requesting lock to be Locked
2019-01-25 19:33:38.015 Detail, Node002, Queuing (Send) DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x11, 0x4f
2019-01-25 19:33:38.015 Detail, Node002, Queuing (Send) DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x12, 0xb2
2019-01-25 19:33:38.015 Detail,
2019-01-25 19:33:38.015 Info, Node002, Sending (Send) message (Callback ID=0x11, Expected Reply=0x04) - DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x11, 0x4f
2019-01-25 19:33:38.024 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-01-25 19:33:38.024 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2019-01-25 19:33:40.438 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x11, 0x00, 0x00, 0xf2, 0x08
2019-01-25 19:33:40.438 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x11 received (expected 0x11)
2019-01-25 19:33:40.438 Info, Node002, Request RTT 2422 Average Request RTT 2596
2019-01-25 19:33:40.438 Detail, Expected callbackId was received
2019-01-25 19:33:48.016 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-01-25 19:33:48.017 Detail, Node002, Removing current message
2019-01-25 19:33:48.017 Detail, Node002, Notification: Notification - TimeOut
2019-01-25 19:33:48.022 Detail,
2019-01-25 19:33:48.022 Info, Node002, Sending (Send) message (Callback ID=0x12, Expected Reply=0x04) - DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x12, 0xb2
2019-01-25 19:33:48.030 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-01-25 19:33:48.030 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2019-01-25 19:33:52.799 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x12, 0x00, 0x01, 0xdd, 0x25
2019-01-25 19:33:52.800 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x12 received (expected 0x12)
2019-01-25 19:33:52.800 Info, Node002, Request RTT 4777 Average Request RTT 3686
2019-01-25 19:33:52.800 Detail, Expected callbackId was received
2019-01-25 19:33:58.023 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-01-25 19:33:58.023 Detail, Node002, Removing current message
2019-01-25 19:33:58.023 Detail, Node002, Notification: Notification - TimeOut
it appears that I am indeed requesting the door to be locked however, timeout?
too puzzling
Thanks, David
Is the lock your only node on the zwave network?
I’m having a similar issue as posted by dadof3and3 - “Entity not available:lock.front_door_lock_locked”
My Network key is setup and working correctly and I am showing battery status, however the lock status is Unknown.
I can lock and unlock it with no problems - any thoughts on what I might have overlooked?
Did you rename your lock to lock.front_door_lock_locked ?
If not go to the <> menu and edit the name:
I copied the code from earlier in this post (Kwikset 912) as a first step into figuring out HA - I’ve got zero experience with linux and or coding, so I may have bitten off more than I can chew.
That said - your pictures pointed out to me that I can change the name of the entities of the node and by default they were something like zwave.kwikset.a.bunch.of.other.things.
So I’m playing around with those. I now have the status fixed but I somehow broke the battery, so working on that. Appreciate the detailed info - it definitely pointed me in the right direction.
FWIW, when you set your Network Key in the configuration.yaml, manually check the options.xml files in the same directory to ensure they’re getting copied there. I still have the issue that it’s not being copied – too far down the list of things to figure out – but don’t trust that if it’s in the YAML, then it’s problem-free. It’s XML -commented out by default, but check that it’s uncommented, and matches your values.
Hi Liwen,
Thanks for this info on disconnecting the zstick, pairing just the stick, then adding through secure_node. Is there any additional details to add? I am very new to this, tried to pair my Kwikset 909 to my Aeotech Z-Stick Gen5 while attached with no luck, so I tried your approach. I plugged the zstick back in while it was flashing yellow, and it stopped, but now HA marks it as unavailable. After a reboot it’s available again… “ADD NODE SECURE” just causes the pair, or did you again set the 909 in pairing mode? Or…
Thanks for any & all info…
Kendall
OK… so manually (button on the Aeotech) excluding the lock (thank you all), resetting the Aeotech (not sure if both of those were needed), and as far as I can tell, the lock added:
2020-06-24 14:32:27.580 Info, Adding node ID 4 - Secure
2020-06-24 14:32:27.580 Detail, Notification: ControllerCommand - InProgress
2020-06-24 14:32:27.892 Detail, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x05, 0x04, 0x00, 0xb9
2020-06-24 14:32:27.892 Detail,
2020-06-24 14:32:27.892 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-06-24 14:32:27.893 Info, ADD_NODE_STATUS_PROTOCOL_DONE
2020-06-24 14:32:27.893 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-06-24 14:32:27.893 Detail, Notification: ControllerCommand - InProgress
2020-06-24 14:32:27.893 Detail,
2020-06-24 14:32:27.893 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-06-24 14:32:27.945 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x06, 0x04, 0x00, 0xba
2020-06-24 14:32:27.946 Detail,
2020-06-24 14:32:27.946 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-06-24 14:32:27.946 Info, contrlr, ADD_NODE_STATUS_DONE
2020-06-24 14:32:27.946 Info, Node004, Basic device class (0x04) - Routing Slave
2020-06-24 14:32:27.946 Info, Node004, Generic device Class (0x40) - Entry Control
2020-06-24 14:32:27.946 Info, Node004, Specific device class (0x03) - Secure Keypad Door Lock
2020-06-24 14:32:27.946 Info, Node004, COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_DOOR_LOCK
2020-06-24 14:32:27.946 Info, Node004, Mandatory Command Classes for Node 4:
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_BASIC
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_DOOR_LOCK
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_USER_CODE
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_MANUFACTURER_SPECIFIC
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_VERSION
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_SECURITY
2020-06-24 14:32:27.947 Info, Node004, Mandatory Command Classes controlled by Node 4:
2020-06-24 14:32:27.947 Info, Node004, None
2020-06-24 14:32:27.947 Detail, Node004, Queuing (Security) SecurityCmd_SchemeGet (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x98, 0x04, 0x00, 0x25, 0x0b, 0x53
2020-06-24 14:32:27.947 Info, Node004, Optional command classes for node 4:
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_SECURITY (Existing)
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_MANUFACTURER_SPECIFIC (Existing)
2020-06-24 14:32:27.947 Info, Node004, COMMAND_CLASS_VERSION (Existing)
2020-06-24 14:32:27.948 Info, Node004, None
2020-06-24 14:32:27.948 Detail, Node004, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2020-06-24 14:32:27.948 Detail, Node004, QueryStage_ProtocolInfo
2020-06-24 14:32:27.948 Detail, Node004, Queuing (Query) Get Node Protocol Info (Node=4): 0x01, 0x04, 0x00, 0x41, 0x04, 0xbe
2020-06-24 14:32:27.948 Detail, Node004, Queuing (Query) Query Stage Complete (ProtocolInfo)
2020-06-24 14:32:27.948 Info, Node004, Initializing Node. New Node: true (true)
my best guess is that the value_template @netopiax mentions must correspond to an existing state and its attributes. I don’t have battery_level or lock_status attributes. I have:
lock.kwikset_spectrum_brands_touchpad_electronic_deadbolt_locked
with attributes
node_id: 4
value_index: 0
value_instance: 1
value_id: 72057594110836736
friendly_name: Back Door Lock
Additionally the add secure node process added two sensor services, but neither have those attributes. I will continue to plod on…
If you have lock.kwikset_spectrum_brands_touchpad_electronic_deadbolt_locked you’re done, don’t mess with it any more 
1 Like
Hi @firstof9, thanks for your reply. I’m messing with it because it does not seem to be configurable. Many of the states/attributes mentioned in this thread do not seem to exist for this state.
But more specifically,
- Asking the device to lock or unlock doesn’t work:
2020-06-24 15:39:31.468 Info, Node004, Value::Set - COMMAND_CLASS_DOOR_LOCK - Lo
cked - 0 - 1 - True
2020-06-24 15:39:31.468 Info, Node004, Value_Lock::Set - Requesting lock to be L
ocked
2020-06-24 15:39:31.469 Detail, Node004, Queuing (Send) DoorLockCmd_Set (Node=4)
: 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x62, 0x01, 0xff, 0x25, 0x0e, 0x56
2020-06-24 15:39:31.469 Detail, Node004, Queuing (Send) DoorLockCmd_Get (Node=4)
: 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x62, 0x02, 0x25, 0x0f, 0xa9
2020-06-24 15:39:31.469 Detail,
2020-06-24 15:39:31.469 Info, Node004, Sending (Send) message (Callback ID=0x0e,
Expected Reply=0x04) - DoorLockCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04,
0x03, 0x62, 0x01, 0xff, 0x25, 0x0e, 0x56
2020-06-24 15:39:31.477 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x0
1, 0xe8
2020-06-24 15:39:31.477 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stac
k
2020-06-24 15:39:32.755 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0x0
e, 0x00, 0x00, 0x80, 0x65
2020-06-24 15:39:32.755 Detail, Node004, ZW_SEND_DATA Request with callback ID
0x0e received (expected 0x0e)
2020-06-24 15:39:32.755 Info, Node004, Request RTT 1286 Average Request RTT 1206
2020-06-24 15:39:32.755 Detail, Expected callbackId was received
2020-06-24 15:39:41.470 Error, Node004, ERROR: Dropping command, expected respon
se not received after 1 attempt(s)
2020-06-24 15:39:41.470 Detail, Node004, Removing current message
2020-06-24 15:39:41.470 Detail, Node004, Notification: Notification - TimeOut
- Going to Configuration->Z-Wave->Z-Wave Node Management, there is apparently no way to set codes for the device. Lower down on the page, there are “Node Configuration Options”, but the primary parameters are 30 "User Code Type"s, rather than just User Codes. So…
Or maybe I’m just not understanding these messages. That very well could be the case. But the device isn’t responding to commands. That much is clear.
How many nodes do you have?
1 Like
If you are unable to lock/unlock the device from HA, then the lock is either not paired through the add secure node process, or your network key is not set or malformed. You should not try and pair the lock manually with the stick disconnected. You should only pair it through the Zwave configuration page in HA.
1 Like