Easiest way to migrate Openzwave to ZWave-JS-UI

[tjabas]

so after installing z-wave js, do i need to rename all switches and sensors again,and redo all the blockys and scripts again?

[MikeyMan]

so after installing z-wave js, do i need to rename all switches and sensors again,and redo all the blockys and scripts again?

Yes...

[tjabas]

so after installing z-wave js, do i need to rename all switches and sensors again,and redo all the blockys and scripts again?

Yes...

oh man.. that is something im not looking forward too, i have 140 nodes, i have spendt at least 7 years building blockys and scripts, i really dont want to do it all over again.
what if i never update domoticz again, then i would be safe or...?`

[JeroenL]

Dear all,
My migration worked actually very smooth, one small "issue" remaining, see at the bottom.

1) Installed Zwave JS UI on Homeassistant, which I have running on another PI.
2) dis-abled OpenZwave in domoticz -- the switches etc. do get greyed out (which is not a problem)
3) I moved my Aeotec GEN 5 stick from domoticz to the home-assistant pi (note: the old Gen5 stick does not work on a Pi4)
4) In ZwaveJS UI on homeassistant, I selected my USB Gen 5 stick, and the devices start being read from the usb-device (I have a 50+ zwave devices)
5) A bit of work, giving all the nodes a similar name as in domoticz -- do this first, before turning on MQTT etc.
6) Finish the MQTT & Gateway settings in Zwave JS UI as per the wiki (do not forget the Autodiscovery switch in the HomeAssistant section)
7) Turn on MQTT Autodiscovery -- I created a "new" hardware called ZwaveJS, which has the MQTT auto-discovery behind, devices start being added to domoticz
8) Then going one-by-one along all the greyed-out OpenZwave switches choose "Edit / Aanpassen" and select the corresponding newly discovered ZwaveJS device.
9) All the scripts keep working, as the original ID's and names preserved.
10) I changed the name of the "unwanted" discovered devices to $unwanted, so they remain hidden in domoticz
You are done.
8< - - - - - - - - - - -
My remaining issue:
I use my Aeotec Gen 5 stick as a secondary controller (Fibaro HC 3 is primary), it is just that if I change status of a device/switch on the HomeCenter, the ZwaveJS UI does not update/cascade the new status of the device to domoticz.
Do no think this is a domoticz issues, but more a ZwaveJS UI setting/issue.

Has anyone experienced this too? Is there a work-around, so the switches in domoticz represent the actual state they are in.

Thanks for any thoughts !
Jeroen

[JeroenL]

so after installing z-wave js, do i need to rename all switches and sensors again,and redo all the blockys and scripts again?

Yes...

No !!
see my post above.

[sincze]

home-assistant pi (note: the old Gen5 stick does not work on a Pi4)

Small addition:
Try a USB2.0 HUB in between the Pi4 and the stick and it will start working on a Pi4.

Great instructions on how to replace rhe old devices many thanks.

Also a tip on how to easily wake battery operated devices?

[solarboy]

so after installing z-wave js, do i need to rename all switches and sensors again,and redo all the blockys and scripts again?

Disable but do not delete the old OZW. This will leave the OZW devices in Domoticz.

Then when the new devices arrive from zwavejsUI you can use the "edit" feature of each of the OLD devices to "replace" with the newly created devices, preserving all your routines, blocklys, dzvents, scenes etc etc

You may have some devices that won't replace, for me it was some RGB bulbs that zwavejsUI created slightly differently. I did have to change all my scripts involving these devices which was a pain but otherwise it's quite painless. I actually prefer to use node names as it helps decypher the newly created devices.

I would wait a couple of weeks before finally deleting the old OZW hardware just in case you forget or miss something.

[MikeyMan]

@solarboy that doesn't work. If you disable the hardware you cannot replace anymore.

[Egregius]

I have one small issue with zwave-js-ui instead of openzwave.
A lot of my dimmers don't respect the soft dimming time set to the minimum and use the factory default 3 sec. Because of that a lot of lights react slow.
Just tested by restoring an old snapshot of my domoticz server and the lights all switch on instantly. With zwavejs that takes 3 seconds.
Other than that no issues here. But these are big enough for me to stay on openzwave for a while. Don't update domoticz anymore so that shouldn't be an issue until I add some fancy modern device somewhere.

[waltervl]

I have one small issue with zwave-js-ui instead of openzwave.
A lot of my dimmers don't respect the soft dimming time set to the minimum and use the factory default 3 sec. Because of that a lot of lights react slow.
Just tested by restoring an old snapshot of my domoticz server and the lights all switch on instantly. With zwavejs that takes 3 seconds.

This is issue seems to be related to this https://github.com/domoticz/domoticz/issues/5179

[solarboy]

@solarboy that doesn't work. If you disable the hardware you cannot replace anymore.

Not true for me on latest stable, I've just done exactly that before Xmas.

https://www.domoticz.com/wiki/Zwave-JS-UI

Scroll down to the "Migrating From Openzwave" section.

[MikeyMan]

@solarboy that doesn't work. If you disable the hardware you cannot replace anymore.

Not true for me on latest stable, I've just done exactly that before Xmas.

https://www.domoticz.com/wiki/Zwave-JS-UI

Scroll down to the "Migrating From Openzwave" section.

I know how it works. In theory.

I'm on the latest beta and no way to do this. The moment you disable the hardware, the devices disappear in the regular tabs. And the replace option isn't available in the devices page under settings.

[solarboy]

That's really odd. You could try something else, change the OZW USB device to something random but don't disable, that might work.

When I did it the switches etc were in the usual tabs but greyed out. It was still possible to open the edit tab and "replace".

[ronald1827]

OMG spend half the day to get Zwave-JS-UI running. Had an enormous amount of errors.
Finally got it running, tested 1 switch and working. So started updating all the names, took about 5 hours to complete.
Suddenly lots of errors dropped, switch not found, nothing was working anymore. Restarted the docker and it worked again, for several minutes and stopped again.
Returned back to Openzwave, can't leave it in an erroneous state for the evening/night.

I wanted to to this to , started with snap , installed that and then you heve to confirm that the hello-world example works, it did but with the famous preload error , so i thought that's not good that at this point a allready get a eror.
So what i did i have a few rpi 4's and installed Home Assistant on it , plugged in AEOTEC spare zwave stick , added a Everest switch and a Heimann smoke detector with the new ZW JS allready built in HA , so added after that Mosquitto , registered a Tasmota device and works fine.
For the smoke sensor a made a automation rule, added push over notification that i use and it works.
I was pleasently surprised at what HA has built in allready and what you can add to it.
So i am learning HA and will migrate to it.
As an example , with Tasmota you need to add every sensor to it , but in HA it's all in 1 panel , power, cos phi used power everything is in there.
I think that the Domoticz developers should make a user friendly transition on the zwave side otherwise people will move away from Domoticz, i use it for years but this is just not good .

[waltervl]

There is always the option to move to the ZigbeeforDomoticz python plugin. No MQTT, no Zigbee2MQTT install, no Docker.....

[MikeyMan]

@waltervl does that also offer Zwave?

[waltervl]

@waltervl does that also offer Zwave?

Oh My, stupid me.... No, Mixed Zwave up with Zigbee

[Nautilus]

Hi, after migrating to zwavejs2mqtt I started seeing strange devices, e.g. fibaro plug offers:

switch_switch
sensor_water_tank_capacity
sensor_temperature_air
sensor_illuminance
sensor_electricity_power
sensor_electric_w_value
sensor_electric_kwh_value

Fibaro PIR offers:

binary_sensor_any
sensor_temperature_air
sensor_illuminance
sensor_generic_general_purpose
sensor_humidity_air
sensor_gas_carbon_dioxide
sensor_electricity_power
sensor_temperature_exhaust
sensor_water_tank_capacity
sensor_generic_particulate_matter_25

The bolded ones I do not understand why they are there. Something I did not see with OZW. I tried looking for references also in the HA forums as I imagined there would be plenty of people wondering the same - but I found none. Is this an issue on my setup only? The devices (the relevant sensors and switches) work fine and I can alway ignore the irrelevant ones - just wondering why this happens. And I understand it is not a Domoticz problem as such, just interested to hear if you've noticed the same and found ways to handle these?

[aukesp]

I try also to migrate to zwave-JS on a Windows machine with Docker instelled.
Everything is going fine but....
My USB devices are not seen/ connected.
In all packages the note: Like the other methods replace /dev/serial/by-id/insert_stick_reference_here with the serial device for your Z-Wave stick.
Where ever I look i do not find any serial/ USB device.
Also the command: lsusb is not found??
ls -l /dev/ttyUSB0 gives no result.

Where am I going wrong or have I missed something?

Before I can install Zwave_JS container do I have to install something else maybe?

[MikeyMan]

@aukesp this is more a docker issue than anything else I presume.