[SOLVED] Danalock V3 - Z-Wave

Delete the Thing and readd it (don’t exclude/reinclude)

1 Like

Hi all. This seems like a good thread to hijack for the problems I’m having :slight_smile:

I’m trying to get my first secure node, a Danalock V3, included. First I BT paired with phone and then got the lock included, as smooth as a breeze. Then I realized that it wasn’t securely included and thus not useful. So I got the advice to factory reset the lock (here) which I have done now (ten pushes using a paperclip). However, after factory resetting I can’t seem to do anything with the lock, it doesn’t even turn up in the Danalock app so I can BT pair it with my phone again. Tried resetting it again. Anyone got any tips? Or have I completely bricked my expensive lock now?

Also, when/if I succeed with BT pairing the lock, I guess I’ll try the inclusion again and just hope that it works. But is all this hassle really the only option? I wish I could tell the controller that if it can’t include securely it shouldn’t include at all, it’s just stupid to include it in a non working way…

edit: Fixed it. Turned out a factory reset does NOT reset everything, the lock still thought it was included. So I had to first exclude it properly, THEN factory reset and then redo everything from the very beginning. Now dismounted the lock and put it only centimeters from the Z-stick and the secure inclusion worked!

Thanks for the update and explaining how to fix it. Is that the only thing required, keeping it really close to the zwave stick, to get it securely included? Or do I need to do something else, put it in secure inclusion mode or something?

If I’ve understood things correctly three things are important:

  1. The distance. Seems to be important for the device to be close to the controller. My door is about two meters from my home server but I guess that was too far away.
  2. The time. A secure inclusion needs to be done within 15 seconds.
  3. Pure luck. If you don’t succeed the first time, it might be worth trying the exact same thing again. And as I said, it’s not enough just factory resetting the device, it also needs to be excluded.
1 Like

Yes, distance is important as secured connection is a direct communication.

Thank you!
Very useful!

2 questions though :slight_smile:
which channels does the dana lock provide?
How long is the battery life?

Only two channels, one for the lock itself (open/closed) and one for the battery level.

I have had mine for about half a year now and my batteries are down to 93%. I haven’t used it very actively though since my wifes first reaction was quite negative so she’s actively refused to use it. And if just one person in the household uses the key to lock/unlock things get out of phase and the lock doesn’t work as intented…

Wow - that’s impressive.
So I will order one right away :slight_smile:
I just found that there is an Entry Alarm channel.

I wonder when this will be triggered (vibration without lock activities!?)
Do you use this channel?

That’s weird, I don’t see that channel here. I guess it must be a channel that didn’t exist when I first set up my lock. No idea how that would work, but I’d love to know :slight_smile:

Any hidden channels in the PaperUI config?

Anyway: I will report, as soon as I have mine up and running.

Is the inclusion procedure different than the regular inclusion?
I am about to include my danalock as well :slight_smile:

Well, it seems to be much more sensitive. Look at my post above from the 25:th of april, I have summarized what seems to be important.

Thanks and sorry that I did not see this yet! :crazy_face:

Where do I get the information from your screenshot below?
I checked my xml file in the openhab zwave directory and found:

I assume that means it’s not included securely!?

Got it! Habmin in “Attributes”
My controller does not show any security :frowning:

In PaperUI Security is set correctly - I assume:

Or should I use
All Devices?

Yes, this should be fine. You should exclude the device, reset it, and try and reinclude. The timing is important.

Alright - thanks will do
(and as close as possible as far as I read.)

Modern devices should not require this - the ZWave spec was altered many years ago to remove the requirement for devices to use low power for inclusion, and they are now required to use full power. However, maybe this device still implements this old requirement, so if others have found this is necessary, then maybe it is…

I just installed my danalock a few days ago and am pretty happy with it.

The channel “Entry Alarm” exists in my case, but I don’t know what it means yet.
When locking I get:

2020-08-17 08:36:41.284 [vent.ItemStateChangedEvent] - Z_Lock_Alarm changed from OFF to ON
2020-08-17 08:36:41.697 [vent.ItemStateChangedEvent] - Z_Lock changed from OFF to ON

when unlocking (Auto Unlock):

2020-08-17 09:08:33.122 [vent.ItemStateChangedEvent] - Z_Lock_Alarm changed from ON to OFF
2020-08-17 09:08:37.893 [vent.ItemStateChangedEvent] - Z_Lock changed from ON to OFF

I installed a extra danalock in openhab 3.1.0m4 this is what i get

When i look at my already included lock i see this

i found the node was not securly included, but is there another way then press scan in openhab to sercure the inclusion?

also my controller last node before i included my lock was 49 and when i included the lock it jumped to 62 then I unincluded the lock a couple of times but with no succes.

Check this thread. I had same issue and I thought that it is OH M4 but it was not. You need to include Danalock securely. Otherwise channels will not visible.