Iris Keypad v3 Shows Armed After Open Contact Failure

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.