i had issues with dropouts, fixed it by getting a new module from nimly support, i took a screenshot of RSSI etc and showed them it was unstable
been running fine since then (this was around 12th of september)
I resolved this by making an automation that updates the entity every hour. Has not ātimed outā since.
I just paired my lock to Zigbee2mqtt, but i alos have the gateway. Now the lock is offline in the gateway. Does anybody know if itās possible to have it paired to both HA and Gateway? Felt easier to handle users in the gateway then HA.
AFAIK a Zigbee mesh/network can only have one coordinator, and devices can only belong to one mesh, so either HA or the Gateway. Unless the gateway can pair with your HA coordinator? But I doubt that
Would it be possible to integrate with the Nimly Connect Gateway instead of accessing the lock directly using Zigbee. I also believe the gateway blocks accessing the lock as it communicates via Zigbeeā¦
Hi!
Iām not familiar with Mifare, could you share why you think they are insecure?
Update: Paired it with deConz, could see when someone opened with a code. Could not set codes or figure out how to get user info in deConz, might be me not understanding the UI. Might also be the unintuitive UI of deConz, Phoscon didnāt show much at all. It also seems like it disabled my master code after a while, couldnāt figure out why or which command.
So I finally switched my setup to Z2M, as expected I had to downgrade the fw of my conbee II, the sunricher dimmers wouldnāt finish interviewing otherwise.
My current problem is that I canāt connect Nimly to Z2M, there is nothing in the logs.
What I tried:
- Got both a sunricher dimmer and a TrƄdfri repeater within 2m from the door.
- Reset both the module and the lock.
- The manual mentions a 6 digit master code is required for connect, so I set that also.
Suggestions appreciated!
Could you please post your automation?
1 Like
Hmm is this don using Z2M or what?
Just bought and installed this lock but when I unlock I get no on which user (the one I saved code or fingerprint on ) but I donāt seem to get it on my fingerprint (master) anyone else having this problem or just me thinking wrong:-)
What Firmware Version?
Mine didnāt work either. I contacted Nimly Customer Service and they send a new Module that worked. It has FW 4.7.79.
I have
4.7.79 in zigbee2mqtt
Update2:
I replaced myu Conbee II with a Sonoff Zigbee-e, rebuilt the network but the lock still didnāt pair.
After some back and forth with support they sent me a new module which paired instantly, they asked me to send the old one back in a pre-stamped envelope.
Status of the new module:
Firmware build date 20240625
Firmware version 4.7.79
Finally happy customer, can display last unlock user and set codes etc.
I bought one with 4.7.78 which died after 2-3 days.
It disconnected from zigbee after every night and had to take the batteries to reconnect to the zigbee network.
Had it changed in the shop and got one with 4.7.79 which has worked perfectly.
Has build date 20240625 also.
Spoke to Nimly directly and they said they were working on a new one and it would take 2 weeks before they could ship it.
I also have the Sonoff Zigbee Dongle -P but I canāt get my Nimly Code to appear in Zigbee2MQTT. Iām running HA on a RPI4 with the dongle directly connected to one of the USB 3.0 ports. Maybe I need an extension cable?
So i just got the lock, tried to connect to HA. Using ZHA and Sonoff USB 3 dongle. Worked without any problems but only had the basics as lock/unlock. Saw that some had better luck with Z2M so figured id try that, upgraded firmware on dongle before trying and now i cant get the lock to pair at all, not even if i go back to ZHA. And ofc i didnāt check what firmware i had from the start. Anyone got it working with a Sonoff USB dongle 3.0 P and could check what firmware they are using?
I was replacing some batteries in my Zigbee network the other day and thought now I am going to get that Nimly lock module replaced with a newer version to fix the 50% battery bug.
Got a new module today and put it in. Still shows 50% with new batteries.
I read the posts a bit back in this thread but dont quite understand if its something I need to change or if its been merged into the code when we update Zigbee2MQTT.
This is how it shows up now:
Is it something I need to/can do to fix this?
My guess: He is referring to how easy they are to clone and their reliance on UID for authentication.
If you are planning to lock up your pension fund, the defense industry or the national reserve, you would probably want to avoid using the MIFARE tags. But if it is for locking your house, garage or similar; I would assume that any intruder savy enough to clone tags or take advantage of weak encryption would probably have chosen a different career path before visiting your house.
I just created a PR in ZHA that adds the following fields for Nimly locks:
- Last action source
- Last action
- Last action user
- Last pin code
- Auto relock
- Sound volume
1 Like
I was curious about this too, and Iāve actually asked nimly support about that recently. Hereās what they replied:
This is actually a conscious decision on our part, primarily for security reasons. We want to ensure the system canāt unintentionally restrict exit from the inside, which could be critical in certain situations.
That sounds reasonable, especially if for whatever reason the locking command will be executing in a loop, making it difficult to unlock the interior door handle. Or I guess in a case of fire one might be in a state of panic, in which entering the unlocking combination could be problematic. Which is probably why they wanted to exclude a possibility of āunattendedā automatic locking of the interior door handle.
However, they also added this:
Weāll definitely pass your feedback along to our development team. Itās a great suggestion, and exactly the kind of input we value when planning future updates.
So it might be implemented after all, especially if a big enough number of users will request it like I did. So Iād suggest everyone interested in having this feature to contact nimly and let them know about it.