If you have the same module as I did, you have to press and hold the small button on the Zigbee module.
As mentioned in my previous post, I did not have success with this. I have tried with two modules. I even purchase the Nimbly Gateway with the hopes to get it firmware updated that way, but also without luck.
Yeah Iāve been trying that a lot of times now on three different modules.
The orange led starts to blink rapidly and I release.
Do you know if yours started to blink slowly on the orange led after resetting?
Where you very close to your Zigbee coordinator? Iām trying when Iām very close to the closest powered node in my network.
Iāve noticed this as well on one of my (two) locks. This one (that disconnects) is idle quite often (meaning little to none zigbee actions and perhaps opened once every 2-3 days), which might have something to do with it? Pulling the batteries and reinserting them reconnects it to the network tho.
If you hear back please let me know, preferably there would be an OTA that we could flash which is the least hassle.
I got mine to connect, Iām feeling a bit stupid right now.
I didnāt think that it made any difference in having the outside and inside part connected when trying to pair. But as soon as I connected them the zigbee module started to behave as per the installation manual.
Hopefully this post might at least reduce time spent for someone else.
Iām still struggling with getting the locks to connect. I have done the whole procedure with removing the batteries, taking away the cover and pressing the reset/connect ? button on the module.
Deconz actually sees the connection trials but does nothing further, ie I still canāt seem to get it connect properly and I canāt see the device in HA.
Iām pasting the log if anyone can see where we go wrong. After the below, nothing more interesting happens in the logs.
deconz | 19:56:57:136 set fast probe address to 0xF4CE3674F125398B (0x1610)
deconz | 19:56:57:136 FP indication 0x0000 / 0x0013 (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:57:136 ... (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:57:136 device announce 0xF4CE3674F125398B (0x1610) mac capabilities 0x80
deconz | 19:56:57:136 DEV Tick.Join: event/device.anounce
deconz | 19:56:57:137 DEV Tick: fast poll 0xF4CE3674F125398B, mac capabilities: 0x80
deconz | 19:56:57:599 FP indication 0x0104 / 0x0000 (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:57:599 ... (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:072 [1] get node descriptor for 0xf4ce3674f125398b
deconz | 19:56:58:072 ZDP get node descriptor for 0x1610
deconz | 19:56:58:243 ZCL attribute report 0x086BD7FFFEB6B305 for cluster: 0x0B04, ep: 0x01, frame control: 0x08, mfcode: 0x0000
deconz | 19:56:58:424 FP indication 0x0000 / 0x8002 (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:424 ... (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:424 ZDP indication search sensors 0xF4CE3674F125398B (0x1610) cluster 0x8002
deconz | 19:56:58:424 ZDP indication search sensors 0xF4CE3674F125398B (0x1610) clear timeout on cluster 0x8002
deconz | 19:56:58:430 [2] get active endpoints for 0xf4ce3674f125398b
deconz | 19:56:58:431 ZDP get active endpoints for 0x1610
deconz | 19:56:58:570 FP indication 0x0000 / 0x8005 (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:570 ... (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:570 ZDP indication search sensors 0xF4CE3674F125398B (0x1610) cluster 0x8005
deconz | 19:56:58:571 ZDP indication search sensors 0xF4CE3674F125398B (0x1610) clear timeout on cluster 0x8005
deconz | 19:56:58:577 [4.1] Get model ID
deconz | 19:56:58:577 [4.2] get basic cluster attr 0x0005 for 0xf4ce3674f125398b
deconz | 19:56:58:660 FP indication 0x0000 / 0x8005 (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:660 ... (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:660 ZDP indication search sensors 0xF4CE3674F125398B (0x1610) cluster 0x8005
deconz | 19:56:58:666 wait response fastEnddeviceProbe() 0xF4CE3674F125398B, elapsed 89 ms
deconz | 19:56:58:871 ZCL attribute report 0x00124B000EE9B139 for cluster: 0x0702, ep: 0x01, frame control: 0x18, mfcode: 0x0000
deconz | 19:56:58:899 FP indication 0x0104 / 0x0000 (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:899 ... (0xF4CE3674F125398B / 0x1610)
deconz | 19:56:58:899 Clear fast probe timeout for cluster 0x0000, 0xF4CE3674F125398B
deconz | 19:56:59:474 DEV no DDF for 0xF4CE3674F125398B, modelId: NimlyPRO
deconz | 19:56:59:474 DEV create on-the-fly DDF for 0xF4CE3674F125398B
Only blue light, no orange happens when the two lock parts (outdoors, indoors) are not connected.
They must be connected for pairing to happen.
For me pairing at power on is working reliably, but the lock always looses contact after being idle for a few hours and needs to be powered off and paired again.
Iām also struggling with pairing the lock.
Iām running zigbee2mqtt using a Sonoff ZBDongle-E and have other devices like Sonoff temp/humidity sensors working fine.
Canāt see anything about the lock in the logs at all.
Both blue and yellow are blinking when I insert the battery.
[Update] My problems were solved by replacing the Connect module with a new one.
(I did not have issues pairing initially but the pairing was always lost after a few hours and had to be redone)
Unfortunatly Nimly customer support does not want to tell me if the new module has a newer firmware or not, so I canāt tell if the problem in my first module was a firmware bug or some really odd hardware issue.
It is possible to read out the moduleās firmware version (or rather the firmwareās builddate) from Z2M - under the āAboutā tab for the lock.
The versions I know and have tried are:
20220614 - Works with Z2M
20230210 - Works with Z2M
20230530 - Does NOT work with Z2M
20230530 - Does NOT work with Z2M
Thatās interesting, but that means it was still found by z2m then?
I get absolutely nothing from my lockā¦
Ok so I can confirm then that 20230210 works for me. I donāt have the energy to take the lock apart again apart and put the not-working module in and check its build dateā¦
Yes, it was found by Z2M but not correctly paired. It was not possible to read lock status or change settings from Z2M. But it recognized manufacturer, build date etc.
Wow ok I got it working now! It was a newbie mistakeā¦ Apparently my walls are too thick for the Zigbee signal because now that I moved the Zigbee stick to the same room the lock was immediately found and seems to be working. Signal strength is 116 lqi with 2m distance which seems a bit low? But it will probably be fine when I add more nodes to the network.
My firmware is 20220614.
My lock with module firmware
20211118
works. We have used the lock for over a year, but I just recently reinstalled the bluetooth/zigbee module because we initially had battery drain and connection problems. It works flawlessly now, I guess some Z2M update fixed it 
What is your setup?
230210 gives me Unsupported Device in Z2M, however identifies unit as NimlyTouch
Anyone having the connect gateway? Possible to configure the lock with the nimly app and simultaneously control it using Home Assistant (via ZHA or Z2M)?
Can you share how you did that?
Hi Adnan, do you mean the battery part or the sound volume part?
Iāve been in contact with Nimly tech who claims that the HW does not accurately detect the battery levelā¦ just when it becomes critical. Iāve yet to establish if I get any meaningful measurement out of the lock at that point.
Thanks.
I was also wondering about the volume change using development tools. Do you have a snippet for that? Perhaps you could also add codes and remove codes using development tools?