Unable to start Z-wave JS addon

I have Home Assistant virtualized in ESXi using the official OVA for HA, and a Z-stick gen 5.

I recently moved the VM from a datastore to another and since then I’m having issues setting up the Z-wave JS addon. I can start it but after just one second, the logs report that the addon has been stopped.

Logs here:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
/package/admin/s6-overlay-3.1.0.1/etc/s6-rc/scripts/cont-init: line 14: /etc/cont-init.d/config.sh: Permission denied
cont-init: info: /etc/cont-init.d/config.sh exited 126
cont-init: info: running /etc/cont-init.d/structure.sh
/package/admin/s6-overlay-3.1.0.1/etc/s6-rc/scripts/cont-init: line 14: /etc/cont-init.d/structure.sh: Permission denied
cont-init: info: /etc/cont-init.d/structure.sh exited 126
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I have tried uninstalling and reinstalling the addon, trying with a non-zwave USB device and unplugging and plugging back in the USB. It is correctly passed throught in VMWare and it is selected in the Z-wave JS configuration. However, the same process has ocurred every time.
Log level set to silly does not output any more information. How should I proceed? I can provide more information if needed.

Which version of the addon is installed? There’s a known problem that just showed with the latest

There was an issue with addon 0.1.59. This has been resolved with 0.1.60 which was recently released

1 Like

I had just updated to 1.59 (I think it also happened in 1.58 but can’t tell for sure, that’s why I didn’t think of a version bug). Updated to 1.60 and boot process seems normal. I will update if if fails. Thanks for the help