I've just updated the HA core and now receive this message
Newer version of Z-Wave Server needed
Error · Reported by Z-Wave
The version of Z-Wave Server you are currently running is too old for this version of Home Assistant. Please update the Z-Wave Server to the latest version to fix this issue.
My main ZWAVE is fine its the remote ZWAVE on a raspberry pi. That ZWAVE JS UI Is running fine and says there are no updates when I click check - but
zwave-js-ui: 11.8.2
zwave-js: 15.17.1
home id: 3304353291
home hex: 0xc4f46e0b
Hello,
I have the same issue. My ZWaveJsUI is running in a VM, and the Snap package on the latest/edge channel only offers version 11.14.2. Do you know which version is now required or enforced by Home Assistant?
It has an check for update button on the web interface, which is not finding an update. I'd think that should work regardless of base of configuration.
But it's in raspbarian using a snap distribution
I don't have easy access to the base OS at night as its in a seperate building,
That'll teach me not to upgrade Home Assistant in the evening
For the moment I have restored a backup of the HAOS and it works again
I'm not sdure how to confirm this is fixed before I do the update again
For my HAOS - I'm now on
Installed version 2026.5.4
Latest version 2026.6.0
It appears this is not a well supported method of installation. I think the snap repository is not part of the supported deployment of new versions
However in my searches I really could not find another way.
I think the zwavejs is recommended to be on docker
I'm not ready to try that yet.
I'm even unsure if my raspberry pi could handle it as logged on directly is really slow
I can't find any recent recommendations about how to establish a zwave network in a second location remote from the home assistant install .
Id love to know if you've found anything better
Snap package seems pretty old indeed. Can anyone explain why this method is preferred above docker or addon? (i'm running as docker image and very happy with that choice)
@checking12 Could you explain how you handle Docker updates? I’ve just migrated from Snap to Docker a few hours ago, and I want to be prepared so I don’t run into the same issue on a different technology
Docker itself or the images ?
docker itself i barely touch. I have portainer setup on it and it shows me when images have updates. When they have, it's a recreate with image pull and all handles itself. As i have more runinng in docker, i got myself DIUN setup and pushing notifications to HA for autoamted task list so i know something is pending.
alias: portainer image updater
description: Verwerkt pushes van DIUN naar notificaties en taken
triggers:
- trigger: webhook
allowed_methods:
- POST
- GET
local_only: true
webhook_id: diun_update_xxxxxxxxxxx
conditions: []
actions:
- action: notify.mobile_app_xxxxxxxxxxx
metadata: {}
data:
message: Update voor image '{{ trigger.json.image }}' in portainer beschikbaar
- action: todo.add_item
target:
entity_id: todo.portainer_images_updates
data:
item: Update {{ trigger.json.image }}
mode: single
The search results says Docker or Standalone - Standalone seems to be a problem from what I can gather -
None of the rest of the results address the ZWAVE JS UI install - which is where the problem is - None of those posts I found in that search mention than its (I think) Docker that should be used - the only install guide I found uses the SNAP update - which seems to be a problem
How it works: Set up a lightweight computer (like a Raspberry Pi or an old thin client) at the remote location with a Z-Wave USB stick plugged into it. Install Z-Wave JS UI on it using Docker or a standalone install
Not entirely clear, but I assume it's suggesting running on a dedicated or standalone machine not running anything else -- I do that on a Rpi4 and Rpi3 -- vs. on a machine running perhaps other containsers. I also have ZUI running on a linux machine that has other things running on it. Reguardless, it's all just running zui in docker somewhere.
That first link is to when I set up ZUI running as a second z-wave Add-on on HAOS by creating a local addon config. I haven't used that setup in a while.
Ah.. i see. I never considered the standalone route as addons are docker images anyway so i considere running the docker version seperately was best fit without looking further
Installing docker and setting up zwave is pretty doable with compose files or add portainer to have a UI for yoursefl (like i did, i'm lazy as .... For cli installs, so only did docker and the rest is portainer)
No "docker containers or standalone" implies standalone is not Docker in normal use. The first search result for install zwave js ui standalone or raspberry pi is the now non-working snap method
