I have started to experience connectivity issues with my Danalock V3 BT/zigbee today. There were no changes in the setup for quite some time already.
The unlock command sometimes goes through, the lock turns, ST does not log the event and ST app does not update the lock’s status, and eventually gives me a network error.
The native lock’s app works fine (via BT).
I have changed to some other Edge drivers and back, changed batteries, excluded, included, recalibrated the lock, restarted hub, changed zigbee chanel to 20 - did not help. All other devices work fine as usual, no delays.
I have also noticed the ST default driver got updated.
Is it a bug in the updated native ST driver for zigbee locks or the lock’s zigbee module gone bad? I have no access to any other compqtible Edge drives just to eliminate the last variable before I buy a new lock.
Any advice here?
I’ve got two zigbee locks running this driver, and both are working just fine and haven’t had any issues or messages like what you’re getting.
Sounds like you’ve tried what I would have recommended, but have you also tried to use the advanced web app to initiate a lock or unlock command?
The commands in the advanced web app actually work. So it`s the ST frontend (mobile app) that is the issue? The lock unlocks and locks when I use the commands, but the app does not sync the lock`s tile in the mobile app.
I have deleted app cache and all data, I get now a message that I use a unofficial driver in addition already existing issues. What is happening 
That’s ok, just dismiss the message and it shouldn’t come back.
But the main issue is still there. I can not lock/unlock via the ST mobile app, and automations do not function.
I’d recommend sending in a ticket just to bring awareness to the people at smartthings support. I got the same message you did, but I’m not experiencing what you are.
1 Like
There’s your problem.
You have to delete the device in the app and add it back again whenever you switch drivers.
I changed drivers as an attempt to fix a non responsive lock. Not that I changed the drivers and the problem appeared.
Understood. You still need to delete the device and add it back again, but before you do that, you should delete any custom Zigbee lock drivers.
There was one change to a sub-driver three weeks ago that isn’t relevant in your case. Another change from July that might be relevant, but that’s from almost three months ago.
Edit: and your driver was updated in-between these changes at least one more time when a fingerprint for a new device was added.
Thnx. I will remove a driver that the lock hooks up to upon enrolment, just to make sure it hooks directly to a native one straight away.
1 Like
Yeah. You should never just switch back to the stock driver from a custom driver. Zigbee devices want to be configured correctly. Long story…
1 Like
Thank you guys. It seems that the lock became functional again. I deleted all custom drivers that I could select for the lock, removed the lock from ST, enrolled it again.
The story began when the batteries most likely were too week ( showed 68% in ST, low in Danalock app) and at one moment of my try to `fix` things I decided to unenroll the lock. Upon re-enrollment, the lock was hooking to a non native driver straight away and I was switching to the native one manually - that was the problem.
1 Like
Wondering when we’ll have the option to choose which driver to use on enrollment. Long story…. 
