I recently began my migration off of SmartThings to a HAOS Yellow.
I have 79 devices, 13 sensors, 9 fans, 2 locks, 3 motion, 14 outlets, 35 switches, and a few odds and ends. All Z-Wave…
For the most part the devices came over fine. I removed each device one at a time, factory reset, then added to HAOS. The biggest challenge I had was three battery sensors - still looking into those.
I had all 79 devices working and “ready” in HAOS.
Then I decided to tackle the Locks. I already knew this was going to be a problem so I moved the HA Yellow from the utility room to right next to the lock.
Ofcourse I had problems with the lock and I am still working on that, but I decided to move the HA Yellow back to it’s normal location and bring the lock to it rather than it to the lock.
Now I am seeing 32 devices “not ready”. I can not rebuild the Z-Wave Network, Every device I try to reinterview just sits there on ProtocolInfo.
I had some weird issues adding the Locks - where it would drop two nodes in the Devices and lock up. I could not remove the dead nodes using “Remove Failed” but I could use “Delete”. Interestingly, if I try to add the locks again, it seems to kick off the previous Z-Wave “Add Device” which never finishes…
I say all that because it seems my attempt to add the locks put the Z-Wave controller into a state where it’s still trying to add the locks and thus blocking everything else.
I just got started using this platform, where can I start looking to figure out what’s going on?
First bit of advice. Do not. Treat ZWave in HA like SmartThings. ST abstracts the ZWave stack and prevents you from doing some things.
One of those is spamming the network with repairs.Don’t do that. Target repairs full network repairs on a 50+ node network will flood it and you’ll be waiting a bit till it clears.
I suspect when you moved your controller you caused a signal issue elsewhere. First step is get the controller back to home shut it down, restart the then get a log so we can see what’s going on.
I would start by ensuring the mesh is stable first. Identify your devices closest to the controller and ping them. If they respond work outward. You don’t say if you are using Z-wave JS UI, but if you’re not you are probably making life much harder. You can check the route quality of each device in that Add-on.
When I check the logs on verbose and following the initial boot.
I notice it errors trying to set regions to USA Long Range (not sure if that matters)
Then it hits all the nodes but begins to loop on these entries below. It all the log says after the initial reboot.
I read… " If you’re running full Home Assistant with supervisor, you will be presented with a dialog that asks if you want to use the Z-Wave JS Supervisor add-on. You must uncheck this box if you are running the Z-Wave JS server in any manner other than the official Z-Wave JS add-on, including using Z-Wave JS UI add-on."
I selected “Supervisor”… I am still looking for freshcoast migration post - he has a lot of posts.
I see all my keys… Adding them to Z-Wave JS UI says, must be different.
I disabled Z-Wave JS - I assume uninstalling will release the hold on the keys?
Question, will I loose my devices?
Also, I did not see an entry for “Network Key” for Z-Wave JS UI
Factory reset those 2 devices and wait for network to stabilize. You can delete them from zwavejsui after factory reset if desired.
Check tx/RX retransmit and you can individually heal devices with retransmits in the hundreds. Before doing this however, try sending device a command to verify it’s either slow responding or non responsive. If it works ok do nothing. If you do heal device check operation has improved
After verifying all is ok, try adding the 2 problems devices back
Well, I think I’m back to a stabilized environment. I have a Razbery Z-Way Pro internal radio. So I went down the rabbit hole of upgrading the firmware to the device - which typically requires installing Z-Way Integration into HAOS - which essentially is just another wrapper for Z-Wave Device Management.
Oddly, using the menu inside Z-Way.Me - I was able to initiate a Device Exclusion and remove the lock. This did not remove the problematic nodes - but the lock responded with a green checkmark - which it has never done before unless using SmartThings exclusion.
I upgraded the firmware of the radio and things seemed to work much better.
I’m not sure if it’s the radio firmware or if it was putting another Z-Wave device manager into the mix that kicked things off.
Now off to a Z-Wave Network Repair… I’m not sure I trust trying to add these locks again.
