Z-Wave JS UI 7.0.0 update killled my HAOS VM

madbrain · February 5, 2026, 7:49pm

Edit:

Turns out the ZUI 7 was coincidental to the issue of HA not coming back up, and not the trigger.

Not sure if anyone else ran into this, but my HAOS VM hung, and became unbootable~~, after upgrading to ZUI 7.0.0~~ . It was quite a nightmare to recover from, since I could no longer login to the HA GUI to restore a tar backup.

github.com/home-assistant/core

HAOS becomes unbootable after upgrading to Z-Wave JS UI 7.0.0

opened 07:46PM - 05 Feb 26 UTC

madbrain76

needs-more-information

### The problem I have a very complex setup with over 130 Z-wave nodes. When th…e update notification came, I accepted it. HAOS became non-responsive. I tried to restart the VM. I could no longer connect to it. The whole OS was effectively nuked. I had to restore a VM snapshot. I could not use the HAOS restore facility, since the HA web UI was no longer accessible. ### What version of Home Assistant Core has the issue? core-2026.2.0 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue N/A ### Link to integration documentation on our website N/A ### Diagnostics information I unfortunately can't provide any diag info, since the VM became unusable, and I had to roll back the snapshot. ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt Unfortunately, nothing. ``` ### Additional information I'm using VMWare Workstation Pro 25H2 on Windows 11 Pro. I accepted the ZUI update while over 10,000 miles away from home. I have never seen any HAOS or add-on update get the VM into this state. I normally rely on the HA backup facility, and not VM snapshots. I thus did not have a snapshot to rollback to. I had to restore the entire VM from an Acronis disk backup. Now that I do have snapshots, I can reproduce the problem by doing the following : 1. start with working HAOS VM 2. take snapshot 3. upgrade to ZUI 7.0.0 4. HA hangs 5. restart the VM through VMWare GUI 6. HA GUI is no longer acccessible 7. restore VM snapshot 8. HA works again I won't be back home to investigate further for another 10 days. For now, I have marked the ZUI update as skipped.

petro · February 5, 2026, 7:52pm

That really doesn’t prove it was Zwave JS UI that caused it. Correlation doesn’t mean causation. Unfortunately, I don’t think that issue is going to get any dev response because it doesn’t have any information.

I’m currently running the zwave js ui 7.0.0 without issues.

madbrain · February 5, 2026, 8:05pm

It is reproducible, so I do know the ZUI 7 install was the trigger.

I don’t expect the issue to be worked on while I’m abroad and unable to collect further diagnostic. I posted this here as a warning, in case it happens to anyone else.

petro · February 5, 2026, 8:11pm

Are you sure your system has enough room to download the container?

Also, keep in mind that Zwave JS UI is a custom app, the issue should be written against that repository. Home Assistant Core is not the correct place for that issue.

NathanCu · February 5, 2026, 8:53pm

FYI cannot reproduce on proxmox VE 8.4.x + HAOS:

madbrain · February 7, 2026, 9:17am

Yes, there was enough room.

The only reason I filed it against HA is the instructions for Z-wave JS UI github component, that direct anyone not instructed by a developer to file against HA, not against ZUI.

After further investigation, I no longer believe ZUI was the trigger for the issue of HA not coming back up, and thus updated the title of this thread, and will update the OP. I still don’t know the root cause, though, but will add what I found so far to the bug, which I believe is actually rightly filed against HA core.