CentraLite Keypads

No. nothing in live logging. And when I look at the smartapps installed on my phone, it lists about 40 (yes 40) instances of “3400-x Keypad Manager”.

Okay. I stumbled through getting everything deleted related to the keypad, including the 40 instances of the smartapp installation.
Could you do me one favor and list links to current device handler and smartapp for the keypad?
I do love being able to use the IRIS keypad and it worked beautifully before SHM crashed. Thanks in advance!
Brian

I spoke too soon. The device manager works but the smart app will not. I can set the lock/unlock codes via the device manager in the API (if that makes sense) but the app on my phone will not work.

It doesn’t. I’m not aware of a way to set that in the IDE (assuming that’s what you mean). The device handler doesn’t have a place to set the code. Only the smart app does. Maybe try it without the Keypad Manager app and use the Lock Code Manager instead. If it works with LCM, then its my smart app that’s not working.

I can’t reproduce this issue. Might be an Android app issue. I’ll dig out my Android tablet later today and try to reproduce it there.

I’m attaching two screen shots. One of my phone showing the keypad installed. One of my API device handler for the keypad. Strangely, it looks different today. What is on the screen shot is not what I saw yesterday. Yesterday I had the ability to set and change the keypad code. Today I don’t. Yesterday the keypad worked to change the SHM mode. Today it doesn’t. When I try to add the smartapp to the device, the name “Centralite Keypad” appears on my list of available smartapps. “3400-x Keypad Manager” does not appear. Although it does appear on my list of smartapps in my phone. STRANGE!


I would not try to change any settings from the IDE. Just copy and paste the code into the IDE, save and publish. Nothing else needs to be done in the IDE. The rest of the setup needs to be performed from the ST app. The 3400-X app should appear in the Marketplace under “My Apps” once you’ve saved and published it. Install it from there and you should be prompted to set your preferences including PIN.

1 Like

Tried just about everything my little mind could handle. The keypad smartapp WILL NOT publish or be listed on my available apps. Just does not work. I tried two other phones thinking it would be that but nope. The device handler seems fine. Any other help?

I wish I could offer more help. If it published and there weren’t any errors when doing so, it should show in Marketplace, under the SmartApps tab, in the My Apps category. Otherwise you might have to see if support will give you a hand.

Any chance of adding support for the panic button?

1 Like

First post and new to SmartThings. Hoping to get a little help (no – a bunch of help) on setting up the Iris keypad with Smart Home Monitor.

edit - Figured it out / I think

1 Like

Having an issue getting an iris keypad (3405-L) to configure. Adding the DH and SA have no issues, but after pairing the device, I get temperature and battery, but the network light just keeps blinking.

Looking at the logs, configure is being called, and the device replies with a bunch of unhandled messages:

bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:46 PM: debug Received battery level report
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:46 PM: debug Parsing 'read attr - raw: E54B0100010A200000201C, dni: E54B, endpoint: 01, cluster: 0001, size: 0A, attrId: 0020, result: success, encoding: 20, value: 1c’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:46 PM: debug TEMP
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:46 PM: debug Device: read attribute response: catchall: 0104 0402 01 01 0140 00 E54B 00 00 0000 01 01 00000029620A
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:46 PM: debug Parsing 'catchall: 0104 0402 01 01 0140 00 E54B 00 00 0000 01 01 00000029620A’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:45 PM: debug Unhandled profile-wide command: catchall: 0104 0001 01 01 0140 00 E54B 00 00 0000 07 01 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:45 PM: debug Parsing 'catchall: 0104 0001 01 01 0140 00 E54B 00 00 0000 07 01 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:45 PM: debug Unhandled profile-wide command: catchall: 0104 0402 01 01 0140 00 E54B 00 00 0000 07 01 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:45 PM: debug Parsing 'catchall: 0104 0402 01 01 0140 00 E54B 00 00 0000 07 01 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 3B 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Parsing 'catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 3B 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 3A 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Parsing 'catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 3A 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 3C 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Parsing 'catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 3C 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 38 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Parsing 'catchall: 0000 8021 00 00 0040 00 E54B 00 00 0000 00 38 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Unhandled profile-wide command: catchall: 0104 0500 01 01 0140 00 E54B 00 00 0000 04 01 00
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:38 PM: debug Parsing 'catchall: 0104 0500 01 01 0140 00 E54B 00 00 0000 04 01 00’
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:33 PM: trace Method: refresh(): [st rattr 0xE54B 1 1 0x20, delay 100, st rattr 0xE54B 1 0x402 0, delay 100, raw 0x501 {09 01 04 0000}, send 0xE54B 1 1, delay 100]
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:33 PM: trace Method: sendStatusToDevice(): [raw 0x501 {09 01 04 0000}, send 0xE54B 1 1, delay 100]
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:33 PM: trace Arm mode: null
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:33 PM: debug Sending status to device…
bb44c688-4b9a-4bf8-94d6-34e283b89a20 12:41:33 PM: debug Configure called for device Centralite Keypad.

After this, refresh or configure from the device in the smartthings app gets updated status, and the IRIS LED matches the status of SHM (Red for armed, green for disarmed), but no code entered events are ever sent or received.

Any idea on what I can do here to get the keypad working correctly?

I think I’ve got a fix for the configuration / constant blink issue.

I figured it was a issue with how the configure() call was setting up the bindings and CIE info, so I found similar code in the configure() method for an official smartthings centralite motion sensor, just with bindings to different clusters.

After porting over the configure() code, and changing the binding clusters to be correct for this keypad (500 and 501), my keypad configures properly and functions. I don’t see much difference in how the bindings are done between the 2 though. The official SmartThings DTH uses device.hub.zigbeeEui instead of device.hub.zigbeeId, and the bindings and reporting timings for temperature and battery are placed next to each other.

My code is at

and I’ve submitted a pull request to Mitch Pond’s github as well, for those that are having the issues with the constant blink.

Are we talking about a bug or an unexpected feature? :wink:

@zcorneli Not sure what you did but finally I got my keypad to work! For some reason it does not light the right buttons but that is less of an issue than not working at all, woohooo! :smiley:

@klash If you watch the logs in live logging, it should tell you at least what its trying to do. Then you can figure out if its at least attempting the right thing. I think the status should normally follow SHM.

I’m currently working on getting arm, disarm, and entry/exit delays through SmartAlarm (I know, no longer supported, but the code’s still available, and still a good base!). Would still use User Lock Manager for code management (For now), and then SmartAlarm for the panel status.

Currently available on my github (master branch) should be working panic button and tamper switch, both exposed as a “button” capability (button 1 push is panic, button 2 held is tamper)

2 Likes

@zcorneli Sorry for not being so clear. I bought one of these panels back in October but haven’t gotten it to work until I tried your code for the device handler, I have a X-3400 Centralite keypad. I am using User Lock Manager as smartapp to handle multiple PINs.

As for the comment about the buttons, I have now read that the device handler has arm, stay, night and disarmed while SHM only has three. I like the night symbol better than the stay one so I changed so that stay status is shown as night. It feels more intuitive to me since my routine is called Good night.

1 Like

Hi All, can anyone walk me through how to setup the delay time in the Iris CentraLite Keypad? Following all the posts I was able to get the Keypad working with the SHM i.e. Arm/Disarm/Arm. I do however would like a delay to arm the system when someone enters or leaves the house. Is this possible? Reading through all the posts it’s very confusing what I need to do to setup the delay. It seems that I also have at least one additional issue, I cannot get into the 3400-x-Keypad Manager app on my phone. Message is: Sorry, but there was an unexpected error.
I have DTH:https://github.com/mitchpond/SmartThingsPublic/blob/master/devicetypes/mitchpond/centralite-keypad.src/centralite-keypad.groovy23 and SmartApp: https://github.com/mitchpond/SmartThingsPublic/blob/master/smartapps/mitchpond/3400-x-keypad-manager.src/3400-x-keypad-manager.groovy installed.
What am I doing wrong here…
I’m new at this but good at following instructions (old Engineer)
So, if any of you Wizards can help I really would appreciate.

You can integrate User Lock Manager SmartApp to add multiple users and add an exit delay. There is currently no way to have an entry delay (though the suggestion has been made to the CEO).

1 Like

Thank you so much Ben for the info. I guess I’ll wait for a while until you figured this out as well. Please keep up the good work…

There’s currently no way to do entry/exit delays with SHM.

I currently have SmartAlarm (out of support, I know, but its better than SHM), User Lock Manager, and this keypad working with Exit delay (via SmartAlarm, not ULM) with proper beeping, and with Entry delay (via SmartAlarm).

I’m currently working out a few minor issues, and then I’ll upload the various code, probably tomorrow.