Home Assistant: 2026.4.2
Home Assistant OS: 17.2
Z-Wave JS: 15.22.1
Nabu Casa Connect ZWA-2
Z-Wave Devices: 8
I simultaneously updated HA, HAOS, and Z-Wave JS (oops) and since then, none of the device-specific entities for any of my Z-Wave devices are available.
That is, looking at either the Z-Wave JS web page or the new Settings → Z-Wave section, I can see all 8 devices. The hard-wired devices all show as Ready and the battery devices are Asleep. The visual map also shows all 8 devices as if nothing is wrong
The “stock” Z-Wave entities are all active. I can see Node Status, Last Seen, Signal Strength, etc and all show valid values. Z-Wave JS is definitely seeing the devices and recognizes them.
All of the devices have a bunch of entities devices defined because they had been working for months and in regular use. But now all of the device-specific entities are “Unavailable” and have been so since I did the update.
I have re-interviewed all of them multiple times (and even rebuilt routes, just in case). The re-interview works almost instantaneously, always successfully, but it’s still only showing the stock entities and none of the device-specific ones.
I’m not sure where to go next with this. Any ideas?
Oh? Isn’t it the other way around? I was using Z-Wave JS UI for a year or so but when I got my ZWA-2, I was directly supported by the HA-preferred Z-Wave JS and so I migrated over.
The official HA Z-Wave page also still just talks about migrating from JS UI to just JS and not the other way around.
Unless they changed again and I do need to switch back?
The community app will likely be discontinued at some point. It’s still being updated and you can keep using it for now if you want, but keep that in mind for the future. The migration to the core app is pretty straightforward.
Any new users should use the core app. There is no point in using the community app any longer.
The Z-Wave JS core app and the Z-Wave JS UI community app both provide Z-Wave JS UI.
The device entities (and not the others) could become unavailable if the node is “not ready”. This status can be seen in the device info panel. If that’s the case it means the interviews did not complete. Did you remove Z-Wave JS UI app after migration?
I did finally fix this but you’re not going to like how – I had to REMOVE all of my Z-Wave devices and then RE-ADD them. After doing so, all of the device-specific entities worked again. Thankfully, I only have seven devices (one Yale deadbolt; three Zooz hard-wired switches/dimmers; and three Ministon remote “scene” switches). It did still take about three hours!
My procedure:
Track down the manuals for all of my devices to figure out how to put them into exclusion and then inclusion modes (and how to factory reset them, just in case)
Expose all of my hard-wired switches to make their PINs visible (and QR codes but I don’t trust them)
For each device; mark as ‘removed’ in the HA zwave setting to put it into exclusion mode…
Then do the device-specific method to put the device in exclusion mode. In all but one case, this immediately worked. In one case, I needed to “factory reset” it.
Then Add Device in the zwave settings
Then do the device-specific method to put the device in inclusion mode. In all cases, the HA z-wave js core instantly saw it
Enter in the PIN that I tracked down earlier
Re-enter the name and area of the device
Revel in the now-working device!!
Go fix the many now-broken automations
Fixing the automations is what took the majority of the time. The old-school automations where fine as long as I named the re-added device to have the same name as before, since the automation would just use the string like lock.assure_deadbolt and we’re golden.
But most of my automations involving z-wave have been worked on more recently – AFTER HA switched to using device ids instead of those strings as the primary key. And whoops… removing/re-adding devices generates a brand new key and now all of the dozens of reference to the old device ids are now completely broken!! And you better know where they are, because they don’t jump out at you nor are easily found!
I did find a non-terrible way to fix the automations that might have 10 triggers for a single z-wave device (like my scene devices) – basically, HA will just show YAML for the broken triggers since it no longer recognizes the device. But what is the new device id? To find out, I just added a random trigger for the new z-wave device and then clicked on the “Edit in YAML” option. This shows me the new device id… which I then copy and paste into all of the existing triggers’ YAML configs. And that works!
Good thing I didn’t have more devices or that could have been exponentially worse.
Going forward, I’m definitely keeping a backup of my zwave config after any change!
FWIW, I migrated from Z-Wave JS UI to the core Z-Wave JS back in November, when I got the ZWA-2. I bought and setup most of my Z-Wave devices since then so most of them have only ever been part of Z-Wave JS and were never included in the old Z-Wave JS UI.
The migration went without a hitch for the few devices I originally had and all of the new ones were added just fine. They have all been working perfectly for between three and five months (depending on when I got the device). That strongly suggests to me that the interviews all worked just fine.
They just ALL abruptly stopped working for me when I did the update earlier this week. Re-interviewing each device appeared to succeed (no errors at all) but the missing entities were still missing. I was only able to recover those devices by removing and re-adding them.
It is worth saying that I apparently didn’t REMOVE the original Z-Wave JS UI after doing the migration in November. It was never a problem and so it was an out-of-sight / out-of-mind thing. I’m willing to think that maybe my problems were. a case of some core Z-Wave JS bits conflicting with any existing Z-Wave JS UI (even one not being used) and getting confused.
I just updated to 2026.4.2 and one zwave device stopped working. It’s a Enbrighten Z-Wave Smart Motion Sensor. This has worked perfectly till I updated. If I power cycle the switch it will work for a short time. Not sure if I should try removing it from home assistant and reinstalling it or roll back to 2026.3. Any suggestions on the best approach would be great.
Google Gemini:
To uninstall your Enbrighten Z-Wave Smart Motion Sensor from Home Assistant, you need to perform a process called Exclusion. This tells the sensor to leave the Z-Wave network and allows Home Assistant to clean up its entities.
How to Remove the Sensor
Enter Exclusion Mode in Home Assistant:
Navigate to Settings > Devices & Services.
Select the Z-Wave integration.
Find your motion sensor and click on it to open the Device Info page.
Click the three-dot menu (next to the “Configure” or “Re-interview” buttons) and select Delete .
When prompted, choose Remove a working device. This puts your Z-Wave controller into “Exclusion Mode.”
Activate Exclusion on the Device:
While Home Assistant is “Searching for devices to remove,” you must physically trigger the sensor.
Quick-press the program button on the sensor (often located inside the battery compartment or on the side/bottom) 3 times quickly .
Home Assistant should display a notification that the device has been successfully excluded.
Troubleshooting & Alternative Methods
If the device is dead or unresponsive: If you cannot trigger the physical button (e.g., the sensor is broken), select Remove a failed device in the Z-Wave settings. Home Assistant will attempt to ping the device; when it doesn’t respond, it will force its removal from the controller’s memory.
Factory Reset: If the exclusion fails, you can factory reset the sensor by pressing and holding the program button for 10 seconds (check your specific Enbrighten manual as some models vary). Note that a factory reset removes the network info from the sensor, but you may still need to “Remove Failed Node” in Home Assistant to clear the ghost entry.
Automation Cleanup: Be aware that removing the device will break any automations that used its specific Device ID. If you plan to re-add the sensor, try to use Entity IDs in your automations instead of Device IDs to make future replacements easier.
