Easiest way to migrate Openzwave to ZWave-JS-UI

[thomasbaetge]

I migrated my system on the weekend.
I already had all installations done a while ago, so I only had to move and replace my devices.
All went smoothly and it seems that this is now a bit faster.

The most time consuming task is to replace the old devices with the new ones.
I took screenshots from my openZW installation before, which was a good idea.
The newly found devices will appear unter the same node ID they had before, so they are a easy to identify and the ID will even be shown in the generated device name.
I did the migration of my 'functional' devices first, i.e. switches etc. then the passive devices.
All in all it took me about half a day to migrate everything.

I had to wake up a few devices and re-interview them, but that was only 5 out of 66.

It might be worth to update the Wiki as to the where the z-wave security key goes under zwJS (or did I oversee this information?)

[Justintime]

I have a Problem with the Fibaro eye it is not sending Lux values any more.

In the Domoticz log i got am error from the Fibaro node

2024-01-08 13:29:53.958 Error: Mqtt discovery: sending switch commands for switch type 'binary_sensor' is not supported (yet...) (zwavejs2mqtt_0xd52a5bf3_33-48-0-Any/Sensor Fibaro)

I have tried to exlude and include several time but no luck.
What also dazzles me....how to set the parameters/options form the fibaro eye. ??

[akamming]

I understand, bit it is more difficult and also updating your systeem is more difficult. A simple sudo apt update && sudo apt upgrade -y won’t do the trick anymore… you have to upgrade each individual container as well

Anyway: not saying it is a bad idea, but since this thread is called the “easiest way to migrate” I Thought we can keep it simpler

Updating a docker (if necessary... ) can be done by the executing the following command in the dockers folder (which you can place in a file in your /sbin folder so you can use it whereever needed)

Code: Select all

docker compose pull && docker compose up --force-recreate --build -d && docker image prune -f

a nice..tx! now a script which updates all my docker containers, but i think i can make that myself with this hint!

would be good to add this to the wiki though...

[Hinkob]

I have been reading and tinkering (and reinstalling and restarting mosquitto/Zwave-JS-UI a lot) with getting zwave to work on Zwave-JS-UI too.
I have gotten to the point where I do get nodes populated in the JS-UI, but then after a couple of seconds they disappear and I get errors (failed to initialise driver: the serial api did not respond after soft reset) and that connectivity was lost. Then after a little while, i see my nodes back again followed by the same disappearance.

Code: Select all

024-01-08 16:11:.513 INFO Z-WAVE: [Node 001] Ready: AEON Labs - ZW090 (Z‐Stick Gen5 USB Controller)
2024-01-08 16:11:.979 INFO Z-WAVE: [Node 014] Interview started
2024-01-08 16:11:.994 INFO Z-WAVE: [Node 012] Interview started
2024-01-08 16:11:.005 INFO Z-WAVE: [Node 023] Interview started
2024-01-08 16:11:.014 INFO Z-WAVE: [Node 026] Interview started
2024-01-08 16:11:.025 INFO Z-WAVE: [Node 030] Interview started
2024-01-08 16:11:.277 DEBUG MQTT: Publishing to zwave/nodeID_6/status: { time: 1704726673276, value: true, status: 'Alive', nodeId: 6 } with options { qos: 1, retain: true }
2024-01-08 16:11:.282 INFO Z-WAVE: [Node 006] Is alive
2024-01-08 16:11:.964 DEBUG SOCKET: New connection fj1MFZpIsjPgGzAcAAAB
2024-01-08 16:11:.021 DEBUG SOCKET: Event INITED emitted to fj1MFZpIsjPgGzAcAAAB
2024-01-08 16:11:.109 DEBUG SOCKET: New connection Dv0BZl9YwgRenFKEAAAD
2024-01-08 16:11:.131 DEBUG SOCKET: Event INITED emitted to Dv0BZl9YwgRenFKEAAAD

does anyone know how to solve this?

[waltervl]

Perhaps this can help https://github.com/zwave-js/node-zwave-js/issues/6341

[thomasbaetge]

One thing I came across today:

if you want to give your devices 'meaningful names' in zwJS, you better do that, before you map them in Domoticz.
I did it today for some cleanup, and they stopped working.
Solved by a reboot.

[Hinkob]

Perhaps this can help /zwave-js/node-zwave-js/issues/6341

Thanks Walter, that looked promissing, but after updating the firmware, it still gives te same behaviour

Code: Select all

2024-01-08 17:20:.017 INFO Z-WAVE: Controller status: Driver: Failed to initialize the driver: ZWaveError: The Serial API did not respond after soft-reset (ZW0100)
    at DriversoftResetInternal (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driverts:2586:11)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at DriverinitializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driverts:1445:5)
    at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driverts:1226:5) (ZW0100)

This error starts on the following new connection in the debug:

Code: Select all

2024-01-08 17:51:642 DEBUG SOCKET: New connection Vq2UjdabmHpZnxRqAAAG
2024-01-08 17:51:674 DEBUG SOCKET: New connection j0Ct8BjILzN01vEMAAAH
2024-01-08 17:51:701 DEBUG SOCKET: Event INITED emitted to j0Ct8BjILzN01vEMAAAH
2024-01-08 17:51:778 DEBUG SOCKET: Event INITED emitted to Vq2UjdabmHpZnxRqAAAG

Can it be that another service interferes by opening a connection to the usb or something?
I have deleted the old " unknown" zwave hardware in domoticz

[waltervl]

How do you mount the stick with docker compose? Through the /dev/serial/by-id ?

Did you disable the soft reset as a last resort as mentioned in the Zwave-JS issue?

[Hinkob]

How do you mount the stick with docker compose? Through the /dev/serial/by-id ?
Did you disable the soft reset as a last resort as mentioned in the Zwave-JS issue?

yes to both questions Walter. after disabling the soft reset, the questioning of devices stays a bit longer but does reset again.
I have given up for now and went for the Domoticz beta update with " old" zwave setup.
thanks for your help!

[vco1]

I think it's not fair to (fully) blame the Domoticz developers for all the troubles people seem to have with the migration to zwave-js. But in all honesty, this wasn't a fun job at all and I spent way more time and energy on this migration than I wanted to (or should have).
I have a relatively small setup, but even with that it took a lot of trial and error and a couple of excludes and includes to get 'fully' up and running again. Fully between quotes, as I still have to work on a few scripts.

ZWave-js turned out to be rather flakey, to say the least. Switches and dimmers that were working flawlessly for many years, all of a sudden became unresponsive.

The fact that Domoticz manages almost all the lights in my house, didn't help either. Luckily it's easy to replace the sd card and go back to a stable system at the end of the day.

Anyway, let's hope this all keeps working for a long time.

[AimoPaukku]

I have tried so many times...

Why this OZW had to be removed?

I cannot go back to 2023 version.

Did you now? And where exactly did it went wrong?

I did not know, I made normal database backup and just updated, like so many times and trusted this will be better and better.

Now everything is total mess....

Hi, I came to say goodbye to each one of you, I hope we meet on the other side.

I bit the bait and finally tested Home Assistant.
WHOAH every single device I have popped in the system via Z-Wave JS.

It seems that I need to upgrade my raspi3 ja real x86-64 PC but that gives me so much more...

Still, I think removing ozw from domoticz was the best thing to happen, moving to HA was pretty painless after all.

Signing out...

[tiga]

so in short: if you cant use /dev/serial/by-id you are screwed and cant use the zwave anymore??


You can still use default devices names (could change if you plug something more and reboot) or use persistent usb devices,
https://www.domoticz.com/wiki/PersistentUSBDevices

i used the method for persistentusbdevices , at startup the zwave dongle uses the new port /dev/ttyUSB/Zstick-5G (selectable in domoticz)
but after 30 seconds or so i get time outs for my nodes....
when selecting /dev/ttyACM1 all the nodes are fine again.

but i want it to stay on /dev/ttyUSB/Zstick-5G so i can migrate to zwave-js-ui

can i fix this somehow?

[Eugene]

Hi Guys,

I just made my attempt to migrate to ZWave-js-ui and i have failed. The problem i was getting is all devices were showing as "unknown" except the Zwave stick. Some of the devices started eventually changing status light to "green/available" but still details were unknown about them. The device index numbers have been preserved as there were in Domoticz. When i enabled debug i was also able to see messages transmitted across my Zwave network.

Any suggestion what did i do wrong? Zwave js ui view is attached. I installed it in the docker.

thanks.

[thomasbaetge]

In case of battery operated devices this may take some time.
You can try to wake them up by briefly removing the battery and reinserting it, then click on Re-Interview Node in the 'advanced' menu of that node.
I had to do this for a few devices, others cam up after half a day or so, depending on the set 'wake up interval' on the device.
Some are more bitchy than others....

[tiga]

i am totally stuck with the migrating...seems that the usb ports keep switching random and total mess after reboot.

i want to set up a new fresh (spare pi i have) to give myself the most chanse of succeeding.

what os do you guys recommend?

i now use:
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

but here /dev/serial/by-id doesn't exist.

can you give me advice please?

[tjabas]

i also have tried with the migration i also got stuck with the usb port that seems to change all the time, for 1-2 minutes i got the nodes visible but after that they dissapeared, and it was switching like that all the time, i gave up and got back to openzwave, i have spent several days to get this to work, but for now im going to go on with openzwave and perhaps in the future it will be an easier way to change from openzwave.

[gizmocuz]

i am totally stuck with the migrating...seems that the usb ports keep switching random and total mess after reboot.

i want to set up a new fresh (spare pi i have) to give myself the most chanse of succeeding.

what os do you guys recommend?

i now use:
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

but here /dev/serial/by-id doesn't exist.

can you give me advice please?

You can follow this guide to make them persistant yourself.

What OS are you using that has no /dev/serial/by-id ?

Did you google for "no /dev/serial/by-id"

[tiga]

i used the method for persistentusbdevices , at startup the zwave dongle uses the new port /dev/ttyUSB/Zstick-5G (selectable in domoticz)
but after 30 seconds or so i get time outs for my nodes....
when selecting /dev/ttyACM1 all the nodes are fine again.but after a while this allso stops.

for some reason it is not working for me....it is one big mess....even after updating to 2024.2 and using Openzwave again it keeps switching ports.

i had the luck of having a discarded pi somewhere running domoticz 2023.2......plugged it in and averything is good and stable.
so now running on this platform.

but i want to setup a clean one for the future.

[tiga]

Seems to be a common issue that by-id has dissapeared: https://forums.raspberrypi.com/viewtopic.php?t=351113

[tiga]

just did a fresh install on a fresh pi and:

pi@raspberrypi:~ $ ls /dev/serial/by-id
ls: cannot access '/dev/serial/by-id': No such file or directory

pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian

what am i doing wrong?