Anybody knows if there are any plans to implement the beep capabilities of the V3? It would be nice to hear the chime when doors are open or closed, or when the system arms and disarms. Have they said if they will activate this feature?
It's already there...
I have an Iris V3 keypad using the V3 driver and latest hub updates. The keypad sounds when arming, but I can not get it to beep on command or via a rule at all.
Does it beep from the driver?
No sir. Not from the driver command nor RM.
Interesting, does the keypad work at all?, any sounds out of it? Beep works, and there's only one firmware version for these that I'm aware of...
Yes, it chirps and flashes when I arm it. Motion lights it up. It arms and disarms my HSM.
I saw a post earlier about using the beep as a door chime. That is when I discovered it would not beep on command or through a rule.
How do I determine the firmware version on it? It shows to be an Iris Model iL02_1.
I reported this days ago.
You can't without an Iris hub.
Ok, and mine beeps, yours doesnt, same driver.
It's impossible to fix something that can't be reproduced.
Okay.
Have either of you tried joining the device from scratch?
I was going to tomorrow. I will try it and respond back.
I noticed this in the logs when I click the Beep button on the device details page. Don't know what it means and it may not reveal a clue at all.
[dev:1060](http://192.168.86.5/logs#dev1060)2019-04-05 11:26:36.198 pm [info](http://192.168.86.5/device/edit/1060)skipped: [raw:catchall: 0104 FC04 01 01 0040 00 3C8D 00 01 104E 0B 01 0083, profileId:0104, clusterId:FC04, clusterInt:64516, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3C8D, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:104E, command:0B, direction:01, data:[00, 83]], description:catchall: 0104 FC04 01 01 0040 00 3C8D 00 01 104E 0B 01 0083
[dev:1060](http://192.168.86.5/logs#dev1060)2019-04-05 11:26:36.196 pm [debug](http://192.168.86.5/device/edit/1060)descMap: [raw:catchall: 0104 FC04 01 01 0040 00 3C8D 00 01 104E 0B 01 0083, profileId:0104, clusterId:FC04, clusterInt:64516, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3C8D, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:104E, command:0B, direction:01, data:[00, 83]]I have the same issue. It behaves normally except it ignores all the rules where it is selected to beep.
My device was joined from scratch since I bought it brand new last week. Also, mine does NOT beep when clicking on the beep box in its device page.
BTW, while trying to figure out this issue I found out something I think it's cool. When you have a delay set up for arming, the keypad beeps to let you know alarm activation is imminent and you should leave. When you have more than one keypad, and have them all setup the same way, only the keypad where you pressed "ON" will beep this countdown; the rest of the keypads will start it but will stop after a couple of beeps. This is great because in the long run it saves battery power vs having every keypad throughout the house doing the countdown every time you go out.
I removed the device, factory reset it and rejoined from scratch.
It behaves normally except it will not beep on command or by rule.
Ok, let's try the reverse, how many people have the V3 running 2.0.8.113 platform and are able to make the device tripple beep using the driver beep command?
Mike, I had purchased a V1 Iris keypad, model KPD800. I know you had said no promises if this would ever work with Hubitat. I've now located more V2 Keypads on Ebay and was wondering if you think its a better idea to purchase the V2, that we know work, or just hold tight for a "Possible" driver for Version 1. Much appreciated!
@mike.maxwell, I have another V3 headed my way. I will install it next week. Maybe it is a firmware issue. Either way, I will post the results to whether the triple beep works or not on it.
