This (z-wave indicator class) is implemented in 0.80
Check out this post I made to a similar thread & the one I linked to there:
1 Like
Is it possible to adapt this somehow to use Fibaro Siren’s chime?
If it uses the z-wave indicator class, likely yes.
Hey netopiax, did you by any chance figure out how to do the chime? The indicator sensor shows up now but i am not sure how to activate a chime.
Yes - there is a service called zwave.set_node_value you need to use. You will need the “indicator value id” for the siren’s indicator setting. Some additional instructions are in the last few posts in the other feature request thread.
Thanks netopiax, I got it working. For those of you interested here is the steps:
- go to dev-state developers tab, and find your siren indicator for me it was sensor.elexa_dome_siren_indicator (I have Elexa Dome Siren)
- get the node_id and value_id from attributes column
- use those parameters along with value:1 to fire off zwave.set_node_value service to get the chime
You can test it out by going to dev-service tab, selecting zwave.set_node_value and firing off this json
the value number 1-10 represents the chime that you will get
replace XX with your node_id and value_id values
{
"node_id": XX,
"value_id": "XXXXXXXXX",
"value": 1
}
Hit call service and you should hear a chime
You can then use this in your automations
1 Like
I know it’s been awhile …but do you by any chance experience repeat chimes when it only suppose to sound off once?
I noticed that out of 5 notification chimes, 1 of them will just keep repeating. Not sure if the issue is with Dome Siren or zwave.
1 Like
Sorry - haven’t run into that…
I can never get this to work with the value_id in a script even when I get the correct value_id from the Zwave area (LIke this:Z-Wave Indicator class support) it always throws the error “Failed to run script… extra keys not allowed @ data[‘value_id’]”
If I remove the value_id I get no error, however it does not change to the secondary tone, it instead will play the primary tone.
The only way I am able to change to the secondary tone is in the Z-wave configuration page, manually selecting the Node Config Options.
What stupid thing am I doing here?
@morrowsend, Looks like you are calling the wrong service, you should be calling zwave.set_node_value not zwave.set_config_parameter. The “value” number coresponds to what tone to play. Make sure you get the “value_id” of the *_indicator sensor that’s created when you set your dome siren.
You also don’t need the action part in your automation, you just need to fire-off that service call and it will play the chime.
Here’s what I tried, with no luck:
I copied this value_id and pasted it into the UI:
After saving and running the script, I get the error :
have you tried just using call service option in developer tools instead of the script?
The number you have copied is not the same as in the siren indicator more info box, there is a 9 at the end ?
So when I copy and paste it, it is correct. When I save the script, then run the script, it changes to end in 800. WTH?
Also, I get the same result when I use the call Service area. It is clearly printed as ending in 809, but the error I get shows 800. I want to eventually put this in an automation.
Very odd…
The value_id is too big for javascript. It works if you put it in quotes e.g.
node_id: 8
value_id: "72057594178551809"
value: 1
1 Like
A little old, but yes, I have a Zooz ZSE19 Siren/Chime, and it presents as a binary switch for the Siren, but nothing for the chime. Someone found a workaround by setting the parameter that determines the chime to sound, which most of the time, sounds ONCE. On many occasions though, and I can’t find a pattern, it might sound anywhere from twice to 10 times in a row on a single trigger. I don’t see anything in HA’s logs that indicate that it is repeating the command, so I think it is the device. The manufacturer says it is probably due to the way it is being triggered, i.e., not as designed. It is set to use a Sound Command Class, which the V1.4 OZW Add-on doesn’t support. I don’t know if it is included in the New OZW 1.6 beta or not.
I am now looking for another chime that will work correctly with HA if anyone has found one, preferably one where you can upload your own WAV files (which you can do with the Zooz).
i was finally able to fix this by moving the Sire closer to the hub and also sending an off command right after just incase.
Yeah, my solution works ‘mostly’, but sometimes I still get up to 5 chimes, and sometimes only the very beginning of the first one that is truncated. Most times it is a single chime. The logs show that the 4 second times I have set in my python script is working based upon the timestamps, but the problem is random lags in zwave comms. I see errors of no response from the siren and having to retry the send command, or sometimes the sends are sent 4 seconds apart (i.e., start, stop), but they reach the siren either back to back (truncated chimes) or spread out if there are errors (multiple chimes). I’ve pretty much resigned myself to not getting this to work reliably. Makes me wonder if the sound.switch function will work either, depending on how they code it. Having to rely on wireless for timing is unreliable at best.