No worries. I really wish they get to the bottom of these issues though. My V3 has started displaying a strange behavior where I can turn off Partial mode at the keypad, get the chime that tells me the command was accepted (and the keypad correctly lights up the OFF key letting me know the system is disarmed) yet if I open a door I get the countdown I set up for AWAY mode (which I set up but which should not be activated since the keypad shows the system is OFF). If I don't try to turn off the system at the keypad at this time, the alarm/sirens get activated. There is obviously some delay between the command being received and the action being executed, but then why should the keypad respond as if it correctly received/registered the mode change? Frustrating...
My keypads IrisV2 and Centralite V2 remain on Smarthings with my SHM Delay SmartApp, everything else moved to HE. Hopefully 2.0.9 will fix all of the keypad issues.
One can only hope...
Part of the issue here is that what gets reported problematically is usually the overall stated objective.
As with all debugging endivours, app and driver behavior needs to be separated.
Does the keypad do on its own from the driver what you expect it to do, and then and only then can we look at the interraction(s) with applications.
I have an Iris V2 that I used with the HE Iris V2 DH.
- It stops making sounds after or during entering a pin (that worked)
- Sounds return after holding the 2 key
- Same behavior continued
- I stopped testing at this point.
We do not set the volume on these, there is no zigbee command for that.
Holding the 2 button increases the volume, that's not something the driver has any access to, not in HE, Iris or ST.
I understand your comments, however as strange as it may seem, that is what occurs. I received the keypad from another user who experienced the same behavior on HE after the last driver update.
HOLD THE PRESSES!!!
After the 2.09 update, all my V3 keypads started beeping when the mode changes. They still do not beep to announce if a door opens or closes, and still do not beep when clicking on the "beep" box under their device settings, but at least now they do announce mode changes (interestingly, they use a multi chime when arming and a single/double beep when disarming). Either way, this is progress and a welcomed improvement because I had grown accustomed to hearing a reassuring chime in the morning letting me know the system had disarmed.
Hi friends, just wondering @mike.maxwell did you have any luck with the keypad @spalexander68 sent you?
I just picked up 2 of these off ebay... they both seem to have the bum firmware (show up as "device" when pairing) when using the Iris v3 driver. I did mess around, if I use the centralite driver, beep works...
using the Centralite, Iris v1, v2, or v3 driver, I have a pretty significant delay before anything happens, but I think that's something else entirely... (for instance, press On... wait a minute... perhaps 2, then the keypad chirps and on may or may not light up, and HSM may or may not actually arm)
Same here - purchased 2 of these off eBay, shows up as device when paired and has the old firmware. I can get most of the functions I need by selecting Iris V3 manually, just not beeping.
edit: Using the Iris V3 device handler manually causes the Keypad to fall off the zigbee mesh eventually. They keypad does a weird double beep and goes into pairing mode again automatically. I re-paired with hubitat, let's see if it lasts. Strange device,,
I'm getting the same delay, in saying that a reboot of the hub and it all works for a day or so, then overnight it slows again, I go to disarm in the morning and it wont for two or three tries and then will with a long delay, 30 seconds or so. About to give up on the keypad as everything else is still instant although I do notice a slight delay in the dashboard (going from one to another) as well and this normally means the keypad will no longer work reliably. Mine paired as device and I use the Iris V3 driver. Works well for a day or so until the slight slow down and then seems like it times out or something.
Another ping on this. Wondering if @mike.maxwell had any luck troubleshooting the older firmware on the V3. I got mine a week ago and it's been acting all sorts of weird. I thought I had the issues ironed out but then the batteries died (after 1 week???) and it started acting weird again (i.e. ON button would activate Armed Night for some strange reason).
the older firmware is lacking the door chime, other than that, they both do the same thing.
if the batteries are dying that soon it's having issues communicating with the hub, so repeaters can help here...
Well that's discouraging. Maybe I have a bum unit, though it looked pretty much brand new when I got it off eBay. I guess I'll factory reset it again and see if it starts working properly.
re: battery life... not sure what's up there b/c I added a couple of those Aeon z-wave repeaters a couple weeks ago to get my Schlage locks on the mesh better and the keypad is about 4 feet from a repeater, which itself is only 12 feet from the hub and another repeater, so it really shouldn't be an issue connecting.
the keypad is zigbee, so you'll need zigbee repeaters for the keypad.
I had similar issues feeding my keypad with batteries until I hardwired it to a Li-Po battery back up, so I have the best of both worlds. A mains powered keypad with battery back up. 
You should not need to feed it batteries that often. Do you have any rules that are polling the keypad or setting codes all the time, anything at all? Left to it's own devices, my v2 keypad lasted almost 2 years and my v3 still reports 80% after almost a year.
A big duh on my part of that. Still, it's got direct line of sight to the hub sitting 12 feet away, I wouldn't think a zigbee repeater would be necessary.
humor me...
HELP- anyone who has this keypad working correctly on hubitat -and has smarthings, can you pair to ST and check the firmware version? I have firmware : Current Version: 0x10036230
- Target Version: 0x10036230
and my key pad is not accepting the programmed PIN's using the stock driver in HE .
It will triple beep on pairing in both HE and ST so I suspect it is pairing correctly. I tried both the stock HE driver and the centralite(x) driver(mitch pond/Zack Cornelius/Arnb) on both ST & HE. Anyone have any ideas?
I finally got it working. It was in-fact Zigbee communication related. I had the HE hub sitting directly next to my Netgear R7000 router. I turned off the 2.4GHz Wifi on the router and the keypad magically sprang to life.
So I ended up changing both the channel used for the 2.4GHz Wifi (to channel 3) and the Zigbee channel on the HE hub (to channel 20).
I also moved the HE hub slightly away from the hub... only by 18" or so, but that seemed to do the trick.
My guess is that with the HE hub sitting directly next to the Wifi router, the Zigbee signal was just getting buried under the Wifi signal.
