I got the new zigbee module and have installed it now. Seems to work fine so far but the firmware version seems old.
Firmware build date
20230211
Firmware version
4.5.24
I have asked the Nimly support why.
I got the new zigbee module and have installed it now. Seems to work fine so far but the firmware version seems old.
Firmware build date
20230211
Firmware version
4.5.24
I have asked the Nimly support why.
The new module I got seems to have even more problems. Disconnecting all the time and refuse to connect almost every time when reinserting the batteries.
Think I will return the lock + module. The lock works fine but apparently they are totally incompetent when it comes to zigbee development.
I’ve been running the same FW and build date as you for an week now, not even one disconnect on both of mine. Only issue I have is both reports around 30% battery with newly recharged batteries.
Quick question, which Zigbee Coordinator are you using and which Zigbee integration (ZHA vs Zigbee2mqtt)?
I’m using Sonoff Dongle-P with zigbee2mqtt 1.35.1
Z2M 1.35.1 with a Skyconnect.
Had a Conbee 2 before with same problems.
Strange, I’m starting to think it is something wrong with my lock. I also have a friend with two locks with no issues.
I submitted a PR that should solve the battery reporting never going above 50%
Has anyone gotten updates from Nimly? I recently purchased the Nimly Code with the zigbee module. When I try to pair the module with zigbee2mqtt, it seems to work for about 20s (or maybe just until I make one action?) and then refuses to send or receive data anymore. Then I have to play a whole song and dance to disconnect it and reconnect to get another 20s of use. I reached out to Nimly but haven’t heard back yet.
Firmware 4.5.24
I recently got 2 replacement modules with build date 20230211 and FW 4.5.24. These have been working fine since replaced (about 2-3 weeks now). Only issue is the battery reporting (ref post above yours). This is with Sonoff Dongle-P with zigbee2mqtt 1.35.1.
@jkaberg Yes that’s the build date I have also. It seems like we have the same setup, so maybe I have a defective unit. It’s identifying as easyCodeTouch_v1 but stops working right after I send it a successful unlock message.
Hi all,
I’m eyeing a Nimly smart lock with ZigBee module and have two quick questions:
Thanks for sharing your experiences!
Update: I exchanged for a new module and it seems to work now. I guess it was a defective unit.
Did you guys do anything special to pair it with z2m?
I also got a replacement module but it refuses to stay paired.
I have successfully paired it multiple times but it instantly goes offline in z2m
I managed to pair the previous module earlier but dont really remember if i did anything special
I have the same issue. And it also eats batteries. Hope to get an answer soon.
Got the newest firmware build send as well.
I had similar issues as mentioned in the thread, device offline and high battery usage. Sent an email to Nimly support and they responded that I had a faulty module.
After a week or two I received a new module which has worked flawlessly.
New unit has firmware 4.5.26 with build date: 20240201.
It is connected to Z2M with a sonoff ZBDongle-E.
Nice thanks for the feedback.
Which entities are exposed from Z2M if I may ask?
1.The lock dosent take the command Auto Relock in my Homey instance.
See here: Nimly Touch Pro - Can't disble AutoRelock - Devices - Homey Community Forum
No fun at all.
Still going strong? I received 2 modules for my 2 locks in January which I’ve had to reconnect batteries on due to the device going offline, mines on FW ver 4.5.24 FW build date 20230211.
Will reach out to Nimly now
UPDATE: Nimly are sending 2 new modules again
i had to update firmware on my conbee III to get it to kinda correctly work with the nimly connect module, it seems to disappear once in a while in logbook
HA’s ZHA
Conbee III
Nimly Connect Module
I have now also got a (third) zigbee module with firmware 4.5.26 with build date: 20240201.
Seems much better. No problems so far.