Are you entering the PIN last? On mine it’s PIN then mode on the keypad. Doesn’t work the other way for me.
Just installed my second IRIS keypad, this one at the office. No problems and was quick.
Key thing was to keep keypad close to hub.
Start smart things include in app
pull battery tabs from keypad
waited 4 minutes
checked IDE: found “Thing” and changed to Centralite Keypad DH, set room and name
stopped smart things include in app
Waited for the keypad to go dark (sleep)
Went to room in the app that I chose in the IDE, and device was there.
Chose device, and then hit configure
30 seconds later, I got battery, etc
I installed Locks Manager that mentioned in thread above via the IDE, and then installed the smartapp from the My Apps section of the Marketplace.
(/**
- User Lock Manager v4.1.5
- Copyright 2015 Erik Thayer
- Keypad support added by BLebson
*/)
Set first user code and filled out rest of app (keypad settings, arm/disarm settings).
At this point, I finally touched the keypad. I entered by code for my user, and selected OFF.
The app then reflected disarmed status.
All good.
I have tried both ways, Neither one will work.
I tried again to follow these steps but my keypad never goes dark (sleep) it blinks away with the green flashing icon wifi signal looking thing. after awhile (25 mins) I push the tab to try to get it to finish but it just keeps blinking until finally it times out.
what shows in the live log when you try to pair the device?
I believe the green blinking only stopped after I did configure. Or when I set the device handler and opened it in the app. I can’t quite recall now, sorry. This is for the IRIS version.
Here is the log for keypad:
8ae75b05-8805-4b18-9d94-22cea8805cda 5:18:21 PM: debug Parsing ‘temperature: 24.31’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:52 PM: debug Received battery level report
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:52 PM: debug Parsing ‘read attr - raw: BB860100010A200000201D, dni: BB86, endpoint: 01, cluster: 0001, size: 0A, attrId: 0020, result: success, encoding: 20, value: 1d’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:52 PM: debug TEMP
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:52 PM: debug Device: read attribute response: catchall: 0104 0402 01 01 0140 00 BB86 00 00 0000 01 01 000000297F09
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:52 PM: debug Parsing ‘catchall: 0104 0402 01 01 0140 00 BB86 00 00 0000 01 01 000000297F09’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:50 PM: debug Unhandled profile-wide command: catchall: 0104 0001 01 01 0140 00 BB86 00 00 0000 07 01 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:50 PM: debug Parsing ‘catchall: 0104 0001 01 01 0140 00 BB86 00 00 0000 07 01 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:50 PM: debug Unhandled profile-wide command: catchall: 0104 0402 01 01 0140 00 BB86 00 00 0000 07 01 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:50 PM: debug Parsing ‘catchall: 0104 0402 01 01 0140 00 BB86 00 00 0000 07 01 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:50 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 72 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:50 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 72 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 71 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 71 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 70 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 70 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 6F 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 BB86 00 00 0000 00 6F 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Unhandled profile-wide command: catchall: 0104 0500 01 01 0140 00 BB86 00 00 0000 04 01 00
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:49 PM: debug Parsing ‘catchall: 0104 0500 01 01 0140 00 BB86 00 00 0000 04 01 00’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:48 PM: debug Parsing ‘updated’
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:48 PM: trace Method: refresh(): [st rattr 0xBB86 1 1 0x20, delay 100, st rattr 0xBB86 1 0x402 0, delay 100, raw 0x501 {09 01 04 0000}, send 0xBB86 1 1, delay 100]
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:48 PM: trace Method: sendStatusToDevice(): [raw 0x501 {09 01 04 0000}, send 0xBB86 1 1, delay 100]
8ae75b05-8805-4b18-9d94-22cea8805cda 5:17:48 PM: trace Arm mode: null
Hey @mitchp, does this show any reason as to why the keypad might not be pairing? I’m still a novice when it comes to ZigBee devices.
Well, it is paired and sending temperature… It’s also sending some messages that I haven’t seen from the Xfinity model.
0000 8021 00 00 0040 00 BB86 00 00 0000 00 70 00 This looks like a ZDO End Device Bind Response…maybe? I’ve never seen these passed through to logging.
I have to wonder if there is a newer hardware or firmware revision that is filtering out to the stores…
1 Like
When i choose “configure” in the app (light still blinking on device) I get the following in live log:
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:52 PM: debug Received battery level report
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:52 PM: debug Parsing ‘read attr - raw: 621B0100010A200000201D, dni: 621B, endpoint: 01, cluster: 0001, size: 0A, attrId: 0020, result: success, encoding: 20, value: 1d’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:51 PM: debug Received battery level report
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:51 PM: debug Parsing ‘read attr - raw: 621B0100010A200000201D, dni: 621B, endpoint: 01, cluster: 0001, size: 0A, attrId: 0020, result: success, encoding: 20, value: 1d’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:51 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 15 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:51 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 15 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:51 PM: debug Unhandled profile-wide command: catchall: 0104 0001 01 01 0140 00 621B 00 00 0000 07 01 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:51 PM: debug Parsing ‘catchall: 0104 0001 01 01 0140 00 621B 00 00 0000 07 01 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:50 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 14 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:50 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 14 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:50 PM: debug Unhandled profile-wide command: catchall: 0104 0001 01 01 0140 00 621B 00 00 0000 07 01 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:50 PM: debug Parsing ‘catchall: 0104 0001 01 01 0140 00 621B 00 00 0000 07 01 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:50 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 13 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:50 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 13 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 16 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 16 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Unhandled profile-wide command: catchall: 0104 0001 01 01 0140 00 621B 00 00 0000 07 01 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Parsing ‘catchall: 0104 0001 01 01 0140 00 621B 00 00 0000 07 01 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 13 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 13 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 16 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 16 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 16 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:49 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 16 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:48 PM: debug Unhandled profile-wide command: catchall: 0104 0500 01 01 0140 00 621B 00 00 0000 04 01 701000
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:48 PM: debug Parsing ‘catchall: 0104 0500 01 01 0140 00 621B 00 00 0000 04 01 701000’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:48 PM: debug Unhandled profile-wide command: catchall: 0104 0402 01 01 0140 00 621B 00 00 0000 07 01 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:48 PM: debug Parsing ‘catchall: 0104 0402 01 01 0140 00 621B 00 00 0000 07 01 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:47 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 15 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:47 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 15 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:47 PM: debug Unhandled profile-wide command: catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 14 00
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:47 PM: debug Parsing ‘catchall: 0000 8021 00 00 0040 00 621B 00 00 0000 00 14 00’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:47 PM: debug Unhandled profile-wide command: catchall: 0104 0500 01 01 0140 00 621B 00 00 0000 04 01 701000
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:47 PM: debug Parsing ‘catchall: 0104 0500 01 01 0140 00 621B 00 00 0000 04 01 701000’
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:42 PM: trace Method: refresh(): [st rattr 0x621B 1 1 0x20, delay 100, st rattr 0x621B 1 0x402 0, delay 100, raw 0x501 {09 01 04 0000}, send 0x621B 1 1, delay 100]
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:42 PM: trace Method: sendStatusToDevice(): [raw 0x501 {09 01 04 0000}, send 0x621B 1 1, delay 100]
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:42 PM: trace Arm mode: null
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:42 PM: debug Sending status to device…
61ea7387-2c12-4e55-8203-53ded621ed43 6:07:42 PM: debug Configure called for device Centralite Keypad.
At this point, I’m calling it quits and moving on in life. Thanks to everyone who has tried their best to help!!! If by some miracle I figure out a solution in the future I will be sure to let everyone know.
Seems odd that we’ve only heard of a one or two instances of the issue. Is there anyway to pull the firmware version from each one to tell?
Yes. There are attributes in cluster 0 that identify model, mfg, as well as versions. I wish this was something that the platform pulled on its own and made available in the device listing… I’m out right now and don’t have the spec reference handy, but sending a readAttribute with the right cluster and attribute ID would list it out.
Hi guys, I have had the same issues as @bestguy24 although I have not done a detailed trace. Maybe we are more than a few but we just gave up when it did not go according to plan. Kudos to Jay for hanging in there. How can we find out what firmware version is in the device?
1 Like
I just got around to pairing my Xfinity keypad (from ebay)… I followed your procedure, except, I had to press the “Wall Button” maybe 5 minutes after pulling the battery tab… this caused the Network Indicator to stop blinking… the app never stated that a device was found, but the Live Logging showed the activity… my keypad was properly recognized as a Centralite Keypad, so didn’t need to change the device type… it did show up in the app as Not Yet Configured, where I took normal steps, then configured a new instance of Lock Code Manager for the 4 digit pins and tested…
Jay- sorry for the late reply. I never got it working. I tried an two different Iris devices and a Xfinity device and neither worked, so I was focusing on looking at something unique to my v2 hub or configuration as the root cause. I even tried completely resetting my SmartThings hub so that this would be the first and only device on the hub- still no dice.
It seems like it half pairs- meaning I can get the keypad to reflect SHM status when I change it through the app. But as far as getting the keypad to respond to key presses- nothing at all.
I spent wayyyy too much time on this trying to get it to work. In the end, I think I’ll just mount a cheap tablet on the wall when I have time to run power. I’ve found that for the price of one of those keypads, I can magnetically mount a tablet to the wall by putting a strong magnet on the back of a tablet and then screwing a metal 2 gang electrical plate cover to the wall. The magnet and plate form a strong bond, and I can easily rotate the device from portrait to landscape or pull off the tablet from the wall. With a recessed usb outlet behind the tablet it all looks very clean.
Thanks for the reply. I also tried 2 iris keypads then the xfinity keypad. I also am going to end up mounting a tablet. I agree it’s not pairing 100%. Frustrating, so I am also moving on to next project. Funny because I also tried uninstalling everything and then tried pairing keypad as first device and it still wouldn’t work.
1 Like
Have you made your sacrifices to the ST Gods? It doesn’t work unless an engineer receives a case of beer with your account email address attached to it.
hahah
Has anyone found that xfinitiy 3400 keypads work better than the lowes iris keypads or vice versa?
Also, is there any risk that buying a used keypad may leave the door open to some vulnerability or a backdoor put in by the seller?
Sorry for the noob questions…
Thanks
The iris keypad works well for me (I use two). It’s not working as well for some others. I think the device handler at the top of this thread was designed for the xfinity keypad. You could try either, essentially.
I don’t know that a Zigbee device like that can have a backdoor. Just reset it to the factory setting and then it’s as (in)secure as anything else connected to ST.
1 Like
I successfully installed your smartapp and setup up multiple codes shared on 2 IRIS keypads. Is there a way to require a code when the user accesses the smartapp on the phone so family members with the Smarthings app can’t modify or see the codes?