Z-Wave JS not starting after update

Configuration Z-Wave
1

I updated Z-Wave JS to 0.1.59 and now it will not start. Here is what I see in the log

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 rebooted the raspberry pi a couple of times but not getting any love there. I do note that the files /etc/cont-init.d/config.sh and /etc/cont-init.d/structure.sh Donn’t exist when I ssh into HA. so I assume these are in a separate container or are flat out missing hone the ought not be missing.

I have no idea how to manage containers in this home assistant os thing. I think HA may also be running in a container and I can’t get to the container host maybe? Anyway, an upgrade should not cause this kind of havoc in my mind.

frustrated.

Bill

2
3

Same issue here. Just started running HA last weekend and this is the first update I performed. Doesn’t exactly inspire confidence in the platform.

4

Wow… rolling back to 0.1.58

5
1 Like
6

I had the same problem and reverted back to 0.1.58. Thank goodness for backups.

7

Same here, will be reverting as well!

8

Same here. Never had a problem before.

9

0.1.60 is live now.

2 Likes
10

Same happened to me. I tried to roll back to 0.1.58 but was unable to get that to work. Had to roll back to 0.1.56, which will come to bite me if the problem with 0.1.59 cannot be worked out because I am 3 versions behind now. After rolling it back I had to rename all of the custom named zwave entities. Can anybody get this resolved?

11

look 6cm up :face_with_hand_over_mouth:

12

Like any product, don’t install updates straight away - give a bit of time for people to post threads like this.

If you do get caught out, leave the backup option ticked when you install and then you can simply go Settings > System > Backups and restore the backup that was taken before the update :wink:

13

If EVERYONE will do so, the issues will never come. And so we had the last update ever.
Someone has to be the first… :stuck_out_tongue:

14

Had teh same issue. Reverted to a backup. Trying the 1.6 update now.

15

How do you roll back just Z-Wave JS? I don’t see any of my sensors, lights, etc.

16

Restarting Z-Wave JS worked. All sensors are back and I’m using a USB dongle in a VM.