Lock Events: unlocked by unknown codeNumber: null

🛎️ Get Help
1

Was excited to see that the code reporting was added to the 114 update. But for me, it's not working properly.

Lock was unlocked by unknown codeNumber: null

It appears this lock isn't working at all, again. Was working before the update, is clearly reporting something to the hub, but the hub cannot control the lock at all, and the getcodes command is not working either. The hub continuously thinks this lock is unlocked at this point. This happened before, once I got the crashing of my hub sorted out, it started working fine (ghost nodes deleted, I think solved that). Now that it's not working I'm concerned I'm in for another round...

It appears it's lost it's * zwaveSecurePairingComplete: true

Also saw this in the logs, when using GetCodes
maxCodes is not set, unable to get any of the device lock codes
zw device: 37, command: 9881, payload: 00 80 03 64 parsed to ['name':'battery', 'unit':'%', 'value':100, 'descriptionText':REDACTED battery is 100%]

2

What brand and model is your lock?

3

Kwikset 910z

4

my 910 seems to be working properly

5

I have two. Only this one has ever been a problem, the other works perfectly without fail. But it's been a consistent PITA on HE. I'm reticent to replace it because it worked 100% on ST.

6

I have a total of three of these 910's, two in production and one in the lab.
They are all working as expected, I've not had any issues getting or keeping them paired.
Also, my production hub is the one that gets all the pre release builds, so it gets rebooted quite often.
I don't know if there's something up with the lock itself, the location of the HE hub, or some other interference related problem.

1 Like
7

I’m leaning toward replacing it. It’s been too much trouble. Your’s and others’, and my own other lock... it’s got to be the device itself with the problem. It’s proximity is more choice than the one that works reliably. Damnit these are pretty expensive.

Thanks all.

8

Have you looked into just replacing the zwave module?
https://www.ebay.com/sch/i.html?_nkw=kwikset%20zwave%20module&ssPageName=GSTL

9

@doug in line with what @mike.maxwell suggested, maybe start by swapping the zwave module? If the problem follows the module, then you can pursue replacement. On the other hand, I've also seen where the swap of a something fixes it. You end up assuming that it wasn't plugged in well. The pins sliding out and back in "cleans" the contact and it starts working.

10

Hmmm, I had no idea I could do that. I will investigate that and csteele's line of thinking. Thanks for the advice.

11

BTW, the lock is behaving better today. Configure/Save button dance brought back codes. Taking a few clicks to get all the codes back.
zwaveSecurePairingComplete: true is still missing though.