That is not default behavior. You must have set up a rule or an app to do that. I would suggest removing it if it's not doing what you want. I can say, I have a v3 and it doesn't do that. How would it even know which contact sensors you want to do that for? or is it just every contact sensor in your whole system? And without an app, it couldn't know that happened. Devices can't talk to each other except through an app.
So the default behavior does not include a chime when the contact sensors are assigned in HSM? Interesting that would make sense then -- it just sees it as another rule to trigger the alarm then. Why wouldn't the chime function be a default behavior? I also tried to do a notice for when a door is left open -- to send a text message if open for longer than 5 minutes. That does not seem to work either so far. I really do not understand the need for more than 3 modes in HSM -- Home, Away and Partial -- but offers Day, Night and Evening and I guess these modes may be useful, I just haven't figured it out yet. I am really new to all of this so it will dawn on me in time.
I just have Home and Away Modes now.
HSM does not do chimes for open/closed sensors by default. I think this makes sense. Not everyone wants chimes just because they're using contact sensors to detect intrusions in HSM, nor would it know which sensors are actually doors (they can be used on windows, refrigerators, washing machines, or anything) or which chime device(s) to use or how to create the desired effect (some like the Dome support multiple chimes; others will do a non-stop siren if just sent a simple "on" command). It's easy to set up yourself with a custom rule, but I don't think you want to do this either. HSM custom rules will create an "alert" that has to be cleared in HSM, otherwise you'll see HSM as having an "alert" every time you look at the app list or load the app in the admin UI. HSM is really meant for things you care to (need to) acknowledge. That could be leaving a door unlocked, but it's likely not opening a door...but the choice is yours. Blank canvas to do what you want. 
For the text that isn't working, you may wish to post a screenshot of your rule to see if anyone sees problems. Also make sure that your number is in the exact format specified and that you haven't exceeded the 10/day limit (consider other notification services like Pushover or the forthcoming mobile app to work around this).
As for modes: HSM does not offer Day, Night, and Evening. It sounds like you are talking about mode (sometimes also called location mode). Away, Day, and Night are the default modes, but you can create as many as you want. These are not tied to HSM. They're for Hubitat as a whole and can be used for any purpose, but most people use them to restrict apps/automations (e.g., don't run this lighting automation in day mode, or only run this automation in night mode). HSM has only Armed-Home, Armed-Away, and Armed-Night, plus disarmed (and "disarm all rules," which will stop the execution of any custom rules you made as described above; there's also a momentary "cancel" action that will cancel the alerts from these rules). Location mode and HSM armed/disarmed status are separate, but it's confusing because "Away" is included as a default location mode (that is something I have yet to find a use for; I do use modes but for mostly determining how my lighting automations should operate based on time of day).
1 Like
Thanks -- the text are working now. If you do not use HSM for the "chime" feature, what other app would one use for that purpose -- esp with this keypad? I already miss that feature coming over from Iris. It is something I def need with kids in the house and to monitor the coming and going. I have heard some use Alexa and I have yet to find that option.
Here’s what I use. It requires Google Assistant Relay, but that is a very useful tool for other thing, so it’s worth the extra effort. Most solutions require a Node.js server. However, you can do it all cloud.
A few of the options are linked to in my post.
In addition to the above suggestion, you could also just use Rule Machine. (It's a bit complex if you're new, but you can find help here if you want.) There are probably also purpose-built apps that can do something similar with a bit less work (besides installing the custom code), but I haven't used any.
You could also just use a siren that has a Chime function like the Dome Siren. That along with a simple rule in RM and there you go. I have the following rule set up. I have the delay there so that if the sensor rapidly closes/opens multiple times when it's triggered (can happen when the batteries are dying) i don't get like 100 chimes in a row.
I have ordered the dome siren (I already have one without the chime); I was hoping the chime would work on the Iris Keypad like it did on Iris, seems it should be simple but no big deal, will figure it out. I will give your solution a try when the dome arrives.
I am looking into the TTS configuration -- but wow.. that is really complex with the node portion.
Thanks so much for all the responses.
@mike.maxwell Absolutely LOVE the new Iris Keypad Drivers. KUDOS!!! A couple of observations:
-
With the V3 keypad, if I use the "beep" function sometimes I get one, sometimes I get two. At first I thought it was tied to first command versus second command but further testing proved that untrue. It seems random.
-
When I arm-away HSM from HE, I am able to cancel arming from one of the keypads (v2 and V3) and that in turn disarms the other keypad. At this point both keypads are in sync. However, HE still displays as Armed Away and alarms still trigger. If I cancel during arming from HE, then it cancels the keyboard countdowns and leaves HSM disarmed, correctly. Also, when I go back in and then disarm HE from the App's page, the keypads finish their armed-away countdown and are armed-away even though HSM is now disarmed. There seems to be something going on with this situation.
-
During Delayed-Intrusion there is a noticeable delay between entering the code on the V3 keypad and the system disarming. So much so that the alarm went off on me several times while i was testing it. I believe this might be related to how the beeping. It seems to be VERY close together...almost too much so at this point. Which brings me to my next point.
-
The beeping for delayed arm-away and delayed-intrusion on the v3 keypad is great to have but it's very overwhelming. Especially for delayed armed away. 1 every other or every 3rd second until the last 10 seconds is plenty, IMHO, for delay-armed-away and for delayed armed intrusion. There is so much beeping now that I might go back to the Centralite driver for my V3 keypad. I have it on the lowest volume setting and it's a big much.
-
The Alarm function on the v3 is VERY inconsistent to control. During one of my accidental alarm triggers during testing, my Dome siren shut off immediately and continual presses to the off command on the device edit page did nothing. It went off for close to a minute. I as on my way to pull the batteries when it finally stopped. Don't know if this also has to do with the multiple commands being sent to it for the beeping but I won't be using the siren function on this one I'm pretty sure. Don't know if there's anything that can be done but thought I would mention it.
That's all for now. I'll prolly have a bunch more when I start digging into it further. If you want me to pull any logs or anything feel free to reach out here or by PM. Thanks for all the improvements. It's definitely getting better. Just a few rough edges that need sanding down at this point. Really great work!!
@tebiv1, where did you find the Dome siren? I have been trying to order one, but everywhere I have looked is sold out. Don't know what is going on with them.
I found a used one on Amazon -- add this https://www.amazon.com/gp/product/B01M1NLPKZ/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 to your wish list and if one becomes available you will get a notice. The company said they are sold out for now.
I didn't see anything in the 2.08 documentation regarding driver updates for Iris V3 keypads. Were the issues addressed with this update?
Yes,
.
1 Like
Thanks Mike.
Just in time for my v3 to arrive. Sweeeet. 
1 Like
There's still issues per the release notes...
Where are those listed? I don't see anything called out in the 2.0.8 release on the forum.
