Multicast to ALL switches does not work. (Or I haven’t found a way to)
Multicast to a list of switches that all have the same parameter, DOES WORK. If you use a group, and that group expansion example, it’s nearly as good.
2 Likes
That makes sense as multicasting a Config param change to all devices seems like it would cause problems since different vendors devices may use the config parameter for different purposes.
I think @DaCeige meant multicasting to all the WD200 switches? I realize that other switches might not work, but should all the WD200 respond?
I believe that it is now supported by HA ( Z-Wave JS Config DB Browser ), but how do I create an Automation that sets the parameters depending on another device’s status in Trigger ?
I currently use the WD-200 with another hub, but would like to move it to my HA.
How did you get a single LED to blink? Not the whole group of LEDS
This were the settings I had with the Universal Devices eisy hub. Depending on the IF (Trigger) the top ‘sentinel’ light would go red and flash.
I have not been able to do the same with HA. I ordered a HS 300 Dimmer, as I read in this forum that the HS 300 is more compatible with HA.
As you probably understand the “Balcony North” is the HS 200 Dimmer.
Would it be possible to show how to do this in the Visual Editor as I am not (yet…) comfortable with Yaml ?
I would like to reproduce in HA what I had in my eisy hub (Universal Devices) :
When using the HA Call Service, Set Zwave parameter, I get the same error
The above code looks like this in the visual editor…
Please note, the example above will work on all the switches as it sends a command to each switch.
If you have a ton of switches and need less zwave commands, you can rather substitute
service: zwave_js.set_value
for
service: zwave_js.multicast_set_value
Which will send one command to the whole group of switches with the caveat that if one of the switches goes stupid and doesn’t think it supports the command, then none of the switches will update.
(my feature request, stop validating the command before sending it, it’s multicast, but I digress)
This is the order I did it in.
1… service: zwave_js.set_value
2… service: zwave_js.multicast_set_value
3… use those groups I describe
Personally I use 2&3 for most my lights.
When the lights stop updating, I check the logs and there’s a switch that doesn’t accept the parameter. I go and re-interview it, and it keeps working.
Thanks so much. That is extremely useful Where does the ‘112’ come from ?
Now I know how to set the ACTION in the automation, but not sure yet about the trigger.
I would like the trigger to be when any of the lights in room A is ON then property 21 will be value 4 and if all lights in room A are OFF then property 21 will be value 2. How would I design the Trigger ?
Not sure… but this is where I found them from… have to investigate zwave stuff for why they’re called that.
Additional edit since I cant reply more than 3 times…
Here’s an example of one of my automations. Hopefully this gives you some ideas. More recently I started writing my automations together for off and on, and leveraging “trigger ids” to then set a condition based on which trigger ran… but get the first one working first.
(ps… make sure you enable status mode or else you wont see the leds change.)
Delete the {{ }} part to get it to show up in the visual editor…
alias: "StatusLED3 Basement - Motion "
description: ""
trigger:
- platform: state
entity_id:
- group.basement_motion_sensors
to: "on"
from: "off"
condition: []
action:
- service: zwave_js.multicast_set_value
data:
property: "23"
command_class: "112"
value: 2
target:
entity_id: "{{ expand('light.wd200_switches') | map(attribute='entity_id') | list }}"
mode: single
Yes, I’d like to multicast to all WD-200 or WD-300 switches. Ideally, being able to send to all the switches that support it would be nice for less complicated deployments.
Optionally, just a subset of the swtiches (works today)
I do not care if one if them is offline or not responding (does not work with multicast).
Thanks so much again. I am not sure to understand your example, but I think that I made it work like this, using YOUR Action command class 112, Property 21, Value 2 :
Trigger
kitchen device 1 state to off
kitchen device 2 state to off
kitchen device 3 state to off
Condition
kitchen device 1 state is off
kitchen device 2 state is off
kitchen device 3 state is off
Action
I have not yet figured out how to set a specific led (any of 7) to blink.
I tried
Command Class 112
Property 31
Value 6
but that did not do it.
1 Like
Not sure if I explained it well enough. This is one of my automations that turns on the second from the top LED to the color of white when my deck lights are on, showing status of the deck lights. I have both WD200 WD300 switches.
How can I also make the second from top LED blink? only when the trigger happens. I have other automations that turn this and other LED different colors and I don’t want them to blink.
- alias: Deck Lights Turned ON
id: DeckLightsTurnedON
initial_state: true
trigger:
platform: state
entity_id: light.homeseer_technologies_hs_wd200_wall_dimmer_level
to: 'on'
action:
- service: zwave_js.set_config_parameter
target:
entity_id:
- light.wall_dimmer_switch
- light.homeseer_technologies_hs_wd200_wall_dimmer_level
data:
parameter: '26'
value: White
Really thanks for your help…
I am trying to understand, but not so far.
What I really want to add is Parameter 31, Value 3
my reply was for DaCeige sorry
What version of Zwave are you running? I’m running the latest Zwave js.
Driver Version:
10.16.0
Server Version:
1.28.0
same as mine, change device_id to entity_id: and if that doesn’t work just use only one target at a time.
- service: zwave_js.set_config_parameter
target:
entity_id: light.20_21_balcony_north_all
data:
parameter: '26'
value: White`