I don’t understand your question… The Danalock has batteries. There are no other options for this product.
Hi heisenberg!
I’m looking at buying Danalock, and as yourself, I have a multilock door, with no push handle (just a bar). To open my door, I need to turn the key for about a quarter after unlocking. On their website, I found a feature called Hold back latch, which seems to do the trick, and is actually recommended for doors not having a handle outside.
Have you tested this feature? I understand that your door requires you to lift the handle in order to activate the multilock latches.
By activating the Hold-back-Latch feature, the Danalock holds back the latch in your door.
You can configure it to hold back the latch for up to 15 seconds. This feature must be activated if you don’t have a handle on the outside of your door.
Thanks!
I have seen that Hold back latch option in the app but I haven´t tested it because as I mentioned my door doesn´t open just by turning the key (i.e. pushing the handle is always required to open the door), but according to your description of your door it should work in your case
1 Like
I just installed my Danalock on Saturday and flashed the new Firmware “0.20.0” that was published on March 31st.
The lock only works a few times, then the Zigbee connection drops completely. I cannot access the lock anymore in any way. In the phone app under settings for Zigbee it even says “This is not a Zigbee Variant”. When replugging the batteries it works again a few times.
Does anyone else have these problems with Zigbee and Firmware Version 0.20.0?
@prior I wasn’t aware of an update so haven’t seen these issues yet however it seems like a repeat of when I was using ZHA for zigbee devices. Haven’t seen that happen on zigbee2mqtt (well, I have seen it happen twice but both those occasions where after 3 power cuts back to back with a 5 minute window of power being back up - long enough for HA to start up and start checking devices and then power went out again so I put it down to DB/zigbee network corruption).
What are you running your zigbee network on?
Upgraded mine yesterday aswell, no issues yet… but I’m not using it more then maybe two times per day.
I kindly asked Danalock support to work out the issues together with deconz/zb2mqtt/zha and they responded the same day:
We are aware of the Zigbee issues. I will contact phoscon/dresden-elektronik today and suggest we work together to find a solution.
I doubt that this has any effect on the Zigbee issues, but FWIW maybe you’re desperate enough to try:
I used the Danalock V3 Zigbee with Duracell CR123 batteries, however the batteries seem to go low after a few weeks already (I’m also using auto-lock so the lock is always locking after it was opened) and maybe that actually has an effect to the connection. I am using the ConBee 2 and have integrated the lock into Home Assistant but it would always lose the connection (i.e. I can not lock/unlock via Home Assistant anymore) after a few days. Then I always remove a battery and re-inserted it to get the lock re-connected.
I then looked for rechargeable batteries and bought this CR123 A Li-Ion Akku mit 3,7 Volt, 760mAh 8 Stück und LCD-Schnell-Ladegerät | BonusPacks | Akku nach Größe | Akkus | Akkushop
They have a slightly higher voltage, but the lock is working fine with that. More importantly: I haven’t been facing any of the disconnection issues again since then. The rechargeable batteries held about 3 months and recharging them takes just a few hours. I am now at month 4 using them. So FWIW, maybe thats an option for some of you.
1 Like
I have just installed my brand new Danlock V3 and I’m trying to get it to connect to ConbeeII/Deconz. When I go into the app and zigbee join, then search for the device in Deconz, after a few seconds the app foes back to the first menu and Deconz cannot find it.
Firmware is version 0.20.0.
Any ideas?
OK, I managed to pair it by updating my Conbee firmware and Deconz. But now it seems to connect for a few minutes then it stops responding to anything but the bluetooth app. rebooting the lock (removing a battery) fixes it for a few minutes.
Do you use Phoscon when adding the lock?
Sounds like you might be doing it from deconz when you write “join”.
I used Phoscon, add as New Light.
Remove from deconz first if it’s still there from previous attempts.
From the phoscon web app. Join is the term when enabling the joining process within the Danalock app.
I can see the device in Phoscon, but it stop responding after a few minutes and the only way to get it back is to remove a battery and reinsert it.
Is it present in deconz?
If it is, delete it from there before adding in Phoscon.
Deconz/Phoscon are the same thing. I added it through Phoscon to begin with.
They’re not actually, they both handle parts of the conbee zigbee processes but they are not the exactly the same.
I’ve been solving some issues that could only be done in deconz but not in Phoscon.
Anyway, what have you got to lose?
If you find the lock in deconz, right click and select delete. Then try joing in Phoscon again.
I never go into Deconz. I’ve always just added devices through Phoscon. Not sure what deleting it and re-adding it will do.
This is the problem I am having, except I don’t get the “not a Zigbee device” error in the app.
ETA. Just tried to remove it from the Zigbee network from within the Danalock app and I am getting the “this is not a zigbee enabled device” error.
Further edited. The message “this is not a zigbee enabled device” error coincides with the device dropping off the Zigbee network. If you do nothing, then reboot it, not only can it be controlled from HA but you can also get into the Zigbee menu in the Danalock app without the error.
My suspicion is that the firmware is losing it’s connection to the Zigbee radio after a few minutes so it thinks it’s not a Zigbee lock. That’s why you get the error and you can’t control it with HA. I’m going to contact Danalock.
I had issues first time I added it as well.
What I did to solve it;
- Reset the the Danalock, think it’s done by pressing the button on the small hole 10 times.
- Setup the Danalock through the app, just the basic settings, not any Zigbee stuff (as the screenshot you provided)
- Make sure the lock is deleted in Phoscon and Deconz, if not delete entry.
- Start the paring on the Danalock with the same button as before, don’t remember number of presses.
- Start the pairing from the Phoscon interface (add light actually).
Phoscon finds the light and you are set.
Don’t understand your unwillingness to look for the lock in Deconz and delete it. You’re coming here for help and you discard that, eventhough it’s coming from someone with a working zigbee Danalock since 2 years back. You’d rather call Danalock. Well, good luck.
I’ve just tried every step you just mentioned, which is the same way I set it up in the first place.
Unfortunately it’s still the same.