Problem upgrading to 3.9.2. from 3.4.1 #695
Comments
|
I believe I'm having a similar issue, but I'm stuck at Z-Wave JS UI 3.6.0 and Home Assistant core 2024.6.4. In early June my Home Assistant auto-updated Z-Wave JS UI from 3.6.0 to 3.7.1 and it froze the VM (I'm also running VirtualBox). I rolled back to 3.6.0 and it started working again. I asked about this on the Home Assistant Discord, but didn't get any fruitful responses: https://discord.com/channels/330944238910963714/1247691086533496895 I tried updating to Home Assistant Core 2024.7 when that came out, hoping whatever was going on might be sorted out, but ran in to the same error about Z-Wave JS UI 3.6.0 not working with 2024.7; and trying to update Z-Wave JS UI 3.6.0 again (from 2024.7) just crashes the VM, same as trying to update it from 2024.6.4. I'm happy to share any relevant logs, but am not sure where to look. |
|
Im documenting all my process here. I managed to update to the last version (by setting the addon to not load at boot and then reboot and, without the addon started, update it). But my system is still in this weird state where any change to the ZWave JS UI or the ZWave JS configuration (config change, try to stop it, etc..) makes the whole system crash. |
|
Correcting myself. The ZWave JS Integration does not seem to make the system crash. I think it did when I was playing around trying to get my system into a stable state, when I removed the integration, but it's not happening anymore with any change to the config I've tried. The issue remains with the ZWave JS UI Addon. Even updating the config to enable log to file or backups makes it crash. Also note that I ended up fully removing the ZWave JS UI add on and installing it from scratch, and then the only thing I recovered from my prior instalation were the nodes.json file. I also copied some settings manually to the settings json file, but preserving the structure of the new file (I just copied values because it was faster than making the addon not start at boot, so I could update configs without it making the system crash). This is my very last journalctl log before crash. The only action I did was clic save on the add on settings (without actually making any change). I've also enabled ZWave JS UI to log to a file and set log level to debug, but I did not get anything interesting in that file (I clicked save at 23:31, that's when the system crashed) |
|
By doing the same workaround (setting the addon to not start at boot, rebooting -with a crash of the system- and then when the addon is not running, updating it) I've managed toupdate to the last version, 3.9.3 However, after the update, I'm getting the following error, and the addon will not start: And this in the journald log The error repeats every time I try to start the addon. I've tried rebooting, but I had no success. I had seen a similar error before already, when I updated last time while keeping an existing configuration. I only solved that by removing the whole addon and installing a fresh one, and then manually setting everything again. So this time I went for a temporary solution until I find out what's going on: reverting to prior version (loading the backup) After reverting, the add on started again, and it showed this: Which tells me that the first thing the add on does is starting the s6rc-oneshot-runner, and apparently this does not work with the new version (but it did not work after update earlier either, it's weird!) |
|
Looks like the problems I was facing were a combo of
|
|
For what it's worth, I'm using a different controller (Zooz ZST10) but think I'm having a similar problem. I also have the VirtualBox USB controller set as USB 2.0: https://go.benish.io/TJSNxBfH |
|
I think it's an issue with the USB 2.0 driver. I ended up solving it by switching to usb3, which required a firmware update of the controller in my case, plus plugging the controller directly to the server without a USB hub that I was using. See the full details and the solution here: https://community.home-assistant.io/t/help-z-wave-js-ui-addon-breaking-my-system/758887 |
|
@othermore Thank you for chasing this down and the link to that other thread! I'll try your solution when I have a moment. |
|
@othermore I updated my Zooz ZST10 to the latest firmware and set the VirtualBox USB controller to USB 3 and that has solved my issue as well. Thanks! |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
Problem/Motivation
I can't update to the last version of the addon. I can't stop the addon. Forcing the update works, but the fresher version of the addon will never start.
Expected behavior
Addon should be stoppable and updatable. New version should work.
Actual behavior
Addon can't be stopped. Addon can't be upgraded. Forcing the upgrade to last version results in addon not starting up.
Full details
I have ZWave JS UI addon version 3.4.1, when the latest version (published 1 week ago I believe) is 3.9.2. There’s been a bunch of intermediate updates I have not installed.
I also have Home Assistant Core 2024.3.3, when the latest version is 2024.7.4.
If I update Home Assistant Core to the latest version, ZWave JS UI stops working because it's too old for this core. However, I can’t install the update for ZWave JS UI (tried both with Home Assistant Core 2024.3.3 and 2024.7.4).
Issue 1: update fails
I try to update through the Home Assistant UI, and as soon as I click on update, the whole Home Assistant freezes. It's running on a VirtualBox and the ha> prompt freezes too (i.e. the whole Virtual Machine stops responding). Only forcing a reboot gets it back, and the update has not happened.
This is what I found in the journald logs around the time of the attempt to update (note I clicked on "update" exactly at 00:15:00):
So to me it looks like there's nothing useful thing. Last command I see is the JSUI image being downloaded. Then nothing happens until I force a reboot several minutes later.
Issue 2: I can't stop the addon
If I try to stop the addon using the Home Assistant UI, it fails as well. Same behaviour than on issue 1: everything freezes and I need to reboot the machine. Then the journald logs show similar output as stated above:
So my guess is that the first step to install the update is to stop the running one, and that is failing
Issue 3: If I force the update, then I get another error
The only way I found to install the update was stoping the addon by setting it to not start at boot, and then rebooting. That way, when Home Assistant reboots, the add-on is not running. After that, I was able to install the update through the UI.
Immediately after installing this update, the addon is unable to load. The error log line from ZWave JS UI says:
I've seen the same exact error log in a ESPHome github issue, so I'm guessing there's some common dependency that causes this error. The post is also for about a week ago, so it may be related.
The text was updated successfully, but these errors were encountered: