Easiest way to migrate Openzwave to ZWave-JS-UI

[nigels0]

I’m getting similar - it’s running, but the web page isn’t opening.

Code: Select all

 pi@domoticzpi:~$ sudo snap logs zwavejs2mqtt -f
2022-11-08T13:34:20Z zwavejs2mqtt.zwavejs2mqtt[685]:  / /__\ V  V / (_| |\ V /  __/ \__ \/ /_| | | | | | (_| | |_| |_
2022-11-08T13:34:20Z zwavejs2mqtt.zwavejs2mqtt[685]: /_____|\_/\_/ \__,_| \_/ \___| |___/____|_| |_| |_|\__, |\__|\__|
2022-11-08T13:34:20Z zwavejs2mqtt.zwavejs2mqtt[685]:                             _/ |                      | |
2022-11-08T13:34:20Z zwavejs2mqtt.zwavejs2mqtt[685]:                            |__/                       |_|
2022-11-08T13:34:21Z zwavejs2mqtt.zwavejs2mqtt[685]: 2022-11-08 13:34:21.003 WARN STORE: settings.json not found
2022-11-08T13:34:21Z zwavejs2mqtt.zwavejs2mqtt[685]: 2022-11-08 13:34:21.017 WARN STORE: scenes.json not found
2022-11-08T13:34:21Z zwavejs2mqtt.zwavejs2mqtt[685]: 2022-11-08 13:34:21.223 INFO APP: Listening on port 8091 host localhost protocol HTTP
2022-11-08T13:34:21Z zwavejs2mqtt.zwavejs2mqtt[685]: 2022-11-08 13:34:21.349 WARN BACKUP: Store backup is disabled
2022-11-08T13:34:21Z zwavejs2mqtt.zwavejs2mqtt[685]: 2022-11-08 13:34:21.356 WARN BACKUP: Nvm backup is disabled
2022-11-08T13:34:21Z zwavejs2mqtt.zwavejs2mqtt[685]: 2022-11-08 13:34:21.380 WARN ZWAVE: Zwave driver not inited, no port configured

[waltervl]

https://github.com/zwave-js/zwave-js-ui/issues/2783

[BartSr]

Went back to 2022V1 until problems with 2022V2 are solved

[waltervl]

Went back to 2022V1 until problems with 2022V2 are solved

Your problem with ZwaveJS UI will not be solved with changes in Domoticz. You can move to 2022.2 and still use OpenZwave.

[lost]

I have noticed, Openzwave support will be dropped in one of the next beta versions.

Hope this'll be delayed by a few weeks, just in case brand new stable shows issues & need fixes: This already occurred in the past, but adding undelayed zwave switch to this sub-optimal JS/MQTT/Docker based headache instead of current no-brainer OZW library integration without delay would not be nice experience!

Rollback may also this time more complex as many stable users were probably waiting to update from Debian 10 to 11 in sync with Domoticz...

[Gravityz]

it might be good to know what they mean by "Openzwave support will be dropped in one of the next beta versions"

do they mean they will no longer develop on OZW or fix things(likely)
or do they mean the will remove the complete functionality (this will eventually stop a lot of users from using domoticz because MQTT is still not mature, idiotproof and 100% supported on all devices)

[lost]

do they mean they will no longer develop on OZW or fix things(likely)

IMO, this'll be a stop: OZW changes since lead (and almost unique) developer step-back almost 2 years ago only concerned some new config files for new HW... But nothing on code side to enhance functionality/zwave recent evolution.

So on development side, this was already over in OZW & as a consequence in Domoticz... So current announce must be removing OZW integration from Domoticz soon.

Issue is, conceptually, ZwaveJS IMO really smells bad: So many layers added & using a interpreted language designed for dynamic web to drive HW: WTF??? Must be too old for this kind of computer (non) science!

Just expect this'll be delayed enough to make sure 2022.2 does not have still hidden issues... as next step, if nothing change meantime, will really need time & hold one's nose!

[Micha123]

i stay on OpenZwave, i have realy much Zwave devices (the whole home, lights, relays, temp/hum sensros, meeters (kwh), motion sensors, and and and


if i need to switch to other solution i wil be bussy a week or so.

the second think is, OZW works perfekt on my setup. no any kind of problems, why i need to switch do other solution and risk that not all wil work like now ?

[ferrosk]

the second think is, OZW works perfekt on my setup. no any kind of problems, why i need to switch do other solution and risk that not all wil work like now ?

You can still use it while is available in Domoticz 2022.2 but it may be removed in future Domoticz releases because OZW is no longer maintained - see the project on github. If not maintained, there won't be anybody who can fix issues with OZW, nobody will implement new Zwave features to OZW etc. I think there is no other option for Domoticz developers as to remove OZW in future releases. And be happy they worked hard to implement MQTT AD so we can use Zwave JS UI.

[Gravityz]

question regarding migration

i have zwave-js-ui running
i think the further actions are
disable domoticz(so the zwave stick becomes available)
enable zw-js-ui docker container
fill in the path to the zwave stick (/dev/ttyACM0 in my case)
save
now the device get discovered hopefully.


question. do i need to rename all the devices to a different name or as the same name they have now(i guess different)
if the interviewing is complete can i then remove the path from zwave-js-ui and enable domoticz again(without AD active)

i like to play around with zwave-js-ui to make it perfect(nemove/rename devices) before i start sending out all the devices through mqtt to domoticz.

e.g. i want to make sure everything is recognized but i do not want domoticz offline to long.

is that possible(have zwave-js-ui active and domoticz active ) so i can tune/play around with zwave-js-ui
hopefully this works when i remove the path

second question: zwave devices have lot's of parameters. are these available from zwave-js-ui as well?

[MikeyMan]

So I've managed most of the migration.
Devices are available in domoticz.

But how do I replace the devices I had previously? Disabling openzwave caused the devices to be removed from their respective pages. How can I now replace them then?

[waltervl]

With edit - replace. Order is important so try first on an unimportant device.

[MikeyMan]

With edit - replace. Order is important so try first on an unimportant device.

But where is that edit button then?

The 'old' devices are not on the tab with buttons after deactivating the hardware.

[waltervl]

Could be that you can use the replace on the new device. The behavior of the replace function changed a few times.

[MikeyMan]

Could be that you can use the replace on the new device. The behavior of the replace function changed a few times.

So, go to the new device, select edit, replace and select the old device there?

The interface says 'new device'... Bit weird isn't is?

[Gravityz]

No,
go to the old device(the device you want to replace which is not active), press replace and select the new device(which is active)

the new device will get active but with the id of the old device and with the history of the old device

[MikeyMan]

No,
go to the old device(the device you want to replace which is not active), press replace and select the new device(which is active)

the new device will get active but with the id of the old device and with the history of the old device

Like I said, the old device is not on the switches tab anymore after disabling. The devices page under settings doesn't have the replace option anywhere. I'm lost.

[naeblizz]

Hi guys I have big problems getting zwavejs2mqtt to work. Have been trying to get docker-compose running for a few days now but just getting alot of errors when trying to install.
I have docker installed , but get alot of errors when trying installing docker-compose
This is what I get in last part of error
:cwd: /tmp/pip-install-nhnd1mar/cryptography_073380f738914c88877fdcc62ce74f87
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

anyone know what to do to get it working ? tnx
Im running on Rpi3b btw

[waltervl]

Pleasu use the official docker compose installation method. there is no pip in that.
https://docs.docker.com/compose/install/

[Gravityz]

good point.
if you disable the old zwave controller the old devices might greyed out.
not sure how this can be solved.
i would say enable both zwave and zwave-js-ui so the old devices appear and then do the replace thing.

anybody else have any ideas

No,
go to the old device(the device you want to replace which is not active), press replace and select the new device(which is active)

the new device will get active but with the id of the old device and with the history of the old device

Like I said, the old device is not on the switches tab anymore after disabling. The devices page under settings doesn't have the replace option anywhere. I'm lost.