I was able to reproduce belgian_style’s issue, I timed it for at least 2:30 and it was still going. I’ll leave the notification going and see how long it stays.
I am using parameter: 16 since it is the correct parameter for “LED Strip Effects” on the dimmer version
Settings
node_id: 20
parameter: 16
size: 4
value: 74975765
Do not want to hijack the OP question, but as a noob, I ended up adding a Red Series dimmer in Vera (acts as my Z-Wave controller) and adding the ID of the dimmer into HA running in Docker on Synology NAS. I am not seeing any of the other entities or states for the switch.
Any help on what I need to do so I can program ramp rate, led, etc. etc. without manually pressing the config button? Not super clued in on the machinations of GitHub etc.
Any help to get the most out of this switch greatly appreciated as I move my entire Z-Wave network from Wink to Vera/HASS.
Thanks.
Hi @belgian_style, I am looking through my old notifications and I apologize for missing this. Hopefully you figured it out, but it looks like you may have used the notification calculator for the switch (there is a different one for the dimmer). Or maybe there was something wrong when you calculated the value. I actually prefer to use the calculator provided by our community member @nathanfiscus.
@pdong Do you foresee updating the status manager to handle the dimmer switches? The main differences being modifying parameter 16 instead of 8, and the ability to have the “chase” effect. For now getting around this with the “change” node and abandoning any plans to use “chase” effect.
I have scenes working on a red series on/off but can’t get it to work on red series dimmer, it keeps dropping message. Any suggestions?
Zwave logs
2019-12-11 13:22:47.520 Detail, Node020, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x14, 0x05, 0x5b, 0x03, 0x5a, 0x83, 0x02, 0x62
2019-12-11 13:22:47.520 Detail,
2019-12-11 13:22:47.520 Warning, Node020, Received a Clear Text Message for the CommandClass COMMAND_CLASS_CENTRAL_SCENE which is Secured
2019-12-11 13:22:47.520 Warning, Node020, Dropping Message
Edit: Nevermind. Figured it out removed the issecured line
Made a home assistant LED script based on yours for the LZW31-SN Dimming switch https://pastebin.com/FKiJnyaK
The only difference is the parameter number and the numbering for effects.
Hi Eric, I haven’t figured this out and I originally used that version of the calculator. Anything I can do to troubleshoot further?
Thanks.
@belgian_style Can you tell me the options you are selecting and the config value you are sending? I will test it on mine.
Hi @EricM_Inovelli ,
I have attached a screenshot of the Automation that I am using. I think it has all the info that you are asking for. If not, please let me know and I will work to collect it.
@belgian_style Can you also let me know what behavior you are trying to see? Like, “fast blink red at full brightness for 2 minutes”.
I was attempting to get the light to pulse yellow (really any color other than the default blue) for 2 min at full brightness. Then go back to the standard blue.
Thanks for the help.
@EricM_Inovelli I was able to reproduce the issue with the “hanging notifications” that @belgian_style and others have mentioned in this thread . I ran a series of tests using the following parameters:
Device Type: Dimmer
Color: 1
Brightness: 10
Effect: Solid
I changed the notification duration and then visually timed it with a stop watch. Most of the timings were off and the larger the duration, the larger the delta. Once I got past 62 seconds is where things really diverged from what was expected. Here is a table of the results:
| Desired Duration | Actual Duration (Approx) | Notification Value |
|---|---|---|
| 0:10 | 0:11 | 17435137 |
| 0:30 | 0:33 | 18745857 |
| 1:00 | 1:06 | 20711937 |
| 1:01 | 1:06 | 20777473 |
| 1:02 | 2:13 | 20843009 |
| 1:03 | 3:30 | 20908545 |
| 1:04 | 4:30 | 20974081 |
| 1:05 | 5:30 | 21039617 |
| 1:06 | 6:40 | 21105153 |
If anyone else could run these and see if they get similar times and also double check the calculated values that would be helpful to verify. I also ran a test with the two minutes spoken of here in the thread. It lasted for over an hour, but I don’t know exactly how long as I went to bed. I will try and follow up with the same test using a switch.
I didnt run through them all, but I did jump right to 1:06 and can confirm that I got the same actual duration as you:
| Desired Duration | Actual Duration (Approx) | Notification Value |
|---|---|---|
| 1:06 | 6:40 | 21105153 |
I tried the same value on my Red Series switch, and while I didnt time it for the full duration, it definitely lasted more than 3 minutes.
Edit: I tried a couple other values, and got similar results to yours:
| Desired Duration | Actual Duration (Approx) | Notification Value |
|---|---|---|
| 0:10 | 0:11 | 17435137 |
| 0:30 | 0:32 | 18745857 |
| 1:00 | 1:04 | 20711937 |
| 1:01 | 1:05 | 20777473 |
| 1:02 | 2:12 | 20843009 |
| 1:06 | 6:40 | 21105153 |
Thanks for the confirming those results. Were all of these times on the a switch or did you use a dimmer as well?
All these times were on my dimmer. I tested the 1:06 duration on the switch, and confirmed that it lasts more than 3 minutes, but I did not time the full duration or test any other values on it.
Can you explain how I can interface with this script in Home Assistant? It would be great to use this to calculate values in HASS instead of having to effectively hard code values into my automation’s!
script: !include scripts.yaml in your configuration yaml. And in that file paste the led code from my paste in. Call it in automations like
- alias: Front door locked switch notification
trigger:
platform: state
entity_id: lock.front_door
from: unlocked
to: locked
action:
- service: script.turn_on
entity_id: script.zwave_inovelli_led_color
data:
variables:
color: red
duration: 0
effect: pulse
level: 10
node_id: 15
On mobile so formatting might not be right.
That’s the exact additional info I was looking for. Thanks!!
@EricM_Inovelli, do you need any additional information to help fix this? I would love to be able to use the notification timing, but can’t due to the massive time discrepancies.