Easiest way to migrate Openzwave to ZWave-JS-UI

[lost]

Yup, same reason I went for snap. Docker seems to be quite heavy on config and resources on a pi.

Did not tried the jump from OZW myself but... why the hell using any containerization stuff? Direct install of zwavejs and mqtt server does not work at all? Understand this may help cope with dependancies resulting from what really looks like a quick&dirty pile of SW compared to OZW but is this really mandatory?
If so, not sure to do the move towards such accidentaly working stuff soon.

[sincze]

The dockers work just fine (On my pi4).

[MikeyMan]

Mqtt is installed on my nas. In docker. Hate it madly, but it works.

I haven't seen any guides apart from snap or docker.

[user4563]

Has anyone tried on Windows yet? There appears to be binaries for both Mosquitto and zwave-js-ui for Windows, so no Docker needed:

https://github.com/zwave-js/zwave-js-ui/releases
https://mosquitto.org/download/

[thomasbaetge]

Same behavior after a reboot, and why Snap because the tutorial seems easier to me, but i'll try with docker. Do you have a step by step installation guide of ZWave-JS-UI that include the docker installation and setup ? I found a lot of thing but nothing explaining the complete process step by step like the tutorial i link in my first post did for snap method

That is really simple:
Create a directory for it (somewhere in home), find a docker compose file for zwJS, modify that to your needs (persistant data storage location and serial ID), fire it up with 'docker compose up -d' and you are done. Literally a matter of minutes.

[d3smo]

That is really simple:

I'm sure it is when it's done, but for people like me not expert on Debian it's always a challenge to put lines in the terminal, even if i love to learn and progress on that, and hopefully this kind of forum from the old internet sill exist.

So let me summarize what i understand and putting step by step what i need to do, if you can just confirm. I think I'll take the opportunity when i will have the full procedure to share it for other newbies like me !

Install Docker

Code: Select all

curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh

Add pi user to docker group

Code: Select all

sudo usermod -aG docker pi

Install Docker Compose

Code: Select all

sudo apt install docker-compose -y	

To run Z-Wave JS UI as a service by Creating a docker directory at home and create docker-compose.yml found here: in it

To find your Z-Wave USB stick reference

Code: Select all

ls -l /dev/serial/by-id

Replace/dev/serial/by-id/insert_stick_reference_here with the serial device for your Z-Wave stick.

Uncomment and replace TZ=America/New_York by your timezone (see https://en.wikipedia.org/wiki/List_of_t ... time_zones)

To run Z-Wave JS UI

Code: Select all

docker compose up -d

Browse Z-Wave JS UI to http://192.168.XX.XX:8091 and setup

And that's it ? It gonna be running on each startup ? Now i just need to install mosquitto and MQTT Auto Discover Client gateway in Domoticz ?

[thomasbaetge]

Yes, that's kind of it.

You may want to change the storage location (or use the one that's given).
I have:

Code: Select all

   volumes:
      - /home/thomas/docker/zwjs/store:/usr/src/app/store

first portion is my local storage in the home dir, second is the mount point in the docker image (don't change that).
But that is really just a personal preference. I'm using it, because my home dir is being automatically backuped every night, so I like to keep everything in one place.
You need to start this only once, due to the 'always' restart policy in the docker compose file.

From there you should be good to go.

[d3smo]

I finally migrate i think i gonna publish the step by step migration method, because honestly for linux newbies it's a little bit hard to do.

[sincze]

I'm pretty annoyed while moving from a perfect OpenZwave 1.6. to this Zwave-JS-UI.
I now have:

zwave0706.png (37.68 KiB) Viewed 4070 times

- Not all devices are now KNOWN anymore (Fibaro, NEO)
- Not all devices have all their capabilities (some even don't switch on/off but do report their W , V kWh just fine)

Any tips on how to fix this? I tried re-interview or heal per node.
Range should not be the issue as it worked with OpenZwave in Domoticz.

Seems I am a bit lost with this new tool.

Should I remove some json files and start over ?

[MikeyMan]

I'm pretty annoyed while moving from a perfect OpenZwave 1.6. to this Zwave-JS-UI.
I now have:
zwave0706.png

- Not all devices are now KNOWN anymore (Fibaro, NEO)
- Not all devices have all their capabilities (some even don't switch on/off but do report their W , V kWh just fine)

Any tips on how to fix this? I tried re-interview or heal per node.
Range should not be the issue as it worked with OpenZwave in Domoticz.

Seems I am a bit lost with this new tool.

Should I remove some json files and start over ?

Wait... Or re-interview the devices...

Yes its annoying. But the result of being dependent on Mqtt messages being received.

[d3smo]

or activate them manually, or press pairing button once to wake up them

[sincze]

or activate them manually, or press pairing button once to wake up them

tnx MikeyMan and d3smo for the fast replys.
Is the wake up also applicable to 220v Powered Devices ??
I knew the trick for battery operated nodes, but these seem the least of my worries.

I also notice some devices do have Home Assistant mentioned and others don't.

zwave-HA.PNG (4.03 KiB) Viewed 4056 times

[d3smo]

As promised i've sum up a step by step tutorial to make the migration from Open ZWave to Z-Wave JS UI using the Docker compose method. Here is a link to the tutorial

Tutorial

[rron]

Thanks,
That’s very helpfull.

[tjabas]

Why is it so hard to get this new wave working, why can't we have the openzwave any more, what is better with the new wave js-ui?
I have spent years setting up open-wave and I have about 130nodes, I really don't want to reconfigure it all again,
And why do we need to istalll all these new plug-ins just to get the new z-wave to work?
With open z-wave there where only one plug in, now it's many more.

[d3smo]

Why is it so hard to get this new wave working, why can't we have the openzwave any more, what is better with the new wave js-ui?
I have spent years setting up open-wave and I have about 130nodes, I really don't want to reconfigure it all again,
And why do we need to istalll all these new plug-ins just to get the new z-wave to work?
With open z-wave there where only one plug in, now it's many more.

Agree with you but Open Zwave is depreciated and development stopped, so we may have it stop working or bugging with next version of domoticz. It is why i decided to migrate has a lot of us, to anticipate any future issue. But i understand that 130 nodes is a lot of work to do, on my side i've only 20 and it was a hard job. Neither the less imagine a future update of domoticz makes your Open Zwave stop working well, you'll have 130 nodes down without having anticipating the new solution.

[HansF]

Now i wonder why should i update Domoticz further if this takes so much effort and time. It works well with OpenZwave. But maybe I'll change my mind when I have nothing to do...

[tjabas]

With all that work that needs to be done I might move on to home assistant, I really like domoticz but hass seems like it's more supported, but I will give the new z wave a quick try at first.

[thomasbaetge]

As promised i've sum up a step by step tutorial to make the migration from Open ZWave to Z-Wave JS UI using the Docker compose method. Here is a link to the tutorial

Tutorial

Thanks a lot for the useful tutorial.
I am still shy of migrating due to the several reported flaws here.
I understand that this step will be inevitable but for now I will stick with OZW because I am replacing devices with zigbee options which - in my mind- are the better (and mostly cheaper) choice.
...so at the end of the day there will be less to migrate...

[sincze]

I'm still waiting for days for the full interview to get completed.
I see these round blue circles with 'NodeInfo' & 'ProtocolInfo' for 220v Operated Nodes.
However these nodes are in Domoticz and bring partial data to the table. For example W, kWh however not the SWITCH (On/Off) function.

To help me out if the Network is not to crowded. I created a Grafana dashboard, maybe I can determine the rootcause with that one..

zwavemessages2.png (220.26 KiB) Viewed 3944 times