Can't control Danalock v3 (Z-Wave)

Configuration Z-Wave
1

I just got the new Danalock v3, and trying to get it work with Home Assistant. First, I paired it without using secure Z-Wave. Then, I unpaired it and have tried again with secure a couple of times. I don’t get an updated status, and I don’t see anything change when I control the lock from the app. The same goes for open-zwave-control-panel.

I have configured z_wave.network_key, and used secure add while having the controller ~ 2 meters from the lock.

From the logs:

2017-09-30 20:00:32.869 Always, OpenZwave Version 1.4.2474 Starting Up
2017-09-30 20:00:43.495 Info, Setting Up Provided Network Key for Secure Communications
2017-09-30 20:00:43.495 Info, mgr,     Added driver for controller /dev/ttyACM0

…

2017-09-30 20:04:49.650 Info, Node020, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2017-09-30 20:04:49.651 Info, Node020, Value_Lock::Set - Requesting lock to be Locked
2017-09-30 20:04:49.651 Detail, Node020, Queuing (Send) DoorLockCmd_Set (Node=20): 0x01, 0x0a, 0x00, 0x13, 0x14, 0x03, 0x62, 0x01, 0xff, 0x25, 0x59, 0x11
2017-09-30 20:04:49.651 Detail, Node020, Queuing (Send) DoorLockCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x62, 0x02, 0x25, 0x5a, 0xec
2017-09-30 20:04:49.651 Detail, 
2017-09-30 20:04:49.651 Info, Node020, Sending (Send) message (Callback ID=0x59, Expected Reply=0x04) - DoorLockCmd_Set (Node=20): 0x01, 0x0a, 0x00, 0x13, 0x14, 0x03, 0x62, 0x01, 0xff, 0x25, 0x59, 0x11
2017-09-30 20:04:49.659 Detail, Node020,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-09-30 20:04:49.659 Detail, Node020,   ZW_SEND_DATA delivered to Z-Wave stack
2017-09-30 20:04:49.836 Detail, Node020,   Received: 0x01, 0x07, 0x00, 0x13, 0x59, 0x00, 0x00, 0x12, 0xa0
2017-09-30 20:04:59.651 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-09-30 20:04:59.651 Detail, Node020, Removing current message
2017-09-30 20:04:59.651 Detail, Node020, Notification: Notification - TimeOut
2017-09-30 20:04:59.651 Info, Notification: Notification home efa01b35 node 20 Timeout
2017-09-30 20:04:59.652 Detail, 
2017-09-30 20:04:59.652 Info, Node020, Sending (Send) message (Callback ID=0x5a, Expected Reply=0x04) - DoorLockCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x62, 0x02, 0x25, 0x5a, 0xec
2017-09-30 20:04:59.660 Detail, Node020,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-09-30 20:04:59.660 Detail, Node020,   ZW_SEND_DATA delivered to Z-Wave stack
2017-09-30 20:04:59.804 Detail, Node020,   Received: 0x01, 0x07, 0x00, 0x13, 0x5a, 0x00, 0x00, 0x0e, 0xbf
2017-09-30 20:04:59.804 Detail, Node020,   ZW_SEND_DATA Request with callback ID 0x5a received (expected 0x5a)
2017-09-30 20:05:09.652 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-09-30 20:05:09.652 Detail, Node020, Removing current message
2017-09-30 20:05:09.652 Detail, Node020, Notification: Notification - TimeOut
2017-09-30 20:05:09.652 Info, Notification: Notification home efa01b35 node 20 Timeout

Any help or advice is appreciated!

2

Did you pair it through the HA control panel? If not then that might be part of the problem.

The messages you posted suggest that there’s a communication problem. Is the controller close to the lock, or do you have mains powered Z-Wave devices providing a route between the controller and the lock?

3

I did pair it through HA, 1-2 m away from the lock.
I now tried to pair it through ozwcp, and it worked! I could open and close the lock. It also recognizes the lock as a Danalock. It also worked in HA :slight_smile:

4

I am having the exact same problem as you; could you explain how you did it? I am running Hass.io on a Raspberry Pi. How do I access OZWCP?

I have other devices working with secure connection.

5

Don’t use OZWCP
Don’t use OZWCP
Don’t use OZWCP

:wink:

Use the embedded Z-Wave control panel - it does everything you need. If you use OZWCP (or the controller’s button) then you run the risk of a broken pairing. Amongst other problems, some devices only send their capabilities at pairing time, and if you don’t use the HA control panel then HA never gets to properly know about the device.

1 Like
6

Ok, thanks for letting me know.

However, I have only used the embedded control panel, and it does not work. I have tried excluding and including again. I get a device called ‘lock.locked’, but it does not seem to do anything.

Do I need to be 1 meter away? Currently, the lock is about 7 meters away… Could this be it?

7

Seven meters, through walls, could well be a problem. Hence why I was asking about the location, and whether or not there are other powered Z-Wave devices.

Try moving your controller nearer, or placing a powered Z-Wave (Plus) device between the controller and the device.

8

I now tried including it again with about 1 meter from the Z-Stick to the Danalock, and got the exact same result.

Also, I see that the Fibaro door sensor that I added earlier is not working anymore. It showed as six different sensors (as it should), but after reboot, I only see one sensor (only one I have customised), and it does not return correct state… Under the ‘Z-Wave Node Management’ it says ‘Node: 3 Probe’, but it said ‘Node: 3 Complete’ when it was working.

Any ideas?

9

I tried several times with the embedded secure add, no luck. It worked flawlessly after first try in ocwp. Are you sure there would be any issues? The zwcfg is shared, the hardware is the same - I assume the software behavior is what differs.

10

If the zwcfg_*.xml is really shared (and not just copied back and fore) you should be fine. Lots of installs aren’t that way, and so people end up in a mess.

11

Probe says that the Z-Wave stack is pinging the device to see if it’s awake. For battery powered devices that’s perfectly normal. You’d need to wake it, or wait for it to wake, for it to progress past that.

12

Thanks, I eventually got my Fibaro sensor working again.

The Danalock, however, I still can’t get to work. I am running Hass.io version 0.50; could there be any changes to this in newer versions? I am updating to 0.54 now.

13

0.54 did bring a bump of the OZW libraries, which may help.

14

Just tried again with 0.54, no success this time either. Any clues?

I could add that I have also tried including it on my Tellstick ZNet v2, which kinda worked. The inclusion got stuck at 1% (every time), but it did add a “generic” device with on/off functionality, and I was able to control the lock with this.

15

I wonder if there’s a fault in the Danalock you’ve got.

Once added have you tried running a Heal and Test Network from the Z-Wave control panel? When you look at the Z-Wave entity, what are the figures for:

  • averageRequestRTT
  • sentFailed
16

Might be the Danalock, but I will try some more before making any conclusions on that.

Here is the full node information on the Danalock:

averageRequestRTT: 322
averageResponseRTT: 0
battery_level: 100
capabilities: frequent,beaming,routing
friendly_name:
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: true
lastRequestRTT: 29
lastResponseRTT: 0
manufacturer_name:
max_baud_rate: 40000
neighbors: 1
new_entity_id: zwave._
node_id: 8
node_name:
old_entity_id: zwave.__8
product_name:
query_stage: Complete
receivedCnt: 0
receivedDups: 0
receivedTS: 2017-10-01 19:28:57:799
receivedUnsolicited: 0
retries: 0
sentCnt: 11
sentFailed: 0
sentTS: 2017-10-01 20:13:25:290

EDIT: Did run a heal and test before copying that information.

17

I just checked the OZW library, and under Polycontrol (manufacturer of Danalock) it does not list Danalock v3.

I suppose this could be the reason, but isn’t it odd that @stiansoevik got it working then?

18

stiansoevik may have manually created the required entries - most standards compliant Z-Wave devices will work regardless of whether or not they’ve got an entry in the library.

Other than the fact that the controller is the only other powered device it can see, the stats for the lock look fine. I see though that it doesn’t have it’s final name yet, it’ll be worth restarting HA to see if that fleshes that out. It shouldn’t matter to the operation of the lock though.

19

I think I’ll send an email to Polycontrol to ask if they might know what’s up. Currently, their documentation on the Z-Wave capability is not very impressive…

I have restarted HA multiple times after I included the Danalock, but it does not receive a name.

20

I have a separately downloaded and compiled ozwcp instance, which I assume is newer than the one bundled with HA (0.51.1). That might be why inclusion worked in ozwcp and not in HA. I did not manually create anything. After inclusion, it worked well in HA :slight_smile: