Page 14 of 23
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 10:00
by Varazir
waltervl wrote: ↑Tuesday 01 August 2023 9:56
Varazir wrote: ↑Tuesday 01 August 2023 9:38
This is giving me a headache
I'm already running Zigbee2MQTT MQTT Auto Discovery Client Gateway with LAN interface, and a MQTT broker Mosquitto.
How should I go about to install this new zwave setup ?
This is more easy for you. Just install Zwave-JS-UI and connect your Zwave dongle to it and you are ready.... (almost).
if you have the default MQTT AD settings in Zigbee2MQTT (eg discovery topic is "homeassistant") then the Domoticz MQTT AD Client Gateway with LAN interface will also pick up your Zwave-JS-UI devices.
If you want to keep the hardware separate then you should change the discovery prefix topic in Zwave-JS-UI (eg zwavejsAD) and make an extra MQTT Auto Discovery Client Gateway with LAN interface in domoticz with this changed discovery topic name. See also the instruction in the Zwave-JS-UI wiki.
https://www.domoticz.com/wiki/Zwave-JS-UI
Next will this change the devices I have setup? I need to re add them and change the name etc or will they just get replaced with the new ones from the new hardware ? Edit I read in the wiki I need to do. It's maybe time to switch to another platform if I need to replace all my devices.......
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 11:08
by Varazir
waltervl wrote: ↑Tuesday 01 August 2023 9:56
Varazir wrote: ↑Tuesday 01 August 2023 9:38
This is giving me a headache
I'm already running Zigbee2MQTT MQTT Auto Discovery Client Gateway with LAN interface, and a MQTT broker Mosquitto.
How should I go about to install this new zwave setup ?
This is more easy for you. Just install Zwave-JS-UI and connect your Zwave dongle to it and you are ready.... (almost).
if you have the default MQTT AD settings in Zigbee2MQTT (eg discovery topic is "homeassistant") then the Domoticz MQTT AD Client Gateway with LAN interface will also pick up your Zwave-JS-UI devices.
If you want to keep the hardware separate then you should change the discovery prefix topic in Zwave-JS-UI (eg zwavejsAD) and make an extra MQTT Auto Discovery Client Gateway with LAN interface in domoticz with this changed discovery topic name. See also the instruction in the Zwave-JS-UI wiki.
https://www.domoticz.com/wiki/Zwave-JS-UI
I managed to install Zwave-JS-UI and access it, but I get error
Code: Select all
Driver: Failed to open the serial port: Error: No such file or directory, cannot open /dev/zwave (ZW0100)
What do you mean with connect my zwave dongle?, it's a Raspberry pi HAT
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 11:18
by waltervl
The Domoticz OZW gateway in Domoticz should be stopped (disable Hardware in menu setup hardware) else 2 process are trying to connect the same serial port which is not possible.
And I mean the Zwave controller (most people have a USB dongle), sorry for the misunderstanding but I could not know that.....
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 14:08
by Varazir
waltervl wrote: ↑Tuesday 01 August 2023 11:18
The Domoticz OZW gateway in Domoticz should be stopped (disable Hardware in menu setup hardware) else 2 process are trying to connect the same serial port which is not possible.
And I mean the Zwave controller (most people have a USB dongle), sorry for the misunderstanding but I could not know that.....
I disabled it.
But I think it's something I missed the config, I used snap to install. I didn't point to the zwave controller.
Trying to check where I'm going to do that.
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 14:18
by waltervl
In the Domoticz Wiki AND the Zwave-JS-UI snap install documentation there is a specific warning for installing Zwave-JS-UI with snap on a RPi.
If on a RPi 32-bit you have to read this:
https://github.com/zwave-js/zwave-js-ui ... ent-759534
Could also be this issue:
https://github.com/zwave-js/zwave-js-ui/issues/3192
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 14:33
by Varazir
Found the setting, but still
Code: Select all
2023-08-01T12:15:12.968Z DRIVER version 11.6.0
2023-08-01T12:15:12.969Z DRIVER
2023-08-01T12:15:12.970Z DRIVER starting driver...
2023-08-01T12:15:12.970Z DRIVER opening serial port /dev/ttyAMA0
2023-08-01T12:15:22.014Z DRIVER Failed to open the serial port: Error: Operation not permitted, cannot open /d
ev/ttyAMA0
2023-08-01T12:15:22.016Z DRIVER destroying driver instance...
2023-08-01T12:15:22.023Z DRIVER driver instance destroyed
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 14:48
by waltervl
Perhaps better use docker.....
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 15:07
by Varazir
waltervl wrote: ↑Tuesday 01 August 2023 14:48
Perhaps better use docker.....
Then I need to upgrade OS on my pie. I'm going to check on the devs discord.
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Tuesday 01 August 2023 19:09
by Varazir
waltervl wrote: ↑Tuesday 01 August 2023 14:48
Perhaps better use docker.....
Talked to them and looks like the Razberry isn't supported installed using snap, to install Docker I need to upgrade OS.
Option is to reinstalling everything, I have another Rpi3 that I could do a fresh installation on.
But looks Like I'm going to keep to the stable release for some time until I get the energy to set it all up again.
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 14:18
by lost
Varazir wrote: ↑Tuesday 01 August 2023 19:09
Talked to them and looks like the Razberry isn't supported installed using snap, to install Docker I need to upgrade OS.
(...)
But looks Like I'm going to keep to the stable release for some time until I get the energy to set it all up again.
For snap, did you saw this?
https://github.com/zwave-js/zwave-js-ui ... nt-4298652
Well, this looks to have been difficult (but maybe previous zwave setup issues were present)& must agree that's not very appealing (as all zwavejs labyrinthine system)!
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 17:00
by waltervl
Running it in a docker environment seems to be the way to go. I do not understand why for Docker one should need an OS upgrade. Or the OS is very very old and you will need an OS upgrade anyway.
According docker docs:
Code: Select all
OS requirements
To install Docker Engine, you need the 64-bit version or 32-bit version of one of these Raspbian versions:
Raspbian Bookworm 12 (testing)
Raspbian Bullseye 11 (stable)
Raspbian Buster 10 (oldstable)
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 17:32
by lost
waltervl wrote: ↑Thursday 03 August 2023 17:00
Running it in a docker environment seems to be the way to go.
Can understand some may want to avoid this... just looking Docker image for zwavejsui its over 100MB compressed. Domoticz bare install is 15MB.
Add the containerization stuff and at the end of the day does this still fit on former raspberries? Especially if you need some tmpfs to preserve the sd card...
Zwavejsui, thats devops guys going to driver development with ttm as the only optimization skill!
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 18:27
by Varazir
waltervl wrote: ↑Thursday 03 August 2023 17:00
Running it in a docker environment seems to be the way to go. I do not understand why for Docker one should need an OS upgrade. Or the OS is very very old and you will need an OS upgrade anyway.
According docker docs:
Code: Select all
OS requirements
To install Docker Engine, you need the 64-bit version or 32-bit version of one of these Raspbian versions:
Raspbian Bookworm 12 (testing)
Raspbian Bullseye 11 (stable)
Raspbian Buster 10 (oldstable)
I need a driver libseccomp2 -t buster-backports but the key that you need to installing arn't working
https://zwave-js.github.io/zwave-js-ui/ ... h-with-820
I get this when I try to install the docker image
Code: Select all
docker run --rm -it -p 8091:8091 -p 3000:3000 --device=/dev/ttyAMA0:/dev/zwave --mount source=zwave-js-ui,target=/usr/sr
c/app/store zwavejs/zwave-js-ui:latest
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7ea8b4a4
Edit : I have a bit more energy today see if I can fix it. You know linux and hitting walls after wall due to missing libs etc drains you.
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 21:02
by waltervl
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 22:18
by Varazir
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 22:57
by Varazir
It's working now, just wait I guess
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 22:59
by waltervl
Varazir wrote: ↑Thursday 03 August 2023 22:57
It's working now, just wait I guess
Great!
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 23:04
by Varazir
Then to the next step that don't work.
I followed this
https://www.domoticz.com/wiki/Managing_ ... ace_device but I can't find the old device on the utility screen all are gone.
I can see them in the device list. so now I can't replace the old as it say I need to.
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 23:07
by Varazir
and I did by mistake the other way around and now the new device gon and the old one. this going great.
Re: Easiest way to migrate Openzwave to ZWave-JS-UI
Posted: Thursday 03 August 2023 23:09
by waltervl
Perhaps Enable the old zwave hardware gateway (it will give errors as the zwave controller is already in use). Also look through this topic as it is described earlier. I do not use zawave so did not go through this process.
The new device will come back if you restart Domoticz as it is rediscovered again.