I attempted to confirm this after updating my dimmer to v1.57 Z-Wave MCU (Target 0) and v1.45 Holtek MCU (Target 1). Unfortunately, setting the color to 255 still displays a red color. I also tried directly setting parameter 13 to 255 and nothing happened.
I also copied @kschlichter’s spreadsheet, and selected white as a parameter and the resulting value still turned the led red.
I have white as an option in the Z-Wave JS to MQTT web UI, but I’m on firmware 1.61 / 1.45 so maybe that’s the difference? Punching 33490687 into parameter 16 successfully set the switch effect to solid white forever.
I’m still on older firmware 1.47 Z-wave MCU and 1.41 Holtek MCU
I can confirm setting parameter 13 to 255 directly in the zwavejs2mqtt web UI changed the LED to white on my dimmer as well. Using the zwave_js:set_config_parameter service in Home Assistant also successfully changed the LED to white.
Initially, I updated to 1.47 to use the parameter 51 “instant on” option (remove 700ms delay). At the time, even though everything showed successful with the firmware update, that option didn’t work initially. When I applied the firmware update again, it worked the second time. My only other thoughts to get white working would be to try and apply the firmware updates again in case something didn’t stick, or possibly that there was a problem in 1.57 that got fixed again in 1.61
May 26, 2022 change: Added support for the White LED color.
* Support for the color white was supposedly added to the LZW31-SN dimmer [in Firmware 1.45 accoding to Inovelli](https://support.inovelli.com/portal/en/kb/articles/firmware-change-log-lzw31-sn-dimmer-switch-red-series).
* I ended up having to flash both LZW31-SN Z-Wave 1.61 and LZW31-SN Holtek 1.45 firmware twice before I could see white light.
@mwav3 and @kschlichter:
I tried the 1.61 beta Z-wave firmware instead of 1.57, and I tried reflashing the 1.45 Holtek firmware for good measure. 255 now produces white light! Thank you both for the suggestions!
@takissd and @RarelyComplete:
Thanks for the heads up. I don’t know why I didn’t think to update the firmware on my dimmer, but it works now.
Not to completely derail this thread, but I have a question for those of you who upgraded your switches (with what I assume was the OTA method). I recently did one of my switches via OTA Z-Wave JS, using the ZWAVEJS2MQTT integration, and both targets updated successfully. However, I wasn’t expecting that I would have to exclude and re-include the device to get Z-Wave JS and Home Assistant to recognize it after the update.
Z-Wave JS did attempt to re-interview the device after the upgrade but eventually failed. Is this common? I have several more switches to update, but I’m thinking twice if I need to go through all this with each one.
No, I did not have to remove/re-add my Inovelli dimmer.
The Zwave JS 2 MQTT web interface showed a progress ring to show it was working on the upgrade for each firmware. I sent them over one at a time, waiting for the first to complete before uploading the second.
May 26, 2022 - update #2
1. This is the first release only supporting Z-wave JS!
2. Added support to send the same notification to multiple Inovelli switches and dimmers. (Thanks to Danny Schuh)'s contribution to the blueprint.)
From now on only the Z-Wave JS versions of this script and the blueprint will only get updates. The OpenZWave and Zwave integrations were officially removed from Home Assistant version 2022.4.
I’ve done several firmware updates. Most of the time, all config and zwave settings were fine and the switch did not need to be reincluded.
One time though, the red series dimmer switch completely factory reset and I had to reinclude and resend all the config settings. It was in the same room as the zstick, and I only did the one firmware update and tried not to use any switches or create zwave traffic, so I can’t think of anything I did to cause this. I guess it depends on the firmware version?
I’ve been skittish about applying zwave firmware updates since that happened. I probably won’t unless I see support in the change log for a new feature I really want.
Hello, I just recently found this script and I’m playing with it on my LZW36 fan/light switch. I have been able to make the LED strip for the light button work with the script but the fan button doesn’t seem to respond to commands. Is there something special I need to do to get the fan LED strip to use the effects?
I found this thread and tried your script, which appears to solve my issues (as I believe it has to do with the deprecated Z-wave protocols is was evaluating or something along those lines). Anyway, the script works great for this Blueprint, except I am getting this error related to the “for_each” part of the repeat section.
Integration: Script (documentation, issues)
First occurred: 20:09:18 (1 occurrences)
Last logged: 20:09:18
: Repeat ‘for_each’ must be a list of items in , got: light.mudroom
This automation is only dealing with one Inovelli switch, so there’s not a list of entities it’s going to update. I’ve tried adjusting the script to only do the one, but I haven’t figured out how to resolve this error. Do you have any suggestions on how I should modify it so it’s OK with only one entity and not expecting an entire list? I’d really appreciate any pointers you can provide. Thanks for posting this.