Not shure to leave Open Z-wave version
Moderator: leecollings
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Not shure to leave Open Z-wave version
I am using the latest Domoticz Open Z-Wave version 2023/2 on a Windows 11 computer. I am not an expert and have not yet dared to update due to the complicated transition to Domoticz JS. I had also heard about many problems after switching to the JS version, including for the Spirit Z-Wave Plus thermostats, of which I use eight. Is there now a simple guide or video that explains exactly how to proceed step by step to ensure that the JS version runs without errors ? My Open Z-Wave version runs absolutely error-free, but some brand new sensors, etc. can no longer be integrated. I'm not sure whether updating from Open Z-Wave to the JS version makes sense for me.
- madpatrick
- Posts: 758
- Joined: Monday 26 December 2016 12:17
- Target OS: Linux
- Domoticz version: 2025.2
- Location: Netherlands
- Contact:
Re: Not shure to leave Open Z-wave version
I had the same questions but must says that it is advisable to move over
-= HP server GEN11 =- ZwaveJS-=- Domoticz v2025.2 -=- Dashticz =-
-= Checkout https://github.com/MadPatrick for the plugins =-
-= Checkout https://github.com/MadPatrick for the plugins =-
-
jannl
- Posts: 823
- Joined: Thursday 02 October 2014 6:36
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2025.5.x
- Location: Geleen
- Contact:
Re: Not shure to leave Open Z-wave version
I started with a docker container on my production po. Mainly because I only have 1 zwave usb stick. In this way you can test it.
I must say way less zwave issues since. I just followed the instructions in the wiki.
Just reserve half a day or so when you really switch.
I must say way less zwave issues since. I just followed the instructions in the wiki.
Just reserve half a day or so when you really switch.
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
Thanks for your recommendation to switch. But it looks too complicated for me overall. I also couldn't find any simple instructions for Windows and switching from Open Zwave to the JS version. Apparently, there is also no video explaining the entire process for Windows to better understand the whole procedure. I also didn't understand what Docker is needed for. Some recommend it, others advise against it. I'm also afraid that my Spirit thermostats will no longer work, as many people report problems with them.
I will not use new Z-Wave sensors and continue to run the Open Zwave version as long as it still works. So far, there have been no problems, including the control of my solar system.
I will not use new Z-Wave sensors and continue to run the Open Zwave version as long as it still works. So far, there have been no problems, including the control of my solar system.
- waltervl
- Posts: 6677
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2025.1
- Location: NL
- Contact:
Re: Not shure to leave Open Z-wave version
You can always try it, if it does not work you have the fall back to the old OpenZwave integration.
The only thing is you cannot have the Zwave-stick communicate with both on the same time. So in domoticz you have to disable (not delete!) the openzwave hardware before you can start Zwave-JS-UI.
The only thing is you cannot have the Zwave-stick communicate with both on the same time. So in domoticz you have to disable (not delete!) the openzwave hardware before you can start Zwave-JS-UI.
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
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
OK, good idea. Will test it in some time.
-
gmarchionni
- Posts: 21
- Joined: Sunday 11 June 2017 0:00
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
in my opinion, docker makes it a lot easier for the long term. It's easier to update, easier to backup, easier to restore.
There are a lot of ai chatbots. if you are not an expert, ask for help to one of those...and they will solve most of the problems for you. If you have a rasp with at least 2gb of ram from my opinion it's a non-sense to install on the bare metal.
maybe you should also think about installing it domoticz on a dedicated hardware like raspberry or similar.
There are a lot of ai chatbots. if you are not an expert, ask for help to one of those...and they will solve most of the problems for you. If you have a rasp with at least 2gb of ram from my opinion it's a non-sense to install on the bare metal.
maybe you should also think about installing it domoticz on a dedicated hardware like raspberry or similar.
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
Thank you very much for your tip about Docker. As a layman, I asked ChatGPT and received the answer that Docker is only easier if you use Linux. I use a mini Windows 11 computer and it should be much easier without Docker, as everything runs natively under Windows. That's what ChatGPT recommended, but it doesn't sound easy either. Perhaps you could comment on what is easiest under Windows.
ChatGPT instructions:
INSTALL NEW Domoticz 2025.2
IN THE SAME FOLDER AS THE OLD VERSION
Example (very important!):
C:\Domoticz\
Start the installer
Select EXACTLY this folder
Allow overwriting
Result:
• New domoticz.exe
• Old domoticz.db remains
• Blockly & devices are still there
NO import takes place here.
The new version automatically uses the old DB.
START Domoticz 2025.2 ONCE (without Z-Wave)
• Start Domoticz
• Open web interface
Check:
• Are devices there?
• Is Blockly there?
If yes → everything is fine
(The Z-Wave devices may still be “dead” – this is NORMAL)
Install Mosquitto (MQTT)
If not already present:
• Start the installer
• Leave “Install as Service” enabled
• Done
MQTT is now running in the background
Don't do anything else yet
Install Z-Wave JS UI
• Start the installer
• Install
• Do NOT connect the program to the stick YET
NOW THE DECISIVE STEP
OpenZWave is already gone – now JS takes over
Z-Wave JS UI s
ChatGPT instructions:
INSTALL NEW Domoticz 2025.2
IN THE SAME FOLDER AS THE OLD VERSION
Example (very important!):
C:\Domoticz\
• New domoticz.exe
• Old domoticz.db remains
• Blockly & devices are still there
The new version automatically uses the old DB.
• Start Domoticz
• Open web interface
• Are devices there?
• Is Blockly there?
(The Z-Wave devices may still be “dead” – this is NORMAL)
If not already present:
• Start the installer
• Leave “Install as Service” enabled
• Done
• Start the installer
• Install
• Do NOT connect the program to the stick YET
OpenZWave is already gone – now JS takes over
Z-Wave JS UI s
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
It seems that most people here use Domoticz Linux and Docker to upgrade from Open Z-Wave to the JS version. Are there any Windows users who can share their experiences on how to make the switch as easy as possible for a layman? Docker programming doesn't look that easy, so is there an easier way to do it on Windows? I have about 60 nodes and a lot of Blockly conditions, so only a simple automatic switch would make sense. Everything works flawlessly with Open Z-Wave, but I can no longer teach new devices because support is now missing.
-
gmarchionni
- Posts: 21
- Joined: Sunday 11 June 2017 0:00
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
unfortunately i'm not able to give any support on this....
my guess anyway is that you should disable openzwave on domoticz first thing...and install zwave js ui and configure the zwave dongle there.
but...as said i never done it on Windows so i cannot be of any help unfortunately. Again an ai bot should be able to help.
my guess anyway is that you should disable openzwave on domoticz first thing...and install zwave js ui and configure the zwave dongle there.
but...as said i never done it on Windows so i cannot be of any help unfortunately. Again an ai bot should be able to help.
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
Thank you for your idea, but I think it it not that easy, i tryed allready and failed .... I hope that someone with Domoticz Windows Experience can give me a hint what would be the most easy way to update open z-wave to js.
- waltervl
- Posts: 6677
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2025.1
- Location: NL
- Contact:
Re: Not shure to leave Open Z-wave version
I believe there is an exe install for Zwave-JS-UI:
- Download the zwave-js-ui-win.zip (or similar) from the GitHub releases: https://github.com/zwave-js/zwave-js-ui/releases
- unpack zip and run the executable. It starts zwave-js-ui.
- open UI on http://localhost:8091 and do the settings
- If running as a service, consider using NSSM (Non-Sucking Service Manager) for better stability.
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
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
Thanks for pointing out the Windows JS-UI exe. It actually seems easier than using Docker, which I couldn't get to work. I've now been able to import most of my 60 devices using JS-UI. I'm in the process of assigning a name and location to each one. Unfortunately, there are also nodes that have been assigned the same number, which I'll have to exclude and re-include, as well as 7 devices that are missing. All in all, it's a lot of work, and Open Z-Wave worked so well for me...
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
I'm getting frustrated. I had everything working fine, but then I had to do a new interview with a node in js.ui-win, and after that, all the names and locations I had assigned in JS-UI and Domoticz disappeared. Where do you save the names in the Windows version so that they don't get lost during updates, new interviews, etc.?
- waltervl
- Posts: 6677
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2025.1
- Location: NL
- Contact:
Re: Not shure to leave Open Z-wave version
From the zwave-JS-UI documentation
Perhaps consider installing Ubuntu on your Domoticz server
I have no idea where that store folder is in WIndows but I would start in the folder where the exe is. Other wise in other typical folders like Appdata or your user local folder.Settings, scenes and the Z-Wave configuration are stored in JSON files under the project store folder. It is a good idea to backup those files, which can be done by backing up the store or using the import/export buttons.
Perhaps consider installing Ubuntu on your Domoticz server
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
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
Thanks for the backup tip. All backups are stored in the “Store” folder in the folder from which zwave-js-ui-win.exe is launched. This folder is easy to back up, so hopefully I won't lose any more data. Most things are now working again. The effort seems to be worth it, as there are better options and new devices can be used. However, I still have one problem: my NeoCoolCam window/door contacts were not transferred to JS-UI because they are battery-operated and sleep. I was able to integrate the NeoCoolCam into JS-UI with “Rebuild Routes,” but they are not visible in Domoticz. How can I integrate these nodes, which work in JS-UI, into Domoticz without encountering new problems? Maybe someone has a tip.
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
NeoCoolCam solved, but I thought I had everything under control now, but then the next problem arose: I had always used the security panel without a numerical code. Now I can't create a security panel because I'm supposedly entering the wrong PIN. Does anyone know of a solution for the Windows version? I need the security panel.
- waltervl
- Posts: 6677
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2025.1
- Location: NL
- Contact:
Re: Not shure to leave Open Z-wave version
To change the pin (password) of the Domoticz security panel see wiki https://wiki.domoticz.com/Security#Security_Panel
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
-
WRBUser
- Posts: 11
- Joined: Friday 26 December 2025 12:13
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Not shure to leave Open Z-wave version
The security panel is now working again, thank you. Does anyone know if you have to activate “accept hardware for 5 minutes” in Domoticz if you want to include existing nodes or new nodes? This is done in JS-UI, which manages the nodes and the Zstick with the network. I did this once, but unfortunately all the names and locations of my 60 nodes in JS-UI were empty.
Can you back up the store folder while JS-UI is running, or can this cause problems with the ###metadata.jasnl file, because this file is being written continuously?
Can you back up the store folder while JS-UI is running, or can this cause problems with the ###metadata.jasnl file, because this file is being written continuously?
Who is online
Users browsing this forum: No registered users and 1 guest