Attempting to add a user, returns to the LCM app home page with no message and no user added.
Deleted LCM and reinstalled: prior users remained when reloaded, still won't take any new users. Nothing in logs
Make sure to go into each lock device and click configure again. The schema for locks changed according to @mike.maxwell in 1.1.17. It could delete you “name” for each code so make sure to document if you do not know them.
Thanks. Based on your suggestion tried that, but no change.
However, I can add users in the Device's Set Code button, that show up in Lock Manager but don't allow a code number change in LCM
Make sure you have the code length set to the same code length your users are entering. They can be different lengths, but LCM may still be requiring the value to be set in advance, unlike setting the codes directly on the lock.
@mike.maxwell is this requirement still there?
the lock drivers were updated to support variable length codes, LCM doesn't care about the length.
can you send me a screen shot of the lock driver details?, redact any visible codes if need be, or you can pm me the screen shot.
1 Like
@arnb
oh, this is a keypad, not a lock.
these only support a fixed code length of 4.
Were you trying to set codes from LCM with a larger code length?
Just fyi that I have my keypad locks for 6 digits. Worked w/ ST's drivers that way and adding removing users worked fine. Not sure what's going on w/ Hubitat's implementation.
all HA locks have keypads, however a lock is not a security keypads (the centralite alarm keypads)
the centralite keypads have a fixed code length of 4, that's a hardware limitation in the device itself.
Our locks and LCM support variable length codes, however some locks don't support this, and the centralight keypads do not support it.
Ah, I was wondering why there was cross info on the thread about LCM having variable code capability and something about being limited to 4 digits. My mistake ...
No, only 4 digit pins.
Well, somehow we have some screwed up codes in the keypad, we need to clear those out before we can do much else.
This can be done in one of two ways, delete then pair the device again, or I can pm you some code that will do that.
The former you can do at any time obviously, the latter won't be until eod tomorrow at the earliest.
If you decide to re join the device and this happens again, please let me know the steps you did that led to this so I can fix it.
Tried the former method.
- Deleted two virtual keypad devices and Lock Manager app
- Added two virtual Centralite Keypad devices and Lock Manage app
- Attempted to add a user with a 4 digit pin, hit enter
- App did nothing then landed on the Lock Manager Home page
Going back over the logs there is nothing from the Lock Manager and two "warn: messages one from each keypad
dev:1952018-11-15 11:56:48.993 pm warninstalled...
dev:1942018-11-15 11:54:52.465 pm warninstalled...
I'm in the process of moving my ST to HE and am using the virtual keypads to test out things prior to moving the physical devices. At the moment I am waiting on some method of catching the entry and exit delays issued to the keypads, allowing me to issue TTS to Lannouncer that include warning chimes.
BTW my method of doing this in my Smartthings app is to issue a user event with a value containing the reason for the event: ExitDelay, EntryDelay, ExitDelayNkypd, ArmCancel, with a second data field containg the delay time in seconds.
In ST ExitDelay is used with the keypad real exit delay
ExitDelayNkypd is used when arming from anything but a keypad
I've not figured out if non keypad delays in HE are real-system remains unarmed, or simulated-ignoring sensor triggers
Were you entering the pin using the driver? or using LCM.
The lock codes that LCM manages aren't stored in the app, so there isn't any need to delete it.
I'll see if I can duplicate this using two keypad drivers that aren't connected to a real device,
1 Like
I tried with LCM. I can enter users in the DTH that then show on the LCM.
The ui flow in LCM is a bit different than other apps, in that it's a two stage commit. You enter the data, the app then verifies it, if it's ok then it displays the expected results and an action button.
This button (add this lock code) in the example below must be clicked to commit the changes.
The Done button in this context functions as cancel.
We only recently had the ability to rename these buttons, so in the next release they will be renamed, this should make this aspect of LCM less confusing.
This is the same thing I ran into when learning the new UI. When you select your lock as in this example image below, you need to click then click or tap space below the lock name as Mike has just shown you as well.
Until you click below the lock name, this...
Will not look like this...
and that's what you need. Click Add this lock code and then you'll be able to add your users.
I am not at home right now to check, but could have sworn that for some dropdowns anyway, there is an "Update" button below the dropdown list that makes it obvious that you need to do something after you select item(s) in the dropdown. That is not showing up in the locks and pads dropdown. I will check when I get home, but seems like the "Update" button would help in this situation?
Understood, and that's what I did. Just trying it again, and it's working about 75% of the time. Really not sure what's going on, sometimes it simply skips the Add this lock code and lands back on add a new user page.
I do notice after entering the user name, then clicking on the tab key, the cursor does not move into the pin field, actually not sure where is goes and have to click on the pin field. This is with lastest versions of Firefox and Windows 10
I’m using Chrome. Can you try that and see if it’s any more reliable?
