Support for Z-Wave Sirens/Chimes

madpb · July 6, 2018, 12:31am

Bump… Any progress on this? I was looking at the Dome or other sirens as well to add to my Home Assistant or if anyone has suggestions. I like the idea of chimes too.

netopiax · July 6, 2018, 4:32am

Please vote on the feature request here. The latest info is that Open Z-Wave doesn’t yet support the Indicator class and until that happens there’s nothing Home Assistant devs can do.

winter · July 8, 2018, 5:51am

This indicator class?

github.com

OpenZWave/open-zwave/blob/master/cpp/src/command_classes/Indicator.h

//-----------------------------------------------------------------------------
//
//	Indicator.h
//
//	Implementation of the Z-Wave COMMAND_CLASS_INDICATOR
//
//	Copyright (c) 2010 Mal Lansell <[email protected]>
//
//	SOFTWARE NOTICE AND LICENSE
//
//	This file is part of OpenZWave.
//
//	OpenZWave is free software: you can redistribute it and/or modify
//	it under the terms of the GNU Lesser General Public License as published
//	by the Free Software Foundation, either version 3 of the License,
//	or (at your option) any later version.
//
//	OpenZWave is distributed in the hope that it will be useful,
//	but WITHOUT ANY WARRANTY; without even the implied warranty of
//	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

This file has been truncated. show original

winter · July 8, 2018, 5:52am

Oh, it’s referring to the python wrapper not supporting the indicator, no the openzwave library itself.

netopiax · July 8, 2018, 5:57pm

Yes, sorry, I should have been more specific. pyozw does not currently support sending the commands related to the Indicator class. The C libraries do correctly recognize support for the class and, as we can see from the header, have the methods we need for set/get.

kvermilion · November 1, 2018, 10:04pm

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:

dinth · November 1, 2018, 10:47pm

Is it possible to adapt this somehow to use Fibaro Siren’s chime?

kvermilion · November 1, 2018, 11:24pm

If it uses the z-wave indicator class, likely yes.

skynet01 · July 3, 2019, 1:16am

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.

netopiax · July 5, 2019, 2:40pm

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.

skynet01 · July 5, 2019, 9:00pm

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

skynet01 · November 9, 2019, 7:22pm

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.

netopiax · November 9, 2019, 7:39pm

Sorry - haven’t run into that…

morrowsend · January 3, 2020, 3:47am

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?

skynet01 · January 3, 2020, 5:09am

@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.

morrowsend · January 3, 2020, 5:49pm

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 :

skynet01 · January 3, 2020, 5:53pm

have you tried just using call service option in developer tools instead of the script?

Holdestmade · January 3, 2020, 5:59pm

The number you have copied is not the same as in the siren indicator more info box, there is a 9 at the end ?

morrowsend · January 3, 2020, 6:10pm

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?

morrowsend · January 3, 2020, 6:10pm

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.