Iris Keypad v3

So my Iris Keypad v3 just came in.

A couple things to note, I'm finding the beeps are delayed up to 2-3 seconds before it starts beeping, and they get turned off in the middle by the following message below.

Also, the motion sensor portion seems shotty. Meaning, I'm sitting in front of the keypad right now and it shows "Inactive".

dev:38062020-06-02 12:48:55.912 pm debugsending response: disarmed status: 0 00 state.delayExpire: 0

dev:38062020-06-02 12:48:55.890 pm debuggetMotionResult: active current: active

dev:38062020-06-02 12:48:55.880 pm debugParse entered catchall: 0104 0501 01 03 0040 00 1D39 01 00 0000 07 00

dev:38062020-06-02 12:48:51.397 pm debugbeep entered: 1 true

The keypad's motion sensor is designed to turn the device's lights on and off sensing motion up to perhaps 6 inches (being generous here) from the device. Similar results using my Centralite/Xfinity and Iris V2.

Beeps are issued for a few things, which beep function is delayed? Also what is the device setting for "old style beep sound"

BTW Beep 1 command means issue 1 beep (may vary depending on device and settings)

Okay, that makes sense then.

Under the device, the only way I can get beeps to work is using "Old Style Beep Sounds". I was hoping the beep could also be louder, but adjusting the sound volume by holding 2 down, doesn't change the beep sound volume.

How can I tell which beep I'm using? I just click beep on the device. It's the same one your app is using.

That means it does not have the updated firmware, that is no longer available afaik. My Iris V3 works fine with the old firmware.

Are you using the Hubitat supplied driver or the Nyckelharpa Centralite driver from my app?

What beeps are expected: Keypad key taps, Entry delay, Exit delay, other?

I'm still in the middle of testing, it appears Entry delay beeps work fine, keypad beeps are also working, and the beep used for open/close contact works.

The issue is two things really, the beeps get cut off due to the disarming command being sent to it.

Second, I can't adjust the beep volume for this type of beep.

If you have keypad tones you likely are using my app's driver. Please confirm which driver is being used.

That's how it's supposed to function on Entry delay, and also Exit delay.

The tone volume adjustment is:
Increase: hold 2 key down
Decrease: hold 5 key down

My Iris V3 is rather wimpy and weak on exit and entry tones; good for key press tones, and good sound on siren which is not impacted by 2 and 5 key adjustments.

This happens when the system is disarmed. If I open a door it sends that response still cutting off the tones.

When using the keypad's door chime command function, when activated terminates any active entry or delay tones. If you are not using the chime function, I have no idea.

Due to this issue I use my Amazon tablets with the Fully Kiosk Browser for Door Chimes and TTS messages.

Are you referring to this? If so, it's on but still cutting out the beeps because of "sending response: disarmed status: 0 00 state.delayExpire: 0"

Yes that's the Input control for the chime. Is the system armed or disarmed when you are opening the door, or are you using the device page's buttons?

When testing, it's disarmed. I'm testing by opening and closing doors.

I'm confused. How are you getting Entry/Exit tones when the system is disarmed?

Should this be by using the device page to create the tone, then opening the door, it is working as expected. Normally when the system is armed and a monitored door opens, it creates an intrusion or intrusion delay with entry delay tones. No need for a door chime at this point.

I'm not.

The debug logs are sending that when the system is disarmed. The normal chimes that go off are being cut off because of these events in the logs.

That's normal, all tones cease when a disarm occurs, logging has nothing to do with anything.

BTW the IRIS V3 was a gigantic PITA to get working in a rational manner. What you see in the logs may not reflect the observed external behavior. Excessive motion around the device may occasionally cause an issue although I've done what I could to mitigate the issues with this device. If this is an issue feel free to dive into the handler's V3 code :crazy_face:

1 Like

Thanks I appreciate the help.

Regarding your app.

Besides the talker and user child apps, what does your app give over the built in Hubitat one?

It's all explained in Github readme Section 2

1 Like

I'm not sure if it will work with the updating the last updated firmware for the Iris Keypad v3. But do you happen to own a SmartThings hub?

I was informed when I bought some Iris Motion Sensor and Contact Sensors (a month ago) that if you add them to the ST hub that it will update to the last released firmware. I was able to update all of the with no problem.
I was told best to add the devices to ST using the ST Classic app.

Here's a screenshot talking about it, hope this helps.

I do not have one.

What will the firmware give me? A different beep?

Smartthings can update the firmware on a few iris devices, but I don’t think the V3 keypad is one of them.

1 Like

ST does not natively support keypad devices, nor does it update these devices.

2 Likes