Added zwave_integration at top of “variables:” section to allow users to define which integration is installed (“zwave”, “ozw”, “zwave_js”). I just don’t see a simple way to auto-detect this.
Added a comment describing the “model” variable.
Replaced personal “script.debug” service call with universal “persistent_notification.create”. Unremarking these lines could help you troubleshoot why something isn’t working as expeceted.
Updated broken spreadsheet link with public copy stored in my Google Docs account. Thanks for the heads up @kschlichter!
I’m trying to get this to work with Zwave JS. I’m not sure it’s possible yet. I think your script will work but I can’t get it to work manually with the configuration piece. Has anyone tried this with Zwave JS? I know they just allowed the ability to use the configuration parameter in the last release. Also btw I did get the scenes working, thanks again for helping me with your code!
I haven’t tried this script specifically, but if you have any of the Red on/off switches (LZW30-SN) it could be that Parameter 8 on the zwaveJS side is broken up into multiple parameters. I had a similar script I had to break out into four service calls to get the notification light to work. Check this out for more info: https://github.com/zwave-js/node-zwave-js/pull/1411
Thank you for forwarding the information. Not sure if it’s possible yet based on the information you provided or I might need to play around with it more since Parameter 8 is broken up.
I can confirm that the script doesn’t work with my LZW30-SN because of the parameter 8 thing. Thanks for pointing us to that GitHub PR@DaveCo1701. I’ll keep an eye on developments there.
I was thinking about buying the dual fan/light switch but was wondering… I see that obviously the leds take a little work but do the switch/buttons work out of the box? Like recognized in HA and stuff.
Inovelli Z-Wave Fan & Light Switch (Red Series) | ZWave Fan Control & Light Dimmer | Independent Controller of Fan Speed & Light Bulbs https://www.amazon.com/dp/B08665WJ2B/ref=cm_sw_r_cp_api_glt_fabc_VTDWYN3ZSW7XCJRYYV6N
Here’s how I’m using the new calls at the moment. It does support both the single param method as well as multiple calls for the other switches. I’ve got a PR in upstream to fix the max value for the lzw31-sn param and see if it should be split apart like the other switches.
It’s also got a set of input_number and template sensor to calculate the value for the duration since that’s not fun to try to do by hand.
With the release of the fixed configs, I’ve updated the above script to use just the named parameters which simplifies the logic immensely. Please note that the zwavejs version is important to make sure the updated configs are there, and I also had to restart Hass in order for it to see the right values.
thanks @firstof9, the code complains about a duplicate “target”
I believe you have forgotten the service call above each target but have to go home and try it.
This works for me.
The weird thing is that I am using the script with the 4 separate messages and it works for the switch, fan, and fan light devices but doesnt work for my dimmers. But then i try the script that sends one message it does work on my dimmers and not the rest. So I ended up calling different scripts for now. Anyone else have this issue?
Standing on the shoulders of giants, I’ve written a script to configure the indicator color alongside—or separately from—the effects. I use the LED indicator strip more than the effects, and it didn’t look like anybody else was doing this. It should be straightforward to use. The current version of the script is for zwave2mqtt container 2.4.0, but there’s a version that will work with 2.2.0 in the history for the script.