Is this new with firmware 1.56/1.57? Is anyone running 1.48 having this problem?
@EricM_Inovelli All of my dimmers are running 1.56. I canāt speak to 1.48 as I updated to the latest fw during my initial install.
Mine are on 1.48 with this problem. So it doesnāt seem to be new to the firmware update, or fixed by the firmware update either.
1 Like
@fluid324 @jreed509 @kelchm Sorry for the mass tagging but I have spent an absurd amount of time problem solving this in the past week. Long story short I am not seeing the extra logging and flood of the zwave network at all with the Nortek HUSBZB usb stick.
The Zooz 700 usb stick was giving me massive problems. I tried the first firmware release for the dimmer switch and the most recent one, different settings on the switch, different number of switches connected, Home Assistant and PC controller software, even multiple Zooz 700 sticks, the ONLY thing that made it work, EVERY time, no retries or timeouts, was the Nortek stick.
LONG STORY VERSION: After a couple years of being on Hubitat I decided it was time to switch to HA. I found Hubitat to be slow when issuing lots of zwave commands to my network so I decided for a unique setup. 3 raspberry pi 3b+, running barebones HA each on itās own floor of the house with itās own Zooz 700 stick. A single raspberry pi 4 running my main HA instance, connecting to the Zwave sticks via zwaveJSmqtt websocket. The idea was to prevent multiple āhopsā on my network for switches that were far away and hopefully speed up the network as a whole using ethernet as the main backbone with no more than a couple dozen items connected to each stick.
I flashed all 27 switches to the latest beta firmware, 6 inovelli bulbs, and 6 inovelli light strips, paired and got them all setup. I found out quickly that turning on/off all lights at once was PAINFULLY slow, and often times several zwave devices remained in the previous state. This was occuring when only controlling 3 or 4 devices at once also. I discovered this post and others from Kelchm on other forums. All 3 Zooz usb sticks were showing a flood of traffic and timeouts. The same device never had issues and sometimes my network would hang for minutes at a time on occasion and be unusable. Obviously this wasnāt going to work. I should also mention, the bulbs and light strips from Inovelli showed no problems. I could turn all 12 of JUST those on and off simultaneously without issues.
After a week of research and too many switch resets and firmware flashes Iām at least relieved that I have a āsolutionā. I would definitely prefer to be on a 700 series usb stick but at least the nortek is proving to be very fast (and costly solution since I need to 2 more of those nowā¦ ) I donāt know if the issue lies with Inovelli firmware or Zwave 700 having capability issues with older chips. I havenāt done a ton of research but Iāve seen posts that I thought mentioned the new Hubitat C7 was having many issuesā¦ but could be wrong. Either way I hope this helps you guys to at least get your network working reliably, happy to answer any questions if you have any.
4 Likes
Very interesting that youāre not seeing this issue on the Nortek stick. Is the Nortek stick in the same physical location as your 700 series sticks?
I can confirm that itās not an issue with 700 series compatibility as Iām also seeing the same flooding on my Aeotec Gen5+ (500 series). That doesnāt necessarily mean itās not related to the stick in some way though.
Exact same location, same switches even. The Zooz 700 shows duplicate reporting with a single switch and I can basically stall my network with just 5 switches attached and quickly turning on and then off. I thought maybe I was overwhelming the resources for the Zwavejsmqtt container but itās the same issue connected to the PC Controller software, albeit it is faster on the PC Controller software overall. Iāve had the Nortek for a couple of years but was only using it for firmware updates, I was expecting more issues with it but itās flawless for the last several hours with constant testing. I currently have 9 switches attached and it never duplicates or times out. Usually takes about 3 seconds to turn them all on, give or take a second or two. My biggest concern is that the 2 new ones I just ordered are slightly updated versions that could introduce problemsā¦ Iāll know on Saturday when they arrive I guess.
This is interesting info and i just might have to test it. I have only tried with the Zooz 700 z-stick and the Aeotec Gen5 (non +) and both had the same problem. However, i do have the nortek HUSBZB laying around so maybe i will give it a go. At this point ive just gotten over and have tried to not toggle multiple lights thru zwave at the same time. But if switching to the nortek stick is a solution i am not opposed to it, will just suck to set up and pair everything again.
1 Like
Agreed, Iāve made so many changes to hubs, switches, sensors, etc I REALLY want this migration to be the last big one for a few years. If you take the dive let us know if it resolves your issues, I would hate for someone else to buy a stick and it not rectify the issue.
Iām just wondering if the fundamental premise of your solution is flawed. Would it be more optimal to just let z-wave mesh itself from one controller and operate up to 4 hops.
My Nortek gets the job done in 2 hops for my 3-story home for every device on the network (almost entirely inovelli) and I struggle to see the benefit of ethernet/websockets beating out a robust mesh network.
Food for thought.
Also, Nortek FTW. Definitely improved my results and speed, and Iāve moved a lot of my automations to multicast, which is literally INSTANT on my network. From press to change I cannot perceive a time lapse at all.
It might be completely flawed, I couldnāt find anyone else who had attempted this. Iāll let you know how well it does/doesnāt work š¤·
1 Like
Thanks for the additional info. The manufacturer is looking into this issue and hopefully they discover what the problem is. Something strange is that these devices have been in circulation for quite a while and this issue seems fairly new. I will update you though with what they find out.
3 Likes
Iām seeing this behavior also, with the Zooz 700 series stick. For the longest time I figured it was just my z-wave network getting slow as I added more devices. My goodnight script turns off 11 z-wave devices (combination of dimmers and on/off switches) and it takes forever to run, most of the time failing to turn everything off to the point itās unreliable and I check HA and manually turn off any that failed.
Seeing this thread I decided to invoke the script and watch the debug output and sure enough, the nodes are sending a bunch of duplicate messages:
2021-09-13 23:03:54.697 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:54.716 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:54.744 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:54.755 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:54.807 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:54.855 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:54.913 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.124 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.168 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.231 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.331 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.411 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.492 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:03:55.639 INFO ZWAVE: Node 14: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:05.466 INFO ZWAVE: Node 17: value updated: 38-0-currentValue 98 => 0
2021-09-13 23:04:05.670 INFO ZWAVE: Node 18: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:05.848 INFO ZWAVE: Node 18: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:05.898 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.143 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.302 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.388 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.442 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.485 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.502 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.598 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.832 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.843 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.896 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:06.930 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:07.052 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:07.248 INFO ZWAVE: Node 36: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:07.304 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:07.376 INFO ZWAVE: Node 19: value updated: 38-0-currentValue 0 => 0
2021-09-13 23:04:07.400 INFO ZWAVE: Node 20: value updated: 38-0-currentValue 0 => 0
Iām running firmware v1.21 on the red on/off switches and v1.48 on the red dimmers. Iāve a total of 58 z-wave devices so Iām really hoping this can be solved without buying a nortek stick and re-pairing everything
Based on my own experience, I really donāt think this is an issue of 700 vs 500 series sticks. I was actually using a HUSBZB-1 when I originally noticed this issue and switched to the Silicon Labs UZB-7 in an effort to resolve it.
Iāll also note that Iāve reproduced the issue with the handful of Zooz dimmers/switches I have in addition to Inovelli.
Hey all ā Iāve been meaning to update this thread as weāve been working closely with a few different companies to resolve this (Silicon Labs, Manufacturer, and a third party who weāre making switches for as they noticed this on their new hub).
Iāll let @EricM_Inovelli give the final green light when the time comes, but we believe we have beta firmware that works around these issues.
As mentioned above, this is a manufacturer wide issue and while thereās a difference of opinion as to whether itās a hub, switch or SDK issue, the important thing is weāre able to replicate it and, āfixā it.
More to come, but I wanted to at least update everyone!
11 Likes
Great to hear! Very excited for the fw update
I wish I noticed this thread earlierā¦ Just tried migrating from HUSBZB-1 to the Zooz 700 series stick, only to notice an absolutely flooded zwave network.
As others have mentioned, itās not just the Inovelli devices. My network consists almost entirely of Inovelli devices, but also a few Zooz smart plugs as well. The smart plugs I have are absolutely horrible. In fact, theyāre the reason the entire network has crashed multiple times over, forcing me to rename all entity ids all over again.
I didnāt intentionally come here to complain though. While testing on my end I noticed something which appears to have increased my networks speed and reliability, and that is to disable active power reports. This was especially true with the Zooz ZEN25ās, but if itās possible to disable power reporting on the Inovelli switches, maybe that will help others as an interim solution. Sucks to lose a major perk of zwave, but if it helps for now Iām personally all for it.
This isnāt a guarantee either, itās something I noticed for myself though so wanted to pass it along should others find it useful. As for me, Iām going back to my trusty HUSBZB-1. Get to test it running zwave 6.10 this time though, so not a complete waste of time!
Do tellā¦
Thanks for posting this! Iāve only paired Inovelli devices and the bulbs and Led strip controller didnāt seem to suffer the same issue I saw with the red series dimmers. Iām really starting to wonder if their is an issue with backward compatibility within the zwave chips themselves. Maybe that is way the zwave alliance has already announced the 800 series chip?
1 Like
Working extremely well thankfully! I guess in the end I just needed to rebuild my zwave network from scratch for it to work.
I donāt want to get too off topic from the original purpose of the thread, but I followed this guide here: [Guide] Nortek HUSBZB-1 NVM Backup/Restore and Updating Z-Wave Firmware - Developers - Hubitat
Just needs a steady hand. I figured Iād give it a go to see how it went, thankfully worked like a charm 
I havenāt created a forum post on this yet, but we have released a new firmware that will greatly reduce the possibility of duplicate packets under certain scenarios.
Edit: I just noticed this thread is about the LZW31 (Black Series), but we havenāt released that firmware yet. The one I posted is for the LZW31-SN (Red Series).
5 Likes