It looks like it’s either not getting a value for the LEDcolor, or maybe I have the parameters wrong. You should be able to set LEDcolor on its own without ledbrightness but try sending both just for debugging.
I do not envy you. I gave up trying to get single LED control on my blue to behave in an expected way. Sometimes the single LEDs just refuse to turn on until an adjacent one is lit.
I’ve played around with using multiple colors across the different LEDs but found that I could really only do 3 “zones” at once. I did have that working but decided I didn’t like the look of it so gave up. I think the defuser smears the light to much to actually have 6 distinct color zones. Regardless you have to do pretty contrasting colors to get useful information out of it and it’s just kinda ugly that way.
It looks like I have the LED indicator intensity parameter wrong, but your logs are complaining about the LED indicator color, parameter 13. Can you show me the code you’re using to call the script? You’re using 2024.03.28 (the latest release); right?
Sorry my responses are slow. I’m busy with work but I do want to get this working for you.
Go to settings → automations & scenes → blueprints. Find this blueprint, click the vertical 3-dot menu and click show scripts using this blueprint. Find one that’s been called recently, click the vertical 3-dot menu and select traces. Click on “changed variables” and send me the text in there. The line, Node(node_id=6) - InvalidNewValue: State '' not found for parameter 6-112-0-13, looks like there’s nothing being passed for the LED color.
Ok. I ran it again and you were correct that I did not set the LED color (because I actually didn’t want to change that). My intent was to try to send effects to the black device and to see how you did that.
Changing the LED color while on works fine. Changing the LED color while off to something other than the color-while-on does not appear to be working.
Additionally, and not really all that surprising, “effects” aren’t working at all on the black device. I assume it’s not actually supported?
Changing the LED color while off to something other than the color-while-on does not appear to be working.
Black Series and Red 500 Series devices (like I have) don’t support different colors for on and off. That’s only supported by Red 800 and Blue Series devices. What you’re seeing is expected.
Additionally, and not really all that surprising, “effects” aren’t working at all on the black device. I assume it’s not actually supported?
Right; the Black Series devices don’t support effects. My blueprint and script will ignore effect settings for Black Series devices.
I should be failing in a cleaner way though. If you had a combination of Black Series devices and devices that do support effects, or LED color when off, I shouldn’t be generating errors for the Black Series devices. I’ll fix that before the next release.
I do have a mix of devices but was only using the blueprint to send commands to the black series. I use scripts and scenes for my existing devices. (The black one is new, got it cheap and wanted to make it work).
Got it. Well, for what it’s worth, my goal with this script is to let you do everything with a single blueprint. By calling areas, groups, and soon labels and floors, you don’t have to worry about which devices are where–the script should just figure it out. I’ll figure out the errors. The Black Series is really limited in its features though.
There is a beta firmware for the black that enables “scene” control via button presses but in my experience it is less stable with low power draw in non-neutral scenarios. I will probably grab a bypass and roll back to that firmware and see what happens. I’ll let you know if there are any issues with this blueprint at that stage.
Is this the Black Series Dimmer with the LED bar that runs the full height of the paddle, or the Black Series Switch with a single LED? Your screenshot from the Z-Wave JS configuration looks like the dimmer and not the switch but maybe the Z-Wave JS config DB is wrong, which would explain the errors.
I’m stumped. My Red 500 Series devices change the LED brightness on and off without errors, even when I don’t set anything for LED color. I’d be interested in seeing the value of LEDcolor in the changed variables section of the trace (comment 47). For me, I’m seeing:
LEDbrightness: 7.7
LEDbrightness_off: 2.1
LEDcolor: no change
but yours seems to be blank. The parameters I have for the LZW31 match the config database and what you showed me:
I think I’ve figured it out. I get errors similar to yours if I set LEDcolor to ‘’ or ’ ’ instead of leaving it blank or a valid value. Make sure your blueprint has LEDcolor either unchecked, or set to a valid value, like “white” or “off” when you call it. I think it has to be something with how this variable is set when the script is called.
2024-05-12 08:24:06.934 ERROR (MainThread) [homeassistant.components.script.inovelli_led] Inovelli LED Settings and Effects: Repeat at step 2: Choose at step 2: choice 1: Choose at step 1: choice 1: Error executing script. Error for call_service at pos 1: Node(node_id=4) - InvalidNewValue: State '' not found for parameter 4-112-0-13
2024-05-12 08:24:06.934 ERROR (MainThread) [homeassistant.components.script.inovelli_led] Inovelli LED Settings and Effects: Repeat at step 2: Choose at step 2: choice 1: Error executing script. Error for choose at pos 1: Node(node_id=4) - InvalidNewValue: State '' not found for parameter 4-112-0-13
2024-05-12 08:24:06.934 ERROR (MainThread) [homeassistant.components.script.inovelli_led] Inovelli LED Settings and Effects: Repeat at step 2: Error executing script. Error for choose at pos 2: Node(node_id=4) - InvalidNewValue: State '' not found for parameter 4-112-0-13
2024-05-12 08:24:06.934 ERROR (MainThread) [homeassistant.components.script.inovelli_led] Inovelli LED Settings and Effects: Error executing script. Error for repeat at pos 2: Node(node_id=4) - InvalidNewValue: State '' not found for parameter 4-112-0-13
2024-05-12 08:24:06.935 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Error for call_service at pos 1: Node(node_id=4) - InvalidNewValue: State '' not found for parameter 4-112-0-13
2024-05-12 08:24:06.936 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [124181395143232] Error handling message: Node(node_id=4) - InvalidNewValue: State '' not found for parameter 4-112-0-13 (home_assistant_error) Kevin Schlichter from 192.168.1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36)
I updated zigbee2mqtt today to 1.38.0-1. Since then, my script below (created by the blueprint) no longer works. My scripts to set effects and colors all work, but I was using this to clear them and it doesn’t function. I don’t see anything in the zigbee2mqtt changelogs that would’ve affected this, but it’s the only thing I can think of that has changed.
alias: "Inovelli Blue Series Master Bathroom Fan Clear Notifications "
use_blueprint:
path: kschlichter/inovelli_led_blueprint.yaml
input:
entity:
- fan.master_bathroom_fan
area:
device:
group:
duration: “Off”
brightness: 0
color: “Off”
effect: “off”
