I have ZWave JS UI (aka zwavejs2mqtt) 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.
I can update Home Assistant Core, but then this update creates a failed dependency (ZWave JS UI neeeds to be newer). However, I can’t install the update for ZWave JS UI (tried both with Home Assistant Core 2024.3.3 and 2024.7.4).
In general, the update of ZWave JS UI fails, but I found a way to force it by stoping the addon (I actually had to make it not start at boot) and then updating once it’s stoped.
The update did work, but then the addon does not load. The error log line from ZWave JS UI says:
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/discovery/type: must be oneshot, longrun, or bundle s6-rc: fatal: unable to take locks: no such file or directory
Reloading the backup (I used a full backup from 3 days ago) was the only solution I found.
My questions
Is this a bug and waiting for a new version of ZWave JS UI will likely sort it out, or is it a different issue?
I’m worried that too many updates have happened, and not being able to apply them incrementally may be the root cause. Is there any way to apply updates incrementally or to update to a specific version of an addon?
Sorry, I just realized I did not explain something.
Basically when I try to update the whole system freezes. I’m running Home Assistant in a VirtualBox, and the machine hangs up (the CLI interface of the machine, where I see the “ha >” console, freezes up). The only way I found to solve this was rebooting the virtual machine (hard power-off and reboot) , but after the reboot I am unable to find any log, I just see that the addon is still on the previous version.
Thanks for that!! That’s damm complicated
I went through it but still coudln’t find anything.
I downloaded the journal and opened with journalctl and I found this.
– Journal begins at Fri 2022-07-15 03:18:42 CEST, ends at Mon 2023-03-27 13:44:47 CEST. –
Looks like I have two directories for journal. One of them is old, and I can read it (the one you see pointed above) but the other one, which is fresher, seems to have a different format. When I only download this directory I get the error
Journal file a2f13a7d358a45f5b34343bb5b91d733/system@e315b543b04741de8b8a5a5d3862dede-00000000016d7a51-00061e685d300cdc.journal uses an unsupported feature, ignoring file.
Use SYSTEMD_LOG_LEVEL=debug journalctl --file=a2f13a7d358a45f5b34343bb5b91d733/system@e315b543b04741de8b8a5a5d3862dede-00000000016d7a51-00061e685d300cdc.journal to see the details.
Journal file a2f13a7d358a45f5b34343bb5b91d733/system@e315b543b04741de8b8a5a5d3862dede-00000000016ed450-00061e7a0a660b0b.journal has unknown incompatible flags 0x10
Failed to open journal file a2f13a7d358a45f5b34343bb5b91d733/system@e315b543b04741de8b8a5a5d3862dede-00000000016ed450-00061e7a0a660b0b.journal: Protocolo no soportado
OK, I managed to update my systemd and that way I could read all the logs. Then I tried to do the JS UI update again, and when it failed and I rebooted, I re-downloaded the logs.
This is what I found around the time of the attempt to update (note I clicked on “update” exactly at 00:15:00:
ago 01 00:14:38 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-08-01 00:14:38.503 INFO Z-WAVE: [Node 044] Metadata updated: 50-1-value-66049
ago 01 00:14:38 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-08-01 00:14:38.505 INFO Z-WAVE: [Node 044] Value updated: 50-1-value-66049 0 => 0
ago 01 00:14:51 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-07-31T22:14:51.764Z CNTRLR » [Node 060] Meter CC values may be stale, refreshing... [Endpoint 1]
ago 01 00:14:51 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-07-31T22:14:51.767Z CNTRLR » [Node 060] querying meter value (type = Electric, scale = kWh)... [Endpoint 1]
ago 01 00:14:52 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-08-01 00:14:52.236 INFO Z-WAVE: [Node 060] Metadata updated: 50-1-value-65537
ago 01 00:14:52 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-08-01 00:14:52.241 INFO Z-WAVE: [Node 060] Value updated: 50-1-value-65537 1.65 => 1.65
ago 01 00:14:52 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-07-31T22:14:52.246Z CNTRLR » [Node 060] querying meter value (type = Electric, scale = W)... [Endpoint 1]
ago 01 00:14:52 homeassistant addon_core_configurator[435]: INFO:2024-08-01 00:14:52,759:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 -
ago 01 00:14:52 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-08-01 00:14:52.759 INFO Z-WAVE: [Node 060] Metadata updated: 50-1-value-66049
ago 01 00:14:52 homeassistant addon_a0d7b954_zwavejs2mqtt[435]: 2024-08-01 00:14:52.761 INFO Z-WAVE: [Node 060] Value updated: 50-1-value-66049 0 => 0
ago 01 00:15:01 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:01.835 INFO (MainThread) [supervisor.backups.manager] Backup 1f3241eb starting stage addon_repositories**
ago 01 00:15:01 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:01.835 INFO (MainThread) [supervisor.backups.manager] Backup 1f3241eb starting stage docker_config**
ago 01 00:15:01 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:01.835 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug 1f3241eb**
ago 01 00:15:01 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:01.837 INFO (MainThread) [supervisor.backups.manager] Backup 1f3241eb starting stage addons**
ago 01 00:15:01 homeassistant addon_cebe7a76_hassio_google_drive_backup[435]: **08-01 00:15:01 INFO A backup directory file was modified, we'll check for new backups soon.**
ago 01 00:15:01 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:01.844 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on a0d7b954_zwavejs2mqtt**
ago 01 00:15:01 homeassistant homeassistant[435]: **2024-08-01 00:15:01.892 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error)**
ago 01 00:15:02 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:02.620 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon a0d7b954_zwavejs2mqtt**
ago 01 00:15:02 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:02.620 INFO (MainThread) [supervisor.backups.manager] Backup 1f3241eb starting stage finishing_file**
ago 01 00:15:02 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:02.624 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 1f3241eb completed**
ago 01 00:15:02 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:02.625 INFO (MainThread) [supervisor.docker.addon] Updating image ghcr.io/hassio-addons/zwave-js-ui/amd64:3.4.1 to ghcr.io/hassio-addons/zwave-js-ui/amd**>
ago 01 00:15:02 homeassistant hassio_supervisor[435]: **2024-08-01 00:15:02.625 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/hassio-addons/zwave-js-ui/amd64 with tag 3.9.2.**
**-- Boot c80eaa9afee04bb3a81716a79acff8d3 --**
ago 01 00:19:43 homeassistant kernel: **Linux version 6.6.33-haos (builder@bfa75d3d66a7) (x86_64-buildroot-linux-gnu-gcc.br_real (Buildroot -gd03dda4f) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Tue Jun 18 13:**>
ago 01 00:19:43 homeassistant kernel: Command line: BOOT_IMAGE=(hd0,gpt4)/bzImage root=PARTUUID=a3ec664e-32ce-4665-95ea-7ae90ce9aa20 rootwait zram.enabled=1 zram.num_devices=3 systemd.machine_id=a2f13a7d358a45f5b34343bb5b91>
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.
I tried to download the docker image from the same server/connection and it took less than a minute to download. I did that in case it was a very slow download and I just had to be patient (would be weird anyway because with ZWave JS UI stopped I was able to run the update quickly and got the other error later)
It may be related or not, but interestingly, this morning my virtual machine was hanged up (no attempt to run an update or anything else). I had to reboot to get it back to work.
This is the journal log for just before the system hanging up:
ago 01 00:48:04 homeassistant addon_core_configurator[441]: INFO:2024-08-01 00:48:04,496:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 -
ago 01 00:48:17 homeassistant addon_a0d7b954_zwavejs2mqtt[441]: 2024-08-01 00:48:17.363 INFO APP: GET /health/zwave 301 0.321 ms - 191
ago 01 00:48:22 homeassistant homeassistant[441]: 2024-08-01 00:48:22.900 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error)
ago 01 00:48:27 homeassistant audit[1979]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=docker-default pid=1979 comm="node" exe="/usr/local/bin/node" sig=11 res=1
ago 01 00:48:27 homeassistant kernel: audit: type=1701 audit(1722466107.056:279): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=docker-default pid=1979 comm="node" exe="/usr/local/bin/node" sig=11 res=1
ago 01 00:48:27 homeassistant systemd[1]: Created slice Slice /system/systemd-coredump.
ago 01 00:48:27 homeassistant audit: BPF prog-id=74 op=LOAD
ago 01 00:48:27 homeassistant audit: BPF prog-id=75 op=LOAD
ago 01 00:48:27 homeassistant kernel: audit: type=1334 audit(1722466107.077:280): prog-id=74 op=LOAD
ago 01 00:48:27 homeassistant kernel: audit: type=1334 audit(1722466107.077:281): prog-id=75 op=LOAD
ago 01 00:48:27 homeassistant audit: BPF prog-id=76 op=LOAD
ago 01 00:48:27 homeassistant kernel: audit: type=1334 audit(1722466107.078:282): prog-id=76 op=LOAD
ago 01 00:48:27 homeassistant systemd[1]: Started Process Core Dump (PID 5252/UID 0).
ago 01 00:48:27 homeassistant systemd-coredump[5253]: Process 1979 (node) of user 0 terminated abnormally without generating a coredump.
-- Boot 7fb78ea5be284f379f7d3ffbab6d59b6 --
ago 01 08:27:04 homeassistant kernel: Linux version 6.6.33-haos (builder@bfa75d3d66a7) (x86_64-buildroot-linux-gnu-gcc.br_real (Buildroot -gd03dda4f) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Tue Jun 18 13:>
If I try to stop the addon using the Home Assistant UI, it fails as well. Same behaviour than on failing update: everything freezes and I need to reboot the machine. Then the journald logs show similar output as stated above:
ago 02 10:58:43 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02 10:58:43.724 INFO Z-WAVE: [Node 007] Is now asleep
ago 02 10:58:43 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02T08:58:43.726Z CNTRLR [Node 007] The node is now asleep.
ago 02 10:58:58 homeassistant homeassistant[439]: 2024-08-02 10:58:58.504 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error)
ago 02 10:59:05 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02 10:59:05.039 INFO APP: GET /health/zwave 301 0.232 ms - 191
ago 02 10:59:05 homeassistant addon_core_configurator[439]: INFO:2024-08-02 10:59:05,400:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 -
-- Boot 3dde8bdaa5854e82aeedba0ca6d35f2a --
ago 02 11:06:23 homeassistant kernel: Linux version 6.6.33-haos (builder@bfa75d3d66a7) (x86_64-buildroot-linux-gnu-gcc.br_real (Buildroot -gd03dda4f) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Tue Jun 18 13:51:59 UTC 2024
ago 02 11:06:23 homeassistant kernel: Command line: BOOT_IMAGE=(hd0,gpt4)/bzImage root=PARTUUID=a3ec664e-32ce-4665-95ea-7ae90ce9aa20 rootwait zram.enabled=1 zram.num_devices=3 systemd.machine_id=a2f13a7d358a45f5b34343bb5b91d733 fsck.repair=yes console=ttyS0 co>
ago 02 11:06:23 homeassistant kernel: BIOS-provided physical RAM map:
So my guess is that the first step to install the update is to stop the running addon, and that is failing. But I don’t seem to find out why.
All of your important information is stored on the controller and in the Z-Wave JS UI store. I would just do a full home assistant backup which will backup the Z-Wave JS UI store then uninstall Z-Wave JS UI and reinstall it.
Technically, I can’t uninstall the ZWave JS UI either… I hit the same problem (it tries to stop it first). I’ll set it up not to start at boot and see if that works.
I did that. Removed the add on and installed it again. Then it won’t start.
The error log in the supervisor says
2024-08-02 13:26:17.828 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/zwave-js-ui/amd64 with version 3.9.2
2024-08-02 13:26:18.417 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_a0d7b954_zwavejs2mqtt application
2024-08-02 13:26:18.629 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-2894' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1429> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/addons/addon.py", line 1443, in watchdog_container
await self._restart_after_problem(event.state)
File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 290, in wrapper
raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
2024-08-02 13:26:18.629 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/zwave-js-ui/amd64 with version 3.9.2
So I managed to set up ZWave JS UI so it communicates to my ZWave Controller and lists all the nodes.
Then I added my nodes.js backup to have these nodes “named”.
However, my home assistant is still freezing constantly, and every time it happens I need to reboot.
I have a feeling that it has to do with ZWave JS (and not the ZWave JS UI addon). But it’s unclear to me if I can make everything work without ZWave JS. I keep removing ZWave JS and it keeps getting reinstalled and enabled at boot automatically. Then the ZWave JS integration is the one showing the devices, but it does not seem to be able to communicate with them.
And the ZWave JS UI integration shows the nodes but I can’t see devices attached to it.
If I disable the MQTT in the JS UI settings, everything crashes.
For now I’ve managed to make it work. Even if I got the nodes back, I lost the devices settings (in Home Assistant) so I had to re-configure them (hide the ones I don’t need, change icons, names, etc). What a nightmare.
I’m still scared of the system not being stable and maybe freezing upon certain conditions or not letting me update. How can I check that everything works fine?
Also, I had auto-updates disabled because in the past some updates made all my devices to get duplicated or change their names or properties, and it was bad, so I wanted to do that manually and then check if everything is good.
But I’m pretty sure that having so old updates was part of the problem, probably things have changed a lot and not doing incremental udpates did not allow the system to be really backwards compatible. What do you recommend?
So actually, every time I update any setting in ZWave JS UI, everything freezes. I haver MQTT enabled, although I’ve set ZWave to connect to ZWaveJSUI, so I think I should disable that.
This is what I get on the freeze:
ago 02 19:54:28 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02T17:54:28.829Z CNTRLR » [Node 005] Sending node back to sleep...
ago 02 19:54:28 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02 19:54:28.869 INFO Z-WAVE: [Node 005] Is now asleep
ago 02 19:54:28 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02T17:54:28.870Z CNTRLR [Node 005] The node is now asleep.
ago 02 19:54:52 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02 19:54:52.159 INFO APP: GET /health/zwave 301 0.314 ms - 191
ago 02 19:55:22 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-f7f541618e2f9da8692aa1a75121f17b4d442e32823dbff6faa184b543835cac-runc.wHmWTG.mount: Deactivated successfully.
ago 02 19:55:22 homeassistant addon_a0d7b954_zwavejs2mqtt[439]: 2024-08-02 19:55:22.193 INFO APP: GET /health/zwave 301 0.286 ms - 191
-- Boot b125ab0c548e42a3b1a47d6ca88a47c5 --
I’m also seeing the following errors in my journald:
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: ValidationError: The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false (default). This could indicate a misconfiguration which wou>
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: at Object.xForwardedForHeader (/opt/node_modules/express-rate-limit/dist/index.cjs:167:13)
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: at Object.wrappedValidations.<computed> [as xForwardedForHeader] (/opt/node_modules/express-rate-limit/dist/index.cjs:362:22)
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: at Object.keyGenerator (/opt/node_modules/express-rate-limit/dist/index.cjs:617:20)
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: at /opt/node_modules/express-rate-limit/dist/index.cjs:669:32
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: at /opt/node_modules/express-rate-limit/dist/index.cjs:649:5 {
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR',
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: help: 'https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/'
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: }
ago 02 19:58:40 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: 2024-08-02 19:58:40.987 INFO APP: GET /api/store 200 10.009 ms - 1304
ago 02 19:58:42 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: 2024-08-02 19:58:42.585 INFO APP: GET /api/store?path=/data/store/settings.json 200 4.041 ms - 2203
ago 02 19:58:42 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: 2024-08-02 19:58:42.613 INFO APP: GET /assets/prismeditor.esm-CB7UZCGn.js 304 2.055 ms - -
ago 02 19:58:47 homeassistant homeassistant[437]: 2024-08-02 19:58:47.412 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will s>
lin
I’ve tried a bunch of different things but my system is still in the same place.
Looks like it’s all driven by ZWave JS UI addon. I can’t stop it, restart it, or make any change (even saving without change) to its configuration. All of that makes the whole Home Assistant OS to freeze.
Many other things, such as rebooting the system, also result in a freeze. I believe it’s because they implicitely require stopping the addons.
I can stop or edit configurations of other addons, add devices, edit automations, etc. So it only seems to affect the ZWave JS UI addon.
Looks like someone followed up in the issue I opened on ZWave JS UI Addon git page, and they are experiencing the same issues.
The add on has not been updated in more than 2 weeks, even if two newer versions of ZWave JS UI have been published. I guess the person that maintains it is out for holidays, because usually these updates come in very quickly.
Looks like a new update has been published. I can’t install it normally (I need to manually set the addon to not boot at start and then hard reboot the system).
Once it is installed, I get back to square 1, with the error I started getting when I first updated, that prevents the addon from starting and ended up focing me to do a new fresh install (loosing all my devices and configurations):
This is the raw addon log
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/discovery/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
This is the journald log
ago 06 21:29:29 homeassistant hassio_supervisor[437]: 2024-08-06 21:29:29.852 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Z-Wave JS UI is unhealthy, restarting...
ago 06 21:29:29 homeassistant hassio_supervisor[437]: 2024-08-06 21:29:29.855 INFO (SyncWorker_0) [supervisor.docker.manager] Stopping addon_a0d7b954_zwavejs2mqtt application
ago 06 21:29:29 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: s6-rc: fatal: unable to take locks: No such file or directory
ago 06 21:29:29 homeassistant addon_a0d7b954_zwavejs2mqtt[437]: s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
