I’m new to ST and I’m sure someone has already asked this…
I am trying to get my Zooz ZSE33 chime/siren to activate in different modes for different states. I have the device handler and can change the Bell/Chime/Siren audio selections. Here’s what I want to do:
Home (Perimeter monitored)-When a perimeter door or window is opened, the Zooz sounds the bell.
While Arming for away mode-During the delay to enter/exit time period, the Zooz Chime sounds during the countdown.
While armed Armed (sleep or away)-If a device is activated, the Zooz Siren sounds
I can get any one of these to happen but not a combination. Is it possible to program this device for multiple functions depending on the status? My alternative is to have 3 of them doing different things.
System configuration currently is as a security system:
Sonos speakers (love the Dogs barking on alarm!)
Zooz Powered Siren (not installed yet)
Echolink Door contacts wired to existing door and window switches at the legacy alarm panel
FYI-I just set up the system and have not completely figured out the best way to program features so this could just be my learning curve.
You’ll need to use the right device type handler (DTH). Fortunately a community member has already written one that should work for you.
So now the question is how do you find it. There’s a lot of information in the forums. but it can be challenging to sort through. Happily, the community – created wiki includes quick browse lists which greatly simplify this process.
One) go to the quick browse lists in the community – created wiki
The one you have works, but because of limitations of the device, you use a switch for one sound and an alarm for the other. This makes one device look like two, so you can set up different automations for each. For any further questions, ask in the author thread for that device type handler and people there will be glad to help.
You can’t use multiple device types, because a single device can only be identified with one device type handler at a time in the SmartThings system.
Instead, you have to have a single device type handler that either creates multiple virtual end points or that uses different capabilities. That way there is only one device type handler, but there are multiple ways into it, which is what allows you to create individual automations for each.
@krlaframboise is a grandmaster at this type of coding. If you are using one of his device type handlers, just ask any follow-up questions in that author’s thread. In that thread they will be able to explain how to set up the configuration to accomplish what you want.