My Danalock v3 Z-Wave Configuration 5. Step Solution

AlmostSerious · June 7, 2019, 9:04am

Seems to me that you are using the wrong quotes. Try to copy and paste this one: "

Robba · June 7, 2019, 3:18pm

Thank you! Now it finally works!

bernfort · July 29, 2019, 7:47pm

I can’t get this to work… I don’t seem to get the latest firmware and when I get it up HA it says “unknown Polycontrole” instead of “Polycontrole Danalock V3 BTZE”

DariBer · August 1, 2019, 9:56pm

My Danalock v3 works now in HA, the only thing that I find annoying is that it’s so slow to report the status back to HA.

If I lock/unlock in HA, it’s fast to lock/unlock, but it’s slow to report back and change status from locked to unlocked and from unlocked to locked. Does anyone else have this issue?

Domoticon · September 1, 2019, 1:16pm

I tried all of the above, without success. I even tried other Z-wave controllers, but with no success. Seems to me the Danalock itself is the problem.

Has anyone got it working with a Danalock V3, firmware version 0.11.0 (latest)?

Al3xand3R360 · September 5, 2019, 4:23pm

Mine is working with firmware 0.11.0. Although I have to say I’ve upgraded my Danalock V3 firmware after it was successfully included in HA.
Did you upgrade firmware before including in HA?

Domoticon · September 5, 2019, 8:39pm

I upgraded first before including.

fribse · September 6, 2019, 11:43am

Hi @Domoticon
Yes, I have it working, and my lock was upgraded quite a while back.
I had to do a complete reset of the lock (mine was unresponsive, so it had to send it to Danalock for that, but they did it free of charge).
Then I enrolled it in the Danalock App, and got that working.
In the HA, the Z-Wave stick from aeotec was autodiscovered, so that was set up with an autogenerated secure key.
I then activated Z-wave pairing from HA, and from the lock via the app, and it was discovered right away.
Final step was to send the ‘lock.get_usercode’.

Then it worked, and have worked since then, it has been running for quite a few months now.
I do have the z-wave stick quite close to the lock (a few meters), so I don’t know about the range.

fribse · September 6, 2019, 5:04pm

actually now that I look at the history of the firmwares, it might have been installed pre-0.11 So I might not be of any help.

RayBomb87 · October 13, 2019, 8:24am

Thanx for this thread. I was able to get my two locks working.
However, one on my locks won’t do the twist assist anymore. I’m unsure if this had to do with the HA integration, or if the lock itself is faulty.
Anyone else had this problem?

KKlitgaard · October 13, 2019, 9:08am

I had the same issue. Appeared a couple big weeks ago. I did a full Z-wave exclusion and reset on the device followed by a new secure inclusion. Now twist assist works again.

For reference I update to the latest HA on a monthly basis at least.

RayBomb87 · October 13, 2019, 9:39am

I just fixed the twist assist problem.
This is what I did:

Activated “remove node” in HA config zwave
In Danalock app I set the device in inclusion mode.
Did a “heal’ in HA
Removed the device in Danalock app
Added the device again in Danalock app
Turned off twist assist in app
Changed the calibration doing a manual calibration and saved a new unlocked position and a new locked position.
Reactivated the twist assist

Now it started to work again

I suspect I didn’t have to do step 1 to 5. So if I where you I would first try step 6,7 and 8

Of course you would need to again do a correct calibration for the lock positions after you get the twist assist working again…

Good luck!

Who_Carez · October 17, 2019, 1:11am

Dear all,

I have been trying this for weeks now.
With Hass, Hassbian, HASS.IO

I have Aeotec Z Stick Gen5, and it sees the DANALOCK, however, when sending LOCK or UNLOCK I am getting TIMED out.
At this moment the raspberry pi 3 plus Z stick is about a meter (3 ft) from the lock.
When trying to lock/unlock i am getting following in log:

2019-10-16 19:06:59.636 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2019-10-16 19:06:59.636 Info, Node003, Value_Lock::Set - Requesting lock to be Unlocked
2019-10-16 19:06:59.636 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x49, 0xe9
2019-10-16 19:06:59.636 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x4a, 0xeb
2019-10-16 19:07:06.043 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2019-10-16 19:07:06.044 Info, Node003, Value_Lock::Set - Requesting lock to be Locked
2019-10-16 19:07:06.044 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0xff, 0x25, 0x4b, 0x14
2019-10-16 19:07:06.044 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x4c, 0xed

Before I used to get timeouts.
I used the mentioned 5 steps several times.

Who_Carez · October 18, 2019, 12:27am

Hi all,

ok tried AGAIN
Removed everything again and did the 5 steps. And now I am getting the timeouts.

UNLOCK

2019-10-17 18:08:25.113 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2019-10-17 18:08:25.114 Info, Node003, Value_Lock::Set - Requesting lock to be Unlocked
2019-10-17 18:08:25.114 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x7b, 0xdb
2019-10-17 18:08:25.114 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x7c, 0xdd
2019-10-17 18:08:25.114 Detail,
2019-10-17 18:08:25.114 Info, Node003, Sending (Send) message (Callback ID=0x7b, Expected Reply=0x04) - DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x7b, 0xdb
2019-10-17 18:08:25.123 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-10-17 18:08:25.124 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2019-10-17 18:08:26.374 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x7b, 0x00, 0x00, 0x7d, 0xed
2019-10-17 18:08:26.374 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x7b received (expected 0x7b)
2019-10-17 18:08:26.374 Info, Node003, Request RTT 1259 Average Request RTT 1279
2019-10-17 18:08:26.374 Detail,   Expected callbackId was received
2019-10-17 18:08:35.115 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 18:08:35.116 Detail, Node003, Removing current message
2019-10-17 18:08:35.116 Detail, Node003, Notification: Notification - TimeOut
2019-10-17 18:08:35.120 Detail,
2019-10-17 18:08:35.120 Info, Node003, Sending (Send) message (Callback ID=0x7c, Expected Reply=0x04) - DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x7c, 0xdd
2019-10-17 18:08:35.128 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-10-17 18:08:35.129 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2019-10-17 18:08:36.378 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x7c, 0x00, 0x00, 0x7e, 0xe9
2019-10-17 18:08:36.378 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x7c received (expected 0x7c)
2019-10-17 18:08:36.379 Info, Node003, Request RTT 1258 Average Request RTT 1268
2019-10-17 18:08:36.379 Detail,   Expected callbackId was received
2019-10-17 18:08:45.121 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 18:08:45.121 Detail, Node003, Removing current message
2019-10-17 18:08:45.121 Detail, Node003, Notification: Notification - TimeOut

LOCK

2019-10-17 18:10:49.484 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2019-10-17 18:10:49.484 Info, Node003, Value_Lock::Set - Requesting lock to be Locked
2019-10-17 18:10:49.484 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0xff, 0x25, 0x7d, 0x22
2019-10-17 18:10:49.485 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x7e, 0xdf
2019-10-17 18:10:49.485 Detail,
2019-10-17 18:10:49.485 Info, Node003, Sending (Send) message (Callback ID=0x7d, Expected Reply=0x04) - DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0xff, 0x25, 0x7d, 0x22
2019-10-17 18:10:49.494 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-10-17 18:10:49.494 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2019-10-17 18:10:50.793 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x7d, 0x00, 0x00, 0x82, 0x14
2019-10-17 18:10:50.793 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x7d received (expected 0x7d)
2019-10-17 18:10:50.793 Info, Node003, Request RTT 1307 Average Request RTT 1287
2019-10-17 18:10:50.793 Detail,   Expected callbackId was received
2019-10-17 18:10:59.487 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 18:10:59.487 Detail, Node003, Removing current message
2019-10-17 18:10:59.487 Detail, Node003, Notification: Notification - TimeOut
2019-10-17 18:10:59.491 Detail,
2019-10-17 18:10:59.491 Info, Node003, Sending (Send) message (Callback ID=0x7e, Expected Reply=0x04) - DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x7e, 0xdf
2019-10-17 18:10:59.500 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-10-17 18:10:59.500 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2019-10-17 18:11:00.750 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x7e, 0x00, 0x00, 0x7e, 0xeb
2019-10-17 18:11:00.751 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x7e received (expected 0x7e)
2019-10-17 18:11:00.751 Info, Node003, Request RTT 1259 Average Request RTT 1273
2019-10-17 18:11:00.751 Detail,   Expected callbackId was received
2019-10-17 18:11:09.492 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 18:11:09.492 Detail, Node003, Removing current message
2019-10-17 18:11:09.492 Detail, Node003, Notification: Notification - TimeOut

I am really quite new here.
This is HASS.IO on Raspberry PI 3

This lock part is really quite important to me. This is the one and only thing i REALLY want to have working first before I start the others.
Really looking forward to somebody being able to help me on this. I will try to provide everything you need to help me.

Who_Carez · October 29, 2019, 5:58pm

nobody any idea?

upwind_anderl · November 7, 2019, 1:08am

also for me… no chance to get some control via HA

And this is my LOCK Log

2019-11-07 02:05:34.957 Info, Node010, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2019-11-07 02:05:34.957 Info, Node010, Value_Lock::Set - Requesting lock to be Unlocked
2019-11-07 02:05:34.957 Detail, Node010, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2019-11-07 02:05:34.957 Detail, Node010, Queuing (Send) DoorLockCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x62, 0x01, 0x00, 0x25, 0xb2, 0x1b
2019-11-07 02:05:34.957 Detail, Node010, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2019-11-07 02:05:34.957 Detail, Node010, Queuing (Send) DoorLockCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x62, 0x02, 0x25, 0xb3, 0x1b
2019-11-07 02:05:34.958 Detail,
2019-11-07 02:05:34.958 Info, Node010, Processing (Send) Nonce Request message (Callback ID=0xb2, Expected Reply=0x04)
2019-11-07 02:05:34.958 Info, Node010, Sending (Send) message (Callback ID=0xb2, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x98, 0x40, 0x05, 0x02:
2019-11-07 02:05:34.966 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-07 02:05:34.966 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-07 02:05:34.989 Detail, Node010,   Received: 0x01, 0x18, 0x00, 0x13, 0x02, 0x00, 0x00, 0x02, 0x00, 0xb1, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0x44
2019-11-07 02:05:34.990 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2019-11-07 02:05:34.990 Info, Node010, Request RTT 31 Average Request RTT 53
2019-11-07 02:05:35.014 Detail, Node010,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x0a, 0x0a, 0x98, 0x80, 0x49, 0x61, 0x06, 0x62, 0xf8, 0xe9, 0x15, 0x30, 0xb1, 0x00, 0x38
2019-11-07 02:05:35.014 Info, Node010, Received SecurityCmd_NonceReport from node 10
2019-11-07 02:05:35.014 Info, Node010, Sending (Send) message (Callback ID=0xb4, Expected Reply=0x04) - DoorLockCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x62, 0x01, 0x00, 0x25, 0xb4, 0x1d
2019-11-07 02:05:35.027 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-07 02:05:35.027 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-07 02:05:35.056 Detail, Node010,   Received: 0x01, 0x18, 0x00, 0x13, 0xb4, 0x00, 0x00, 0x03, 0x00, 0xb1, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0xf3
2019-11-07 02:05:35.056 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0xb4 received (expected 0xb4)
2019-11-07 02:05:35.056 Info, Node010, Request RTT 98 Average Request RTT 75
2019-11-07 02:05:35.056 Detail,   Expected callbackId was received
2019-11-07 02:05:44.958 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-07 02:05:44.958 Detail, Node010, Removing current message
2019-11-07 02:05:44.959 Detail, Node010, Notification: Notification - TimeOut
2019-11-07 02:05:44.967 Detail,
2019-11-07 02:05:44.967 Info, Node010, Processing (Send) Nonce Request message (Callback ID=0xb3, Expected Reply=0x04)
2019-11-07 02:05:44.967 Info, Node010, Sending (Send) message (Callback ID=0xb3, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x98, 0x40, 0x05, 0x02:
2019-11-07 02:05:44.974 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-07 02:05:44.974 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-07 02:05:44.999 Detail, Node010,   Received: 0x01, 0x18, 0x00, 0x13, 0x02, 0x00, 0x00, 0x02, 0x00, 0xb1, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0x44
2019-11-07 02:05:44.999 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2019-11-07 02:05:44.999 Info, Node010, Request RTT 31 Average Request RTT 53
2019-11-07 02:05:45.023 Detail, Node010,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x0a, 0x0a, 0x98, 0x80, 0xa6, 0xb4, 0x50, 0x85, 0xbd, 0x81, 0x5d, 0x9e, 0xb1, 0x00, 0x78
2019-11-07 02:05:45.023 Info, Node010, Received SecurityCmd_NonceReport from node 10
2019-11-07 02:05:45.023 Info, Node010, Sending (Send) message (Callback ID=0xb5, Expected Reply=0x04) - DoorLockCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x62, 0x02, 0x25, 0xb5, 0x1d
2019-11-07 02:05:45.036 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-07 02:05:45.036 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-07 02:05:45.064 Detail, Node010,   Received: 0x01, 0x18, 0x00, 0x13, 0xb5, 0x00, 0x00, 0x03, 0x00, 0xb1, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0xf2
2019-11-07 02:05:45.064 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0xb5 received (expected 0xb5)
2019-11-07 02:05:45.064 Info, Node010, Request RTT 98 Average Request RTT 75
2019-11-07 02:05:45.064 Detail,   Expected callbackId was received
2019-11-07 02:05:54.967 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-07 02:05:54.967 Detail, Node010, Removing current message
2019-11-07 02:05:54.967 Detail, Node010, Notification: Notification - TimeOut

Time Out with no motion
I’m on the newest firmware 11.9 and on a
Z-Wave. Me ZME_UZB1 USB Stick

This is my insertion in the config.yaml

zwave:
  usb_path: /dev/serial/by-id/usb-0658_0200-if00
  network_key: "0x04, 0x03, 0x01, 0x07, 0x09, 0x06, 0x05, 0x02, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10"

I used the direct path to the zwave stick because of another zigbee stick in the usb slot nearby

fribse · November 7, 2019, 8:31pm

Well I haven’t anything in the configuration.yaml, I’m using the integration. I couldn’t make it work back when I tried with the configuration.yaml, but with the integration, and doing the steps carefully it works perfectly here.
I, of course, do not have the same stick, so there might be other issues at hand here.

upwind_anderl · November 12, 2019, 6:49am

GOT IT !!!

Another try like fribse did My Danalock v3 Z-Wave Configuration 5. Step Solution
and now it’s perfectly integrated

The time before i used the same danalock with a raspberrian module and z-wave.me
Now i switched to HA in combination with a Z-Wave. Me ZME_UZB1 USB Stick

I’m also use the ozwave integration
And be sure you take the correct USB_PATH if you have another usb hw device on your device
I don’t recommend the generic:

usb_path: /dev/ttyACM0

because it’s easy to failure if you have more hw connected°!

jimi.wester · December 2, 2019, 9:52pm

Great!! It was exactly what I needed.
The last note about putting the lock in inclusion mode “AGAIN”… that was all that was needed.
And during this pressing the lock.get_usercode …

Thanks.

sebimt301 · December 10, 2019, 10:03am

My I ask your help please? I cannot set up my Danalaock v3. I use Aoteck Z-wave 5GEN usb stick. I tried to add with integration and tried via configuration.yaml also. I see my device but I cannot lock or unlock it. I made the lock.get_usercode process also. Please help me! Thank you!