It’s a bug in the ST Android app which causes it to enter a decimal point by default where it shouldn’t. Just remove the decimal points and tap Save and it should work fine. Also report it to ST with the reference Ticket number provided so they can fix it. See this post:
[RELEASE] Enhanced ZigBee Keypad Lock - Centralite Keypad, Lowe IRIS Keypad, UEI Keypad and Xfinity Keypad Device Handler
I know this has been somewhat discussed but I’m struggling to understand a few things about the DTH and Lock manager app. I’ve recently picked up a couple of the Iris v3 keypads. I like the design and everything but I’m starting to have some concern over connectivity, as has been also mentioned recently.
Here are a few general questions (may be specific to my Iris v3):
- Can I change/mute the keypad press beep sound? I’m referring to the sound when you press the numbers/keys, but also would like to have full control over all sounds if possible. I’ve read about using #2 and #5 for that but I’ve had no luck. Could this be added to the DTH?
- What does the sync button do inside ST? I’ve had a situation where my kepad “Partial” has been lit red but the system is not Armed Stay. I’ve hit the sync button but it does not help. If there’s no auto sync option, this could be a deal breaker as I plan to arm through phone app, wall tablets and this keypad.
- I’m trying to understand the “Lock/Unlock” button inside the ST device settings. Is this the same as SHM “Armed”? Or is it meant to be used for door locking or keypad locking features? I’m confused here.
- Is it really true there’s no way to require a PIN in order to Arm the system?
Hey @Rboy, so while I still have off and on connectivity issues with the v3 IRiS keypad, it seems that it does work for the most part. Not sure why it’s so bad at staying connected, even with a new Sinope ZigBee device mounted on the opposite side of a wall, go figure. Not sure if that’s something that is solvable unless they release a FW update or there is some secret sauce in the protocol that IRiS has with their hub since I would think they would have the same problems that I’m having.
Two questions for you (or anyone else with v3 keypad experience):
Battery life - seems that the keypad slowly burned through the OEM Alkaline batteries over about 2 weeks, albeit with a lot of trial and error on my side. I replaced it with Lithium batteries but I was just wondering if you’ve seen any issues after the latest DTH changes? I know the latest DTH made a difference in functionality but I see a lot more pings with the 0000 status so I was wondering if it could be related.
Garage door keypad replacement - I’m experimenting with having it control the garage door to replace the traditional keypad from Chamberlain. With LUM, I set up a code with only the action to open the door when unlocked and that seems to work fairly well. However, closing the door is another thing. Since the v3 keypad arms without a code, I can’t think of a way to get it to close. Any good ideas or mods that could be done?
Regardless, thanks for the great support. This is exactly why I’m an RBoy Apps lifetime subscriber - you have actual support. While I enjoy writing and publishing my own little apps, my first stop is always to the RBoy website to see what’s on the shelf because I know I’ll be getting something that’s battle tested.
Glad to hear you’re on the same mission as myself regarding Iris v3. I really like the keypad but there are def some bugs to work out.
For the garage door question… are you using a virtual door opener smartapp? If so (and I have not tested this), couldn’t you just trigger the relay switch that opens, and then the same code would open and close it?
Hmm, I hadn’t thought about that. In the RBoy Lock User Management (LUM) app, there is a direct action to open a garage door upon unlock and close a garage door upon lock and have been using the unlock to open. But I think what you’re suggesting is a more indirect method to have LUM toggle a switch and have the switch force the open and close?
Other than adding an additional hop (any whatever delays, etc.) that sounds reasonable but I would have to check to see if the custom actions in LUM support toggling a switch. Maybe that’s an RFE to LUM, allow me to toggle the garage door state when I unlock. FWIW I am using the RBoy GoControl DTH which has the garage door as a switch if I recall correctly since I can Alexa to “Turn off the Garage Door”.
I think I follow you. I’m pretty sure with my setup I could use the unlock action, select “Turn On Switch” and then select my Garage door relay switch, which basically needs a “turn on” command for both open and close, since it resets to the off state. I don’t know how the GoControl is configured inside ST.
Are you still losing signal with your keypads? I’m about to give up and return my 2 Iris v3 keypads. They consistently disconnect within a few feet of my hub. I have to think there’s no way they could handle 25 ft away.
Yes, it seems to disconnect a lot but seems better with the latest DTH from a few weeks ago. But it also seems to work most of the time so I’m also wondering if it is like somehow designed to go to sleep and wake up. I have to think that there is something that the IRiS hub does that is different – unless people there are having the same issues. Maybe I’ll give IRiS support a call.
I’ve also been having an issue with the keypad draining the batteries. I had that happen twice recently but I think it is oddly related to the location I had it. I’m not sure yet but what I had done was put it inside a cabinet which also happens to have a battery-powered PIR-triggered LED light and, although I almost can’t believe it, I suspect that it was constantly getting triggered and caused the batteries to drain in a matter of days. I moved the keypad, we’ll see. Another weird behavior perhaps.
I haven’t decided what I’m going to do. But yeah, I’m frustrated and would jump at almost any Zwave keypad (or even another ZigBee) if I could find one.
Have you tried using a ZigBee repeater? It’s been fairly stable when using it through a repeater (Away from the hub). However when used while it’s directly connected to the hub, it seems exhibit issues maintaining a connection.
Maybe, or at least I thought I was. I have a few other ZigBee devices but perhaps they aren’t repeaters.
Is there a way to tell the difference or find list of ones that are? And how would I know if the device is using the repeater? Finally where would one want to position said repeater?
Sorry for the amateur questions, just limited experience with ZigBee as I only have the Halo, Hampton Bay, Sinope, and the ST fob. I had heard about some plug device, loosely called a “peanut plug” that folks use with the Hampton Bay device but I never had any issues so never investigated until now.
Most mains powered ZigBee devices are repeaters (except bulbs because folks tend to turn off the switch). See this topic:
Battery life is a function of usage and how much radio power / retransmission is needed (keeping aside the hardware design). It seems to have a longer battery life when used with a repeater.
For closing the garage door through LUM just assign a door/lock specific/individual “lock” action to close the garage when the keypad is locked.
EDIT: Regarding battery, don’t forget to set the battery type (Lithium, Alkaline, Rechargeable) in the device preferences page (gear icon) as it reports the remaining battery life based on the battery chemistry/discharge curve.
Thanks @RBoy, this makes sense about the repeater. I picked one up and will give it a shot later this week. I guess the Peanut one is popular because it’s only $10 and others claim it works great for them so we shall see. And it turns out that the Halo devices are not repeaters despite being powered (not to mention that I found out at the same time the company is gone, yick!).
As far as that, I don’t think this is possible with the v3 keypad unless you just use it to control the garage door, no? I mean that since you don’t enter a code on the v3 to lock/arm/partial you wouldn’t be able to distinguish arming the system from closing the door and would thus be forced to have two separate keypads I think. Or did you see it in a different way?
It’s treated as a keypad lock without a code, like a Yale or Schlage keypad lock with One touch mode/Lock n Leave enabled.
I think I’m missing something.
Assume I set up the v3 keypad with various users, each with a code and in LUM Iset up the keypad to control SHM. All is well as I can arm the system without a code and On / Partial or disarm the system by entering my code and the Off button. I think this precludes me from using the same keypad to control a garage door because while I could open the door with a disarm, when I hit On / Partial I don’t enter a code and LUM would just arm SHM.
It would still “lock” the keypad which will generate a Locked via Keypad event with no code (like the Yale/Schlage locks I mentioned earlier)
The SHM/ADT arming/disarming is a feature of LUM that will be used to control SHM only if enabled in the app.
The keypad DTH still operates like a lock device that locks when you “arm” it and unlocks" when you disarm it which is used by LUM to take actions. If there is an associated code with the lock/unlock event it can be used to create user specific actions, if not it can still be used to generate generic Keypad lock/unlock actions correspondingly.
Enhanced ZigBee Keypad Lock - Version 01.05.08
- Fix for some keypad models (IRIS v3) dropping connections/losing status
- Panic button resets automatically after 1 minute
- Turn off built in Alarm/Siren when keypad is Disarmed
A SmartApp like Lock User Management or SHM Delay etc is required to arm/disarm SHM directly from the keypad.
Real-time Updates With SmartLocks
TIP: While this device handler is compatible with SmartLocks, if you would like to see real time updates to the dashboard in Smart Locks (locking, unlock etc), change the name of the device handler in metadata section around
line 70 from
name: “Enhanced ZigBee Keypad Lock”
name: “ZigBee Lock”
Publish -> viola, real time updates in SmartLocks
I’'m sorry if this is a question that has already been answered or the answer is implied. I have an existing Xfinity security system that is monitored by Xfinity. Will this app/device handler allow me to integrate Xfinity Home Security into Smartthings?
This allows you to integrate the Keypad with ST instead of whatever Xfinity hardware you have. It’s not a bridge.
Keypad beeps stop working?
Do I miss something here, as soon when I use Rboys DTH on my Iris v2 (3405-L) keypad the keypress beeps are just faint clicking noises, however when I press the option in the App to locate the keypad I here normal beeps. When I switch back to the original DTH keypad beeps are working fine. I have checked the settings and made sure the beep length is on 1, I’ve also check this in the IDE. Any thoughts?