HAOS running in VirtualBox on Gentoo Linux hosts. It’s been wokrking mostly fine for months, but the latest upgrade of Z-Wave JS UI from 13.6.1 to 13.7.0 took multiple attempts, with the HA system completely freezing and requires a clean start. The upgrade finally went through, but on the Overview, all my devices are disabled. The areas (garage and porch) seem enabled, but toggling them has no apparent effect. Going to Settings/Addons/ZWave JS UI and clicking “Open Web UI” gives “The add-on seems to not be ready, it might still be starting. Do you want to try again?” Telling it to retry gives the same message again, and telling it to not try again says “502: Bad Gateway.”
Loading the backup from just before that upgrade sucessfully downloads to 13.6.1 and the system works correctly. I’ve tried the upload again, and it did take two reboots of the VM, after which I have again the same problems.
The last line in the ZWave JS UI log is “s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/discovery/type: must be oneshot, longrun, or bundle” and I thought I had seen more of that message earlier today, but don’t see it now.
Is this a known issue, or what logs should I post, or what other troubleshooting can I do myself?
Thanks for any suggestions.
S6 is the init service that most docker containers use. If your seeing an error saying onewhot, etc. it’s because one of the s6 service run files has wrong syntax or missing syntax. Does it say what service the error is coming from?
No, that’s the whole message. This whole installation is pretty standard. I have not yet done anything “creative.” What logs should I look in? (I’ll try to download that entire log, in case there is something I’m not seeing by not scrolling back far enough.
I set the log level to debug, and while the addon was restarting I already see this at the end of the 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
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/discovery/type: must be oneshot, longrun, or bundle
When it finishes restarting, I’ll download the whole log and browse/grep for problems.
Open an issue in the z wave JS repo, that’s the init code and is baked into the docker layers from building the image. One of the maintainers needs to fix an S6 service file.
It’s weird your the only one with the issue so far though, if it’s really an S6 unit file, all docker images should be throwing this error from that version.
While trying to find various version info for logging that issue, I found that Settings/Devices and Services/Integrations/Z-Wave shows
Failed setup, will retry: Failed to connect: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Connect call failed (‘172.30.33.0’, 3000)]
but the config shows URL ws://a0d7b954-zwavejs2mqtt:3000 which seems to be what the docs call for. Poking around some more shows the hub as “unavailable.” Hub is a Zooz 800 ZST39 LR, which is definitely connected, showing up in lsusb on both the host and in the VM, and it is one of the 7 Z_Wave devices shown.
I’m restarting the VBox again, but I"m just getting increasingly confused.