Hey - what version of JS UI are you running?
Just got a flag to update to 2.0.1.
Weirdly I saw another reference to it as 9.0.1… which obviously would be very different.
Currently running 2.0.1 on HA 2023.9.2 - should be the latest.
Thanks. For what it’s worth, I just spent a bit trying again with the Zooz stick.
I added them all unsecured this time. It definitely went better. But still having major issues - have attempted like 15 switches. Was able to get maybe 12 of them paired; have 3 of them that refused despite includes/excludes/resets, etc.
Also having issue with those switches with my “alternate” stick (Atrim).
I’m starting to think this is some issue between the 800mhz sticks and the switches. These paired flawlessly with my old Homeseer Znet. Unfortunately it’s an old unit and I can’t make it work right now with HomeAssistant (working on that separately).
I think my next step is going to be to get a hold of a 700 series stick and see if that works any better.
Unless anyone here has any other suggstions?
Please continue posting updates here, and I will do the same. We’ll get this figured out.
I’d be willing to bet your problems aren’t the switches but is rather the 800 stick with zwave-js. I’ve used and migrated between 500 and 700 sticks a fair bit. I have ~40 inovelli switches and a handful of other devices (locks, bulbs, etc) and never had any problems with the 500 or 700 sticks. I bought the same Zooz zst39 800 stick and had nothing but problems. When I did some digging I found it just wasn’t supported very well in zwave-js yet as 800 is still fairly early. I haven’t revisited it in quite some time so maybe it’s better but I’d bet if you got yourself a 700 stick all your issues go away.
@keylooper - thanks for chiming in.
So I had the same thought, actually. Given that I was seeing issues with 2 separate 800 series sticks. I purchased a 700 series aeotec.
Started with a fresh install of HAss OS.
First 5-6 switches paired beautifully … then things just stopped. Every other switch I tried after that wouldn’t respond- wouldn’t include, wouldn’t exclude… even after resetting the switches, airgaps, etc. I have no idea what to make of this, to be honest.
My next thoughts are to install HAOS directly onto the bare metal system (I’m running via proxmox, and wondering if there’s some issue with USB pass-through)…
Beyond that, I think I’m going to get ahold of an Rpi and see if that makes any difference. Unfortunately I don’t have one so that involves buying one and you obviously know how hard that is still right now…
Appreciate your input - any other thoughts?
Or preorder RP5.
I run as everything as containers on unRAID and it works well. Proxmox doesn’t do Docker though, right? I honestly don’t understand who’d want it for home use without native docker support but lots of people run it.
Are you pairing all the devices in their final location? Did you try healing after adding those 4-5 devices? Is it switches by chance that are having issues?
Hey @PJF
Honestly I’m relatively new with proxmox and docker. This is my first foray into the Linux world to be honest. So I don’t know if or how it works with docker.
Yes, I am pairing them in their final location. Yes, have run a heal and have been doing that after every 4 or 5 devices I add.
Yes, it is generally the switches that are causing issues. It’s more the on/off switches (LZW30 IIRC) than the dimmers (LZW32-SN).
I have found that when I’m adding several devices, a network heal isn’t enough with HA/zwave-js. I have found I have to restart the entire HA system and for best results, I do this every 2-3 devices. I’ve found if I don’t do this, then devices stop being able to add as S2 encryption and will only add with no encryption. If I continue on, they will just stop being able to add. So if I see the failure to S2 auth I remove that device and reboot everything. If I get three good adds, I reboot everything.
I’m on an HA Blue (but saw the exact same behavior when I was running on docker) with an Aeotec Z-Stick 7 currently.
So that’s interesting, because that’s very similar behavior to what I’m seeing.
So I’m running HA through proxmox. When you “reboot” in the settings menu on HA on your computer, does that actually reboot the entire computer (I’m assuming it does). In proxmox that’s not the case - it just reboots the VM. Though I can reboot the entire machine from proxmox itself.
I will try this. If it’s not working, I’m going to install HAOS on the mini pc itself and see if that makes a difference (i.e. take proxmox out of the equation).
Edit: I did try this, didn’t notice any difference. I am going to install HAOS now on the bare metal and see if I see any change in behaviors.
Ya, I never had to reboot my server to keep things working. Worst case, restart the zwave-js-ui container, which would be like re-starting the add-on in HAOS. That was usually because a software update wasn’t doing anything and it needed rebooting to try again.
I did find that some switches wouldn’t add securely and were just harder to add overall. The LZW30’s.
A rPI is a sucky way to run HA unless you use a SSD. Don’t expect the SD card to last unless you take all the steps to block as much use of it as possible. HAOS by default likes to write a lot of data.
My 2¢: I’ve had TONS of trouble with my Nortek HUSBZB-1 after updating to ZWaveJS v1.9x OR ZWaveJS UI v2.0.x. See my post here.
Don’t know if this helps, but if you have the opportunity to downgrade to ZWaveJS v 1.8x or ZWaveJS UI v1.x, try that…
Perfect storm for me – major ZWaveJS driver/controller bug, new Inovelli devices, need to set device associations (can’t with HA ZJS yet) 
The different versions are for different assets.
The v2.0.1 is the HA Add-on moniker, while the v9.0.1 is the Docker container that it runs. Then there are versions for Server, Controller, Driver. 
Here is the current zwave-js-ui versions I have,
zwave-js-ui: 8.24.2.1caa735
zwave-js: 11.14.0
I’m curious what exactly is at v1.9.x or v2.x?
The HA addons (Z-Wave JS UI) is 2.0.2.
The UI reports these versions:
zwave-js-ui: 9.0.3
zwave-js: 12.0.2
I see, the add on in HAOS. I’m not a fan of HAOS, I run it as containers. There is a standalone container that has the versions I posted then one made as a HAOS add on. I don’t see what versions of zwave-js server and the ui front end it actually uses at GitHub, must run it to see I suppose.
My container has an update, but I haven’t done it yet.
I just stumbled upon this thread. It almost matches exactly what I’ve been experiencing.
I had a Aeotec 500 stick, which died. USB no longer recognized the stick. I replaced it with an Aeotec 700 before I understood all the issues with the 700 series. It worked fine for about a week, then all the nodes went dead, including all the devices on my Ring Alarm. I tried using a Zooz 800LR, but was only able to get 1 of 18 red switches to pair, even after resetting them back to factory default. I purchased an Atrim 800 stick from Inovelli, but USPS is playing games with the delivery at the moment. Hopefully, that will arrive today and I’ll give that a try.
HA is at 9.3 and Zwave JS Ui is 9.1.2.
If you run into any issues, I have a direct line to the CEO and will work with him on it with you.
1 Like
Hey RV -
Appreciate you posting. I’ve not seen anybody else with these issues, and so far haven’t been able to make sense of it.
I saw that Eric (CEO) chimed in. Appreciate that. I’ve been working with Eric (CTO) via email and direct message, Sorry I haven’t updated the post in a while.
I haven’t really gotten anywhere with it. Still having the same issues. RV - for what it’s worth, the atrim stick did not work for me.
My plan was to give it one more try after doing a more thorough reset of the aeotec stick and see if that brought any success. If it doesn’t, my next play is to try to get the ZNET dongle from Homeseer working. Prior to this mess of an attempt to move to home assistant, That device was paired successfully with all of my switches using homeseer on the back end.
Eric did offer to take a look at the switches. So I may pull out One of the dimmers and one of the on-off switches that are causing me the most issues. I’m still skeptical that it’s the switches, given that I’m having problems with so many of them.
Very frustrating problem. If you would, I’d really appreciate it if you kept posting and I’ll do the same. I really don’t want to go back to homeseer but I want things working again…