OpenZWave 0.6.0 not starting due to missing vnc_lite.html

[GeertvanHorrik]

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

[Veldkornet]

I have the problem as well after updating to 0.6.0.

[miouzikal]

Same here. :( Addon was working fine before

[staticlama]

Same issue for me. Just updated this morning.

[Veuchez]

Same problem with update 0.6.0

[SimonG-GH]

Same here

[schildgenb]

same problem here

[callahan17]

Same here, couldn't update to 0.5.3 issue #1572, but now 0.6.0 has installed but does not start, logs as above. No Zwave.

[t3miLo]

experience the same when upgrading to 0.6.0 had to revert to 0.5.2 to get my zwave back up.

[gcorgnet-vista]

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

[t3miLo]

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

[Madelaide]

same, awesome...

[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... [10:40:07] INFO: Auth database exists [cont-init.d] auth.sh: exited 0. [cont-init.d] mqtt.sh: executing... [10:40:10] 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... [10:40:10] 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.

[GeertvanHorrik]

One of the things I am thinking about is to create my own add-on "repository". Then you can choose what versions are actually available and install the "latest" stable from there. Will let you know how it goes.

[sanderlv]

One of the things I am thinking about is to create my own add-on "repository". Then you can choose what versions are actually available and install the "latest" stable from there. Will let you know how it goes.

Yes! The dock "drop-down-select-whatversion-you-want-or-latest" a-like :-)

[GeertvanHorrik]

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

1. Copy the current config and store it so you have easy access to it
2. Remove the old integration
3. Add this custom addon repository: https://github.com/GeertvanHorrik/hassio-addons-repo
4. Install openzwave
5. Paste your config
6. 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).

[Ascariota]

Same error, I restore my snapshot with old version.

[foxy82]

Is it possible to revert to 0.5.2 using a Docker command? Or is it possible to upgrade from 0.4.X to 0.5.2 as my snapshot has a really old version.

[neildownie]

Same problem here. No Z-Wave :-(

[bruxy70]

Me Too

[hmorkemo]

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

[hmorkemo]

The workaround mentioned above installs and starts, but now all my z-wave device names are gone, and the HA integration seems to be messy. So I'm still waiting for the official fix...

[GeertvanHorrik]

The workaround mentioned above installs and starts, but now all my z-wave device names are gone, and the HA integration seems to be messy. So I'm still waiting for the official fix...

Only in the admin tool. The mappings in home assistant are done via node ids so everything should keep working?

[hmorkemo]

The workaround mentioned above installs and starts, but now all my z-wave device names are gone, and the HA integration seems to be messy. So I'm still waiting for the official fix...

Only in the admin tool. The mappings in home assistant are done via node ids so everything should keep working?

Works now! After I restarted HA it's ok. Thanks!

[Quart666]

Same problem

[MartinHjelmare]

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.

[ThePirat91]

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

1583

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

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!

[lukewaite]

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.

[MartinHjelmare]

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

[ThePirat91]

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!

[ngergely]

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

[hmorkemo]

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!

[Veldkornet]

Were there problems in 0.5.3 that it was rolled back to 0.5.2?

[MartinHjelmare]

• 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.

[moto3001]

Running HassOS VM on a NUC 64-bit w/ a Zwave USB stick. OZW 0.5.3 and 0.5.4 worked fine but 0.6.0 broke it. Reverted back to 0.5.2 via snapshot, since that was the latest one backed up.

[neildownie]

So this helps.....

[chaddy1701]

Processed the 'update available' and reinstalled 0.5.2 but the add on wouldn't restart. Had to restore a snap shot.

[beestarbush]

The downgrade to 0.5.2 did work, but are there plans on fixing this issue and updating the OpenZWave version to 0.6.0?

[MartinHjelmare]

Yes, but we have no ETA.