Image homeassistant/amd64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js

[louisostrowski]

The problem

Failed setup will retry error with none in error description

What version of Home Assistant Core has the issue?

Core-2023-10-1

What was the last working version of Home Assistant Core?

2023-09-3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zwave JS

Link to integration documentation on our website

No response

Diagnostics information

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[AndrewPaglusch]

I'm experiencing the same issue. I see this in the logs:

2023-10-06 21:01:42.361 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/core_zwave_js/start - Image homeassistant/aarch64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js

After a downgrade to v0.1.94 of the add-on, things seem to be working again for me.

[michaelsteigman]

just happened to me as well. what is the process for downgrading, @AndrewPaglusch ?

[AndrewPaglusch]

@michaelsteigman My Home Assistant is configured to automatically take a backup before updating an addon (enabled by default, I believe), so I simply reverted the addon from that backup.

[operator207]

This hit me too. Still on 2023-9-3 as I don't update for a few days to try to keep stuff like this from happening. It auto updated about 5 hours ago, and stopped working afterwards. SO glad backups exist! I set mine to not auto update after it came back up on 1.94. I'll wait until something after 1.96 comes out. I am glad 1.96 fixed other's issues in home-assistant/addons#3234 but it sucks that it broke ours.

[michaelsteigman]

@michaelsteigman My Home Assistant is configured to automatically take a backup before updating an addon (enabled by default, I believe), so I simply reverted the addon from that backup.

thanks! for anyone unfamiliar with this process, you need to go through settings -> system -> backups then click on the backup to get the restore option.

i can't seem to find a way to disable auto-update, though, even with advanced mode enabled. if any one has any tips, i'd appreciate it.

[SpartyNumber1]

I had the same issue this evening after auto update to 1.96. Did partial restore from addon backup to 1.94 and now working as expected. Disabled auto update until issue is resolved.

[SpartyNumber1]

@michaelsteigman My Home Assistant is configured to automatically take a backup before updating an addon (enabled by default, I believe), so I simply reverted the addon from that backup.

thanks! for anyone unfamiliar with this process, you need to go through settings -> system -> backups then click on the backup to get the restore option.

i can't seem to find a way to disable auto-update, though, even with advanced mode enabled. if any one has any tips, i'd appreciate it.

Settings -> Add-Ons -> Z-Wave JS then toggle Auto update switch off

[teji24]

same here - auto updated to 1.96 - crashed...
reverted to 1.94 - work again - auto-update set to OFF.

Home Assistant 2023.8.4
Supervisor 2023.10.0
Operating System 10.5
Frontend 20230802.1 - latest

[gastonbe]

Can confirm this affects my installation also.
As per info here, reverted to 1.94 and it works again.

Home Assistant 2023.10.1
Supervisor 2023.10.0
Operating System 10.5
Frontend-versie: 20231005.0 - latest

[monsdar]

Looks like the Docker image for ZWave JS isn't pulled automatically. I was able to manually pull the image and then successfully start the addon. Here's (from the top of my head) what I did:

• Switch your HA to advanced mode
• Install the Addon Advanced SSH & Web Terminal, disable protection mode, set SSH key (or password)
• Within the terminal call docker pull homeassistant/TODO-addon-zwave_js:0.1.96 which will download the right version of the Docker image onto your HA server (See below how you can figure out the right image for your system)
• Update the ZWave JS addon to 0.1.96
• Restart HA (probably not needed, but shouldn't hurt anyways...)

Right now the addon is working for me as it should in v0.1.96.

UPDATE: Please not NOT blindly copy/paste the docker image version from here. Your hardware could be different and so your image needs to fit that.

[monsdar]

Here you can check which images are available, for future reference: https://registry.hub.docker.com/r/homeassistant/aarch64-addon-zwave_js/tags

[hendrix04]

Wow, definitely making sure auto update is off on this one. This has been a huge inconvenience.

[hendrix04]

• Within the terminal call docker pull homeassistant/aarch64-addon-zwave_js:0.1.96 which will download the right version of the Docker image onto your HA server

Note that if you are not on a raspberry pi, the command is...

docker pull homeassistant/amd64-addon-zwave_js:0.1.96

[FireStarter75]

Same here; Failed to start add-on
Image homeassistant/amd64-addon-zwave_js:0.1.96 does not exist for addon_core_zwave_js after latest update

[akfincode]

Reverting back to addon_core_zwave_js_0.1.94 from the System > Backups fixes the issue. 0.1.96 update does not work.

[milad-soufastai]

Pulling the correct image via Terminal does work as a fix and potentially opens up an enhancement request.. Could Advanced Settings for add-ons be able to manually select and/or change the version of the addons that they use? Definitely could be more sustainable then having to SSH into the machine to pull an image

For those of you going that route:

1. Try to start zwavejs and note which image is missing (Copy and paste the full name: Ex. homeassistant/amd64-addon-zwave_js:0.1.96). NOTE This step is important as you don't want to blanket copy and paste from responses here since each machine can be different.
2. Enable Advanced Settings and Install Terminal Addon onto your HASS instance
3. Open the terminal Addon and pull the correct image with the command: docker pull ***string you copied above***
4. Go to ZwaveJS and start the addon and make sure it runs
5. To disable SSH, stop/disable/uninstall the terminal addon

[davefrooney]

Same issue. Rolled back to previous release and back working again. Using a Aeotec gen5 stick

[boxer747]

Same issue here... :(

[monsdar]

@boxer747, @davefrooney, @akfincode and all the others that might come: Please do NOT just post comments like "Same issue here...". This does NOT provide any useful information in addition to what is already known about the issue. For anyone coming here in the future it just makes life harder because they need to sift through a lot of these responses to find the actual useful information.

[hendrix04]

Do we have an RCA on this issue?

From someone who isn't familiar with how HA handles these docker add-ons, it seems like the add-on upgraded its docker dependency, but there is no process in place for HA to pull that new dependency.

Is this an issue of a lack "package lock" / package management within HA?

Is there any process in place for this?

Did the developer not follow some standard process that would have avoided this?

What do we need to do in the future to have appropriate checks the prevent this issue from happening again?

[iloveicedgreentea]

I had an issue with both the js add-on and the integration after upgrading to 10.1, and random failures with some devices like a zen17. The add-on refused to start (no error) after I restarted it. It loaded the container just fine it just did not update the start status. It also added a duplicate integration with a ton of disabled entities.

Restoring from the 9.x backup fixed my issues.

I did not have any error regarding the docker image and it was outputting logs without being marked as started, so it seemed to be starting okay. My devices were just unavailable at that time.

[agners]

Can someone who experience this issue please attach the full Supervisor logs from Settings > System > Logs, then choose Supervisor on the top right.

[FirewizzNL]

Can someone who experience this issue please attach the full Supervisor logs from Settings > System > Logs, then choose Supervisor on the top right.

supervisor_2023-10-09T07-48-52.043Z.log

[agners]

@FirewizzNL thank you very much 🙏 . Unfortunately the log is a bit too short to show the crucial problems (right after the udpate).

Can you get the logs through a terminal with the following command?

ha host logs --identifier hassio_supervisor --lines 1000

[FirewizzNL]

@agners That is still of no use, nothing else then that there.
But I updated more than a week ago, just stopped working yesterday, atleast then I noticed

[FirewizzNL]

@agners Solved it with solution above to pull the missing docker container.
If needed I can post detailed manual to do this.

[FirewizzNL]

For people who need a detailed description of a fix:

1. Install "Advanced SSH & Web Terminal" through "Add-ons" menu
2. When installed open the addon and disable the switch for "protection mode"
3. Find missing docker file by going to add-on -> Z-Wave JS and press start, it should notify you the missing file
4. Start the advanced terminal add-ons -> advanced... and click "open web-UI"
5. run "docker pull YOUR_MISSING_FILE" In my case 'homeassistant/amd64-addon-zwave_js:0.1.96'
6. restart add-on Z-wave and zwave service or reboot device.
7. Enjoy zwave again

[agners]

@agners That is still of no use, nothing else then that there. But I updated more than a week ago, just stopped working yesterday, atleast then I noticed

You can bump the line numbers even higher, if that helps. But yeah, if its more than a week, you might not have a lot of log buffer to get back to when the update happened 😢

[FirewizzNL]

@agners I think the fix is easy enough to do in this case. The problem seems to be the case that the docker container was not correctly retrieved when updated.

[agners]

The problem seems to be the case that the docker container was not correctly retrieved when updated.

How do you know?

Typically, connection errors like connection reset get properly handled. The update fails in this cases, and deleting the old images doesn't continue:

It might be that a particular type of download error doesn't get handled correclty, but so far I am not able to reproduce the problem here 😢 To better understand what is happening the logs from Supervisor right when this happened would be really helpful.

[FirewizzNL]

I have nothing that helps I am afraid in my logs.
I checked my logs and excluded all the dns checks and not exist lines and this remains:

[agners]

Hm, I see. Thanks for checking!

[cuppieinc]

Just FYI. Having the same issue I reverted back to version 0.1.94 via a backup restore. Today I wanted to follow the manual steps to do the correct upgrade to 0.1.96 as described by [FirewizzNL] but after upgrading z-wave.js from within the add-on section it just updated and started correct. Seems the upgrade is working now

[KroniK907]

I had this same issue. I reverted to version 0.1.93 (which was the version available to me in my backups) and then manually updated the Z-Wave JS addon back to 0.1.96. This seems to have installed 0.1.96 successfully as it is now running without error.

It seems the issue was isolated to updating via the automatic update procedure.

EDIT To add some detail regarding automatic updates and my experience of this bug:
I had automatic updates enabled, and it appears that the automatic update process was triggered, updating the addon from 0.1.93 to 0.1.96 some time around 1:00 am UTC on October 7th (my best guess based on device history graphs). We noticed the issue around 1:30 am UTC.

[agners]

@KroniK907 hm, interesting observation.

@cuppieinc @FirewizzNL and others, do you have automatic update enabled?

[cuppieinc]

Yes, I have automatic updates enabled, my initial update also broke by the automatic update at October 7th

[cuppieinc]

interesting. After the manual upgrade to 0.1.96 I rebooted my PI, just to make sure all was OK after a reboot, now the z-wave add-on pops up with another update to 0.1.97. Just did a manual upgrade again, all OK, z-wave is up and running

[KroniK907]

I went digging and was able to get the following from the supervisor logs:
hassio_supervisor log with zwave-js error.txt

Hopefully this helps confirm if #4619 was the culprit. Sorry I didn't go digging for this earlier.

I included several cycles of normal operation before and after it starts showing the error to hopefully provide some context.

EDIT: after taking a more detailed look at the log, it does seem like my system was trying to update from 0.1.94 to 0.1.95 and then upon restarting the zwave-js service, proceeds to complain that it cant find version 0.1.96. That seems to at least look similar to what is described by the #4619 pr.