Lock manager stops after 4 keycodes

[endorphin_junkie]

When I try to add a 5th keycode it returns to the main screen with no error message, but also no new keycode user. It just quietly does nothing.

Because Hubitat has hardcoded 4 as the keycode length for keypads (you transmit a 4 when I entered a 6) you're forcing us to have twice as many keycodes since we use longer keycodes on the locks... but even if we only had 1 keycode each I need 6. Since you force us to use 4 digits codes for keypads, we need 12 different keycodes.

[mike.maxwell]

@endorphin_junkie

Since you force us to use 4 digits codes for keypads

This is a built in limitation of the centralite and iris keypads, not a Hubitat issue.

[aaiyar]

@mike.maxwell

This is a built in limitation of the centralite and iris keypads,

This is at least the third time you've had to point that out in the last couple months ....

[bcopeland]

I mentioned this in another thread.. Like Mike just said it’s not a limitation of HE it is a device imposed limit.. TBH this is the biggest missing product of the DIY smart home market right now.. No one is currently manufacturing keypads (besides proprietary) .. I actually have been debating making this..

Centralite keypad

It was my understanding that these devices had a fixed 4 digit code length.. I don’t think this can be changed.

[bcopeland]

I found the parts / Chinese manufacturing facility to reproduce in mass.. I want to make one that looks / functions like a hardwired alarm system.. With a LCD screen for status info, etc..

[endorphin_junkie]

This is a built in limitation of the centralite and iris keypads, not a Hubitat issue.

Are you certain? I ask because the code accepts a value, but then sends out a 4 in the transmission. Are we certain it's not a code limitation?

This is at least the third time you've had to point that out in the last couple months ....

That would likely be due to an interface that offers to adjust the code length, accepts a value, and does not provide feedback that the value would not be accepted. It does not appear to the user that they've chosen an invalid value -- it reads like a bug in the software: "I submitted a 6, but it says it successfully set it to 4..."

[bcopeland]

@endorphin_junkie

Are you certain?

You are replying to someone who has worked on the code you speak of and the drivers... He is probably certain..

Plus I have had this hardware on 3 smart home platforms.. The limit was always 4

[mike.maxwell]

@endorphin_junkie

it reads like a bug in the software: "I submitted a 6, but it says it successfully set it to 4..."

Fair point...

[endorphin_junkie]

@bcopeland

You are replying to someone who has worked on the code you speak of and the drivers... He is probably certain..

I knew that. I probably phrased it poorly, but it was mostly a lead-in to the next statement about the UI. "Because if you are certain..."

[SmartHomePrimer]

Ring has their Z-Wave keypad. It just needs to be made to work with HE.

[endorphin_junkie]

@endorphin_junkie

When I try to add a 5th keycode it returns to the main screen with no error message, but also no new keycode user. It just quietly does nothing.

For the record this problem disappeared in the lastest hub upgrade. Thank you, whoever fixed this! (assuming Mike?)

@mike.maxwell would you possibly entertain automatic truncation for devices with limited sizes, so that we don't have to create lock codes at two different lengths as if they were completely different identities? It doubles the user list not just in LCM but also in every rule...

[anon61068208]

@endorphin_junkie

4 digits codes for keypad

I absolutely despise this limit also but for now it is all we have that is usable in HE. We need better keypads, both zwave and zigbee, that are much more flexible.