Iris Keypad v3 Shows Armed After Open Contact Failure

vasilios · December 13, 2021, 2:26pm

I'm not using anything from Nyckelharpa... is this the recommended solution for these keypads?

arnb · December 13, 2021, 2:50pm

Nyckelharpa is an optional user app, and won't / can't change the Iris V3's firmware locking up issue.

Suggest using something other than the Iris V3 for your primary keypad.

vasilios · December 13, 2021, 2:55pm

Not sure there are a lot of options in this space.

arnb · December 13, 2021, 2:56pm

What do you have for keypads?

vasilios · December 13, 2021, 2:58pm

All v3s... I had some v2s but those were acting worse than the v3s.

arnb · December 13, 2021, 3:06pm

My V2's work well. What issues did you have with them?

vasilios · December 13, 2021, 3:10pm

If I remember correctly (it's been a while) it was related to audio issues. Some of them the sounds/beeps worked correctly (dis/arming, open door, etc) and some stopped beeping after they were armed. They were more buggy than the v3 I had, but this was over a year ago. I eventually swapped to all v3s. I'll try the nyckel app see if it helps. The beeps not being sync'd is the least of my issues with these, it's more the keypad showing as armed after an HSM arming fail.

arnb · December 13, 2021, 3:14pm

I noticed this issue when I initially switched from ST to HE, prior to using my Centralite Keypad driver with Nyckelharpa. My keypad driver requires the Nyckelharpa app to function, but the beeps and sounds work.

oldcomputerwiz · December 13, 2021, 3:28pm

I am using the Nyckelharpa app with the Centralitex driver. I have a UEI keypad and an Iris V3 keypad. They both work great using Nyckelharpa and I have not seen them go out of sync when a contact is open during arming.

arnb · December 13, 2021, 3:34pm

Nor have I, and that's likely due to Nyckelharpa not arming, unless forced, with an open contact sensor. I have experienced the V3 refuse to accept a disarm during the arming exit delay time.

UPDATE: The V3 does disarm during exit delay, pin then Off, just tried it.

The Xfinity does not have an OFF key and disarms with a pin only, and for whatever reason the V3 remained silent when entering the disarm pin, although it usually makes key touch sounds. Unless you know better you may beleive it's not working.

vasilios · December 13, 2021, 4:11pm

So I tried using the custom driver, first difference is that with the default driver, it beeps 3 times when opening a door, and now it beeps 6 times. Second things is that once it beeps, it freezes until I hit refresh (the connectivity light goes off and the keypad buttons do nothing).

It did prevent the keypad from going into an armed state when a contact was open, so that's an improvement (did not thoroughly test this).

If I put it back to the default driver, the beeps go back to 3, it does not stop responding, but it will arm if a contact is open.

I'm having deja vu here, I think part of what I'm remembering with audio problems was having tried this in the past.

arnb · December 13, 2021, 4:29pm

I've not experienced the excess beeping issues with the V3, don't use that function, and it's been a long time since I tested it. I use TTS for open/closed with device name messages.

Will test this later when I get some time.

arnb · December 13, 2021, 6:05pm

Set the following Nyckelharpa app setting to an Iris V2 Keypad device

The following were already set for the V2 Keypad's in device settings

Opened and closed a monitored window a few times.
Result: Selected keypad beeped 3 or 4 times during the 1 second beep on time, no device freezes.

There are at least 2 respective firmware versions for the V2 and V3, and both devices may need a bit of experimentation to get them working in an acceptable manner. AFAIK it's no longer possible to update either keypad's firmware.

Hope this helps

BTW did you remove the Keypads from HSM monitoring and usage when testing Nyckelharpa and the user device driver?

arnb · December 13, 2021, 9:24pm

Ran same tests with the Iris V3 with identical Nyckelharpa and Keypad settings.

Result:
Iris V3 keypad beeped 4 short high pitched tones when door opened, then when I attempted to arm Away the keypad beeped perhaps 12 times and locked. Arming then disarming from another device unlocked the keypad.

Turned off keypad beeping and retried arming with door open. Keypad beeps 12 times then locked.

The V3 was a nightmare to code for, locking on all sorts of conditions that I thought were handled, I'm surprised I never encountered this error. I will take a look at the code when I get the opportunity.

@oldcomputerwiz does your V3 also fail with an open contact? Hopefully all it needs is to receive a disarm command.

vasilios · December 14, 2021, 1:23am

I tried it again, removed them from HSM as dis/arming devices, and as siren alerts for the various modes. I've left them as siren alerts for my smoke detector alerts.

I brought all my keypads together for testing. I set one of them to the custom driver and left the other two as the default driver. I am using Lock Manager for pins. I set up a virtual contact. When I open it, I get my voice notification on my Google mini, which is great, the default keypads beep about three times, and the custom beeps six times. I've set the timing to the lowest possible (1s). After they beep, the custom keypad starts having issues. The OFF button is red on the other two but none of the buttons are lit on the custom keypad, and/or it's followed up by all three blinking, then going back to no buttons being lit. It remains in this state until I do something from the UI, like refresh. However, it WILL beep again, even in this state, if I open the contact again. But the buttons do not do anything.

The logs show this repeating:

dev:7732021-12-13 08:21:15.034 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:15.030 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:13.520 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:13.516 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:12.031 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:12.027 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:10.521 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:10.517 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:09.018 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:09.015 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:07.929 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:07.925 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:07.717 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:07.714 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:06.229 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:06.225 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:04.723 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:04.719 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:03.901 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:03.897 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:02.366 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:02.362 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:21:00.882 pm debuggetMotionResult: active current: active
dev:7732021-12-13 08:21:00.868 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:20:59.375 pm debuggetMotionResult: active current: inactive
dev:7732021-12-13 08:20:59.362 pm debugParse entered catchall: 0104 0501 01 03 0040 00 F3DA 01 00 0000 07 00
dev:7732021-12-13 08:20:48.231 pm debugbeep entered: 1 true

The other keypad (also set to debug) does not do this.

arnb · December 14, 2021, 3:41am

Your results are similar some testing I did earlier this evening. It's only when a V3 initiates the arming, and the arming is rejected, that V3 keypad locks. During the testing I confirmed a disarm command is sent to the V3 when there is an open contact so that is not the issue. When the arming is initiated from another keypad or non keypad device, the V3 works as expected.

I'm sure this was all tested back when, so I'm unsure what changed. The V3 uses no pin at arming, and ignores any pins that may be entered, so it just may be it is expecting a completed arming no matter what, or perhaps it's a timing issue. There are a lot of comments and warnings in my driver's logic regarding the v3 device locking. I was not expecting or wanting to remember this stuff

oldcomputerwiz · December 14, 2021, 4:05am

I don't believe so but I will check it again tomorrow.

arnb · December 14, 2021, 4:07am

The fact that the refresh command clears the freeze is likely the key to fixing this.

arnb · December 14, 2021, 6:07pm

I coded and tested a "workaround' test version using a 4 second delayed refresh command on a V3 device initiated arming failure. I consider this very fugly, but it works. It should be noted that reducing the refresh delay time below 4 seconds failed to correct the issue for me.

Instructions when converting from HE system driver:

Install and setup Nyckelharpa. Hubitat Package Manager is suggested.
Manually install test version of Centralitex driver V1.0.7 (scroll down)
Remove the target Iris V3 from HSM monitoring
Change driver to User: Centralitex driver; Save device
In V3 device display scroll down to "Data"
Version must be 1.0.7. if not reload device screen or reinstall 1.0.7
Model must be 1112-S. If not scroll up to device's model command: Enter 1112-S
Tap/Click on Model command
Redo Step 5
Verify Use Lock Manager Pins is ON
When Data: softwareBuild is less than 10046230, you likely need to set Old Style Beeps: ON. Note Freeze issue does not appear to occur with 10046230, but does occur with 10036230 (this is on my device) Thank you @oldcomputerwiz for testing with a V3 at 10046230.
Do a Refresh command
Open a Nyckelharpa monitored door(real or virtual contact) Arm from target device no pin needed, tap On or Partial

Please let me know your results.

PS: I understand you are very concerned about the number of beeps, but the V3 hardware and software is what it is. Feel free to change the driver.

PPS: I use my keypad's temperature readings to control my house heating and cooling and was doing a RM refresh every 5 minutes to three keypads.
1.0.6 was supposed to be private to me. I changed the configuration to more frequently report device temperature changes eliminating the RMs. If you don't do a configure command it remains with whatever was set, or change the values and configure to your liking.
Values are: minimum reporting time seconds. Max reporting Time in seconds, Delta value
1.0.5 values: 30,3600,0x0064 (one degree celcius) I believe this is also the HE driver setting.
1.0.6 values: 30,3600,0x0008 (8=.125C or .18F)

The 1.0.7 version of the Centralite keypad driver is at

github.com

arnbme/hubitat/blob/master/Centralite-Keypad107.groovy

/**
 *  Update Url:   https://raw.githubusercontent.com/arnbme/nyckelharpa/master/Centralite-Keypad.groovy
 *
 *  Centralite Keypad
 *
 *  Copyright 2015-2016 Mitch Pond, Zack Cornelius
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *  Dec 14, 2021 v1.0.7 Iris V3 locks after device initiated arrming cancelled. In acknowledeArmRequest issue a refresh delayed 4 sseconds 
 *  Oct 30, 2021 v1.0.6	change configure, increase temperature reporting to stop doing a RM refresh every 5 minutes on the keypads
 *								zigbee.configureReporting(0x0402,0x00,0x29,30,3600,0x0008)  
 *								changed 0064 to 0008 to get more reporting 64=1C or 1.8F, 8=.125C or .18F

This file has been truncated. show original

arnb · December 16, 2021, 7:12pm

Please manually update and reinstall V107 from the github library above.

The prior version caused my Centralite Xfinity and Iris V2 to blink all of their lights at arming and disarm and sometimes fail to operate.