Both! The reporting (Last action, Last action source, Last action user and Last PIN code) was there the first few days after finally getting it working, then after around two weeks the whole thing fell out and I had to remove and re-add the battery for it to connect again.
I would be very interested to hear the results of your investigations!
And I’ll definitely put the migrating to Z2M on hold as I understand there are issues with this integration and the lock as well.
Obviuosly it’s the same jævla issues with Z2M as with whatever you’re doing. The two week thing is really a thing here… I just flashed my Sonoff Zigbee Dongle-E to the latest firmware from GitHub - Nerivec/silabs-firmware-builder: Silicon Labs ZigBee firmware builder I will see if that makes any difference at all, and then I’ll go down in the rental appartment (they will tell me when they’re both out for a few hours - I prefer to work alone!) and do the reset and rejoin. So to be continued…
On 2026.1.3 I had no issues with sensors.
Since 2026.2.x I only get updates on locked/unlocked.
I have notices that the quirk ha is using , zigpy.quirks.v2.CustomDeviceV2 for the lock is some kind of “fallback quirk”. There is an actual quirk for the lock , zhaquirks.easycodetouch.EasyCodeTouch, it might be possible to force ha to use this quirk with custom quirks . Haven’t tried it yet
@Vestmarka The result of the experiment is puzzling. I could not get the lock to pair with the IKEA Trådfri where it was, it insisted on pairing with the SONOFF dongle, that did not have the same, good link quality.
So I moved the Trådfri down a floor, to the appartment we rent out, half a meter from the lock. I reset the module (waiting a few minutes until it stops blinking, holding in the button and releasing it when the yellow fast blinking stops). Took the batteries out and put them in again (that’s when it starts pairing after a reset), and I thought I had the jackpot, because it paired. The link quality was great (at least for my system) with 148 instead of less than 100.
I then removed the batteries again while I moved the IKEA Trådfri up to it’s place (which I did so the lock should not connect to the dongle again while the Trådfri was offline), went back down again and put the batteries in. That was an hour ago. And the lock hasn’t shown up on ANYTHING yet, not the SONOFF or the IKEA Trådfri. This is really frustrating! 
Edit: Oh, there is an always join extension for Zigbee2MQTT, but it’s not possible to choose the device to join to, it always goes to “all devices”.
OK, that was weird… Between 14 yesterday and 06 this morning something happened. I have no idea what, but that’s when it surfaced on the Zigbee network again. No idea if it will last, but now suddenly all the devices in the rental appartment are on the IKEA Trådfri repeater instead of the SONOFF controller! 
It’s not because of a reboot or anything like that, I have a scheduled reboot every night at 04, so two hours before this. I did a couple of reboots yesterday too, without any change. They all show the same LQI as the repeater, at the moment 196. I guess maybe Zigbee is even more black magic than I thought… I will use an interview info every half hour to see if that keeps the lock on the network.
I did the update to 2026.2.3 with a glimmer of hope that it would change something back to a working state.
Unfortunately it didn’t, ZHA is still picking up the zigpy.quirks.v2.CustomDeviceV2 quirk even though the file and configuration for the custom Nimly quirk is present.
I can see the last action sensors but they are not updated when the door is unlocked 
Isn’t that ZHA really obsolete now? Z2M does not have any problems with that, for me it’s connectivity, and that is probably not related to Z2M at all. As long as it’s in, I see all the info.
Oufff so I do need to move all my Zigbee devices to Z2M just because of this stupid lock 
Everything else is working perfectly fine on ZHA.
ZHA is definitely not obsolete, where did you get this information from?
@Vestmarka Is there a reason you use custom quirk instead of the upstream one from the ZHA? The quirk I posted here has been merged to zha quirks (zha-device-handlers/zhaquirks/nimly/lock.py at 23015b4507b0913f1604b3d39c1beccf9219cdd2 · zigpy/zha-device-handlers · GitHub) and should work with your lock.
If there is some model missing we can also add it upstream.
@uvnikita I read it on the forum, apparently that was wrong. Sorry.
Hi @uvnikita, I have been fiddling around with this lock as it would not produce the “last action” data.
As shown in the screenshots, if I remove the custom quirk, the sensors become unavailable. If I add the custom quirk however, the sensors look OK, and for a few days before an update it also worked 
How do I install this quirk? (Think of me as a newbie…)
/Fanan
@Fanan Du glemte “spør for en venn”… 
(Norwegian joke also understood by Swedes I assume, sorry, couldn’t resist…)
Her: AI link
I thought I’d share some of my experiences with Nimly. I’ve had my Touch Pro for almost a year now.
It’s connected to Home Assistant via a Raspberry Pi 4 with a ConBee II. At the moment I’m using an IKEA smart plug as an intermediate router, since the Pi 4 is on the other side of the house and one floor up. This setup has been working well for quite some time now.
In the beginning, I tried using one of the Aqara plugs as a router, but that didn’t work. The lock preferred to connect directly to the ConBee II and ignored the Aqara plug.
I’m also on my second Connect Module. I’m not sure what happened to the first one — it just died. I suspect it failed because when you insert it into the lock’s connectors, there’s nothing physically supporting the module. If the door is slammed shut or closed forcefully, the module is exposed to a lot of movement.
When I installed the new module, I added several layers of double-sided tape between it and the PCB to provide support. I haven’t had any issues since then.
Adding tape sounds like an idea, maybe movement of the module can explain some of the stranger problems with this one?
Yes, that was what I was thinking. My door slams quite often and the support on the module was not good, in my opinion.
Im thinking that a small disconnect from one or more of the pins would have the module behave a bit strange. And it was a easy “fix”.
It should sit firmly in the socket
I finally gave up and moved to z2m.
The lock was the first i interviewed in the network. The lock got included ok, sensors showing up. But it still didn’t report sensor updates (5-6 m to the coordinator, only wooden walls). Damn. But I then included an Ikea switch close to the lock, re-interviewed the lock and yes it worked.
I guess it sends a quite weak signal.
