The documentation is in preparation for what's coming. You need to wait for 2.0.7
copy that...
Yes, right now ...[quote="pdupper, post:49, topic:11212"]
IRIS v2 keypad identifies as a Centralite Keypad
[/quote]
Thanks StephenH & DustyD5 for the replies...they helped tremendously...I am beginning to understand it a little more...I see I need to wait for V2.07 before fooling with keypad much more, plus I kept hitting the "DONE" button too on config and wasted a lot of time on it. LOL
I have the NYCE door hinge sensors made for Iris and I did get one to pair as a test as I don't want the "stick on" Iris contact sensors on my doors. I'm slowly getting there with Hubitat...hated it a couple of days ago but I'm getting there!..."Patience Grasshopper, patience."
1 Like
After several days of trying to get an Iris V2 Keypad to work I was just about to give up.
I finally got a keypad to arm/disarm!
The keypad (#1 ) I had been trying to get to work would pair easily, but never would respond to key codes.
Note that each time this keypad was paired, the light in upper right corner of keypad (the little "iris wave" symbol) would constantly blink after pairing--I had to remove and reinsert batteries to turn off light after pairing.
After several days of frustration, I decided to try another keypad (#2)...reset it and could not get it to pair.
Pulled out another keypad (#3)..it paired easily but I immediately noticed that the light in upper right corner of keypad did NOT continue blinking after pairing.
This keypad responds to key codes and works as it should--it can arm away, home, partial. 
Any idea why this keypad works and others don't? Does the blinking or not-blinking light after pairing have something to do with success or failure of keypad to respond? All of these keypads were working under Iris so they aren't defective.
Any ideas?
If following the steps in the other post canât get the keypads paired and unless youâve got time and energy to burn, I think youâre better off waiting for the next update of HE to sort the niggles out of the keypads.
HERE:
It seems that the flood of Iris hardware versions and firmware builds has created quite a challenge.
There were some issues with the older firmware versions, some driver updates will be available in platform 2.0.7, best to wait for that update.
1 Like
Thanks Mike...will do that. Even though I finally got the keypad to arm/disarm, the Utilitech siren wouldn't sound on sensors tripping whereas before keypad wouldn't work, siren would sound. I'm done with security until V2.07.
If you have a Door/Window sensor or make yourself a Virtual Switch, then you can test and configure the Siren you have.
I often try to break a task down into segments like trigger and action, and test to ensure that each part âworksâ before sticking them together.
Just how I approach things.
1 Like
In this document the Iris V2 Driver is listed as Iris V2. I do not find that driver, only the Centralite driver
It's only available in platform 2.0.7
1 Like
My Iris V2 keypad identifies as "Centralite Keypad" and works just fine. It is identified by the manufacturer (Centralite), not the vendor (Lowes).
The iris V2 driver works almost 100%. The only thing missing is the rapid beeps that would play when the arming delay is almost done. Honestly, I can live without it and wouldn't want to waste the community's time trying to fix such a minor thing.
Thanks to the devs who took the time to get they keypad to work the way it is now with 2.0.7.
This is not possible due to the older firmware versions leaving the lights on when activated via keypad, it was intentionally disabled due to this problem.
After updating to 207, I'm working on the security settings again. Many thanks to the folks who got the IRIS keypads working...
Arming with a delay seems to work great. I can get out of the house without issue... Disarming also appears to work with the delay set to allow enough time to get through the door and enter a code into the keypad...
Here is my problem. I enter the house, get to the keypad and enter my code. Everything seems to shutdown as expected... A few seconds later, the alarm goes off, lights flash, I get texts and push notifications, etc. Then after a few more seconds, it all stops and goes back to normal...
Its like the whole system is on a delay. The keypad gets the correct code and itself decides everything is cool and shuts down... The rest of the system doesn't get the message and all the alarm functions trigger.... Then the system catches up with itself and realizes, oops, I made a mistake and shuts everything down...
Am I doing something wrong?
1 Like
I am sorry but I can't help you here. we use Iris Smart Fobs (gen2) as presence sensors. When we get home, by the time we get to the door, the system is already disarmed. Using the app to turn it off while you are still outside is also a good way to do this. In reality, the keypad isn't really needed. The only thing I really liked it for with Iris was the chime the gen1 keypad did when a door was opened.
If it were just me, the wife and kids, I would say that could be an option. However, my in-laws and a couple of close family friends come and go throughout the day. They use the keypad...
Hoping to get it working again...
This happened to me yesterday and I thought it was a fluke. It happened just now as well as scared the sh*t out of my wife and kid!
Yeah, I've tested it a few times and its pretty consistent... It settles like everything is fine, then about 30 seconds later, the alarm goes off, lights flash and within a few seconds it stops and takes the lights back to their previous status... 
Hopefully it is an easy fix...
I think we need a little more info such as...
Are you using HSM, Modes or just RuleMachine ?
Could you have an errant âdelay on...â
somewhere ??
Maybe a doubled up delay.
Usually my Hub Modes are set using âpresenceâ but I have a keypad for âother guestsâ etc
