zwavejs2mqtt

[BurningTyre]

I upgraded 2 months ago from OZW to zwavejs2mqtt 7.0.0.

I'm very happy with the upgrade, everything reacts much faster.


But today i saw zwavejs2mqtt is renamed to zwave js ui, and there are several new versions released, version 8.4.1 most actual.


How is it possible to upgrade my zwavejs2mqtt 7.00 to the latest version, without any z-wave network information or domoticz z-wave devices are lost.

[waltervl]

I upgraded 2 months ago from OZW to zwavejs2mqtt 7.0.0.

I'm very happy with the upgrade, everything reacts much faster.


But today i saw zwavejs2mqtt is renamed to zwave js ui, and there are several new versions released, version 8.4.1 most actual.


How is it possible to upgrade my zwavejs2mqtt 7.00 to the latest version, without any z-wave network information or domoticz z-wave devices are lost.

Check this thread for some hints viewtopic.php?t=39138

[jberinga]

When doing a restart of Domoticz, switching Z-wave devices isn't working.
But when I am saving the configuration (without making any changes) on the Z-wave JS UI webpage, the Z-wave devices can be turned on\off again.

Any idea why this is happening and how I can keep the switching of Z-wave devices working after a restart of Domoticz?

Domoticz, Z-Wave JS UI and eclipse-mosquitto are running in their own Docker container on my Synolgy NAS.

[jake]

When doing a restart of Domoticz, switching Z-wave devices isn't working.
But when I am saving the configuration (without making any changes) on the Z-wave JS UI webpage, the Z-wave devices can be turned on\off again.

Any idea why this is happening and how I can keep the switching of Z-wave devices working after a restart of Domoticz?

Domoticz, Z-Wave JS UI and eclipse-mosquitto are running in their own Docker container on my Synolgy NAS.

Check in zwave-js at the home assistant settings page: retained discovery is enabled

[nigels0]

Is it possible to put battery status switches in Utility rather than Switches?

[jberinga]

When doing a restart of Domoticz, switching Z-wave devices isn't working.
But when I am saving the configuration (without making any changes) on the Z-wave JS UI webpage, the Z-wave devices can be turned on\off again.

Any idea why this is happening and how I can keep the switching of Z-wave devices working after a restart of Domoticz?

Domoticz, Z-Wave JS UI and eclipse-mosquitto are running in their own Docker container on my Synolgy NAS.

Check in zwave-js at the home assistant settings page: retained discovery is enabled

Just enabled this setting.

Thanks for letting me know!

[BurningTyre]

I have troubles installing Docker-Compose to get zwavejs2mqtt docker container working.

I have started with a fresh sd-card image (Bullseye).

Im using following code to install docker-compose.

Code: Select all

sudo pip3 install docker-compose

But it keeps stopping with the following error:



I already installed Rust (with Rustup), already did pip install --upgrade pip.



I'm totally lost what i can try or do anymore to get Docker-Compose installed.

[Doler]

Docker-compose is part of your Docker install but you must use it as 'docker compose' (without the '-').

[rasper]

I already installed Rust (with Rustup), already did pip install --upgrade pip.



I'm totally lost what i can try or do anymore to get Docker-Compose installed.

try

Code: Select all

 pip3 install setuptools_rust docker-compose

[ferrosk]

I'm totally lost what i can try or do anymore to get Docker-Compose installed.

You can install docker-compose binary from Docker Compose github repository.

Example installing current version (v2.13.0) for your platform (armv7l):

Code: Select all

sudo curl -L https://github.com/docker/compose/releases/download/v2.13.0/docker-compose-linux-armv7 -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose

Code: Select all

$ docker-compose version
Docker Compose version v2.13.0

[BurningTyre]

I'm totally lost what i can try or do anymore to get Docker-Compose installed.

You can install docker-compose binary from Docker Compose github repository.

Example installing current version (v2.13.0) for your platform (armv7l):

Code: Select all

sudo curl -L https://github.com/docker/compose/releases/download/v2.13.0/docker-compose-linux-armv7 -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose

Code: Select all

$ docker-compose version
Docker Compose version v2.13.0

Thanks this did the trick!
Maybe this can be added to the Wiki page? Otherwise i wasn't still be able to install Docker Compose on my RPI.

[waltervl]

The wiki links to the official installation of docker compose https://docs.docker.com/compose/install/linux/
There is no mention of using pip3 so no idea why you used this in the past.

[djdevil]

i did the update yesterday with the addition of zwavejuis but once it deletes the devices i don't want to use on restart they are recreated again! how come this happens? then if I restart and turn on a light manually it is not updated on domoticz in real time also I noticed that the energy devices do not report the Khw but they are electrical entities! I hope someone can help me thanks

[Nautilus]

Hi,
have a bit strange issue. Domoticz seems to get a wrong status from zwajejs2mqtt, but it does not look like it is coming from the bridge. I installed HA to track how it receives the status via mqtt and this reflects the "reality" (turned on at 02:01, turned off at 07:00):

node status in ha.JPG (31.75 KiB) Viewed 1547 times

(I know this is correct as this switch is controlling a water heater which temperature I am tracking as well, and I can see it heated until 7AM)

But for some reason Domoticz sees it like this (turned on at 02:01, turned off at 04:32):

node status in dz.JPG (35.78 KiB) Viewed 1547 times

...to me it looks like that this is coming from mqtt (zwave autodiscovery is the hardware component for zwavejs2mqtt)

What could cause this and is there any meaningful way to try to troubleshoot it?

[waltervl]

Check the MQTT message with mqtt-explorer, see https://www.domoticz.com/wiki/MQTT#Debugging_MQTT
Check also the domoticz log (menu setup - log). You perhaps have to set it to a file log: https://www.domoticz.com/wiki/Troublesh ... bugging.29

[JuanUil]

Hi all,

after a cou[ple of weeks without any problem and a verry good respons of my z-wave devices with zwave-js-ui, this week I had a supurb crash!
For some reason mqtt broker mosquitto failed to connect.
Probally it was my own fault because I was experimenting with some things.
Anyway, I made a fresh install, put in my Aeotec z-wave stick, reloaded my database and started again.
But......
As you can see in the picture below z-wave-js is not collecting all the info of the nodes.
Manufacturer, Product and Product stay as UNKNOW.
More serious is that for multi sensors only motion, battery level and low level battery switches are recognized.
See node 2 which is a pir with motion, lux, temp and battery.
Here lux and temp are NOT created!
I added this node as a new node by the way



anybody any idea?
Jan

[Nautilus]

Check the MQTT message with mqtt-explorer, see https://www.domoticz.com/wiki/MQTT#Debugging_MQTT
Check also the domoticz log (menu setup - log). You perhaps have to set it to a file log: https://www.domoticz.com/wiki/Troublesh ... bugging.29

Thanks for the suggestions. I haven't found any meaningful info yet. The recorder is a nice option which I did not know before this. It just seems I cannot set it up to filter just relevant messages. Seems I am getting quite a lot of traffic through mqtt I wonder if it is expected that zigbee2mqtt is publishing groups, config etc. every second. Also my Tasmota devices advertise every second. Zwavejs2mqtt does not seem to behave like this.

Anyhow, as the automatic heating takes place during night, I will hold of for now to keep the recorder on for several hour. I took a short recording when I was flipping the switch manually, but as expected the switch operated normally in this test so probably this does not tell anything intersting:

Code: Select all

2022-12-16T16:11:59+0200        1       zwave/43/112/0/1        {"time":1653889406928,"value":255,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/3        {"time":1653889406930,"value":0,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/4        {"time":1653889406932,"value":0,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/6        {"time":1653889406934,"value":0,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/13       {"time":1653889406936,"value":0,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/14       {"time":1653889406937,"value":1,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/15       {"time":1653889406938,"value":0,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/16       {"time":1653889406940,"value":1,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/30       {"time":1653889406941,"value":3,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/31       {"time":1653889406943,"value":2,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/32       {"time":1653889406944,"value":3,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/33       {"time":1653889406946,"value":1,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/112/0/39       {"time":1653889406948,"value":600,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/114/0/manufacturerId   {"time":1653889406949,"value":271,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/114/0/productType      {"time":1653889406950,"value":1026,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/114/0/productId        {"time":1653889406952,"value":4098,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/134/0/libraryType      {"time":1653889406953,"value":3,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/134/0/protocolVersion  {"time":1653889406955,"value":"3.52","nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/134/0/firmwareVersions {"time":1653889406956,"value":["2.2"],"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/37/1/currentValue      {"time":1653889406976,"value":false,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/37/1/targetValue       {"time":1653889406977,"value":false,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/37/2/currentValue      {"time":1653889406990,"value":false,"nodeName":"Lämminvesivaraaja","nodeLocation":""}
2022-12-16T16:11:59+0200        1       zwave/43/37/2/targetValue       {"time":1653889406991,"value":false,"nodeName":"Lämminvesivaraaja","nodeLocation":""}

[red59]

Hello,
I have something strange and didn t fond anything on third, i have upadated zwave-js-ui: to 8.9.0.2d95700, and now my fibaro door sensor fgw002 no more reports the state (open or Close) in binary mode
Now the type of sensor_notification_access_control_door_state is sensor and reports in text.
But before it was binary_sensor_door_state and was reporting as binary_sensor. Do you know why ? Is it a bug ??, i find it very disappointing because in domoticz binary sensor are easier to use.. do you have same behaviour ?
Thanks for your help

Regards

[MikeyMan]

So, after finally going from OZW to ZwaveJS... A couple of findings:

- First time it took long (i mean loooong) to get all devices in. Re interviewing it through ZwaveJS did help a bit. Maybe after installing the re-interviewing should always run? Or add a re-interview everything option.
- The IDX-es are now not in order anymore. Not really an issue, but tickles my OCD a bit.
- I do see that sometimes there is a discrepancy between the light and the domoticz dashboard. This is really a flaw in the way MQTT works. Domotics shows the last received status. Not the actual status. OpenZwave did a better job with that.
- I am having some difficulties sometimes with devices being unavailable. Difficult to find out where that is going wrong. The web server of ZwaveJS is running while that happens.

All together not 100% happy compared to what i was used to with OpenZwave tbh.

[mgugu]

All together not 100% happy compared to what i was used to with OpenZwave tbh.

Yes, we should not underestimate the amount of work needed to migrate from OZW to zwaveJS-ui because, as they say, the devil is in the details.
For simple components (lights, switches) it can be quite smooth, for more complex components (sensors, thermostats,...) it can be much more difficult and reserve some bad surprises like for example the need to make specific scripts to work around bugs or differences in operation.
For my part, I consider that zwavejs-ui has not yet reached the level of maturity of OZW in its latest developments.