Hi guys,
I have a Danalock V3 zigbee lock that continually stops reporting its lock state to my hub. It'll work fine for 2-3 days, then stop reporting its state until I power cycle it by removing/refitting a battery. I'm using the "Generic Zigbee Lock (no keypad) driver as recommended, but can't work out why it has this repeating communication issue. Has anyone else here experienced this? Or have a fix? Any help would be greatly appreciated.
Kind regards
James
I have 6 of these locks and none of them exhibit this. However, I have one of them that often times won't lock or unlock from a rule, but always works from the the Device Page. Anyway, have you tried removing and adding it back? That is my next step, but I just hate having to go through that process. Let me know if you try it and it works.
Yeah, I've done that a bunch of times, and always have it next to the hub when repairing it as the configuration during pairing takes ages. I'm not sure if it's relevant or not, but I set it up with the Danalock app first so that the BT auto unlock/hold back latch/twist assist functionality works correctly, then pair it to the Hubitat hub. I'm also using Smartthings smart plugs as Zigbee repeaters.
It's been awhile since I set them up. I forget which order I did them in, and I might have done that lock the wrong way.
I have the same lock and I too have this problem, although not as much as I use to. The symptoms; it stops reporting its state but, it can still be controlled through the Danalock app, and Hubitat (without state report).
I would do the battery pull thing. Remove, re-pair, blah, blah, blah.
My work around solution works like this;
The door that has the Danalock also has a contact sensor. If the door opens and the lock's state still shows locked, I send it a configure which brings the lock's status back to life. I use webCoRE to do this but Rule Machine should have something similar.
I have no proof but I suspect the cause for the lock problem is radio interference because Zigbee is in the same radio band as WiFi. One thing that helped dramatically reduce the issue was changing my zigbee channel down to 15.
Mine has a contact sensor as well, and I use webcore to refresh the lock every time it opens. I'll give the configure command a try though, and hadn't considered wifi interference. I'll check my channels and see if that makes a difference too. Thanks.
Yeah I would move your zigbee channel to 20 or 25. That said, what's your repeater situation? A mains powered zigbee repeater close by (like nearest outlet) and a re pairing might solve it too.
I've got 3 or four houses nearby, broadcasting on 2.4 ghz channels 6, 11 and 13 mainly, and multiple AP's in my house on channels 13/11/8/6/3. I was previously on Zigbee channel 16, but have just switched to 11, although the Danalock is the only device giving me grief out of 75 zigbee devices. I've got a smartthings plug within 3 feet of the lock, and another 4 within the 15 feet space between the hub and the lock (which is open plan, with only one wall separating the lock from the hub.
I've given the webcore device config suggestion a go, but due to the delay in the lock reporting it's state, every time I opened the door it was reporting it as locked, and triggering the configuration command. I've changed it to refresh the lock every time the door is opened, followed by a 60 second wait, and if the lock is still reporting its state as locked it will trigger a device config and a push notification to my phone.
One thing to keep in mind about changing zigbee channels to higher than 20.
I found all my older zigbee devices don't work on the higher channels. Devices such as the first generation SmartThings motion and their first generation multi sensors. If you don't have any old stuff you should be good to go.
That may be too close. I'd drop it to 20 and see how things behave
Won't 20 get interference from wifi channel 8 though?
I haven't ever noticed that myself.
I was using this table to try and steer the zigbee channel away from the wifi channels in use in my immediate vicinity.
I'm just saying most don't use 8 that I've noticed. I have a lot of AP's in my area (city) and 15 or 20 have always been good channels to use. You could start at 15 too
Area 51 is me, lol.
Again, comparing to my area. It also can't hurt to try... Most of the stuff running my area runs at 11 or 13
Download the Hubitat app
