So that means you have looked in Deconz?
You said earlier “I never go into Deconz”
I have looked in Deconz, I said I never go in there because 99% of the time I don’t. When I deleted the lock from Phoscon it automatically removed it from Deconz.
OK, might still be present in deconz but not visible. Had that scenario once, had to delete it through deconz REST API.
A bit tricky but the info is available here somewhere.
Here’s a starting point: Introduction - deCONZ REST-API
Isn’t that what Phoscon does? Uses the Rest API? It was visible in Deconz before I removed it on Phoscon.
What firmware are you using?
If I run GET /api/<API>/lights it’s not listed as a device.
Using firmware 20.x something, upgraded last week so should be latest FW.
OK, if it doesn’t show up there that’s good.
No further ideas.
1 Like
Good to see Phoscon/Deconz investigating. I still think it’s a firmware issue.
Can’t get mine to pair at all now.
I have the same issue with my device since July 2021 (losing pairing + stating not a Zigbee device). I don’t think it’s related to Conbee as mine have the issue with Sonoff ZBridge. I opened a ticket at Danalock but they closed it without investigation stating that my router is not Zigbee certified
Out of desperation and since i needed to change the batteries anyway I went with your suggestion and bought Rechargeable CR123.
Now i am on FW 0.20.0 and this method seems not to work as i still have disconnections but the motor seems a bit stronger and faster with the higher voltage.
Would you mind sharing what FW version do you have on your lock?
I am still on 0.17.15
I haven’t seen any release notes for 0.20.0 yet and from my past experience with Danalock, I simply follow the “never change a running system” formula here, because Danalock sucks and the version jump is too large for them to not have fucked something up.
It’s a shame you can’t downgrade the firmware. I bought mine new with 0.20.0 installed.
Well, the earlier versions are not better either…
Having exactly the same problem. Only thing that fixes it (albeit temporarily) is to remove and reseat a battery to restart the lock.
Have been in contact with Danalock support and they requested:
- log files
- the make, model and approximate distances from the lock of any mains powered zigbee devices
- make and model of gateway
I supplied all the info they asked for and have chased them but haven’t heard from them in 3 weeks. Really frustrating.
I think they are going to get it fixed pretty soon, as they are now collaborating with the Deconz guys on this very problem.
Hopefully, but I honestly think it’s not an issue with any of the third party Zigbee platforms, it’s their firmware. The lock clearly forgets it is Zigbee enabled so their firmware must be doing that.
I don’t think there’s an issue with either, I have firmware 0.20.0 and it works flawlessly with Zigbee thru Conbee II. Been working perfectly for at least 2 years.
Yes, and Deconz guys are helping them solve the problem. Somewhere it was discussed that the problem arises when a previously used route/router device becomes unavailable; the danalock doesn’t react accordingly. I bet the devs at Deconz know the zigbee protocol much better than at Danalock…
1 Like
I just had a response from Danalock after emailing their support yesterday. So maybe there are two issues. The app being misleading and the Zigbee connection dropping.
1 Like