My Danalock v3 Z-Wave Configuration 5. Step Solution

no i removed it bay cliking on the trach can in the gui. it coms back up again after restart

That worked for me too :slight_smile:

2 Likes

If I understand correctly I need to be very close to the lock for this method to work? What kind of Z-Wave stick have you guys successfully used? (I have an Aeotec Gen5)

I have a Aeotec Gen5 too - the HA with the stick is about 4 Meters from my working place.

@Danielhiversen, @db_88 - Did you have to use the lock.get_usercode?

I can finally see the lock in HA ā€œlock.polycontrol_danalock_v3_btze_lockedā€. I get the option to lock it, but nothing happens. I can lock and open from App just fine. Lock/unlocked status is not getting updated in HA either. Did you have to do anything after getting the enitity in HA?

I have a network key and have added the lock as a secure node.

Yes, I did it. But not sure if it was necessary.

I followed the 5 steps in the first post.

1 Like

Thanks!
What information did you populate with? I click the button on the lock, then send this json:

{
"node_id": "5",
"code_slot": "1"
}

image

Did you factory reset the lock before adding it again with a Network key?

This is what I did after I had added the lock without a network key. Do you see any missed steps?

  1. Removed the lock from zwave by setting it in exlusion mode and ā€œremove nodeā€ from zwave.
  2. Removed the zwave config from configuration.yaml, and clicked the trash bin button in integrations.
  3. Restarted HA
  4. Adding zwave integration from the integration frontend with a network key. Not adding config to configuration.yaml.
  5. Adding the lock again to zwave as secure node
  6. Clicking 1 time on lock switch
  7. Sending json on lock.get_usercode, while the lock light is green.
  8. Entity ā€œlock.polycontrol_danalock_v3_btze_lockedā€ is available, but lock does not respond on commands like lock/unlock. Locked/Unlocked state in HA is not correct.

This is the zwave log when trying to send lock commands:

2019-03-02 11:58:02.951 Info, Node005, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2019-03-02 11:58:02.951 Info, Node005, Value_Lock::Set - Requesting lock to be Locked
2019-03-02 11:58:02.951 Detail, Node005, Queuing (Send) DoorLockCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x62, 0x01, 0xff, 0x25, 0x92, 0xcb
2019-03-02 11:58:02.951 Detail, Node005, Queuing (Send) DoorLockCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x62, 0x02, 0x25, 0x93, 0x34
2019-03-02 11:58:02.951 Detail,
2019-03-02 11:58:02.951 Info, Node005, Sending (Send) message (Callback ID=0x92, Expected Reply=0x04) - DoorLockCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x62, 0x01, 0xff, 0x25, 0x92, 0xcb
2019-03-02 11:58:02.982 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-03-02 11:58:02.982 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2019-03-02 11:58:04.142 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x92, 0x00, 0x00, 0x73, 0x0a
2019-03-02 11:58:04.142 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x92 received (expected 0x92)
2019-03-02 11:58:04.142 Info, Node005, Request RTT 1192 Average Request RTT 1206
2019-03-02 11:58:04.142 Detail,   Expected callbackId was received
2019-03-02 11:58:12.951 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-03-02 11:58:12.951 Detail, Node005, Removing current message
2019-03-02 11:58:12.951 Detail, Node005, Notification: Notification - TimeOut
2019-03-02 11:58:12.953 Detail,
2019-03-02 11:58:12.953 Info, Node005, Sending (Send) message (Callback ID=0x93, Expected Reply=0x04) - DoorLockCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x62, 0x02, 0x25, 0x93, 0x34
2019-03-02 11:58:12.976 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-03-02 11:58:12.976 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2019-03-02 11:58:14.241 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x93, 0x00, 0x00, 0x7e, 0x06
2019-03-02 11:58:14.241 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x93 received (expected 0x93)
2019-03-02 11:58:14.241 Info, Node005, Request RTT 1289 Average Request RTT 1247
2019-03-02 11:58:14.242 Detail,   Expected callbackId was received
2019-03-02 11:58:22.953 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-03-02 11:58:22.953 Detail, Node005, Removing current message

I got it working now by removing and adding it another time. Thanks :slight_smile:

Are your lock reporting locked/unlocked state when you turn the lock manually? Did you change the polling intensitity in zwave? mine is 0 atm and does not report any change unless it was triggered by zwave

What Z-wave device are you using? Iā€™ve tried a million times with the AEON LABS Z-STICK GEN5 -ZW090, and Iā€™ve just been told by Danalock that it doesnā€™t support command classes for locks :frowning:

I have the Aeotec Z Stick Gen5. Works great now

Darned, I canā€™t get it working. Now the lock has gone completely bonkers, so Iā€™ve sent it in for repairs (I canā€™t even exclude it & reset it and get it activated for BT anymore).
Iā€™ve created the secret key, and I have the Aeotec inserted properly, but I canā€™t get it to react to any commands. Now Iā€™m a bit ā€˜afraidā€™ of doing it again, so for now the experiment is stopped.
How did you send the json text?

Did you just removed it/added it again and it started workingā€¦?
I have the same problem as you (and the same entries in the log), but after removing/adding it 4 times, still no luck.
Do you use the lock together with Danapad or just the Danalock?

I can confirm that Danalock V3 (0.10.3) is working with HA 0.91.2 and Danapad V3.

Order:

  1. Pair Danalock with app (bluetooth)
  2. Pair Danalock with HA. I use AEON Labs Z-Stick Gen5
  3. Pair Danapad with Danalock (bluetooth)

Note! This lock needs to be close to the z-wave controller or other z-plus device. Max. 1-2 meter.
I have a Heatit thermostat within 1 meters range.

You need to use ā€œAdd Node Secureā€ in HA to include the lock. I use the app to enable z-wave inclusion on the lock.
You also need to call service ā€œlock.get_usercodeā€ with service data:
{
ā€œnode_idā€: ā€œ5ā€,
ā€œcode_slotā€: ā€œ1ā€
}
where node_id is the Danalock z-wave node id. The Danalock needs to be in inclusion mode when the service call is executed.

I have 5 entities:

  • group.all_locks
  • lock.poly_control_danalock_v3_btze_locked
  • zwave.poly_control_danalock_v3_btze
  • sensor.poly_control_danalock_v3_btze_alarm_level
  • sensor.poly_control_danalock_v3_btze_alarm_type
2 Likes

I was about to buy the z-wave Danalock, but am now teetering on the edge of getting the homekit version after reading this thread - it sounds a little nightmarish to install and the closest z-wave controller / node to our front door is at least 5m away at present, combined with the fact (despite installing HA on her phone) my partner refuses to use anything but homekit on her iPhone.
Can anyone who has successfully managed to install the Danalock v3 tell me if theyā€™ve managed to forward it through to the homekit component please?
If so, were there any issues such as additional lag-time when operating from homekit on iOS, or lost functionality?
Thanks so much

Do t his sensors also have value changes ? Mine wonā€™t show alarm_type or anything else but the lock works fine so far.

The values is 0, all the time.

is that normal.? i had danalock v2 before and there was an indicator for manual opening or via app

Ok, THIS WORKS.

I ventured into the danger land.
After bricking my danalock by doing it wrong, and I had to send it in for reset, which they kindly did, I tried doing it with the updated HA (0.92.2) where the z-wave config is much better integrated, so I let it choose all itā€™s own kind of configs, and then after a reboot the AEON Labs Z-Stick Gen 5 was there.

So after poking that with heal, and checking the logs, and everything looked ok, I went into the danalock app on my phone, and set it to z-wave include. I then pressed the ā€œadd secure nodeā€ on HA, and presto, it was visible.
I then reactivated the ā€˜includeā€™ mode in the danalock app, and ran the extra service call. Not sure what it does, but hey.
I can now see status in my UI, and I can lock and unlock from the UI as well, weeheee.

2 Likes

So can I, with Z-wave integration in the Lovelace UI, and doing the ā€˜inclusionā€™ in the Danalock App, it works perfectly.
Itā€™s really fast and responsive, and Iā€™ve already had great benefit of it for package deliveries when we are out of the house :slight_smile:

I still have problem getting more Entities after following your guide. The only one i get is ā€œPoly-control Danalock V3 BTZEā€
The biggest problem for me is that i cant do the Call service part, it says ā€œInvalid Jsonā€ and the ā€œCall serviceā€ button is grey.

What am i doing wrong? :slight_smile:

Call%20service