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.
Extra calls are not required, I’m using the script as is right now and it works perfectly.
i see, i am not sure why it complains for me, i will reload HA and see if this fixes it. thanks for the code again
1 Like
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?
I’ve since adjusted it:
1 Like
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.
https://github.com/kschlichter/Home-Assistant-Inovelli-Red-Dimmer-Switch
3 Likes
I’m just getting in to Home Assistant. How does something like this get implemented into HA. I’m running HassOS on a Virtualbox VM. Do I add the contents to the configuration.yaml file or include a reference it somehow?
Generally speaking what’s the best way to incorporate files from GitHub into HA?
Sorry for the NewB question.
Everybody has that question at some point. I certainly did at first. You can split up the configuration.yaml so that Hass adds *.yaml files in the /config/scripts subdirectory. I use Docker, so maybe the VM doesn’t use /config but it’ll be a subdirectory of wherever your configuration.yaml file is. The exact line in configuration.yaml looks like:
script: !include_dir_named scripts
Then you can either pull the file from git and link it into that directory, or copy it and paste it into a file called WhateverYouWant.yaml
I’m still holding on to hope that the Node-RED Inovelli Status Manager will get updated for ZwaveJS.
1 Like
I’ve forked the original to add more functionality, I can try to update soon to tailor it to Z-Wave JS
4 Likes
Great tip! I also learn if you want to keep your original scripts file intact, but still include scripts in a subfolder (e.g. “./scripts”) it would look like this:
# Origianl scripts file pointer
script: !include scripts.yaml
# Pointer for new folder
script split: !include_dir_merge_named ./scripts
this ensures nothing breaks, even if you haven’t ever used your scripts file, its good practice to keep it there incase you use a frontend tool that expects it.
That would be awesome I looking forward to this as well. I was able to install into node-red but no changes to lights. Can’t wait for zwavejs to be supported!
Right now the node runs fine and sends the correct Z-Wave JS commands, however the values aren’t updating within Z-Wave JS (at least for my add-on). I’m thinking it has something to do with this pull request from the Z-Wave JS Python dependency which allows values outside of the predefined states for the parameters. This has been merged and added to 2021.3.5, however I haven’t tested yet. Fingers crossed, I’ll update the code immediately if any changes are needed!
I think the Node Red module was for the old Z wave. I just send a service call back to Home Assistant and it works OK.
Service call node
Domain: zwave_js
Service: set_config_parameter
Entity_ID: light.upstairs for example
Data:
{
"parameter": "13",
"value": "Red"
}
Updated the gist for version 2021.4.x and up.
2 Likes
I added a Node Red option very similar to this script for anyone who prefers that:
3 Likes
I haven’t tested it, but the node as I’m seeing it in the UI is exactly what I’d hoped for. The only issue I see is that entity IDs are not auto-populating as they do in every other node.
EDIT: Just tested, and I can’t seem to get an LED to respond. LZW31-SN; set to Z-wave JS integration; color 0, brightness level 10, duration indefinitely, effect type fast blink; node shows “sent color: red” underneath when triggered… but no change in status LED.
I’m using the Zwave JS to MQTT integration. Could this be the reason it’s not working?
No this addon/container works fine.
Unfortunately this node is independent from the official Home Assistant websocket node, so at the moment I’m not sure of a way to auto populate the entity_id field. As for not seeing a change with your output, did you connect the output of this node to the input of a HA call-service node?
I did not! Should the call service mode just contain the entity ID of the switch or dimmer?