Easiest way to migrate Openzwave to ZWave-JS-UI
Moderator: leecollings
-
Bliepie
- Posts: 8
- Joined: Thursday 28 November 2019 10:45
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Hi,
I have the exact same question about updating zwave-js-ui, does anyone know how to do this?
Thanks!
Bliepie
I have the exact same question about updating zwave-js-ui, does anyone know how to do this?
Thanks!
Bliepie
- waltervl
- Posts: 7024
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2026.3
- Location: NL
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Best to ask that on the zwave-js-ui forum https://github.com/zwave-js/zwave-js-ui/discussionsbrugje 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
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
- waltervl
- Posts: 7024
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2026.3
- Location: NL
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
On windows or Linux with docker (search with google as there are many ways to do update a docker image)?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
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
funmsa
- Posts: 14
- Joined: Monday 03 December 2018 23:36
- Target OS: NAS (Synology & others)
- Domoticz version: 2023.2
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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
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
- Attachments
-
- image2.jpg (78.53 KiB) Viewed 7477 times
-
- image1.jpg (59.08 KiB) Viewed 7477 times
-
akamming
- Posts: 429
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
if you followed the guides, you installed using docker compose.....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
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
-
mgugu
- Posts: 238
- Joined: Friday 04 November 2016 12:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: France
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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 byfunmsa 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
Code: Select all
docker inspect <container name> | grep IPAddress-
funmsa
- Posts: 14
- Joined: Monday 03 December 2018 23:36
- Target OS: NAS (Synology & others)
- Domoticz version: 2023.2
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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.)
@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.)
- Attachments
-
- image3.jpg (23.51 KiB) Viewed 7434 times
-
mgugu
- Posts: 238
- Joined: Friday 04 November 2016 12:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: France
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Do you see MQTT messages when connecting with MQTT explorer on port 1883 ?
-
funmsa
- Posts: 14
- Joined: Monday 03 December 2018 23:36
- Target OS: NAS (Synology & others)
- Domoticz version: 2023.2
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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.
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.
- waltervl
- Posts: 7024
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2026.3
- Location: NL
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
I think you did not read our instructions: https://www.domoticz.com/wiki/Zwave-JS-UI#MQTT_Broker
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
- Marathon2010
- Posts: 49
- Joined: Tuesday 02 February 2021 23:02
- Target OS: NAS (Synology & others)
- Domoticz version: 2026.4
- Location: Netherlands
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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.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.

- Attachments
-
- Capture-07-06-00041.jpg (106.84 KiB) Viewed 7348 times
Synology DS920+ DSM7 (Docker) | Integrations: Audio, Heating, Gas, Electricity, Water, Alarm, Car, Camera, Doorbell, Garage, Garbage, Washer | SW: Tasmota, DzVents, Pushbullet, Telegram | Plugins: UPS, GPSLogger, BatteryLevel, Hyundai KIA, Rhasspy
-
funmsa
- Posts: 14
- Joined: Monday 03 December 2018 23:36
- Target OS: NAS (Synology & others)
- Domoticz version: 2023.2
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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
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
-
brugje
- Posts: 7
- Joined: Monday 13 February 2023 19:36
- Target OS: Windows
- Domoticz version: 2024.4
- Location: NL (Echtenerbrug)
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
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
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
praet mar frysk
- waltervl
- Posts: 7024
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2026.3
- Location: NL
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
I have no idea
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
Maciek90
- Posts: 62
- Joined: Friday 05 March 2021 23:01
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
I have a question about thermostatic valves. I use Eurotronics Spirit. On menu ZWave UI in the Thermostat Mode tab there are five options to choose from, as in the picture nr 1. In Domoticz I have only three options, as in the picture nr 2.OFF in UI = OFF in Domo, Heat in UI = Heat in Domo, Energy heat in UI = Cool in Domo. What about the other two options from the UI? Is there any way to make them also displayed in the selector switch in Domoticz?
- Attachments
-
- 1.png (6.55 KiB) Viewed 5777 times
-
- 2.png (9.31 KiB) Viewed 5777 times
- user4563
- Posts: 115
- Joined: Tuesday 19 October 2021 17:24
- Target OS: Linux
- Domoticz version: 2026.4
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Have you tried going into Edit and adding those "levels" (0, 1, 11, 15, 31, etc.) manually?
ODroid H4+ / Ubuntu server 24.04 LTS
Aeotec Z-Stick Gen5+
ZWave-JS-UI / Mosquitto MQTT
Domoticz for Android
Domoticz Scenes add-on in Kodi
Aeotec Z-Stick Gen5+
ZWave-JS-UI / Mosquitto MQTT
Domoticz for Android
Domoticz Scenes add-on in Kodi
- waltervl
- Posts: 7024
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2026.3
- Location: NL
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
As "cool" is not in the zwave-JS-Ui list it looks like there could be another device linked to it. If you look at the device list in Domoticz menu Setup - devices are there more Thermostat Mode devices?
Is there in zwave-JS-Ui another Thermostat device that has the option "cool"?
Is there in zwave-JS-Ui another Thermostat device that has the option "cool"?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
Maciek90
- Posts: 62
- Joined: Friday 05 March 2021 23:01
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Today I tried and after a while the added level in domoticz disappears.Have you tried going into Edit and adding those "levels" (0, 1, 11, 15, 31, etc.) manually?
I have 14 z wave devices at home (12 valves, controller and range extender). The situation is the same on each valve. As I wrote earlier, setting in the ZWave UI "off" switches the selector to off in domoticz. If I switch to "heat" in the UI, in domoticz it also switches to "heat". However, if I switch to "Energy heat" in the UI, in domoticz it sets to "cool". Setting the other two options in the UI does not change the state in Domoticz. I would like the other two options, especially "Full power", to also be available in DomoticzAs "cool" is not in the zwave-JS-Ui list it looks like there could be another device linked to it. If you look at the device list in Domoticz menu Setup - devices are there more Thermostat Mode devices?
Is there in zwave-JS-Ui another Thermostat device that has the option "cool"?
- waltervl
- Posts: 7024
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2026.3
- Location: NL
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
I would try the latest Domoticz beta version if you are not already on that version and see if the missing levels pop up.
If not I would advise you to create a GitHub issue with all the required data as explained in the reporting MQTT AD wiki https://wiki.domoticz.com/MQTT_AD_Report_Problems
If not I would advise you to create a GitHub issue with all the required data as explained in the reporting MQTT AD wiki https://wiki.domoticz.com/MQTT_AD_Report_Problems
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
- gizmocuz
- Posts: 3026
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Always try with the latest Domoticz beta version first. A lot has been changed over time.
If that still does not work, please create an issue on Github and follow this guide to report the config topic+payload
https://wiki.domoticz.com/MQTT_AD_Report_Problems
If that still does not work, please create an issue on Github and follow this guide to report the config topic+payload
https://wiki.domoticz.com/MQTT_AD_Report_Problems
Quality outlives Quantity!