Check the status of the zwave. entity in the states menu (<>) under Developer Tools. It should show Sleeping, others have reported it never changes from Ready which would cause the battery to die quickly.
Have you tried upgrading the firmware? It solved the battery drain problem for me.
Talked to support and will get new batteries. Great service.
I have updated firmware and hope that fixes everything
Anyone except Stian that got the danalock v3 work with home assistant?
Im still struggling…
Can’t add the node here either. Upgraded to latest firmware, replaced batteries. Pulled in latest config from open-zwave and ran HA with config_path set to that directory, which should enable HA to detect it. Nothing, I don’t even get a generic lock node.
I managed to pair the lock, with all the right metadata from the open-zwave config, by following this:
Earlier I was trying to pair it using the iOS app’s zwave pair feature, but now I pressed the hw button on the actual lock, that seemed to be the key to getting it working. I can lock and unlock the lock. Let’s see how stable it is now 
You don’t have to set config_path. Set the HA config option for the key and it works without any problems.
For me it works since I got the dana v3.
No ozwcp and no app!
I remembered one more thing I struggled with. As described elsewhere, for secure z-wave devices, a good direct connection with the controller is necessary. One of my successful attempts was with the UZB in a RPI just right to the lock. With my server, however, I could not connect at first, with the UZB stick directly connected to the case (in a different room).
Then I tried connecting the UZB with an USB extension cable to get some distance from the metal case of the server, and it seemed to do the trick.
After reading this blog - thanks to all contributors - I had no problem to add my Danalock V3 to my homeassistant (v 0.59.2) after the following two tasks
-
adding doorlockv3.xml to the folder lib/python3/site-packages/python_openzwave/ozw_config/polycontrol/
-
calibrating the Danalock V3, either automatically or manually as described in Danalock_Anleitung_V3_BTZE.pdf (in German) (show above in the post by torarnv for the english translation)
I am also having issues adding my Danalock V3 to the Z-Wave network (Aeotec Gen 5 USB Stick). I tried all suggestions from in here, but it seems that it is not correctly recognized and therefor some generic lock settings are used (the zwave commands being sent are not valid).
How does your guys “Show Information” look ?
lastRequestRTT: 1346
receivedCnt: 4
neighbors: 1
capabilities: frequent,routing,beaming
new_entity_id: zwave._
is_failed: false
max_baud_rate: 40000
manufacturer_name:
sentTS: 2018-01-13 18:38:51:312
node_id: 3
receivedUnsolicited: 0
product_name:
averageRequestRTT: 1300
old_entity_id: zwave.__3
is_awake: true
receivedDups: 0
lastResponseRTT: 1419
node_name:
sentCnt: 42
is_ready: true
query_stage: Complete
retries: 0
averageResponseRTT: 917
sentFailed: 0
is_zwave_plus: true
is_info_received: true
battery_level: 100
receivedTS: 2018-01-13 17:42:20:766
friendly_name:
Inside zwcfg_0xcfe94b52.xml: https://gist.github.com/tynor88/27a769d89e4dcc115364e0dcf4e51e1f
Some logs when trying to send commands:
2018-01-13 18:38:41.307 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2018-01-13 18:38:41.307 Info, Node003, Value_Lock::Set - Requesting lock to be Locked
2018-01-13 18:38:41.307 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-01-13 18:38:41.307 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0xff, 0x25, 0x4d, 0x12
2018-01-13 18:38:41.307 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-01-13 18:38:41.307 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x4e, 0xef
2018-01-13 18:38:41.308 Detail,
2018-01-13 18:38:41.308 Info, Node003, Processing (Send) Nonce Request message (Callback ID=0x4d, Expected Reply=0x04)
2018-01-13 18:38:41.308 Info, Node003, Sending (Send) message (Callback ID=0x4d, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-01-13 18:38:41.317 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-01-13 18:38:41.317 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2018-01-13 18:38:42.465 Detail, Node003, Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x73, 0x9a
2018-01-13 18:38:42.465 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-01-13 18:38:42.465 Info, Node003, Request RTT 1157 Average Request RTT 1234
2018-01-13 18:38:42.486 Detail, Node003, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x03, 0x0a, 0x98, 0x80, 0x2d, 0x05, 0xca, 0x8e, 0x44, 0x56, 0x89, 0xb4, 0xb9
2018-01-13 18:38:42.486 Info, Node003, Received SecurityCmd_NonceReport from node 3
2018-01-13 18:38:42.487 Info, Node003, Sending (Send) message (Callback ID=0x4f, Expected Reply=0x04) - DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0xff, 0x25, 0x4f, 0x10
2018-01-13 18:38:42.498 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-01-13 18:38:42.498 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2018-01-13 18:38:42.522 Detail, Node003, Received: 0x01, 0x07, 0x00, 0x13, 0x4f, 0x00, 0x00, 0x03, 0xa7
2018-01-13 18:38:42.522 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x4f received (expected 0x4f)
2018-01-13 18:38:42.522 Info, Node003, Request RTT 1213 Average Request RTT 1223
2018-01-13 18:38:42.522 Detail, Expected callbackId was received
2018-01-13 18:38:51.309 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-01-13 18:38:51.309 Detail, Node003, Removing current message
2018-01-13 18:38:51.310 Detail, Node003, Notification: Notification - TimeOut
2018-01-13 18:38:51.312 Detail,
2018-01-13 18:38:51.312 Info, Node003, Processing (Send) Nonce Request message (Callback ID=0x4e, Expected Reply=0x04)
2018-01-13 18:38:51.312 Info, Node003, Sending (Send) message (Callback ID=0x4e, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-01-13 18:38:51.319 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-01-13 18:38:51.319 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
Any suggestions? Perhaps @nklever or @stiansoevik ? Seems you guys have it working
Hi,
I had problems to get my Danalock V3 and Z-Stick Gen 5 to work.
To get the stick to work i added this to the configuration.yaml:
Z-Wave
zwave:
usb_path: /dev/ttyACM0
network_key: “From: https://home-assistant.io/docs/z-wave/installation/”
config_path: /srv/homeassistant/lib/python3.5/site-packages/python_openzwave/ozw_config
With that the controller was finally correct added to home-assistant.
I still didn’t get the lock to work though.
I restarted my raspberry by that runs hassbian.
I removed a node from within home-assistant (configuration / zwave) during this I tailed the OZW_Log.txt. To remove the log I entered the smart home / z-wave in the phone app. I waited for the log to not logging anything and that took a couple of minutes. If you don’t have the possibility to tail the log then just wait five minutes for this stage to finish.
I then added a secure node the same way. At least five minutes wait here to.
After this the lock was added but it did not show correct status and if I tailed the OZW log nothing happened…
From the phone app i then tested for firmware update and there was a new firmaware version 0.8.0. I updated to that version and without any modifications the lock was working!
I get correct status and I am able to lock / unlock from within home-assistant 0.61.0
I can also confirm that firmware version 0.8.0 fixed my problems. Now everything works. Lock/unlock battery status etc.
1 Like
Hi
I’m not able to pair my Danalock V3 BTZE with Home Assistant in secure mode or standard mode.
I have a Aeotec Z-Stick Gen 5 which I know works, because I have 10 Heatit thermostats and a Neo CoolCAM door sensor connected to it. The door sensor is connected in secure mode.
My Home Assistant version is 0.67, installed on a debian stretch minipc.
My config file:
zwave:
usb_path: /dev/ttyACM0
network_key: I have a network key generated from “cat /dev/urandom | tr -dc ‘0-9A-F’ | fold -w 32 | head -n 1 | sed -e ‘s/(…)/0x\1, /g’”
config_path: /srv/homeassistant/lib/python3.5/site-packages/python_openzwave/ozw_config
I have confirmed there is a doorlockv3.xml file in /srv/homeassistant/lib/python3/site-packages/python_openzwave/ozw_config/polycontrol/
I have the latest firmware on the Danalock.
Please advise
Do you have a zwave device that not only use batteries?
I needed to add a fibaro wall plug for it to work.
Sorry, but I forgot to mention that I took the Danalock from the door and put it 0.5 meter from the controller when pairing.
I also have a Heatit thermostat approx. 1 meter from the door, so range shouldn’t be a problem.
Finally it showed up in HA. I have tried adding it many times.
There is a new firmware out: 0.8.2. You can’t use automatic update, I tried on my android device, you have to use manual update on a iphone or ipad. https://danalock.com/manual-upgrade.html
I think it makes Danalock more responsive, but that’s just my first impression.
So, i’m a bit confused by the last comments in this thread.
Is the Danalock working now in HA and without the battery drain issue?
Thanks.
yes its working without the battery drain issue
Is it showing up as Ready or Sleeping for you? It stays on Ready and is awake = true for me. Updated firmware through the iOS app and reincluded it on the latest version of hass (0.71).