Centralite 3400-D pin length unsupported

Good day everyone,

I just bought a Centralite keypad as it's one of the only supported and documented keypad for the hubitat.

The only keypad available on the German market is the third Gen 3400 revision D (3400-D), that seems to be securer then the American counterparts as it only accepts pins with a length of 6 characters.

Trying to change the length via the driver results in nothing, as it seems to be hard-coded to 4 in the driver code, as stated on the [documentation]. (SecurityKeypads - Hubitat Documentation).

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?

Greetings

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.

2 Likes

Here you are:

fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,0402,0500,0B05,FC05", outClusters:"0019,0501", model:"3400-D", manufacturer:"CentraLite"
traceModel:3400-D
traceSoftware Build Id:unknown 
traceZCL version:01
traceManufacturer:CentraLite
1 Like

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.

2 Likes

A beta version of the Nyckelharpa Centralitex driver supporting 6 digit codes for this device is now available.

How to use

  1. Install Nyckelharpa from production Github
  2. Install Centralite driver from Beta
  3. Must Use Lock Code Manager 6 digit pins. (Nyckelharpa pins currently not supported for this device)

Without knowing the device's capabilities, it was setup similarly to an Iris V2 allowing for arming with or without a pin, assuming the device's hardware/firmware allows this option.

1 Like

I'll try to answer anything I got from the "documentation" and my observations.

  • It has two CR123A lithium batteries inside.
  • It has a temper switch on the back
  • Keeping the A button pressed is used to "reconfigure the proximity sensor"
  • The B button is has no function if not given by the driver by default.
  • All icon buttons are being activated by first pressing an icon button and then entering the 6-pin code. The keypad then executes it.
  • Documentation states that: the house button is used to set the alarm system to "at home" or "night" depending on the time.
  • Documentation states that: the running or away button is used to switch the alarm system to away
  • The alarm key arms or disarms the alarm system (it acts like that on on hubitat with the default centralite driver) so this like an arm on/off switch

I bought if from Telekom Germany, from their smart home store, as it was the only centralite vendor I could find that ships to germany: Centralite Security Tastenfeld kaufen | Telekom

They state on the store page that the keypad has four states - but this might be limited to their hub:

  • at home - deactivated alarm
  • at home - activated alarm
  • away - deactivated alarm
  • away - activated alarm

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 for the issues. I did an update to the beta Centralite driver a couple of hours ago that may improve your experience.

Please check the error log and post any errors from the Centralitex beta driver

Please review the device's event log for "codeEntered" events. Anything?

Need to determine how it's operating: status followed by pin or pin followed by status. Try each of the following, check the log, try the next test

  • Press the Home icon key, no pin
  • Press Home then a 6 digit pin
  • enter 6 digit pin (no icon key)
  • enter 6 digit pin, then press Home

These are mainly hardware tests, not too concerned about the driver.

It does not handle 6 dight pins

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

Using an updated driver, I successfully added and stored Lock Code Manager 6 digit pins.

Please update the Centralitex driver from the Nyckelharpa Beta repo, test, and post any log errors or issues.

After installing the driver, the device's pin manager flag must be set ON to use HE's Lock Code Manager pins.

1 Like

@mike.maxwell
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.

1 Like

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...

2 Likes

Hello, I'm sorry for the delay.
I didn't forget the topic and will update with more detail on the latest drivers shortly!
Thank you, for the great support.

1 Like

Hello; I'm finally back.

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.

Nothing happens:

dev:213 2021-01-31 18:11:30.890 debug --- Will become inactive in 10 seconds
dev:213 2021-01-31 18:11:30.885 debug --- Motion Detected
dev:213 2021-01-31 18:11:30.881 debug Parse entered catchall: 0104 0501 01 01 0040 00 A786 01 00 0000 07 00

This disarms the home and sets the armMode and HSM to "disarmed":

dev:213 2021-01-31 18:58:07.752 debug disarm entered
dev:213 2021-01-31 18:58:07.738 debug disarm entered
dev:213 2021-01-31 18:58:07.610 debug sendRawStatus info 0000 to device...
dev:213 2021-01-31 18:58:07.607 debug Entering sendStatusToDevice armModex: disarmed, Device.armMode: disarmed
dev:213 2021-01-31 18:58:07.582 debug In setmodehelper armMode: disarmed delay: 0
dev:213 2021-01-31 18:58:07.578 debug setDisarm entered
dev:213 2021-01-31 18:58:07.547 trace entered acknowledgeArmRequest armMode: 0
dev:213 2021-01-31 18:58:07.531 trace pinStatusSet entered: message null
dev:213 2021-01-31 18:58:07.493 trace createLmCodeEntryEvent entered keycode: 000000 armMode: 0 lmMap: [isValid:true, isInitiator:false, code:000000, name:danir1, codeNumber:1, armMode:0]
dev:213 2021-01-31 18:58:07.472 debug lmPins entered 3400-D [raw:catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 00 00 000630303030303000, profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:923D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 06, 30, 30, 30, 30, 30, 30, 00]]
dev:213 2021-01-31 18:58:07.468 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 00 00 000630303030303000

The keypad beeps with the deep "denial" sound, but it won't send anything to the hubitat:

dev:2132021-01-31 18:13:15.778 debug --- Will become inactive in 10 seconds
dev:2132021-01-31 18:13:15.773 debug --- Motion Detected
dev:2132021-01-31 18:13:15.769 debug Parse entered catchall: 0104 0501 01 01 0040 00 A786 01 00 0000 07 00

The keypad beeps with the deep "denial" sound, but it won't send anything to the hubitat:

dev:2132021-01-31 19:02:32.065 debug --- Will become inactive in 10 seconds
dev:2132021-01-31 19:02:32.058 debug --- Motion Detected
dev:2132021-01-31 19:02:32.043 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 07 00 

I've also found a new documentation about the 3400-D: Click me
Interesting information in it includes that keeping the A and B button pressed for 3+ seconds activates the panic mode.

This is what happens when "Enable Panic Key" in the drivers is enabled:

dev:213 2021-01-31 19:12:13.489 debug --- Will become inactive in 10 seconds
dev:213 2021-01-31 19:12:13.486 debug --- Motion Detected
dev:213 2021-01-31 19:12:13.483 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 07 00 
dev:213 2021-01-31 19:12:11.086 debug beep entered: 255 true
dev:213 2021-01-31 19:12:11.082 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 04 00 
dev:213 2021-01-31 19:12:07.094 debug --- Will become inactive in 10 seconds
dev:213 2021-01-31 19:12:07.090 debug --- Motion Detected
dev:213 2021-01-31 19:12:07.086 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 07 00 

This is what happens when "Enable Panic Key" in the drivers is disabled (the beep command disappears but still makes a sound on the keypad):

dev:213 2021-01-31 19:14:00.048 debug --- Will become inactive in 10 seconds
dev:213 2021-01-31 19:14:00.037 debug --- Motion Detected
dev:213 2021-01-31 19:14:00.033 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 07 00 
dev:213 2021-01-31 19:13:57.380 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 04 00 
dev:213 2021-01-31 19:13:53.016 debug --- Will become inactive in 10 seconds
dev:213 2021-01-31 19:13:53.013 debug --- Motion Detected
dev:213 2021-01-31 19:13:53.007 debug Parse entered catchall: 0104 0501 01 01 0040 00 923D 01 00 0000 07 00