Iris Keypad v3


#1

Anyone else get the Iris Keypad v3 to work with HSM? I am getting the strangest behavior.

First of all, there is no Exit Delay notification when you "arm away" from something else, like a dashboard, unlike the V2. And that is the primary reason that I bought it.
In addition, when you arm-away from this keypad, you do not get the delayed armed action from HSM or an exit delay beep from the keypad. Instead, the keypad does it's own, silent, 30 second countdown and then HSM immediately goes to Armed Away. At this point, my other keypad then begins it's 30 second countdown, even though the system is already armed-away.

So, does HE not support 2 keypads simultaneously? And if it does, is there any way to make this other keypad work even remotely like the V2 keypad? Do I have to have the device configured in a certain way to use it with HSM? There are device settings for Entry and Exit delay in addition to the ones in HSM. Are those what is in conflict? Or is the driver just completely wrong.


#2

40 views and not one comment. What were all of you saying about community again? LMAO. You people crack me up.


#3

Maybe, like me, they saw that you posted the same question in another thread and already got two answers. :wink:

Even if it not: it's only been a few hours since you posted, and while generally helpful, the community is small, and an even smaller percentage probably have multiple keypads, much less this new one, to test with...and as you know, like you, anyone besides staff who responds is just a passionate volunteer.


#4

I have 2 keypads, one Iris and one Xfinity and both works exactly the same in the same hub, when I choose away mode in one both will beep for 30 secs, my setting.

I bet your new keypad needs a new driver or at least a driver update.

Same answer as the other thread.


#5

I just viewed the post out of curiosity, probably the other 40 people as well :slightly_smiling_face:.

I have two of the V2 Centralite keypads and they work fine. I would guess most people don't have the V3 keypad.


#6

Really? Those were answers? I disagree. They were not answers. And I'll post it as many times as it takes to get an answer. Tough.


#7

Then you should contact support@hubitat.com or tag your preferred helper in this thread, like Bruce, Mike or Bobby.


#8

At least one certainly seems helpful to me: checking the firmware version on your device. (Hubitat doesn't really provide a great way to do that, but the keypads weren't exactly manufactured for Hubitat, either.) Do you know that information? Others do seem to have this working. People obviously saw your previous thread. Your best option would be to have created this thread in the first place ask a moderator to split that post into a different topic like this if you think it diverges too much or want more visibility.

Oh, and the moderators, not you, will decide how many posts you can make on the same topic. :wink: If you want official support, take the advice above and contact them. (Chances are they will see this at some point, however. They're pretty good about reading the forums.)


#9

Yes, HSM works fine with multiple keypads. I have no familiarity with the different versions of the Iris Keypad, so don't have a clue what the difference is between it and V2, or if that is the problem. It sounds as though the arm delay setting for this keypad is not right. HSM sets that when you establish it in HSM. I think, but can't test at the moment to confirm, that setting it in the keypad creates a conflict. Perhaps you could show the preferences settings for the keypad, so I could compare them tomorrow to the ones I have at the office that I know to work correctly.


#10

Wow this thread took a weirdly negative turn pretty quick.

I have a V1 iris keypad that is working fine.

I got one of the newer iris keypads and was planning to set it up this weekend. So I’ll share my findings soon. Hopefully that’s a quick enough response.


#11

Is it v2 or v3?


#12

Is this what you are asking for?

When I arm the system from another device, the keypad does not display armed-away until 30 seconds after the rest of the system is armed. When I arm from this device, HSM never goes to dealy-armed status and does not do the delay timer. After 30 seconds it goes directly to armed away. Then, the other keypad will do the std 30 second beeping countdown even though the system is already fully armed-away.

So, something is not being sent to the keypad correctly or not being interpreted from the keypad correctly. I can capture whatever logs you want. You just have to tell me what you need.


#13

Can you show the arming page from HSM. Also, the app events from HSM for when you arm it the two ways. I doubt that I can tell much from these, to be honest. Turn on debug logging for the device, and see if HSM sends it the arm command at the time when you arm HSM from another device. Might also check the same when you arm it directly from HSM itself.

When you arm-away, HSM should send setEntryDelay command to the keypad at the time that HSM is fully armed (after the delay). It should send the armAway command at the beginning of the delay. You should see these in the logs from the keypad.


#14

What driver is that? I don't see the options you asked in the other thread


#15

Arming page:

For arming from the other keypad via device edit page:

Problem keypad logs:

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:48:30.361 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad is active

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:48:30.308 pm [debug](http://192.168.1.12/device/edit/1442)getMotionResult: active

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:48:30.302 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0501 01 03 0040 00 B64D 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:03, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:48:30.009 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad was armed away [digital]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:48:30.009 pm [debug](http://192.168.1.12/device/edit/1442)sendDelayedEvent- data: [armMode:03, data:null, type:digital]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:48:28.524 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad is inactive

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:47:58.535 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad is active

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:47:58.502 pm [debug](http://192.168.1.12/device/edit/1442)getMotionResult: active

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:47:58.501 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0501 01 03 0040 00 B64D 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:03, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:47:55.331 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0020 01 01 0040 00 B64D 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:47:06.446 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad was disarmed [digital]

Working keypad Logs:

dev:4822019-01-05 06:47:56.752 pm infoKitchen Keypad was armed away [digital]

dev:4822019-01-05 06:47:56.744 pm debugsendDelayedEvent- data: [armMode:03, data:null, type:digital]

dev:4822019-01-05 06:47:17.462 pm debugdescMap: [raw:catchall: 0104 0020 01 01 0040 00 F18E 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F18E, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

HSM Events:

Arming from Problem Keypad:

Logs of problem keypad:

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:00:16.611 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad was disarmed [digital]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:59:58.796 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0020 01 01 0040 00 B64D 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:57:58.203 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0020 01 01 0040 00 B64D 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:57:01.928 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad was armed away [physical]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 06:57:01.928 pm [debug](http://192.168.1.12/device/edit/1442)sendDelayedEvent- data: [armMode:03, data:[-1:[code:0000, name:not required]], type:physical]

Logs of good keypad:

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 07:00:16.569 pm [info](http://192.168.1.12/device/edit/482)Kitchen Keypad was disarmed [digital]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 06:59:17.163 pm [debug](http://192.168.1.12/device/edit/482)descMap: [raw:catchall: 0104 0020 01 01 0040 00 F18E 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F18E, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 06:57:35.258 pm [info](http://192.168.1.12/device/edit/482)Kitchen Keypad was armed away [digital]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 06:57:35.257 pm [debug](http://192.168.1.12/device/edit/482)sendDelayedEvent- data: [armMode:03, data:null, type:digital]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 06:57:16.914 pm [debug](http://192.168.1.12/device/edit/482)descMap: [raw:catchall: 0104 0020 01 01 0040 00 F18E 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F18E, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

HSM Events:

Arming from HSM:

From problem Keypad:

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:08:24.410 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad was disarmed [digital]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:08:22.207 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad is inactive

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:08:19.648 pm [info](http://192.168.1.12/device/edit/1442)Living Room Keypad was armed away [digital]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:08:19.647 pm [debug](http://192.168.1.12/device/edit/1442)sendDelayedEvent- data: [armMode:03, data:null, type:digital]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:08:01.144 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0020 01 01 0040 00 B64D 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:07:53.176 pm [debug](http://192.168.1.12/device/edit/1442)getMotionResult: active

[dev:1442](http://192.168.1.12/logs/past#dev1442)2019-01-05 07:07:53.174 pm [debug](http://192.168.1.12/device/edit/1442)descMap: [raw:catchall: 0104 0501 01 03 0040 00 B64D 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:03, options:0040, messageType:00, dni:B64D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]

From Good keypad:

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 07:08:24.352 pm [info](http://192.168.1.12/device/edit/482)Kitchen Keypad was disarmed [digital]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 07:08:19.622 pm [info](http://192.168.1.12/device/edit/482)Kitchen Keypad was armed away [digital]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 07:08:19.617 pm [debug](http://192.168.1.12/device/edit/482)sendDelayedEvent- data: [armMode:03, data:null, type:digital]

[dev:482](http://192.168.1.12/logs/past#dev482)2019-01-05 07:07:16.387 pm [debug](http://192.168.1.12/device/edit/482)descMap: [raw:catchall: 0104 0020 01 01 0040 00 F18E 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F18E, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

Through this testing, I have found that arming from either keypad does not trigger the rule that I have that triggers when I arm away from within SHM (or via a rule). So, it appears that there is something else going on with the driver and HSM that is affecting both keypads.


#16

The Latest iris keypads, the greatstar units do not support pin on arm, so those options are not exposed.
These options were never available in the iris app to begin with, but the older devices supported it, so we implemented it.


#17

You read my mind. And that's not a problem. But even if the keypad doesn't support the Delay-Armed countdown itself, I need it to trigger HSM's delayed arm countdown, which it doesn't appear to be doing presently, from either Centralite V2 or V3.


#18

Yes I know, separate issue. I'm dealing with two topics concurrently here.


#19

Ok....all you had to say Mike. I didn't know that. I left my psychic abilities in my trunk. :slight_smile:

Thank you.


#20

The Iris V3 is an iMagic 1112-S. In SmartThings using SHM Delay, it is supported using a paid for DTH from Rboy Apps. Mitch Pond's Centralite centric DTH does not work with this device (AFAIK). As @mike.maxwell posted, these devices are armed by pressing either ON or PARTIAL, no pin required or sent by hardware. To disarm, enter a pin followed by OFF.

The Iris V2 could be armed with or without a pin, pressing ON or PARTIAL without a pin (depending on firmware may need a double tap), sends pin 0000.

Also there is a new Centralite V3 Keypad available supporting "Panic mode" by simultaneously pressing the two "police badges" keys on either side of the "0" key. The model shows as a 3400-G, older Centralite keypads show as a 3400, however the Raw Description 01 0104 0401 00 07 0000 0001 0003 0020 0402 0500 0B05 02 0019 0501 is identical on both devices.
The older model 3400 has an A and B key vs badges and does not support panic mode.