When typing in pins in the keypad though, nothing happens until I enter two more random characters after the 4-characters length pin I can set in hubitat, because the keypad requires me to type in 6 characters before executing any command.
Could you please fix this behavior and actually let the user decide what code length the keypad transmits via the already existing setCodeLength option in the device driver, so that users of this and other versions can use their keypad like it is supposed to?
Can you replace the current driver with the driver named Device, then open live logging, then click getInfo in the driver.
Please past the log line that starts with fingerprint.
We might be able to accommodate the 6 pin code length for this specific device.
I'm setting up a beta version for this device using Nyckelharpa's Centralitex keypad driver. The device looks similar to the original Centralite/Xfinity 3400, but that does not mean it operates in the same manner.
Please provide the following information should you know.
The icon buttons on top correspond to Alarm Status: Home, Away, Night and: do, optionally, or do not require a pin code to arm.
Off/Disarm is set by entering a pin code without an arming code
The A / B buttons do nothing, or they configured for a Panic response.
The batteries are 2 CR123A Lithium
Should you have links to the documentation or where to purchase this device, that would help. Can't find anything for this device.
I've tested the beta driver, but the keypad seems to be lost when typing in a code.
First, setting a new pin code doesn't seem to apply it on the key lock.
Second, when testing with an already programmed code, the device gets starts blinking after it accepts it and then doesn't respond to any other pin code entries.
When using the build in centralite driver, this won't happen.
Sorry I missed this. It's operating like a Centralite with 6 digit pins.
Please test with the latest beta version and report any errors
That varies from how a USA Centralite keypad functions. The Centralitex driver does have an option for the Iris V2 (made by Centralite) to set the "partial" aka Home icon to set Night or Home mode, but not by time.
It appears the Bell icon is the Off key similar to an Iris V2
I've successfully software tested my beta version of the driver using a virtual 3400-D with 6 digit pins, setting pins with LCM, and arming the system. The test used two new commands: One to set the model, the other to enter the HSM status and pin. I'm currently running the beta version with an Xfinity, Iris V2 and Iris V3. A close contact uses the production driver version with a "Universal Electronics Inc", model: "URC4450BC0-X-R".
However, without a hardware 3400-D device, I'm only guessing how it actually operates, although it's likely closer to a Centralite 3400 than the Iris 3405-L badged Centralite.
I contacted Centralite in the USA, they said the 3400-D was a proprietary model, and it's no longer in production. It is available on the amazon.de site, but for more than I want to spend.
I'm still waiting to hear from the OP. Should you find info about the message formats, kindly forward or post the link.
past experience with centralite OEM devices has shown little difference between any of the -x variants in terms of functionality, my guess would be it's exactly the same as the 3400 or 3400-G except for the updated pin code lengths.
The 3400 (Xfinity 3400-X Keypad) and 3400-G (CentraLite Generic) are covered under our Centralite Keypad driver currently...
I do have someplace kicking around the software technical requirements from centraLite for the 3400 series, I did not find them particularly helpfull in building our drivers...
One thing I noticed: When connecting the keypad for the first time and trying to configure it using the "Configure" button on the "Centralitex Keypad" driver, it won't do anything and the antenna icon on the keypad keeps blinking, signaling an ongoing pairing process (see here).
One way I could configure the device was using the hubitat "Centralite" device driver to pair and then to switch to the "Centralitex Keypad" driver. I'm using driver version 1.0.5 btw.
Now that all of this is working, I can give you the logs for different actions.