Easiest way to migrate Openzwave to ZWave-JS-UI

[MikeyMan]

Ok, seriously... This is a huge step backwards...

Took a hell of a lot of effort to get it up and running. The fact that it's now based on MQTT means that the IDXes are created in order of incoming message. Which causes a huge mess. Then the above scenario where you cannot easily replace the devices.
Also a couple of devices aren't supported it seems. Which never was any issue with OpenZwave.

And i never had this many 'device not found' erros in the last years running it than i have had over the last few days.

I'm going back to OpenZwave for now. And if that get depricated i might just leave domoticz all together.

[Gravityz]

for me there are 2 scenarios.

1: if openzwave stops working i will try to migrate to zwave-js-ui
2: if zwave-js-ui is not satisfatory change all zwave devices with zigbee devices(which connect to the hue hub)

the last one obviously will cost more money

[MikeyMan]

for me there are 2 scenarios.

1: if openzwave stops working i will try to migrate to zwave-js-ui
2: if zwave-js-ui is not satisfatory change all zwave devices with zigbee devices(which connect to the hue hub)

the last one obviously will cost more money

Woudn't it be easier to switch to another hub with Z-Wave support then?

[Gravityz]

yes maybe but that hub probably is not cheap either

i only have 6 zwave devices with 2 build in devices(dimmer and switch) which will cost the most time to replace.

[madpatrick]

Ok, seriously... This is a huge step backwards...

Took a hell of a lot of effort to get it up and running. The fact that it's now based on MQTT means that the IDXes are created in order of incoming message. Which causes a huge mess. Then the above scenario where you cannot easily replace the devices.
Also a couple of devices aren't supported it seems. Which never was any issue with OpenZwave.

And i never had this many 'device not found' erros in the last years running it than i have had over the last few days.

I'm going back to OpenZwave for now. And if that get depricated i might just leave domoticz all together.

As long as it is still working keep it as it is despitate it get despricated.
At lot of hardware will not get updated but still works fine.

[MikeyMan]

Ok, seriously... This is a huge step backwards...

Took a hell of a lot of effort to get it up and running. The fact that it's now based on MQTT means that the IDXes are created in order of incoming message. Which causes a huge mess. Then the above scenario where you cannot easily replace the devices.
Also a couple of devices aren't supported it seems. Which never was any issue with OpenZwave.

And i never had this many 'device not found' erros in the last years running it than i have had over the last few days.

I'm going back to OpenZwave for now. And if that get depricated i might just leave domoticz all together.

As long as it is still working keep it as it is despitate it get despricated.
At lot of hardware will not get updated but still works fine.

That is true, but if they take it out, we're done.
And that seems to be the plan.

[madpatrick]

Not yet the case.
To my knowledge it will not be removed from the builds.
And even then you can continue using it, only not the latest betas.
That is giving you plenty of time to check for a different option before changing.

[Egregius]

I hope there will be a huge warning before updating when openzwave support is dropped. Don't like the idea to be forced to use another system, reincluding everything. That would be a huge work here because of the 75 nodes...

[waltervl]

There is no need to reinclude everything. The only big thing in Domoticz would be to replace all your devices from old to new that you want to keep history of or are used into scripts with name or IDX. And that replace seems to be an issue now with OZW hardware gateway enabled. What happens if you enable the OZW hardware again, perhaps with a fakes usb address?

[Gravityz]

@waltervl

i noticed a question regarding a user who states that the old devices are not available(greyed out) anymore when you disable the zwave contoller
this also goes for MQTT AD controller, when you disable it al devices created by MQTT AD are greyed out.

[MikeyMan]

@Gravityz

I think you can leave the MQTT AD plugin switched on, but close the zwave js program.

[HansF]

My system is working fine, running 2021.1.
If I leave everything as it is, so no upgrade to 2022.2, and not all the hassle, what's against that?

[waltervl]

My system is working fine, running 2021.1.
If I leave everything as it is, so no upgrade to 2022.2, and not all the hassle, what's against that?

You can still update to 2022.2 Stable as OZW is still fully supported in this version. Then you also can update to bullseye OS, this is not possible with 2021.1 (if using python plugins).

[HansF]

So, if I don't update from 2022.2 onwards, everything will continue to work, right? Why bother updating when everything works fine now...

[waltervl]

Because you cannot update at all if 2023.1 does not have OZW anymore. But it is fully up to you. I am fine with it.

[HansF]

Ok, I'll leave it like that for now. Unless there's a really good reason for me to update to 2023.1.

[Egregius]

There is no need to reinclude everything. The only big thing in Domoticz would be to replace all your devices from old to new that you want to keep history of or are used into scripts with name or IDX.

OK, my bad. Misinterpreted by me. Even that would be a huge work. The 75 nodes give me 526 devices of which 303 are used.
I'm also a bit afraid to go to MQTT. Had it running several months for an Homepod mini but saw strange things so removed it again.

[MikeyMan]

There is no need to reinclude everything. The only big thing in Domoticz would be to replace all your devices from old to new that you want to keep history of or are used into scripts with name or IDX.

OK, my bad. Misinterpreted by me. Even that would be a huge work. The 75 nodes give me 526 devices of which 303 are used.
I'm also a bit afraid to go to MQTT. Had it running several months for an Homepod mini but saw strange things so removed it again.

MQTT as such does work nicely over here, running on my NAS with Docker.

However, for this specific application it's less than ideal. It's dependent on the messages being sent, and that seems to work rather irregularly.

[solarboy]

I've just switched over, 34 nodes, quite painless although a couple of problems.

The buggy firmware in my Zipato RGB bulbs means that I cannot switch on these bulbs with "scenes" although once they are switched on they respond to colour commands. It was also not possible to simply "replace" these as they now present as RGBWZ whereas under OZW they were RGBWWZ and RGB so a lot of scenes had to be rebuilt and then scripts altered.

I also have a Qubino Thermostat that seemed to have difficulty receiving commands although that seems to have cleared up now.

Otherwise the UI is much nicer and everything responds much faster, as fast as zigbee2mqtt now. Also nice to be able to back up my Aeotec Zstick without shutting down Domoticz and removing the hardware onto a Windows machine. Contrary to the wiki I used "node names" as it then creates easier to identify devices in Domoticz. I prepared all these names in zwavejsUI first before turning on MQTT and adding the devices to Domoticz.

[Egregius]

Could you update the wiki page where needed? Looks like the description if quite minimal now.