Zwave failed to connect post update

Configuration Z-Wave
1

I recently updated to zwave_js version 0.8.0

right away Im receiving error messgage “Failed setup, will retry: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed (‘172.30.33.1’, 3000)]”

I cannot reload or restart the addon.

Logs from Zwave JS Addon
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
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-supervise zwave_js: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise zwave_js: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise zwave_js: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
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
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-supervise zwave_js: warning: unable to spawn ./run (waiting 60 seconds): Exec format error

image

image
image775×633 41.6 KB

image
image1032×207 20.9 KB

If there is a fix for this already, please let me know.
Or if i can provide any further information to help diagnose, happy to do so.

2

Typically this error results from trying to run a program with the wrong CPU architecture, e.g. your x86_64 VM is trying to run an ARM docker image. I’m not really sure how that could be possible in the HAOS environment. What’s the output of ha info?

~ # ha info
arch: amd64
channel: stable
docker: 27.2.0
features:
- reboot
- shutdown
- services
- network
- hostname
- timedate
- os_agent
- haos
- resolved
- journal
- disk
- mount
hassos: "13.2"
homeassistant: 2024.10.2
hostname: homeassistant
logging: info
machine: qemux86-64
operating_system: Home Assistant OS 13.2
state: running
supervisor: 2024.10.2
supported: true
supported_arch:
- amd64
- i386
timezone: America/Los_Angeles

Additionally, if you have the Advanced SSH & Web Terminal add-on installed with protection mode disabled, you can inspect the actual container image being used.

~ # docker inspect addon_core_zwave_js -f json | jq '.[] | .Config.Image, .Config.Labels'
"homeassistant/amd64-addon-zwave_js:0.8.0"
{
  "io.hass.arch": "amd64",
  "io.hass.base.arch": "amd64",
  "io.hass.base.image": "alpine:3.18",
  "io.hass.base.name": "alpine",
  "io.hass.base.version": "2024.08.0",
  "io.hass.description": "Control a Z-Wave network with Home Assistant Z-Wave JS",
  "io.hass.name": "Z-Wave JS",
  "io.hass.type": "addon",
  "io.hass.url": "https://github.com/home-assistant/addons/tree/master/zwave_js",
  "io.hass.version": "0.8.0",
  "org.opencontainers.image.created": "2024-10-14 09:49:58+00:00",
  "org.opencontainers.image.source": "https://github.com/home-assistant/docker-base",
  "org.opencontainers.image.version": "0.8.0",
  "supervisor_managed": ""
}
3

Actually, easier than all of that, you can go into the Supervisor logs and see which image it is starting.

2024-10-17 15:45:23.559 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-zwave_js with version 0.8.0

System → Settings → Logs → select Supervisor in top right pull-down menu.

4

output from ha info
image

5

supervisor log

2024-10-17 12:38:32.036 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-zwave_js with version 0.8.0
6

That all looks good to me then, the container image should be the correct architecture.

Unfortunately I don’t have any other suggestions except for restoring a previous version from a backup, and then trying again.

7

Fair enough, I was updating everything because I’m getting ready to move it to a new host. Moving away from virtualBox on Windows to QEMU on Linux.

Maybe we’ll see if the move can jostle something loose, or I might be stuck having to nuke and reebuild it