I just replaced 14 switches in my den and porches with a combination of Zen77, Zen72, and Zen32's. A few of them paired ok yesterday but I tried adding the rest today and I cant get a single device to pair. I have tried resetting all of the devices, and gone through the exclusion process as well, but no dice. I am running HAOS in a VM in unraid, using a nortek HUSBZB-1 usb stick. The scene controllers appeared to add fine, but the dimmer switches are the issue, though I did get 1 of the zen77's to pair ok.
#Need Help Adding Zooz Zen77 Switches
1 messages · Page 1 of 1 (latest)
For due diligence, work through https://zwave-js.github.io/node-zwave-js/#/troubleshooting/first-steps?id=first-steps
Z-Wave driver written entirely in JavaScript/TypeScript
You can probably skip the part about reducing reports from the network for now
Before you get too far down the road with the old HUSBZB-1, I'd take a step back and get a ZOOZ ZEN39 800 series controller. I started with the HUSB and HA several years ago, then a SILabs 700 series controller, now the ZOOZ 800 series.
this it?
@dapper remnant and @full osprey , i ordered the ZST39 (arriving today) and a 6' extension (arriving tomorrow). will report back.
ok i want to start fresh with all my zwave stuff with the new zooz stick
i googled and found this:
i dont see "remove node". is this it?
No, No, No, NO. That is from 2017, well before ZWave-JS.
Assuming you want to exclude the devices from your HUSB stick before you install your ZOOZ Zen39 --- In HA, go to Settings > Devices and Services > ZWave > Configure, and select "Remove Device." Then, do what the device manufacturer states to Exclude the device. Repeat "Remove Device" for the rest of your devices. If a device won't remove, first factory reset it per the manufacturer's instructions, then remove its power and it will become dead, then you can "Remove Failed." I'm not sure about removing failed battery devices though
I think I got it. I just backed everything up, removed the current integration, shut down the VM, removed the old stick, and I had to edit the VM. Config to remove the old USB device. Then I just enabled the new USB device in the VM config and booted it up, added the integration, and I'm on my way
So far I've gotten three devices added that I wasn't able to add the other day and it seems to be working great
Technically battery devices are always "failed", because they never respond to a ping unless they were woken up at the exact time. For that reason, you can use "Remove failed" node on battery devices at anytime (be careful!).
boom
have a couple more i havent added because i didnt realize the scene controllers werent dimmers, so gonna move a couple around tomorrow then should have the den and porches 100%. also gotta re-add my locks
then hopefully i can start fiddling with some scenes and automations
thanks @dapper remnant and @full osprey
ok so everything was working great. i even created a couple scenes and automations and wired them up to one of the b uttons on my scene controllers. yesterday i noticed the scene quit working when using the scene controller. went to test some devices and they werent working either
its like my hub is missing, and if i try to reload the integration i get this:
Check the add-on logs.
this is what i have in addons
question: am i supposed to have both of those addons installed and running?
when i googled the error message, one guy in a forum post said he had both addons running which was causing the issue
but ive tried running 1 at a time, both at a time, etc... and no dice
Yikes
You probably want to follow this guide: https://community.home-assistant.io/t/switching-z-wave-js-addons-with-minimal-downtime-z-wave-js-official-to-z-wave-js-ui-community/409904
Home Assistant Community
Introduction This guide describes how to switch from the Z-Wave JS official add-on to the Z-Wave JS UI HA Community add-on, without losing any downtime caused by the re-interviewing of nodes. In this guide, Z-Wave JS UI will henceforth be abbreviated as ZUI. Who is this guide for? This guide is for HAOS add-on users who have already installed ...
You have not switched add-ons properly
If Z-Wave JS UI is already up and running and nodes all interviewed, you can skip all the cache steps.
And just re-configure the integration
well, which one am i supposed to use?
lemme ask it this way. if this is what my stuff looked like the other day, which one WAS I using?
The clue is in your error message
core-zwave-js:3000 is the official add-on, which you've disabled.
not sure why it's not restarting, TBH
Your screenshot there doesn't tell you which add-on you're using, because both provide the same service to HA
is there a way to figure out which one i should /was using when i configured everything?
well lik ei said, one guy with the same error got the error because he was running both
So your choices are either to follow the guide I posted, or the steps in the integration docs to switch over to ZUI, or uninstall ZUI and turn the core add-on back on.
If all your nodes in ZUI control panel have a "complete" interview state, then you can simply re-configure the HA Integration to use the ZUI add-on URL.
I've been away. If you are up to managing VMs. you have the chops to ditch the ZW add-on as freshcoast linked just above and then install ZUI in a Docker container. You will get a full featured stand-alone ZW interface and up to date functionality. that integrates smoothly with HA
@jumper @sour hare i believe this is the issue: https://community.home-assistant.io/t/zooz-usb-800-lr-zst39-unresponsive-controller-troubleshooting/742864/29
i went into my server closet and the led was off on the stick. i unplugged it and plugged it back in, then i reset all my zwave js stuff (stopped zwave-js UI, started zwave-js, and rebooted the VM), and its good to go now
looks like the zooz zst39 has heavy bugs in version 1.3
You should definitely upgrade to the latest fw.