[SOLVED] BE VERY CAREFUL when updating zwavejs2mqtt !!!!

[Sarcas]

I updated my zwavejs2mqtt version 7.0.1 to the latest version 8.0.1. Big surprise, it is no longer called zwavejs2mqtt but zwave-js-ui. I did not know this.

Zwavejs2mqtt used it own name as part of the unique identifier. Zwave-js-ui does this too. So EVERY DEVICE is rediscovered by Domoticz, because it has a new unique ID.

I now have a bit less than 500 devices to somehow clean up. I am pretty annoyed.

So, be careful.

S.

Edit:
I just learned this is going to be fixed asap!

https://github.com/zwave-js/zwave-js-ui/discussions/2697

[FireWizard]

Hi @Sarcas,

It is pitty that you missed a thread a few days ago..
See: viewtopic.php?p=292835#p292835

B.t.w. version 8.0.2 has been published.

Regards

[Sarcas]

Yep, I missed that. And he fixed it indeed very quickly. I'm waiting for the docker image to get to 8.0.2 and then I'll update again.

[thaui]

I had the same problem. Where can we see if the new docker update is launched?

[Sarcas]

It was released about an hour later. The problem is solved, I only had to delete all the new devices.

https://github.com/zwave-js/zwave-js-ui ... elease.yml

[thaui]

Thx for the reply. I tried to install the 8.0.2 but maybe I did a mistake. I am running Domoticz on an Raspberry Pi. So I have removed all zwavejs2mqtt stuff (docker container and directories) and installed the new version. This was not the correct way I guess. What did you do to migrate to 8.0.2 keeping the devices in Domoticz? I heard the Docker container for Raspberry Pi is not ready!?

[mgugu]

You have to KEEP all data in your docker-compose folder. The only thing to adapt is the yml file (https://github.com/zwave-js/zwave-js-ui ... ompose.yml).

[Sarcas]

Depends on how you installed it, I believe. I don’t know much about Docker, I found out that this works for me, if I change

Code: Select all

sudo docker-compose up -d

to

Code: Select all

sudo docker compose up -d

but don’t ask me why

[eSbek]

I install and run my zwave-js-us this way (Raspberry Pi):

Code: Select all

sudo mkdir /opt/zwavejsui
sudo mkdir /opt/zwavejsui/store	
docker run -d --name zwavejsui --restart unless-stopped -v /opt/zwavejsui/store:/usr/src/app/store -p 8091:8091 -p 3000:3000 --device=/dev/serial/by-id/usb-0658_0200-if00 zwavejs/zwave-js-ui:latest

This way I have my config in the folder created in the steps above even if I remove the container.
I also renamed the zwave-js-ui to zwavejsui only to have less chars to type , you can keep the original name by:

Code: Select all

docker run -d --name zwave-js-ui --restart unless-stopped -v /opt/zwavejsui/store:/usr/src/app/store -p 8091:8091 -p 3000:3000 --device=/dev/serial/by-id/usb-0658_0200-if00 zwavejs/zwave-js-ui:latest

to update the docker I found I need to delete local image, finally got this steps (I delete the local image after the installation at the end for future updates as the update checks the local repo first and will not download new version if it finds anything locally, even old version):

Code: Select all

docker stop zwavejsui
docker rm /zwavejsui
docker run -d --name zwavejsui --restart unless-stopped -v /opt/zwavejsui/store:/usr/src/app/store -p 8091:8091 -p 3000:3000 --device=/dev/serial/by-id/usb-0658_0200-if00 zwavejs/zwave-js-ui:latest
sudo docker image rm -f zwavejs/zwave-js-ui
docker start zwavejsui

Some useful commands I collected (sorry just quick copy and paste):
# to restart the docker
docker restart zwavejsui

# to stop the docker
docker stop zwavejsui

# to start the docker
docker start zwavejsui


# list containers/images
docker container ls
docker image ls

# remove container
sudo docker container rm CONTAINER_NAME
# with force if not possible the above way
sudo docker container rm -f CONTAINER_NAME

# remove container image
sudo docker image rm IMAGE_NAME
# with force if not possible the above way
sudo docker image rm -f IMAGE_NAME