I have paired 2 units, one of them twice and never had that issue. I did get confused as to which button is - and which is + as I had one upside down, if there is a right side up...
Have you tried the new driver?
It does power source. I haven't messed with the sounds.
I received an email advertising the Zooz Z-Wave Long Range Siren & Chime ZSE50 800LR. Their website says it works with Hubitat but it also says "Hubitat custom driver coming soon." So, I'm not sure if that means it will eventually work with HE or it currently works with HE.
Is anyone currently using the device? TIA for any info.
Search and ye shall find!
I got that email and ordered a few, should arrive in a few days. Emailed support and they stated the built in Hubitat driver will do most functions and the advanced driver is due to be ready in a few weeks. My main use is .wav or .mp3 files to be played for local voice announcements and they said that works with the current Hubitat driver.
I'm currently using the ZSE50. The generic driver seems to work okay. I have been able to include it in rules to play audio clips based on water lead detection and open/close sensors. It does have a battery that I was hoping could be used to determine if the power goes out but no luck so far. Hoping maybe the custom driver will work for that.
I received one yesterday. I am not too impressed with the volume. It is by no means loud at all with the volume at max. You would almost need to put one in every room for it to be effective as a "siren". It is more like a tiny speaker. I put it in the hallway right outside my bedroom, and with my bedroom door closed I can barely hear it. It definately would not wake me up in the middle of the night even if I put it in my bedroom
Hubitat team is working on a native driver which does expose powerSource as an attribute with description "Master Bedroom Chime AC mains disconnected" -- and a RuleMachine conditional can check "Power Source" for these devices as "mains" "battery" "dc" and "unknown" so I'd say yes, when the driver hits mainstream, you should be able to use this to detect loss of power nicely. Not sure what others on the custom driver front are doing, but it looks promising. ** Update, I just wrote a trigger based on power source change on my units, does the trick nicely!
Thanks for the info John. I look forward to the update from the Hubitat team.
How are you using it in Rules? Basic, Rules machine, etc. I add the device, but when I go to create a rule, the device is not there. Can you post an example of how it's defined as a device in a rule? Like a switch, audio device, etc. I asked Zooz about that and they didn't have an answer.
Finally found where the CHIME settings are in the drop down. Was driving me nuts.
Can you please share how you were able to get the siren to show up as a trigger? I can't get it to come up.
I used the app "Hubitat Safety Monitor". Within the alert section there's a "Siren Alerts" feature. Then select your siren.
Just updated my C7 hub and swapped to the new driver and all is good. Power monitor works, alerts work. I'm using rule machine to announce when different things happen. For example, if someone opens my shed door, a custom alert announces "Shed door open." It's not a loud as I would like but it adds an extra layer to the notification I previously setup. The power monitor is more useful. I have a rule setup to notify me when power drops and is restored. My hub is on a UPS so I get the alerts that the device switched to battery.
Anyone else using the new driver and finding that when you use the chime function, it just repeats the sound over and over again?
It seems like it's related to the siren playback loop function. If i set that to only play once, the sound only plays once but then of course the siren sound only does one loop as well which isn't ideal. I think there might need to be separate device preferences for chime vs siren.
Yes. Main advantage I see is being able to change default settings. And just trigger the siren rather than entering siren number. Although one has to set the siren number, which I didn’t catch at first..
So you want to be able to use one device to do both a single "chime" for certain events, but then also play on a loop for others, is that correct?
I could see that being useful if you wanted to use it for say a doorbell ding but also for something else like an intrusion siren, or a water leak siren.
It could be done with a custom driver, but since that loop vs single play setting is a device parameter the driver would have to verify/change the setting every time it switches. Would probably add ~1s delay to the sound playing.
I will take that into consideration when I get to the point I can work on a custom driver.
Yeah so here's my scenario that i use:
Prior, I had always used the old Aeon siren as a door chime and just a single beep, but i just accomplished that by triggering the beep command and then of course used the siren function for major events.
With the ZSE50 what i've been doing is running a chime command for each door i have, with a custom recording for each door...so i get "front door" when i open the door for example. Problem is that chime function being in the same boat as siren as you mentioned.
End goal here is a door chime that can also act as a siren on occasion, where the siren loops until cancelled but the chime action only runs once. I had some other ideas in my head of having it say things like "water leak detected" or other events beyond intrusion alarm but that wasn't as important in my mind.
Side note after reading your comment about needing to switch the configurations every time, not sure that is as workable. Goal for me was to have as delayless of a chime as possible. I might just stick with what i've got going on here and maybe someday Zooz will add some additional functionality or something, but worth considering imo.
Whatever rule or app you use to do a chime, issue a stop command after a couple seconds. Would that not work?