OpenZwave weird behaviour

[Patricen]

Hello,

I do have some roller shutters that are programmed to open with a timer.
At set time the open command is sent then a close command is sent by OpenZwave.
Do you have any suggestion regarding this issue?

[waltervl]

It could be that the open command is not being accepted/received by the device and it reports back its closed status in Domoticz.
Do you see the blind go open when triggered by the timer?

By the way you are using OpenZwave which will be remove from the next stable release!! You will have to move to Zwave-JS-UI very quickly
https://www.domoticz.com/wiki/Zwave

[Patricen]

It could be that the open command is not being accepted/received by the device and it reports back its closed status in Domoticz.
Do you see the blind go open when triggered by the timer?

By the way you are using OpenZwave which will be remove from the next stable release!! You will have to move to Zwave-JS-UI very quickly
https://www.domoticz.com/wiki/Zwave

Hello,

Yes, I know that OZW is becoming outdated, but I don't have any simple tutorial to switch to Zwave-JS-UI. Is there a simple way proceeding to this migration?

[waltervl]

See the wiki: https://www.domoticz.com/wiki/Zwave-JS- ... _OpenZwave

[Patricen]

Oh...

Never succeeded to build a docker file maybe can I get help.
wiki shows :

Code: Select all

git clone https://github.com/zwave-js/zwave-js-ui.git
cd zwave-js-ui
git checkout -b [the branch that you want] [b]What should I specify there?[/b]
docker build -f docker/Dockerfile -t zwavejs/zwave-js-ui:latest [b]What should be "Dockerfile"[/b]

[waltervl]

You don't have to build it, just use it
https://zwave-js.github.io/zwave-js-ui/ ... ted/docker

[gizmocuz]

And it's "docker compose" you want to use, so you need to use the 'docker-compose.yml' file from the above link

[Patricen]

Ok thanks,

I have to go further in details as Docker is pretty new for me.

[Patricen]

Hello

I've managed to install Z-Wave-JS using docker.
The issue I'm encountering is that there is no devices discovered. I have selected the right usb port -onlu the port number is displayed in the drop-down menu, no serial by id name.

The following warning appears on the trace "Z-Wave-JS driver is not ready yet"
I'm using a Z-wave.me UZB1 stick.

Do you know how to solve this issue?
Thanks

[waltervl]

What is in your docker compose file in section devices.
Should be something like below. Change /dev/serial/by-id/insert_stick_reference_here into the real name on you system.
Do the following command in a terminal window to find the correct USB name

Code: Select all

ls -lah /dev/serial/by-id

devices section Docker compose Zwave-JS-UI

Code: Select all

        devices:
            # Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
            # Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
            - '/dev/serial/by-id/insert_stick_reference_here:/dev/zwave'

[Patricen]

Hello,
I did modify Docker compose file, but still encounter an error.
I have stopped Domoticz to be sure it is not connected to the zwave stick, restarted Zwave-JS-ui but still have the error from attached image.

I tried both /dev/serial/by-id/usb-0658_0200-if00:/dev/zwave and /dev/serial/by-id/usb-0658_0200-if00 within the ZWave section of GUI.
The directory looks to be the right one? Maybe access rights?

[gizmocuz]

Try following the updated guide, this is working

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

[BartSr]

does the debian version matters?

[Patricen]

Try following the updated guide, this is working

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

Brilliant! I now do have MQTT and ZWave-JS-UI that works, but no connection to Domoticz using "MQTT Auto Discovery Client Gateway with LAN interface". I did not use neither localhost nor 127.0.0.1, the only thing that looks strange to me is TLS that I can't disable from dropdown menu.

The issue is in between MQTT broker and Domoticz as I can access messages using MQTT explorer utility.

It looks like MQTT Auto Discovery Client Gateway with LAN interface is the right hardware to use as it is the only MQTT auto discovery hardware available (version 2023.2).

[gizmocuz]

Choose TLSv2 for secured connections (port 8883) or use the default when you connect to port 1883
can you connect with MQTT Explorer?

[Patricen]

Hello,
Yes, MQTT explorer shows results

[Patricen]

Ok! Nothing shows-up within the configuration screen but devices are discovered.
Looks like there is no pending issue.
What is the usage of config screen then?

[Patricen]

So,
The Domoticz device list was populated with devices named as "node_IDXX_", I then decided to give a name to each device within ZW2JSUI, remove the MQTT discovered devices in Domoticz and allow new devices to have the list populated with real names.

The issue is that the devices are not coming back. Is there something to purge in Mosquitto or any other trick to proceed?

[akamming]

Go to settings in zwave js ui and click on save, that will force resending the Discovery messages

[Patricen]

Great, thanks !
That works perfectly, as well as 2024.1 update. So far it looks more reliable than OZW.
Is there a Zigbee-JS-UI that would replace deConz?