With the zwave js 1.0.0 notification zwave js ui, is there no longer a separate zwave js upgrade? Overwhelmed by all the changes. I just started a month ago with HA Green. I want a basic zwave solution for lights, plugs and thermostats. I don’t want anything to break.
1 Like
My upgrade to this version went thought without a hitch. I did a full manual backup before upgrading, just in case.
1 Like
Apps (previously add-ons) are always separate upgrades from HA Core. Z-Wave itself is still provided by the app, and integrated with the Z-Wave integration, this isn’t changing.
This will be the first time that ZwaveJS App/AddOn includes ZwaveJS-UI with it.
Beforehand one had to use either the “official” ZWaveJS App/AddOn (no ZWaveJS-UI) or the “community” ZwaveJS-UI App/AddOn which included ZWaveJS.
Did you move from ZWaveJS-UI App/AddOn to ZwaveJS App/AddOn?
I did not have ZWave-JS-UI installed prior to this 1.0.0 release.
Hi all.
Automatic update for me, from zwave js add-on 0.29 to 1.0 yesterday. I realized nothing works anymore asking aexa to open all the covers and it did nothing.
I found zwave-js ui integrated with this latest update, showing every fibaro fgr223 I got, but no one works.
I revert back to 0.29, waiting to find what is happening with this 1.0 update.
I was not using the UI version. I was trying to get everything running on my new Home Assistant Green with the ZWA-2. Everything was stock.
What does this mean to the operation of HA when zwave js and zwave js ui are both running at the same time?
“Z-Wave JS” is a Javascript (Typescript) library, it doesn’t run on its own. An application uses the library.
“Z-Wave JS UI” is an application that uses the library.
The confusing part is the name of the core application is also “Z-Wave JS”. Call it “Z-Wave JS Application” instead. With the upgrade to 1.0.0 it is now “Z-Wave JS UI”, while before it was a small wrapper around the “Z-Wave JS” library.
Z-Wave JS this, Z-Wave JS that…
1 Like
When I upgrade, it is zwave js ui that will be running instead of zwave js app?
Yes, but the HAOS App is still called “Z-Wave JS”, and it’s just a (mostly) transparent migration. The internals of the application have changed. You won’t notice anything different. You get a new optional Web UI.
There is no need to be. If your system was working before 1.0.0, nothing should break after upgrading to 1.0.0.
You gain the new feature of UI.
Now, to double check, let’s go to Settings → Apps, and check what you have installed exactly…
You should have got only one of those, but which one?
1 Like
If the above posts didn’t make things clear, one should think of ZWaveJS as a server, and ZWaveJS-UI as client that uses ZWaveJS. HA is also a client that only talks to ZWaveJS server.
- Originally, the ZWaveJS AddOn only came with ZWaveJS server (no ZWaveJS-UI).
- The ZWaveJS-UI AddOn came with both ZWaveJS server and ZWaveJS-UI client.
- HA would would only talk to one of these two AddOn’s ZWaveJS server (not both).
So now, the ZWaveJS AddOn comes with both ZWaveJS server and ZWaveJS-UI client.
If you use the original ZWaveJS AddOn, then nothing really needs to change when upgrading to the new ZwaveJS AddOn, you just get the benefit of having ZWaveJS-UI client come along with it.
If you are like me and use the community ZWaveJS-UI AddOn, then we need to figure out if/when to move over to the official new ZWaveJS AddOn/App.
4 Likes
I’ve now crossed off the #1 item on my own, personal HA wish list.
Just curious. Anyone know how this decision was made and what was preventing it before?
It’s going to make helping people so much easier and so much less confusing to users, too.
(And maybe if we get people to use SmartStart and populate device names and areas in ZUI, there will be even less confusion as entities will keep their same ids when re-including devices.)
Me too! And I’ve had issues with past upgrades
You too, it went well?
Sorry, I thought I had replied to the parent post - yes it went well.
AlCalzone is working on a migration process and will undoubtedly publish it broadly eventually. Living on the edge (with backups), I went ahead and gave the current version a shot, so this is as much feedback to him as for everyone else.
Here is a link to his comment from the PR:
Which ultimately gets you to his Google Doc with instructions:
I used the “New and Improved version” and everything went perfectly.
Thanks AlCalzone!