Ok, that was it. Once I managed to properly remove the node, and re-add it with the network key in place everything is working properly!
It also shows more entities for that node (not sure what they do, but I’m also not sure if I care as simply seeing and controlling the lock/unlock state was all I really needed)
One of the other entities probably shows you how the Lock was locked/unlocked. On my Zwave Lock (though not an August), one entity shows locked/unlocked by Zwave, locker/unlocked manually, Jammed, etc.
August pushed another firmware update this week, so I un/re-paired the lock with HA. I’m not seeing any obvious differences in functionality and they don’t publish their changes. If you’re not a hub manufacturer, you have to repeatedly pester their support team if you want to know.
Out of the five entities that are added, only these two appear to do anything.
- lock.[lock_name]_locked
- sensor.[lock_name]_access_control
Last I heard from August, they don’t officially support the other three and they don’t appear to contain data.
What’s the current best way to pair the August Lock Pro (w/ August Connect) with Home Assistant?
I see there seems to be a Wink and a ZWAVE method.
If you have a Wink Hub, you can pair the August to it over Zwave. And then link Wink to HA. That method will work but will have a delay.
If you have a Zwave USB stick, use that and link the August to HA directly. Will be much quicker but you won’t get a few features that still need to be implemented in OpenZwave (though I’m not sure the degree to which Wink has these implemented either - one is DoorSense).
I don’t have either, just the August Lock Pro and August Connect.
Ok, then I think you can pair the lock to Wink with no wink Hub as long as the connect is set up. Set up the August lock, install the Wink app on your phone, then add the lock through the Wink app, it will link your accounts.
Then add Wink to HA and it will pull the lock in. You will notice a significant delay between a command in HA and the lock reacting.
You can use the Wink method, with, or without an actual Wink Hub. All you need is a Wink developer account. That method requires the August Connect and it unlocks the August Smart Lock by sending a signal over the Internet to Wink. Wink in turn sends a signal to your August Connect and the August Connect unlocks the August Smart Lock. I tried it out and it’s every bit as slow as using the August Connect from the August app.
If you have a Smart Lock Pro, I recommend buying a z-wave stick and going that route instead. It’s fast and it doesn’t require use of the Internet. Which is good, should your Internet connection go down, your automations will still work.
I have tried to add my August lock to my HA Hassio but no luck, maybe someone know what can be the issue?
Raspi with HA 0.62.1
Aeotec z-stick Gen5
August Smart Lock Pro Gen3
I push the “Add Secure Node” and then I use the August app to try to pair it and then this is written to the log:
2018-02-05 10:56:45.355 Detail, Queuing (Controller) Add Device
2018-02-05 10:56:45.355 Info, Add Device
2018-02-05 10:56:45.355 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x19, 0x68
2018-02-05 10:56:45.356 Detail, Notification: ControllerCommand - Starting
2018-02-05 10:56:45.356 Detail,
2018-02-05 10:56:45.357 Info, contrlr, Sending (Command) message (Callback ID=0x19, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x19, 0x68
2018-02-05 10:56:45.361 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x19, 0x01, 0x00, 0x00, 0xaa
2018-02-05 10:56:45.361 Detail,
2018-02-05 10:56:45.361 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-02-05 10:56:45.361 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2018-02-05 10:56:45.361 Detail, Node001, Expected callbackId was received
2018-02-05 10:56:45.361 Detail, Node001, Expected reply was received
2018-02-05 10:56:45.361 Detail, Node001, Message transaction complete
2018-02-05 10:56:45.361 Detail,
2018-02-05 10:56:45.361 Detail, contrlr, Removing current message
2018-02-05 10:56:45.361 Detail, Notification: ControllerCommand - Waiting
2018-02-05 10:57:21.371 Detail, Node004, Received: 0x01, 0x0c, 0x00, 0x04, 0x10, 0x04, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x44, 0xb3
2018-02-05 10:57:21.371 Detail,
2018-02-05 10:57:21.371 Info, Node004, Received SensorMultiLevel report from node 4, instance 1, Power: value=6.8W
2018-02-05 10:57:21.371 Detail, Node004, Refreshed Value: old value=6.9, new value=6.8, type=decimal
2018-02-05 10:57:21.371 Detail, Node004, Changes to this value are not verified
2018-02-05 10:57:21.372 Detail, Node004, Notification: ValueChanged
I have followed the https://home-assistant.io/docs/z-wave/adding/ and put in a Network Key. I found this https://aeotec.freshdesk.com/support/solutions/articles/6000096809-cannot-add-include-a-device-to-z-stick-gen5-troubleshooting- and as I order the August Lock from US and have a Aeotec z-stick from EU maybe this can be the issue? I have tried a lot of things and search the interweb but no luck 
Please help me out
and as I order the August Lock from US and have a Aeotec z-stick from EU maybe this can be the issue?
This is likely the issue. Zwave uses different frequencies in North America and Europe, they are not compatible. If you have a US lock and an EU controller, they will not be able to talk to each other.
I cannot find what version there is on the August lock so I cannot be sure about this. Could I run dual Aeotec z-stick in a HA Hassio installation?
I have added the basic August Lock information to ozw. If anyone knows how to set up DoorSense and other features in the ozw config, please share and I’d be happy to add that too.
Might be worth reaching out to August Support, or the Project Manager. Maybe they’d be willing to help now that there’s active development going towards integrating their product. As of November 2017, the Project Manager’s name was Susie (susie[at]august[dot]com).
Ok, I seem to be stuck again.
I upgraded homeassistant (I know, I should know better, but I just can’t help myself!) and I can’t get the lock to work anymore. Symptoms are the same as when I first installed it. lock appears in home assistant, but does not show the state correctly, and can’t be controlled.
Last time this was due to a missing network key in my yaml file, but that key is there now, I also removed the lock and re-paired it, and am still at the same place.
OZW_Log.txt from when I try to unlock the door:
2018-06-22 09:22:03.814 Info, Node029, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2018-06-22 09:22:03.814 Info, Node029, Value_Lock::Set - Requesting lock to be Unlocked
2018-06-22 09:22:03.814 Detail, Node029, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-22 09:22:03.815 Detail, Node029, Queuing (Send) DoorLockCmd_Set (Node=29): 0x01, 0x0a, 0x00, 0x13, 0x1d, 0x03, 0x62, 0x01, 0x00, 0x25, 0xa9, 0x17
2018-06-22 09:22:03.815 Detail, Node029, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-22 09:22:03.815 Detail, Node029, Queuing (Send) DoorLockCmd_Get (Node=29): 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x62, 0x02, 0x25, 0xaa, 0x15
2018-06-22 09:22:03.817 Info, Node029, Processing (Send) Nonce Request message (Callback ID=0xa9, Expected Reply=0x04)
2018-06-22 09:22:03.817 Info, Node029, Sending (Send) message (Callback ID=0xa9, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-06-22 09:22:03.825 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:03.826 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:05.118 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x98, 0x80, 0x7e, 0x38, 0x25, 0xe7, 0x96, 0x03, 0x06, 0x43, 0xb0
2018-06-22 09:22:05.118 Info, Node029, Received SecurityCmd_NonceReport from node 29
2018-06-22 09:22:05.118 Info, Node029, Sending (Send) message (Callback ID=0xab, Expected Reply=0x04) - DoorLockCmd_Set (Node=29): 0x01, 0x0a, 0x00, 0x13, 0x1d, 0x03, 0x62, 0x01, 0x00, 0x25, 0xab, 0x15
2018-06-22 09:22:05.130 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:05.130 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:06.304 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x98, 0x80, 0x30, 0x4c, 0x64, 0xe0, 0x47, 0x44, 0xb5, 0xd5, 0x7f
2018-06-22 09:22:06.305 Info, Node029, Received SecurityCmd_NonceReport from node 29
2018-06-22 09:22:06.305 Info, Node029, Sending (Send) message (Callback ID=0xac, Expected Reply=0x04) - DoorLockCmd_Set (Node=29): 0x01, 0x0a, 0x00, 0x13, 0x1d, 0x03, 0x62, 0x01, 0x00, 0x25, 0xac, 0x12
2018-06-22 09:22:06.309 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2018-06-22 09:22:06.309 Error, Node029, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2018-06-22 09:22:07.421 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xac, 0x00, 0x00, 0x6f, 0x28
2018-06-22 09:22:07.421 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xac received (expected 0xac)
2018-06-22 09:22:07.422 Info, Node029, Request RTT 3604 Average Request RTT 2512
2018-06-22 09:22:07.446 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xac, 0x00, 0x00, 0x72, 0x35
2018-06-22 09:22:07.446 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xac received (expected 0x00)
2018-06-22 09:22:07.446 Warning, Node029, WARNING: Unexpected Callback ID received
2018-06-22 09:22:07.483 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x98, 0x80, 0xcf, 0x8c, 0xa2, 0x34, 0x4b, 0x68, 0xa1, 0xc0, 0x73
2018-06-22 09:22:07.483 Info, Node029, Received SecurityCmd_NonceReport from node 29
2018-06-22 09:22:07.483 Info, Node029, Sending (Send) message (Callback ID=0xad, Expected Reply=0x04) - DoorLockCmd_Set (Node=29): 0x01, 0x0a, 0x00, 0x13, 0x1d, 0x03, 0x62, 0x01, 0x00, 0x25, 0xad, 0x13
2018-06-22 09:22:07.494 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:07.495 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:08.867 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xad, 0x00, 0x00, 0x8a, 0xcc
2018-06-22 09:22:08.868 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xad received (expected 0xad)
2018-06-22 09:22:08.868 Info, Node029, Request RTT 5049 Average Request RTT 3780
2018-06-22 09:22:13.819 Error, Node029, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-22 09:22:13.819 Detail, Node029, Removing current message
2018-06-22 09:22:13.819 Detail, Node029, Notification: Notification - TimeOut
2018-06-22 09:22:13.829 Info, Node029, Processing (Send) Nonce Request message (Callback ID=0xaa, Expected Reply=0x04)
2018-06-22 09:22:13.829 Info, Node029, Sending (Send) message (Callback ID=0xaa, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-06-22 09:22:13.837 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:13.837 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:16.307 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x98, 0x80, 0x7e, 0x70, 0xe3, 0xc5, 0x77, 0x14, 0x0a, 0xe1, 0x44
2018-06-22 09:22:16.308 Info, Node029, Received SecurityCmd_NonceReport from node 29
2018-06-22 09:22:16.308 Info, Node029, Sending (Send) message (Callback ID=0xae, Expected Reply=0x04) - DoorLockCmd_Get (Node=29): 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x62, 0x02, 0x25, 0xae, 0x11
2018-06-22 09:22:16.318 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:16.318 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:17.450 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xae, 0x00, 0x00, 0x72, 0x37
2018-06-22 09:22:17.450 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xae received (expected 0xae)
2018-06-22 09:22:17.451 Info, Node029, Request RTT 3622 Average Request RTT 3701
2018-06-22 09:22:17.474 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xae, 0x00, 0x00, 0x74, 0x31
2018-06-22 09:22:17.474 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xae received (expected 0x00)
2018-06-22 09:22:17.475 Warning, Node029, WARNING: Unexpected Callback ID received
2018-06-22 09:22:17.494 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x98, 0x80, 0xbe, 0x97, 0xbe, 0x37, 0x7d, 0x58, 0x66, 0xa8, 0xaf
2018-06-22 09:22:17.494 Info, Node029, Received SecurityCmd_NonceReport from node 29
2018-06-22 09:22:17.495 Info, Node029, Sending (Send) message (Callback ID=0xaf, Expected Reply=0x04) - DoorLockCmd_Get (Node=29): 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x62, 0x02, 0x25, 0xaf, 0x10
2018-06-22 09:22:17.506 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:17.507 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:17.517 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x98, 0x80, 0x24, 0xb4, 0xb0, 0xc8, 0x1f, 0x7e, 0xec, 0xa5, 0x24
2018-06-22 09:22:17.517 Info, Node029, Received SecurityCmd_NonceReport from node 29
2018-06-22 09:22:17.517 Info, Node029, Sending (Send) message (Callback ID=0xb0, Expected Reply=0x04) - DoorLockCmd_Get (Node=29): 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x62, 0x02, 0x25, 0xb0, 0x0f
2018-06-22 09:22:17.528 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-22 09:22:17.528 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2018-06-22 09:22:18.861 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xb0, 0x00, 0x00, 0x86, 0xdd
2018-06-22 09:22:18.861 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xb0 received (expected 0xb0)
2018-06-22 09:22:18.862 Info, Node029, Request RTT 5032 Average Request RTT 4366
2018-06-22 09:22:18.885 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0xb0, 0x00, 0x00, 0x89, 0xd2
2018-06-22 09:22:18.885 Detail, Node029, ZW_SEND_DATA Request with callback ID 0xb0 received (expected 0x00)
2018-06-22 09:22:18.885 Warning, Node029, WARNING: Unexpected Callback ID received
2018-06-22 09:22:23.830 Error, Node029, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-22 09:22:23.830 Detail, Node029, Removing current message
2018-06-22 09:22:23.830 Detail, Node029, Notification: Notification - TimeOut
It looks to me like there’s 2 way communication, it’s just not actually doing anything useful.
does anybody got the doorsense working using z-wave?? i mean sense when the door is ajar?
I haven’t gotten it to work. I’m not sure if it requires a non-generic OpenZwave configuration, or if August isn’t even transmitting that data over zwave.
There’s a SmartThings DTH available that implements the DoorSense functionality, so it does get sent over ZWave - apparently as part of the Door Lock Operation Report.
Hello, I own a Kwikset 910 Z-Wave Deadbolt (https://www.amazon.com/dp/B013KZRTTG/ref=twister_B017JUFBXO?_encoding=UTF8&psc=1) and had it connected to my Smartthings system working just fine. When I connected it to my Home Assistant system and clicked on ‘Lock’ it, the lock span backwards (I mean, it was unlocked and it span in the same unlock direction), I immediately remove the battery and connected back to my Smartthings system.
The problem is that when this happened, I tried to manually lock/unlock the doorlock and it becomes a little hard, like the gears are stuck in some point, I am able to lock/unlock but using some force. When I try to lock/unlock from my Smartthings app, the motor becomes crazy and stuck.
I am aware that my issues begun with a software problem, now I just want to know if there is a solution to my deadbolt so it could go back to normal. I would appreciate some help.
I was wondering if someone has any experience with z-wave smart locks, I just made my kwikset 910 spin backwards
I use to had a Smartthings system and the lock working fine with it, once I migrate to Home Assistant using Hass, I was able to pair my lock through a Zstick gen5. The problem started when I tried to lock it. At first, when I pressed the ‘Lock’ button, nothing happened, after a rebot, being unlocked, I clicked on the ‘Lock’ button and the lock tried to spin the other way (like in the unlocked way) and it kept doing this repeatedly, I had to remove the battery from the doorlock to make it stop.
In the ‘config.yaml’, I just add this:
zwave:
usb_path: /dev/ttyACM0
network_key: “0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10”
any idea… thanks
The lock trying to turn the wrong way is an issue with the lock itself. Basically by default it’s set up for a door that swings one way, and if you have it on a door that swings the other way it doesn’t know. To fix, remove the battery pack, hold down the lock button on the outside of the door, insert the battery pack, and wait. If it makes a bunch of noise and then extends and retracts the bolt properly, you’re done.
I am having the same exact problem, similar logs. I’m pretty sure it paired securely after adding the network_key. I got a warning in the August app that the security was not S2 and not as good, which I didn’t get before I had the network_key.
Anyone have new ideas?