Cannot add user codes to Kwikset 912 Zigbee

🛎️ Get Help Devices
1

I did a factory reset on 3 Kwikset 912 ZigBee locks. The locks were working fine and the reason I needed to reset them is a whole other story.

2 of the 3 locks paired immediately and I was able to add the users back. The 3rd lock pairs immediately but will not accept any user codes from either Lock Code Manager or from the device screen. I have performed a factory reset multiple times to no avail. The lock is within 10 feet of the hub although the other 2 were paired in place with one being 55 feet away. I can add the users manually on the lock but Lock Code Manager will not update the codes from it.

Any suggestion on other steps I might take to solve this?

Thanks in advance for any help.

2

Update, I have performed a soft reset and restore with no luck. This lock is paired to a C7 and I have reset and paired to a C5 and still no luck.

3

Did you try hitting “configure” on the device page? It should be automatic when pairing the device, but perhaps something went wrong. Also, I have found that it doesn’t really matter that the lock is close to the hub. It is still very likely that it is not directly paired. You can check http://hubIPaddress/hub/zigbee/getChildAndRouteInfo
It will be listed as a child device if it’s directly connected.

image
image1170Ă—2532 655 KB

You can see that one of my kwikset locks is a child device, which happened when I had the breaker off while remodeling the master bathroom, which took down a couple repeaters for several hours.

You could also try installing another instance of LCM. Perhaps something fubared the app which I don’t believe would be fixed with a soft reset.

4

Thanks. I did try hitting configure and it is not listed as a child device. I tried a new LCM yesterday and that did not help.

If I lock or unlock from the device page the lock responds immediately but if I lock or unlock at the lock the device screen does not update. I'm thinking it may been a routing or pairing issue.

I'm also seeing and error in the logs when I try to add a user but I do not understand what the error is about.

dev:11862021-06-29 12:14:37.185 pm errorjava.lang.IndexOutOfBoundsException: toIndex = 6 (parse)

dev:11862021-06-29 12:14:37.175 pm debugparseCommandResponse: [raw:catchall: 0104 0101 02 01 0040 00 097F 01 00 0000 06 01 0100FFFF00, profileId:0104, clusterId:0101, clusterInt:257, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:097F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[01, 00, FF, FF, 00]]

dev:11862021-06-29 12:14:36.645 pm debugparseCommandResponse: [raw:catchall: 0104 0101 02 01 0040 00 097F 00 00 0000 04 01 00, profileId:0104, clusterId:0101, clusterInt:257, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:097F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]

dev:11862021-06-29 12:14:29.381 pm errorjava.lang.IndexOutOfBoundsException: toIndex = 6 (parse)

dev:11862021-06-29 12:14:29.370 pm debugparseCommandResponse: [raw:catchall: 0104 0101 02 01 0040 00 097F 01 00 0000 06 01 0100FFFF00, profileId:0104, clusterId:0101, clusterInt:257, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:097F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[01, 00, FF, FF, 00]]

5

That sounds pretty likely. It seems like it isn’t getting configured properly. You might try taking it near one of the locks that is working correctly and pair it there which may or may not eliminate the problem repeater. It’s things like this that drove me to buy a second hub. The bulbs and other less reliable repeaters are on one hub, and only end devices (Zigbee sensors, buttons, locks) and grade A repeaters on the other. No issues like this since.

6

Is it listed below that in one of the routes?
Or you could try killing the power to nearby repeaters and hopefully forcing it to join as a child device. You would probably have to reset and rejoin it again.

7

No it is not nor are the other 2 that are working fine. In thinking about this all of my main powered ZigBee devices are in the front of my home where the working locks are. I'll try moving the lock to these areas for pairing and see what happens.

1 Like
8

Without going into a long response I too am moving some ZWave devices over to a C5, mainly chatty energy reporting devices and this led to me resetting these locks that started the problem.

1 Like
9

Make sure the hubs are using different Zigbee channels if you haven’t already.

1 Like
10

I've disabled the Zigbee on the C5 as it will only have zwave devices.

1 Like
11

You could always enable it and put this one lock on it if the hub isn’t too far away. Then if one hub crashes you still can unlock a door. Mine is perfectly happy as a child device.

1 Like
12

Problem solved. Not sure if it was the location or LCM. I deleted LCM and moved the lock to a new location. Things were still failing for a brief period and about 45 minutes later I went back and the lock had a bunch of random garbage for users. I was able to delete one so I tried to add a new one and was successful. I went over to LCM to see if that updated and had forgotten I deleted it. I added it back and it updated correctly.

In any event the problem has cleared up. Thank you Ken for the time you spent with me. I owe you one.

1 Like
13

Glad I could help and glad it’s working now.

2 Likes
14

@scunny , @Ken_Fraleigh

So I wanted to chime in here because I just had the exact same error. In my case my batteries died in the 912 w/Zigbee module and when I replaced them I could not set codes / receive events (unless refreshing) but I could lock/unlock.. very frustrating and strange.

I am fairly confident I have a strong ZB mesh in that area but added another repeater (old iris outlet with just the ZB part no ZW) just in case. That did not work.

Tried excluding, resetting, repairing - even switched to another C-5 hub temporarily and STILL got the error. Rolled back firmware to 2.2.7.128 to see if that worked - nope. Even switched the lock over to Home Assistant (deCONZ with conbee2) for a test and that too proved ineffective..

After giving up I re-paired back with the original hub thinking I would limp along until I purchased a Yale replacement - After pairing (still error) I pulled the battery pack, waited a few seconds then put back in. On a whim pushed in and held the programming button (below the "A" button). It beeped at me once or twice and lo and behold a little while later things started working again..

I suspect somewhere in my machinations I may have inadvertently enabled the "master key code" entry and wonder if that was causing the issue or pulling the battery pack that last time or a combo of both.

Anyway things are back to "normal"..

15

Just an additional thought, I have three Kwikset 914 Zigbee locks. I'm guessing the electronics are the same. Two of my locks went in without difficulty. The third caused me no end of grief. In the end a fesh set of batteries, replacing the "new" factory batteries, solved the problen.

16

My issue occurred immediately after I replaced the batteries with fresh ones..

What I suspect happened was it took a little more time then expected for it to fully reconnect and I being far too impatient messed with something (like accidentally activating the master key code) and that caused further grief...

1 Like
17

Sounds a little like the click, click, click mouse thing. Not realizing that the system is remembering all of those clicks. and will "slowly" wait to execute all of them. :wink: I wish I could say I'd never been there, done that.

1 Like
18

It is a lot rarer these days for the issue to be with the hub or device as much as I want to blame those things... mostly my tinkering or screwing up somehow. Pretty much my life story.. just ask my teenager. :roll_eyes: :rofl:

3 Likes