Domoticz

AllesVanZelf wrote: ↑Friday 13 August 2021 21:48 Start ZwaveJS2MQTT via systemd

hestia wrote: ↑Tuesday 24 August 2021 21:08

AllesVanZelf wrote: ↑Friday 13 August 2021 21:48 Start ZwaveJS2MQTT via systemd

Hi AllesVanZelf,
could you please share how to do it, I'm not so good with linux
Thanks!

heggink wrote: ↑Tuesday 24 August 2021 21:45 btw: you can see the node number from the devices tab in domoticz. It's the number after the first / in the device id or name. so /76/xxx is node 76. You can see that in OZW as well as in zwavejs2mqtt.

heggink wrote: ↑Tuesday 24 August 2021 20:15 That's a good idea. Just added some extra explanations here and there. Should be pretty complete now. Have a read and let me know if it's clear and concise enough.

H

heggink wrote: ↑Tuesday 24 August 2021 23:58

Code: Select all

docker run -d --name zwavejs2mqtt --restart unless-stopped -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0 --mount source=zwavejs2mqtt,target=/usr/src/app/store zwavejs/zwavejs2mqtt:latest

-d means it's detached (daemon)
--restart unless-stopped means it's restarted if it stops (unless you stop it)
--name means that it's given a name so you can start/stop/delete it by name

Mind you: since I don't have --rm, I need to delete the container if I want to upgrade it. Since it is normally not deleted, I can stop it (docker stop zwavejs2mqtt), start it (docker start zwavejs2mqtt), delete it (docker rm zwavejs2mqtt) and then rebuild it with the same command as above (which will then download the latest image and start it again under the zwavejs2mqtt name).

You can also see it's state with:

Code: Select all

docker ps

docker run -d --name zwavejs2mqtt --restart unless-stopped -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0 --mount source=zwavejs2mqtt,target=/usr/src/app/store zwavejs/zwavejs2mqtt:latest

docker ps
docker stop zwavejs2mqtt
docker start zwavejs2mqtt
docker logs zwavejs2mqtt
docker restart zwavejs2mqtt

docker stop zwavejs2mqtt
docker rm zwavejs2mqtt

hestia wrote:

heggink wrote: ↑Tuesday 24 August 2021 23:58

Code: Select all

docker run -d --name zwavejs2mqtt --restart unless-stopped -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0 --mount source=zwavejs2mqtt,target=/usr/src/app/store zwavejs/zwavejs2mqtt:latest

-d means it's detached (daemon)
--restart unless-stopped means it's restarted if it stops (unless you stop it)
--name means that it's given a name so you can start/stop/delete it by name

Mind you: since I don't have --rm, I need to delete the container if I want to upgrade it. Since it is normally not deleted, I can stop it (docker stop zwavejs2mqtt), start it (docker start zwavejs2mqtt), delete it (docker rm zwavejs2mqtt) and then rebuild it with the same command as above (which will then download the latest image and start it again under the zwavejs2mqtt name).

You can also see it's state with:

Code: Select all

docker ps

Thanks, it works with this.
To summarize what I've tested
1/ Installation

Code: Select all

docker run -d --name zwavejs2mqtt --restart unless-stopped -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0 --mount source=zwavejs2mqtt,target=/usr/src/app/store zwavejs/zwavejs2mqtt:latest

2/ operations

Code: Select all

docker ps
docker stop zwavejs2mqtt
docker start zwavejs2mqtt
docker logs zwavejs2mqtt
docker restart zwavejs2mqtt

3/ upgrade

docker stop zwavejs2mqtt
docker rm zwavejs2mqtt

+ step 1: installation
(probably a better way with the update command)

hestia wrote:Other questions:
In which way does it work? I've set a name for a node in the control panel (ZWave To MQTT) and it didn't arrive in domoticz. Do I have to do somethings?

Where are located the ZWave To MQTT data (and other stuff). To backup them...

waltervl wrote: ↑Wednesday 25 August 2021 0:30

heggink wrote: ↑Tuesday 24 August 2021 20:15 That's a good idea. Just added some extra explanations here and there. Should be pretty complete now. Have a read and let me know if it's clear and concise enough.

H

I miss a section about migrating from OZW to ZwaveJS.
What is the impact for those users? New IDX, new Names? Tips and tricks to migrate?
Some are there like issue a zwavejs save command to trigger device recreation in Domoticz. But perhaps there are more.

waltervl wrote: ↑Wednesday 25 August 2021 13:42

waltervl wrote: ↑Wednesday 25 August 2021 0:30

heggink wrote: ↑Tuesday 24 August 2021 20:15 That's a good idea. Just added some extra explanations here and there. Should be pretty complete now. Have a read and let me know if it's clear and concise enough.

H

I miss a section about migrating from OZW to ZwaveJS.
What is the impact for those users? New IDX, new Names? Tips and tricks to migrate?
Some are there like issue a zwavejs save command to trigger device recreation in Domoticz. But perhaps there are more.

Perhaps something like: https://community.home-assistant.io/t/s ... qtt/276721

AllesVanZelf wrote: ↑Wednesday 25 August 2021 14:02 I was using a direct systemd service file to start zwavejs2mqtt via docker.
But this was not working well for me.
I found out that docker can start containers at boot if you enable this.

This can be done by:

Code: Select all

sudo systemctl enable docker

I created a ZwaveJS2MQTT folder in Pi's Home directory:

Code: Select all

mkdir /home/pi/zwavejs2mqtt

And start the zwavejs2mqtt container as:

Code: Select all

docker run -dit --restart unless-stopped --name zwave-js -p 8091:8091 -p 3000:3000 --device=/dev/ttyACM0 -v /home/pi/zwavejs2mqtt:/usr/src/app/store zwavejs/zwavejs2mqtt:latest

Till now this is working great and survives a reboot.

waltervl wrote: ↑Wednesday 25 August 2021 14:26 And the 3000 port is conflicting with users running Grafana and or for example NefitEasy server, so either move ZwaveJS or Grafana to another port.