Domoticz

Posted: **Monday 15 April 2024 20:41**

I think I've figured it out what is causing some migration problems for people like sincze, Eugene and me! The problem seems to be Z-Wave SDK related and thus a tutorial issue!

What I did to solve my problem was; I moved the "S2 Unauthenticated key" (which was my Domoticz Z-Wave Security Network Key) to "S0 Legacy" and vice versa.

Then I did per node a "re-interview" + "reset security class" checked in ZWave-JS-UI. My powered devices were quickly discovered. Battery powered devices took a bit longer, although I didn't have much time yesterday so I didn't finish the re-interviewing and migration yet. So I have to plan another day for the real migration. So far I fixed an important part of it.

The thing is, if I interpret it correctly, Z-Wave S2 security was introduced in SDK 6.7x, reading:
https://www.silabs.com/developers/z-wav ... s-versions

So I think @d3smo turorial and @gizmocuz wiki need an update:
--< update / add to tutorial & wiki start >--
1. Copy the Z-Wave Security Network Key from the openzwave plugin under Hardware in Domoticz
2a. When you're running a controller/stick with < SDK 6.70 place the obtained Security Network Key (without 0x and ,) in the Z-Wave section from ZWave-JS-UI in "S0 Legacy"
2b. When you're running a controller/stick with >= SDK 6.70 place the obtained Security Network Key (without 0x and ,) in the Z-Wave section from ZWave-JS-UI in "S2 Unauthenticated"

Note1: when updating the S0 and S2 key's in the configuration because of interviewing issues ("unknown manufacturer" and "unknown product"), make sure to re-interview the device(s) and make sure to check "reset security class".

Note2: as the link suggests there are several benefits of upgrading S0 security to S2 security, like better security and less energy consumption.
--< update / add to tutorial & wiki end >--
Does anyone know how to easily upgrade from S0 to S2 without excluding and including?

Maybe gizmocuz can tell:
- a bit more about S0 and S2 handling in the openzwave plugin code regarding the running Z-Wave SDK?
- how to check you're running S0 or S2 security in Domoticz?

This could have helped @sincze and @Eugene, both running Z-Wave SDK 6.5x like I did.

BTW: you cannot leave out the key for S2 authenticated and S2 Access Control in ZWave-JS-UI, as I was wondering earlier.

Posted: **Saturday 27 April 2024 16:56**

Hi,
I've been using Domoticz since 2016 - running on a RPi4.
I was trying to keep OpenZWave in my Domoticz config, 50 hardware devices and I don't feel like wanting to migrate manually to Zwave-JS.
What are the latest best practices?
In the latest 2024.4 update I've lost a lot of zwave features: not sure why but all my scenes with Zwave Fibaro roller devices do not work anymore.
I'm really asking myself if I should move to another plaform such as Home Assistant as I've lost a lot in the past (Android App with its subscription model, zwave...)
Also an alternative could be to resintall all in a container on my Synology server.
What migration path have you taken?

PS: why something that worked so fine became a hell of complexity?

Posted: **Saturday 27 April 2024 18:39**

cr1cr1 wrote: ↑Saturday 27 April 2024 16:56 Hi,
I've been using Domoticz since 2016 - running on a RPi4.
I was trying to keep OpenZWave in my Domoticz config, 50 hardware devices and I don't feel like wanting to migrate manually to Zwave-JS.
What are the latest best practices?
In the latest 2024.4 update I've lost a lot of zwave features: not sure why but all my scenes with Zwave Fibaro roller devices do not work anymore.
I'm really asking myself if I should move to another plaform such as Home Assistant as I've lost a lot in the past (Android App with its subscription model, zwave...)
Also an alternative could be to resintall all in a container on my Synology server.
What migration path have you taken?

PS: why something that worked so fine became a hell of complexity?

Moving to ha Will not solve your issue. Home assistant has the same issue. Openzwave is no longer supported. So if you want to move to ha you also have to migratie to zwave-js-ui

Posted: **Friday 31 May 2024 11:10**

Hallo,
I have up and running on windows the .exe file version zwave-js-ui-v9.12.0-win. Now there is an update to version zwave-js-ui-v9.13.1-win. What is needed to update. Only replace the .exe file with the new one?
Jan

Posted: **Wednesday 19 June 2024 11:06**

Hi,

I have the exact same question about updating zwave-js-ui, does anyone know how to do this?
Thanks!

Bliepie

Posted: **Wednesday 19 June 2024 13:23**

brugje wrote: ↑Friday 31 May 2024 11:10 Hallo,
I have up and running on windows the .exe file version zwave-js-ui-v9.12.0-win. Now there is an update to version zwave-js-ui-v9.13.1-win. What is needed to update. Only replace the .exe file with the new one?
Jan

Best to ask that on the zwave-js-ui forum https://github.com/zwave-js/zwave-js-ui/discussions

Posted: **Wednesday 19 June 2024 13:28**

Bliepie wrote: ↑Wednesday 19 June 2024 11:06 Hi,

I have the exact same question about updating zwave-js-ui, does anyone know how to do this?
Thanks!

Bliepie

On windows or Linux with docker (search with google as there are many ways to do update a docker image)?

Posted: **Tuesday 02 July 2024 1:17**

Dear all,
I have a big problem to detect my ZWave device from the MQTT server on my Domoticz both are in docker in my synology NAS :

Step 1) I install on a docker image zwavejs2mqtt1 correctly and it's look to detect all my zwave device, nice. I try to configure MQTT like that Image1
Step 2) I also install correctly image Domoticz V2023.2 and add hardware "MQTT Auto Discovery Client Gateway with Lan" and setup it like the image 2

But... Domoticz don't discover into hardware "MQTT Auto Discovery Client Gateway with Lan" (setup button) any zwave devices view into zwavejs2mqtt1 image... why ? What I have bad setuped ?

Best regards

Posted: **Tuesday 02 July 2024 9:20**

Bliepie wrote: ↑Wednesday 19 June 2024 11:06 Hi,

I have the exact same question about updating zwave-js-ui, does anyone know how to do this?
Thanks!

Bliepie

if you followed the guides, you installed using docker compose.....

Then the upgrade instructions would be:
- go to the directory where your docker-compose file is located
- then give the following commands:
- docker compose pull (retrieves the new images)
- docker compose down (stops and removes all containers)
- docker compose up -d (recreates and starts all containers)
- docker system prune -f (cleans up)
- you could also combine this to one command: "docker compose pull && docker compose down && docker compose up -d && docker system prune -f"

You have to do this for every docker compose file you created...., so what i did wat combine all docker compose files to just one docker compose file, and then using this single command i update all my docker containers

Posted: **Tuesday 02 July 2024 10:02**

funmsa wrote: ↑Tuesday 02 July 2024 1:17 Dear all,
I have a big problem to detect my ZWave device from the MQTT server on my Domoticz both are in docker in my synology NAS :

Step 1) I install on a docker image zwavejs2mqtt1 correctly and it's look to detect all my zwave device, nice. I try to configure MQTT like that Image1
Step 2) I also install correctly image Domoticz V2023.2 and add hardware "MQTT Auto Discovery Client Gateway with Lan" and setup it like the image 2

But... Domoticz don't discover into hardware "MQTT Auto Discovery Client Gateway with Lan" (setup button) any zwave devices view into zwavejs2mqtt1 image... why ? What I have bad setuped ?

Best regards

May be a question of IP addresses. Check that the 2 containers are on the same docker network. See https://www.tutorialworks.com/container-networking/. The IP used by the container is given by

Code: Select all

docker inspect <container name> | grep IPAddress

Posted: **Wednesday 03 July 2024 0:32**

Dear all,

@akamming : I'm sorry but I use Docker package on my Synology, I don't use direct command line "compose" or other. I'm not sure it's the problem

@mgugu : I can from my LAN network access web page ZWave-JS-UI and see all zwave devices so... why from docker of my Domoticz, I can access the URL port 1883 ???

About IP address I do the grep and obtain this

root@diskstation2:~# docker inspect zwavejs-zwavejs2mqtt1_V1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "172.17.0.3",
"IPAddress": "172.17.0.3",

Docker is setuped and running on network bridge and I open 2 ports
- 8091 to let me access to HTTP server
- 1883 for TLS MQTT.

but despite this when I click on "Setup" of my hardware "MQTT Auto Discovery Client Gateway with Lan" I still do not see the zwaves devices... Does anyone have screenshots of their hardware config "MQTT Auto Discovery Client Gateway with Lan" in the Domoticz docker in order to see how they managed the setup please ?

I have this on Domoticz log :
2024-07-03 00:48:09.804 Status: zwave-js-ui: Connecting to 192.168.1.160:1883
2024-07-03 00:48:09.904 Error: zwave-js-ui: disconnected, restarting (rc=7/The connection was lost.)

Posted: **Wednesday 03 July 2024 14:33**

Do you see MQTT messages when connecting with MQTT explorer on port 1883 ?

Posted: **Saturday 06 July 2024 7:49**

Effectevly no, MQTT explorer can open a connexion on port 1883. But After reread perhaps I miss something...

What I install is

- Domoticz on a docker container on my sinology and look tobwork fine
- ZWaveJsUI on another docker container also on my synology and is correctly connected to my ZWave pen with allo zwave devices

but... must I also install a MQTT broker on another docker container ? I thought it was incluses on the docker ZWaveJsUI ... If Yes could Simeone vive me the docker URL for that ?

If someone could also explain on detail which port must I open on each contaminer... than surely help me.

Posted: **Saturday 06 July 2024 10:13**

I think you did not read our instructions: https://www.domoticz.com/wiki/Zwave-JS-UI#MQTT_Broker

Posted: **Saturday 06 July 2024 14:32**

funmsa wrote: ↑Saturday 06 July 2024 7:49 Effectevly no, MQTT explorer can open a connexion on port 1883. But After reread perhaps I miss something...

What I install is

- Domoticz on a docker container on my sinology and look tobwork fine
- ZWaveJsUI on another docker container also on my synology and is correctly connected to my ZWave pen with allo zwave devices

but... must I also install a MQTT broker on another docker container ? I thought it was incluses on the docker ZWaveJsUI ... If Yes could Simeone vive me the docker URL for that ?

If someone could also explain on detail which port must I open on each contaminer... than surely help me.

You could start easier (to avoid multiple docker issues) and implement Mosquitto as package on Synology. I'm running ZwaveJsUI under Docker (Container Manager) in combination with Mosquitto. And runs fine. Later on you could migrate to MQTT under Docker.

Posted: **Tuesday 09 July 2024 23:55**

Dear all,

FINALLY is working quiet fine I could correctly setup Mosquitto MQTT Broker and receive all device. The problem was fact than we need setup port for listener 1883 (and let anonymous access to) in MQTT config file mosquitto.conf AND edit the good config file (many was on my Synology and good config file wasn't taked) Without this, only local (into container) could connect to the internal listener...

But I have another problem... from container Domoticz I could see all my zwave devices and status, but I couldn't update it (switch ON/OFF) only from ZWave-JS-UI. I don't know how and after some manipulation I could let to control zwave switch device from Domoticz... but don't work anymore I surely disable something... but what ? Someone know how to control device from Domoticz container ? Which setup must I be careful ?

Best regards

Posted: **Wednesday 17 July 2024 11:05**

Hello,
Windows update.
I have zwave-js-ui running on windows. (no docker) For updating to a newer version I copy the newest .exe file from the zip-file to my folder where zwave.js.ui is running and replace the file by the new file. First close zwave-js-ui before replacing. Only replace this file and not the folder store. Then I restart my computer and run the .exe file. I have automated all my (weather) software to start with a program named StartWatch. Zwave-js-ui is first to start before domoticz start. This works for me and until now no problems.
Groet Jan

Posted: **Sunday 27 October 2024 10:52**

: seismic.png (16.62 KiB) Viewed 664 times

I'm trying to migrate to zwave-js-ui and doing replacement of devices in Domoticz 2024.7.

However I have a FGMS001 Multi Sensor (protocol version 4.5 chip fw 3.2) where "seismic intensity" isn't reported as "percentage" like before but as a "custom sensor".
So I cannot replace it at the moment.

How can this be fixed, on my side or in the code? @gizmocuz @waltervl ?

Posted: **Sunday 27 October 2024 12:32**

I have no idea

Domoticz

Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: Easiest way to migrate Openzwave to ZWave-JS-UI