Probably a stupid question, but have you checked your batteries? All of my door/window sensors showed 70% and were working fine when I unpaired them from Iris. I had all kinds of squirrelly operations when I paired them with Smartthings! Doors that were closed, showed as open. When I opened the door, it showed closed! Some showed as open all the time, regardless of the actual door state, & vice-versa. Batteries now all showed about 45%! Replaced them all with fresh batteries, unpaired/repaired, and they’re all working fine now!
Hello, Is it possible to add a countdown beep when arming and disarming using the Rboy device handler with the Iris v2 keypad? If not, can anyone recommend how to do this?
Thanks in advance.
a) Code Entry on/off enables/disables code entry on the keypad. When it is off, the keypad won’t recognize any input.
Locked refers to the logical state of the keypad. You can use that to trigger lock state of actual physical locks with the
Lock User Management SmartApp.
c) Tamper only shows up if the unit is opened up. Once you close it (which presses a button down) the Tamper icons goes away. The
Panic button is a feature of certain keypads only (Iris v3)
I have several Yale locks and am using the Lock User Management app. I just installed the XHK1 keypad and this device handler and then added the keypad to my Lock User Management app. Suddenly, now I’m receiving all kinds of notifications that all of my codes are no longer compatible and code size is now set to 4 and programming will fail.
Is this device handler / device only capable of 4-digit codes? Or is this a configurable number? I can’t find anything in the config for the device handler for the keypad to allow longer codes, and I typically assign 7-8 digit codes.
Is the code length a limitation of the keypad, or is there a reason the device handler hard-codes the length to 4? I see a codeLength=4 setting in the code, can this simply be adjusted, or is the keypad only capable of 4-digit codes?
Yup, hardware limited to 4 digits…seems par for the course for keypads. I created a short and long code matched users and restrict the short users to only the devices that require a shorter length in LUM.
Does anyone know if this is compatible with the Zipato mini keypad?
Zipato mini a Z-Wave keypad, this DTH will only work for ZigBee keypads and has been certified/tested with the keypads listed in the first post.
I’m sure I’m doing something wrong, but I’m running into two issues after biting the bullet and buying the access to this option.
First of all - while everything installed nicely and I was able to set up our codes for the keypads and how I want them to change modes on the SHM from Away, Stay and Off, those ONLY seem to work on the OLD smartthing app - surely I’m doing something wrong???
Next, I found the setting where the keypad will beep when a sensor is triggered, such as a door to open - but it will only allow me to set it for ONE?? Our house has 4 access doors and with Iris I was able to set that the keypad would beep when ANY of the doors would open…surely this is as powerful if not more, than the old Iris system.
Congrats on getting this far. I am also a previous IRIS user and refuse to bite the bullet to buy a Rob Roy application for as much as what a proper Smarththings device should cost to do the same thing, if Smarththings would listen to their consumers that is.
I have found out though in your problem that what happens in the Classic app does not happen in the new app. My wife is using the classic app because it responds better for her on her phone. But, when she sets the alarm it doesn’t show that the alarm is set in the new app, on my phone. Automation set up in the new app may also not work being that the alarm was turned on in the Classic app. I can’t understand it and I hope someone does. You would think that the app is controlling your Hub settings but that doesn’t seem to be the case. So, when the wife sets the alarm in her classic app she has to be the one that turns it off, I can’t. I would try to only use the new application in setting up your device to work properly.
@Speedy and @Scbart52, I haven’t been following your scenarios, but are you guys aware that SHM in the Classic app is completely different from the new app? In case you’re not, there’s an FAQ on the differences posted in this community somewhere. I’m on my mobile right now, so I can’t easily find and include those links for you right now, but do a search on SHM differences and it should turn up.
Looked for it but can’t seem to find what I think you are referencing so when you get a chance could you send that link? Thanks.
Yes I am aware that there are differences but I didn’t think those would block the keypad for working as it is intended. As it is currently the RBoy app is pretty much worthless as it doesn’t operate the changes as it should nor does it allow “beeps” to be set up for more than one door.
RBoy Apps is now a SmartThings partner for Centralite
Enhanced ZigBee Keypad Lock - Version 01.07.00
- Added support for activating Siren/Alarm in IRIS v2 (3405-L) keypad
After updating the DTH, tap the Refresh tile on the ST Classic app device page to display the new Alarm tile.
The Iris v2 (3405-L) has a built in 60dB siren
The Iris v3 (iL02_1) has a built in 85dB siren
Both keypad siren can be activated when using the Panic button and also independently using the Alarm tile (from the Classic app). The Siren can also be activated through SHM or an app like Intruder Alert with Actions
NOTE: The built in siren feature is separate from the built in beeping feature. The beeping feature can be used as a Chime. The number of rings in a Chime is adjustable and can be defined in the preferences page (gear icon in the ST Classic app). The Chime can be used as door bell or a beeping trigger when a door/window sensor is opened etc. You can create a rule in CoRE or WebCoRE to trigger the chimes/beeping using the Tone capability.
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 74 from
name: “Enhanced ZigBee Keypad Lock”
name: “ZigBee Lock”
Publish -> viola, real time updates in SmartLocks
© RBoy Apps
UPDATE: ST has fixed the platform so all the newer SmartApps like Lock User Management (LUM), Rental Lock Automater (RLA), Lock and Door Synchronizer, SmartLocks, CoRE, WebCoRE etc will continue to work with the existing Enhanced ZigBee Keypad Lock DTH. This update in only required if you’re using SHM Delay, Keypad Coordinator or any legacy apps
Enhanced ZigBee Keypad Lock - Version 01.08.00
- Compatibility update for SHM Delay v2.2.9, Keypad Coordinator etc (legacy SmartApps)
Hello I am having trouble getting the entry and exit delay working via LUM. It seems there is some native functionality which is immediately arming the system and immediately causing an intrusion when the LUM delay is working except it gets overridden by the built in functionality?
For example, if I arm via the keypad, it says waiting 2 minutes to activate, but the SHM is immediately armed. If I manually disarm, LUM does successfully arm after 2 minutes. How can I prevent that initial arming from happening so I can use the delay? Thanks
Seems to be working here as expected. I would check if any other apps are connected to the keypad which may be arming SHM. You can check the Live logs and PM me the results, it’ll show what’s going on. The only other things to check is that you’re in the latest version of LUM
Actually it looks like it was a duplicate version of LUM which was causing the system to arm. I had multiple installed because I was trying to get the single IL021 to chime for all doors. Is there a different way to have it chime for all doors? Or do I need to duplicate the delay settings on each LUM app? I installed everything today so I assume they are latest versions. Thanks!
Right now it’s one sensor per lock for chiming.
This is a common request so we are working on a new app just for chiming/doors bells which will support multiple sensors and be a lot more flexible. It will have many more features like audio notifications and lots more than just a simple chime.
Subscribe to our Facebook page and you’ll get a notification once the app is released along with the details.
Ok thanks for the quick responses. One additional question - I’m not seeing an option for an entry delay, am I missing it? Would like to not activate the SHM alert unless it’s not deactivated in 2min for example.
Classic SHM doesn’t support an entry delay. You will need to create a workaround with a virtual setup using SHM Delay or use a Security system app which natively supports Entry and Exit Delays like Intruder Alert With Actions: