Well, I would assume the Nortek stick is also certified for what that’s apparently worth. Do you know what I need to set for the parameter 12 on the virtual 3-way configuration to prevent the looping they talked about?
It depends on whether you have associations set up both ways (slave → master and master → slave) or only one way (slave → master). The advantage of the master → slave association is to keep the state of the dimmer bar on the slave switch in sync with the load.
What is critical is to ensure that a single command doesn’t loop back and forth and back and forth. That will happen if you have associations set up in both directions AND the “zwave” bit (4) is set to on in parameter 12 on both the switches.
Parameter 12 is a bitmask. It’s a way of encoding several (in this case 4) on/off toggles into a single number via binary arithmetic. The toggles are:
1: local
2: 3 way
4: z-wave
8: timer
For each of those four command sources you want to send a zwave command to the associated device, add the corresponding number. So if you want local and 3-way but not zwave and not timer you get 1 + 2 + 0 + 0 = 3, and you’d set the parameter to 3.
I have mine set to 1 on the slave and 15 on the master, because there’s no 3-way connected to the slave and I don’t have any intention of using the timer on the slave.
2 Likes
You know, I’ve always though my Zwave networks were way slower than they should be. I’m using 2 Aeotec sticks at 2 different sites right now. Mostly it works, but if you push multiple commands it lags badly. I don’t use any security on any device. The Nortek one everyone likes is the HUSBZB-1, right?
There are lots of slang names for these things so someone saying Zooz stick might not be referring to the same one as someone else is using.
I believe someone in this thread has seen the issue with all of these sticks??
Zooz ZST10 - this one seems to be the worst offender, but it appears that ZST10 is the name for stick with both 500 and 700 series chips.
Z-wave.me UZB
Aeotec ZW090
Silicon Labs UZB-7 or SLUSB001A - is this one maybe OK? Can’t find it anywhere now anyways.
Silicon Labs UZB3 or ACC-UZB3-U-STA
Nortek HUSBZB-1 - seems to be the best of the group even if some do see issues.
Yes I am doing the association both ways Master <-> Slave for exactly the reason you said to keep the LEDs in sync.
And I don’t need to speak binary (but I am a systems engineer by trade so I know exactly what you mean) because HA w/ ZwaveJS breaks it down for me:
So basically I only need the “local” toggled on on the slaves and everything default on the masters (all on). I think my confusion arose from my lack of understanding of what “Association Behavior” actually means in this context but I think I get it now. It means only the local button pushes get transmitted to the associated switch. Not that only the local load gets switched nor does it mean anything pertaining to receiving zwave info from an associated partner.
Perfect explanation. Thank you.
I believe it’s the only Nortek controller around but yes it was specifically called out by the HUSBZB-1 model name further up in the thread. It’s aka GoControl and has a Zigbee radio on it also. This is what I ordered. I think the Nortek controller issues were mentioned in regards to Hubitat and the person qualified their statements with saying that the problem was possibly not the controller but Hubitat or something else. I’d have to dig back through this thread and I don’t have the time right this second.
My Nortek won’t come in for at least a week but I’m going to install a fresh copy of HA on a new fanless mini-pc thing I bought and stick this new Nortek in it. I may or may not bring over a backup of HA core (probably not) but I will definitely start my zwave off with a fresh slate. Exclude or reset all devices and include on the Nortek. Going to try to get them all to come in as S2_Unauthenticated as I hear from people that S2 is less chatty and all around faster.
Sorry about all the lingo but yes the Zooz sticks being referred to are the ZST10-500 and ZST10-700. I have one of each now because I bought the 700 in an unsuccessful attempt to fix my issues with the poor response on large-ish (3 or more) light groups. Early on in this thread there were several who also went down the same path as me and one person I think who had an Aeotec Gen-5 and was having issues. You’d have to ask them if that corresponds to the model numbers you are finding if it’s not detailed in their post.
Can I ask you one more question?
Are you adding both switches to all of the groups like so?
I ask because a co-worker of mine is in the same boat as me trying to get virtual 3-way dimmers working with the reds and he read elsewhere in this forum to do “Master dimmer added to group 2 and group 4 of slave” and “Slave dimmer added to group 3 of master dimmer”. He says its working perfectly and he did not mess with param 12. I have yet to test this here. I suppose since he has no overlap he has no loop issue.
The thread in question is here:
3-way setup with two LZW31-SN dimmers in HA in endless loop - Sorting Category - Inovelli Community
Can you take the off topic discussion to your own on topic thread?
Yeah I’m still plagued with a slow network (albeit better after the dimmer firmware fix) where my goodnight script that turns off a bunch of devices almost always fails. Not all of the devices are Inovelli so I’m thinking it’s my Zooz ZST10-700 controller. I’m hesitant to go with the Nortek as it’s a 500 series controller, but I haven’t heard of an equivalent 700-series controller that has the same raving reliability reviews. That and I’ve over 80 devices on my network to exclude and re-add if I change controller 
Only input I have is that my Nortek HUZBZBZBZB-1 or whatever is lightning fast and I’ve had steady, solid reliability for over a year at this point, now using HA/ZwaveJS Integration/ZwaveJS2MQTT.
Yes, it’s 500 series, but that and unsecure pairings (minus security items) have my home working quite literally instantly.
Right now, I found a possible source for the Nortek at $75. It’s not available in many places and reportedly is obsoleted so it will be disappearing. I didn’t want to spend the money, but I think I’ll put an order in and hope I get it and hope it works better and is worth it. Others are having the best luck with it and it seems like the only USB stick solution for sketchy zwave network operation right now.
Are you in the US? If so amazon has it for $48.95:
Canada and that link comes up as unavailable.
1 Like
I’d like to echo what others have said about how much faster my network is after the FW update. Its definitely a huge improvement when controlling a lot of devices at once!
However, I am still seeing duplicate values in my logs whenever using multicast calls with the new update. Here’s the logs for a large multicast call:
Subscribed to Z-Wave JS Log Messages…
2021-12-07T22:54:27.974Z DRIVER » [REQ] [SendDataMulticast]
│ target nodes: 7, 52, 42, 49, 19, 9, 6, 51, 50, 8, 56
│ transmit options: 0x25
│ callback id: 115
└─[MultilevelSwitchCCSet]
target value: 0
2021-12-07T22:54:27.994Z DRIVER « [RES] [SendDataMulticast]
was sent: true
2021-12-07T22:54:28.047Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.073Z DRIVER « [Node 052] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.090Z DRIVER « [Node 050] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.124Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.157Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.195Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.382Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.397Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.424Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.452Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.479Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.505Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.561Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.574Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.666Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.718Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.737Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.788Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.830Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.955Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:28.974Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.048Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.123Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.147Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.176Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.185Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.193Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.233Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.276Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.451Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.483Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.494Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.569Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.629Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.648Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.699Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.720Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.756Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.772Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.795Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.822Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.852Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.926Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.937Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.972Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:29.991Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.000Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.163Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.200Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.253Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.316Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.373Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.395Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.405Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.476Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.487Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.612Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.625Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.639Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.704Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.759Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.773Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.821Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.873Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.899Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:30.950Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:31.001Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:31.049Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:31.263Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:31.354Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:31.443Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:33.020Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:33.091Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:33.290Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:33.527Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:34.535Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:34.725Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:34.969Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:34.987Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:34.995Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.156Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.198Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.207Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.252Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.265Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.425Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.651Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.742Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.766Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.775Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.802Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:35.945Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.004Z DRIVER « [Node 050] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.046Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.225Z DRIVER « [Node 050] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.356Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.406Z DRIVER « [Node 042] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.420Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.448Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.593Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.635Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.645Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.666Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.735Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.756Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.810Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.848Z DRIVER « [Node 052] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:36.911Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.037Z DRIVER « [Node 052] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.085Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.094Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.134Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.156Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.251Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.309Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.389Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.412Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.421Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.491Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.512Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.704Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.817Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.901Z DRIVER « [Node 019] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:37.985Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.040Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.062Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.128Z DRIVER « [Node 049] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.744Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.802Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.882Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.923Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:38.962Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:39.505Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:39.579Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:39.672Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:39.736Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.294Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.368Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.492Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.516Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.553Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.585Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.598Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.678Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.735Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.862Z DRIVER « [Node 051] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:40.973Z DRIVER « [REQ] [SendDataMulticast]
callback id: 115
transmit status: OK
2021-12-07T22:54:40.974Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 116
└─[SupervisionCCGet]
│ session id: 61
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 255
duration: default
2021-12-07T22:54:40.984Z DRIVER « [RES] [SendData]
was sent: true
2021-12-07T22:54:41.110Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.158Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.196Z DRIVER « [REQ] [SendData]
callback id: 116
transmit status: OK
2021-12-07T22:54:41.241Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.274Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[SupervisionCCReport]
session id: 61
more updates follow: false
status: Success
duration: 0s
2021-12-07T22:54:41.275Z DRIVER » [REQ] [SendDataMulticast]
│ target nodes: 53, 20
│ transmit options: 0x25
│ callback id: 117
└─[BinarySwitchCCSet]
target value: false
2021-12-07T22:54:41.282Z DRIVER « [RES] [SendDataMulticast]
was sent: false
2021-12-07T22:54:41.283Z CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
2021-12-07T22:54:41.298Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.366Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.384Z DRIVER » [REQ] [SendDataMulticast]
│ target nodes: 53, 20
│ transmit options: 0x25
│ callback id: 117
└─[BinarySwitchCCSet]
target value: false
2021-12-07T22:54:41.390Z DRIVER « [RES] [SendDataMulticast]
was sent: false
2021-12-07T22:54:41.391Z CNTRLR The controller response indicated failure after 2/3 attempts. Scheduling next
try in 1100 ms.
2021-12-07T22:54:41.395Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[SupervisionCCReport]
session id: 61
more updates follow: false
status: Success
duration: 0s
2021-12-07T22:54:41.447Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.719Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:41.773Z CNTRLR [Node 009] Scheduled poll canceled because value was updated
2021-12-07T22:54:41.773Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 99
2021-12-07T22:54:41.799Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 99
2021-12-07T22:54:42.075Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.290Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.335Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.399Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.449Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.491Z DRIVER » [REQ] [SendDataMulticast]
│ target nodes: 53, 20
│ transmit options: 0x25
│ callback id: 117
└─[BinarySwitchCCSet]
target value: false
2021-12-07T22:54:42.504Z DRIVER « [RES] [SendDataMulticast]
was sent: true
2021-12-07T22:54:42.525Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.572Z DRIVER « [REQ] [SendDataMulticast]
callback id: 117
transmit status: Fail
2021-12-07T22:54:42.615Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.658Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
2021-12-07T22:54:42.690Z DRIVER « [Node 053] [REQ] [ApplicationCommand]
└─[BinarySwitchCCReport]
current value: false
2021-12-07T22:54:42.722Z DRIVER « [Node 053] [REQ] [ApplicationCommand]
└─[BinarySwitchCCReport]
current value: false
2021-12-07T22:54:42.757Z DRIVER « [Node 020] [REQ] [ApplicationCommand]
└─[BinarySwitchCCReport]
current value: false
2021-12-07T22:54:46.694Z DRIVER « [Node 053] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: W
rate type: Consumed
value: 0
time delta: 0 seconds
My “Goodnight” scene turns off ~20 invovelli dimmers/switches. With the new firmware update, using a HA group to turn the devices off takes 5-10 seconds with lights turning off throughout that time span. If I instead use multicast calls, all my lights turn off nearly instantly, but my network is then flooded with duplicate messages and unresponsive for 20-30 seconds
@EricM_Inovelli do you know if the fix applied in v1.61 should apply to multicast messages as well or if its only for unicast?
Curious if anyone else can reproduce this on v1.61 using multicast
Amazon.com did offer it and it was a good price compared to anywhere else so I put in an order. There was no stock but more were on the way so I’ll wait and see if I get it or not.
1 Like
I could try but i’m not even sure how to specify unicast vs. multicast. Using Home Assistant w/ 6 Innovelli LZW-31SN’s and a dozen or so zooz switches/motion detectors and some other misc things. If you tell me how I’ll give it a whirl both ways and capture the logs.
Wow. Only 32 zwave devices here (put a pile of stuff left still to install) but it’s still going to be a massive pain. Can’t imagine dealing with 80. I ordered and received the Nortek stick and a new little mini PC thing to put a clean HA on and set it up with. Been busy with work and life stuff but will hopefully get it all setup and going soon and report back here. Going down to a 500 series device is a bummer but I will sacrifice the fancy provisioning stuff for a solid lightning fast response. Currently devices are dropping out sometimes and the lag on light groups is bad. I can’t heal half the devices. Situation is bad enough that I don’t want to install the new stuff I have until I get this sorted out.
Yeah this is a foreign language starting from the Nortek. I haven’t had mesh issues at all, only healed when adding devices, etc. Can’t say enough positive about it.
Back on topic though, I will check my logs as well when I multicast. I still need to figure out how to multicast notifications, I think we figured it out over on discord (add a parameter for the combined parameter in settings) but I have since lost that.
Follow this post.
Hint, if you have to change services click on the Go To YAML mode button at the bottom and copy the device or entity part from the YAML code so you don’t have to re-pick them all again.
Here’s a yaml snippet that can be run from the developer tab in HA. This will turn off all the entities under target using multicast:
service: zwave_js.multicast_set_value
data:
command_class: '38'
property: targetValue
value: 0
target:
entity_id:
- light.my_dimmer_1
- light.my_dimmer_2
- light.my_dimmer_3
Note that the command_class and value for dimmers and switches is different, so this snippet will only work for dimmers.
1 Like
Looks like those of you who reported moving back to a 500 series stick were on to something:
- 🚧 META-Issue: Problems with 700 series (healing, delays, neighbors, ...) 🚧 · Issue #3906 · zwave-js/node-zwave-js · GitHub
- Does anyone have a solid working G3 system at this time? - HomeSeer Message Board
While I’ve personally experienced basically zero issues since upgrading all of my LZW31-SN dimmers to the v1.61 firmware (likely a result of the fact that the vast majority of my devices are LZW-31SN’s), this basically confirms that this wasn’t at all an issue exclusive to Inovelli devices and instead a more systemic problem with silicon labs’ 700 series stick firmware.
@EricM_Inovelli – I’m not sure if you or your manufacturer would be willing to reach out to Silicon Labs on this topic, but it sounds like some additional reports and details of reproduction steps would go a long way in getting them to prioritize getting this addressed in the stick firmware itself.
4 Likes
I got the stick, can’t get either the zwave or zigbee parts to work and I have no idea why. So, I won’t be finding out if it works better or not.