Lock Code Manager - New user code added to inactivate user

🛎️ Get Help
1

Using Lock Code Manager (LCM), I have found a couple of related issues in LCM.
I have existing users that all work and I think the issue is related to creating a new user to be activated at a future date and then later creating another user (while the future user is still not active).

Steps to reproduce

  1. I added a new user (Let's call it John) with a future enable and future disable date, Code: 1111 (example).
  2. I then added another new user (Let's call it Mark) with a different code and this one is Always Enabled, Code: 2222 (example).
  3. After creating the second I was taken back to the list of users. I could see the first new user, John. I could not see the second new user, Mark. I exited LCM and went back into it to find the same.
  4. Issue 1: I then went into the configuration for John and that (currently inactive) user had both the John and Mark codes listed (1111 and 2222). No user Mark was created.
  5. I deleted Mark's code (2222) from John's configuration (clicked on the code and selected "Delete this lock Code". Which was confirmed. When I pressed Next I was taken back to the LCM Existing users list.)
  6. I clicked on John's name and saw that it only had it's original code (1111), which was expected.
  7. Issue 2: I then clicked Done and got the error "Error: Cannot get property 'lockCodes' on null object". Logging showed a similar message: " [error] java.lang.NullPointerException: Cannot get property 'lockCodes' on null object (codeManagement)"

LCM 1.0.0
HE 2.0.0.102
Browser: Chrome 70.0.3538.77
@mike.maxwell

1 Like
2

This is probably unrelated but you never know.
I was getting similar errors adding and deleting codes from the driver detail page...Kwikset 910. After hitting Configure and waiting a minute or so, I was able to add and delete without issue.

3

I have a kwikset 888 and after the 5th code being added the devices stop responding. I have an email into support

4

My Kwikset gets very finicky once the battery goes below 50. Not sure if it's a battery level reporting issue...but a fresh set of AA's usually get me back on track.

5

Yeah my batteries are only a week old.

6

I get all kinds of fun errors when trying to add to my zigbee locks. Hit configure on the devices after the 2.0 upgrade, locks unlock and lock fine. getCodes errors as well on the device itself. These are Yale YRD210's.

[dev:51](http://10.54.25.34/logs#dev51)2018-11-15 10:56:24.911 pm [error](http://10.54.25.34/device/edit/51)groovy.lang.MissingMethodException: No signature of method: com.hubitat.zigbee.Zigbee.swapEndianHex() is applicable for argument types: (java.lang.String) values: [0001] on line 1105 (setCode)

[dev:51](http://10.54.25.34/logs#dev51)2018-11-15 10:56:24.862 pm [trace](http://10.54.25.34/device/edit/51)validateAttributes returning commands list: [zdo bind 0x351D 0x01 0x01 0x0009 {000D6F0002FB7CE9} {}, delay 2000, he cr 0x351D 0x01 9 0 33 0 21600 {} {}, delay 2000, he wattr 0x351D 0x01 0x0101 0x0032 0x10 {01} {}, delay 2000, he rattr 0x351D 0x01 0x0101 0x0012 {}, delay 2000, he rattr 0x351D 0x01 0x0101 0x0018 {}, delay 2000, he rattr 0x351D 0x01 0x0101 0x0017 {}, delay 2000]

[dev:51](http://10.54.25.34/logs#dev51)2018-11-15 10:56:24.854 pm [debug](http://10.54.25.34/device/edit/51)Zigbee DTH - setting code in slot number 1