It looked to me like the lower end would have the least wifi interference, hence changing the zigbee channel to 11, but I'm far from an expert in this, and not even sure that wifi interference is actually the issue causing the lock to stop reporting its state after 2-3 days (while still working perfectly well in the Danalock app).
I'd still give it a whirl, you can always change it back.
Ok, I'll change it now and see how it responds over the next couple days, thanks for the help
1 Like
Also, I forgot to mention that my hue bridge is on channel 15
1 Like
Switch hubitat to 20 then. My hue is also on 15. That's my current setup and never have any probs
Just a quick update, changing to channel 26 (after testing a number of alternatives) seems to have fixed the issue, its now been over 2 weeks without a problem. Although all my other Zigbee devices worked perfectly fine, the Danalock seems particularly susceptible to wifi interference. As each interference environment will be unique (neighbours wifi channels will vary), if you are experiencing similar issues, all you can do is try switching Zigbee channels until you find one that works consistently.
1 Like
It is just a driver problem. Use Generic ZigBee Lock instead the default Generic ZigBee lock (nokeypad). After this, no more updates problem of the ZigBee lock status.
I tried the Generic ZigBee Lock driver as suggested, but unfortunately the Danalock hardware failed before I could establish if the driver was more reliable. This is the second unit I’ve had fail with the same issue (namely losing its calibration within an hour of being recalibrated rendering it unusable) and as it’s was now out of warranty I’ve decided to cut my losses and replace it with a Nuki lock instead.
Hi, Its 2025 and Danalock is still having the same problems, I have hard wired my lock to a transformer which is plugged into a smart socket and once a night it switchers off the power and resets my lock, thats been working for the pass 2 years.
I've had one of these locks for several years and was plagued with it constantly falling off the mesh. What seems to work best for me is to send it a lock command once per day (Sent this command when the mode switches into night mode. I use webCoRE and inside the piston I disable "command optimization". I'm not sure if Rule has this capability but it allows the command to be sent even if the lock is already in a locked state.
Thank you, I will try this.