Hello MakkaKaplar,
How did you achieve to set locks? Is it in HA or as a standalone Z2M? Please elaborate ![]()
Hello MakkaKaplar,
How did you achieve to set locks? Is it in HA or as a standalone Z2M? Please elaborate ![]()
With these changes we can now see the users pincode in the logfile which is horrible.
Not even an admin should be able to see someone elseās password or pincode.
I will ask Nimly to change this. PINcode should be obfuscated inside the lock and attached to the slot number instead.
Thatās why I disabled this entity by default. You can disable it back if you donāt want to see it in the logs.
That said, I was also surprised to see the actual pin code there instead of just a slot number.
I have firmware version 20240529 on my Zigbee modules. Pairing the locks to Z2M went easy and connection is stable, but the batteries seem to drain. If I was to request new modules from Nimly, which firmware version should be on them?
Iāve sent Nimly support an email. Will see what they say.
Note, I didnāt mean to come so strong. The issue is with Nimly. You only present what they allow you to present. ![]()
I also had issues with the battery drain, on sw_build_id 4.5.26. Had to replace batteries every two weeks.
They sent me a new module with date_code 20240625, sw_build_id 4.7.98. This one has no drain issues, batteries last so much longer.
Out of curiosity, āso much longerā what does this equal to? ![]()
I have so far only used our Nimly lock with their gateway. When I got it, the connection with ZHA was too limited. With their gateway I canāt even remember when we switched batteries last time. Itās been more than a year. (however you canāt see battery level in their app). How much worse does it get with connecting it to Skyconnect / HA?
Also, is it possible to have it connected to both their gateway and to HA simultaneously? I have read different answers to this question. Any one here who can confirm?
You can only pair the module to one Zigbee coordinator at a time, so either the gateway or HA.
Too bad. Setting up new fingerprint users is not possible in ZHA right?
And how long is the battery when using zigbee/ZHA?
Mine says:
Firmware ID
4.7.79
20240625
Iām a bit disappointed that there isnāt support for OTA for this card. It seems to work well, but the battery drains a lot faster then my Danalock. Iāve had the Danalock for a year without issues and the battery is till >80%. Meanwhile, I had to replace the batteries twice on my NimlyPro the last 5-6 month. Itās used more then the Danalock, but I still feel itās draining too fast compared to the Danalock or other models I have access to such as the EasyCodeTouch.
Guys, any updates on how to administrate the Nimly lock in HA regarding the codes? Both adding or removing new codes and also, how do you access the codes within HA?
They are available in Z2M.
What is lacking is a database to keep track of the users.
Found " ZHA Lock Manager" in HACS. Unfortunately I do not use ZHA.
The lock manager seemed nice so that was a god darn shame Per Yngve! ![]()
I am also on Z2M.
But how do then manage the Nimly lock in HA for handling codes at this point, or you don“t use HA for Nimly at all?
I donāt have that many users on the lock
Iāve been struggling with this for a few weeks. Iāve not been able to get more than 1 of my Locks to pair with the Gateway and the one I got paired lost its connection after a few days.
But Iāve now managed to get all of them paired with Z2M and so far shows up and working. There was two success factors involved,
Check that your Zigbee Module in the lock has version 4.7.79 (20240625). Versions before this does not work.
Im considering getting a Nimly locjk with the zigbee module and use my unifi doorbells facial recognition with it. Does anyone know how many seconds it takes from unlocking in homeassistant until the lock actually unlocks?
Itās a matter of a few seconds before it responds to a command. Works great.
I would hold off on getting a Nimly lock for a little while. I was in contact with their support a few months back, clarifying their āfakeā 2FA. About a week ago I contacted them again, asking for updates. They told me that they have a new lock coming out where the 2FA is actually 2FA and not just a two different ways to authenticateā¦