addons: OpenZWave 0.6.0 not starting due to missing vnc_lite.html

The problem

Just upgraded to 0.6.0. The previous version was working fine. Now getting this output:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] auth.sh: executing... 
[23:19:55] INFO: Auth database exists
[cont-init.d] auth.sh: exited 0.
[cont-init.d] mqtt.sh: executing... 
[23:19:56] INFO: Connected to internal MQTT service
[cont-init.d] mqtt.sh: exited 0.
[cont-init.d] network_key.sh: executing... 
[cont-init.d] network_key.sh: exited 0.
[cont-init.d] novnc.sh: executing... 
sed: /usr/share/novnc/vnc_lite.html: No such file or directory
[cont-init.d] novnc.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing... 
[23:19:57] INFO: Ensure upstream MQTT server has the correct OZW status
[cont-finish.d] mqtt.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Environment

Add-on with the issue: OpenZWave
Add-on release with the issue: 0.6.0
Last working add-on release (if known): 0.5.4
Operating environment (OS/Supervised): HassOS 4.13

Problem-relevant configuration

Traceback/Error logs

Additional information

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 37 (5 by maintainers)

Most upvoted comments

I know it can be frustrating having something break with an update, but I’ve got to commend the folks working in this project. The speedy response and roll-back resolution is commendable. I for one am loving seeing the evolution of this project. Thanks

ngergely on Sep 17, 2020

We must all remember that this is a community project with limited development resources available. Having something like this happen once in a while is to be expected (but hopefully not too often…). For important add-ons like this one, I have the automatic upgrade option turned off, so I have a chance to make a backup/snapshot before I upgrade. Your response to this problem was impressive. So keep up the good work, guys!

hmorkemo on Sep 17, 2020

We decided to roll back the add-on to the 0.5.2 image.

https://github.com/home-assistant/hassio-addons/pull/1583

This should show up as an update in the add-on panel.

MartinHjelmare on Sep 17, 2020

what’s the best way to revert to 0.5.2, please?

I was able to use one of my previous snapshot and just reverted ozwave

t3miLo on Sep 17, 2020

0.5.3: failed to build on all architectures.
0.5.4: ozw-admin didn’t work in all architectures.
0.6.0: failed to run successfully.

MartinHjelmare on Sep 17, 2020

When will this ‘update’ be rolled out? I cannot see it yet on my instances and I have 45+ devices offline since this morning… Thanks!

If you run ha addons reload on the CLI it should be available in the UI as an update after that.

You can use the core ssh add on web terminal if you don’t have handy access to the cli already.

lukewaite on Sep 17, 2020

You can also try to reload the add-on store in the GUI.

Ok, reloading the store just worked and all my devices are newly alive. Thanks guys!

ThePirat91 on Sep 17, 2020

And me. An immediate official fix will be very much appreciated!

hmorkemo on Sep 17, 2020

!!! WORKAROUND ONLY - AT YOUR OWN RISK !!!

Copy the current config and store it so you have easy access to it
Remove the old integration
Add this custom addon repository: https://github.com/GeertvanHorrik/hassio-addons-repo
Install openzwave
Paste your config
Start the extension

Note that this is a workaround and will not support auto updates. You will have to redo the revert, but at least this should unblock for everyone.

I tested this, so far so good. But again, use at your own risk. The “only” thing I noticed is that you need to await the refresh of the devices since the zwave config seems gone (but not your devices, that’s stored in the controller).

GeertvanHorrik on Sep 17, 2020