zwavejs2mqtt

[heggink]

Autodiscovery is still beta so it's to be expected that there may be bugs.
The best way to get these resolved is to list the switch type as well as the autodiscovery topic and message so that we can figure out what's not working.

Sent from my SM-G980F using Tapatalk

[hestia]

For instance
Qubino Flush Dimmer Plus ZMNHDD
[59-134-0-protocolVersion] Z-Wave protocol version: 4.5
[59-134-0-firmwareVersions] Z-Wave chip firmware versions: ["3.5","3.5"]
[59-134-0-hardwareVersion] Z-Wave chip hardware version: 4
When I switched the real switch (in the wall), the light switched on/off in real and in the dz GUI (dimmer), but I've got NO trigger (with a dzVents script)
When I switched the switch with dz GUI (dimmer), the light switched on/off in real and in the dz GUI, I've got a log like

Code: Select all

2021-12-02 20:59:10.911 Status: User: admhestia (IP: 192.168.9.201) initiated a switch command (2000/Allée Dim/On

but I've got NO trigger (with a dzVents script)
I was simply thinking that the trigger to dzvents was directly due to the on/off!

[heggink]

I think other people have reported issues with qbino switches as well.

Sent from my SM-G980F using Tapatalk

[solarboy]

Z wave is looking more and more like a dead end as there is no confirmed solid development going forward ; half promises and vague possibilities are not really any use to anyone. It's a shame, personally I spent about 1500€ on hardware over the last 3 years as well as the inevitable problems of e-waste.
However, thanks heggink for your efforts to move things to a newer better paradigm, definitely appreciated by me and hopefully someone can pick up the baton so to speak.

[heggink]

All is not lost. Here's my simplistic view: there's few new zwave devices entering the market so having a solution that works really well with the status quo will do fine for the foreseeable future. To me, that is zwavejs2mqtt running in a docker container. I have not updated it for quite a while as it is stable and functional. We need to iron out the last remaining bugs from the domoticz autodiscovery but then that's also rock solid.

Meanwhile, I have been slowly transitioning some devices into zigbee2mqtt. Devices are cheaper and functional enough. I keep enough zwave around for a functioning mesh and for certain functionality (since zwave does stuff that zigbee just can't) but the rest all goes into zigbee.

Sweet and simple IMHO. Meanwhile, we can figure out whether we need future support for zwave different from the domoticz autodiscovery. That will take time but as long as I have a functioning zwavejs2mqtt docker, no issues. Everything is rock solid so far.

Sent from my SM-G980F using Tapatalk

[solarboy]

All is not lost. Here's my simplistic view: there's few new zwave devices entering the market so having a solution that works really well with the status quo will do fine for the foreseeable future. To me, that is zwavejs2mqtt running in a docker container. I have not updated it for quite a while as it is stable and functional. We need to iron out the last remaining bugs from the domoticz autodiscovery but then that's also rock solid.

Meanwhile, I have been slowly transitioning some devices into zigbee2mqtt. Devices are cheaper and functional enough. I keep enough zwave around for a functioning mesh and for certain functionality (since zwave does stuff that zigbee just can't) but the rest all goes into zigbee.

Sweet and simple IMHO. Meanwhile, we can figure out whether we need future support for zwave different from the domoticz autodiscovery. That will take time but as long as I have a functioning zwavejs2mqtt docker, no issues. Everything is rock solid so far.

Sent from my SM-G980F using Tapatalk

That's a good strategy really, I too am only buying Zigbee now so keeping a basic Zwave mesh going is to be my priority.

[heggink]

Agreed. Having been on domoticz for an eternity now (started of on a Pi2 looong long time ago). My first devices were a combination of shitty KAKU 433Mhz devices, old Legrand 433Mhz based switches (for which I hot rfxcom and domoticz adapted) and my first zwave devices.

Since then, I kicked out all the legrand stuff because it was end of life and started to fail, then I removed all the KAKU devices since they could not be polled and there was no guaranteed delivery. Switched most onto zwave. Added a bunch of wifi devices, added Nuki locks (and wrote the python plugin) and so on/forth.

Point being that we can discuss support and longevity ad nauseam but 1) nothing lasts forever, 2) the best system on paper isn't always the one that survives (V2000) so deal with it, 3) pragmatism keeps stuff working and 4) open source means we ALL need to contribute. I am an old (57yo) C programmer who has gone off to the dark side into sales and marketing (CCO for a software company, not done any professional programming for nearly 30 years). I know f#$%@ all about C++ or python but a little digging here and there ensures that even I can make a small contribution here and there. There's other people out there (Rob, Jos, Morten, Dnpwwo) who are infinitely better than what I do but if we all help just a little, things will be better .

[hestia]

I think other people have reported issues with qbino switches as well.

I've done testing on the 4 Fibaro switches I've got (3 dimmers and 1 on/off)
The On/Off from the wall worked and the trigger also.
For the Qubino, it seemed to work on on/off switch, not dimmers and I have a lot of dimmers.
I didn't find reports regarding issues with Qubino... neither work on it

[rron]

Hello,

I'm a little stuck on the configuration with the zwavejs2mqtt plugin. I have set up a new rpi4 with a new aeotec zw090 gen 5 stick.In the control panel I can see the stick is available. Then I want to include the zwave nodes from my network.In the control panel I click on the action tab and the manage node. The node manager opens and then click on next 2x inclusion is started, put your device in inclusion mode.
The only way to put my stick in inclusion mode is to disconnect the stick from the usb port. I a do this and put the stick in inclusion mode and put it back in the usb port the stick goes out of inclusion. What am I doing wrong?

[solarboy]

Hello,

I'm a little stuck on the configuration with the zwavejs2mqtt plugin. I have set up a new rpi4 with a new aeotec zw090 gen 5 stick.In the control panel I can see the stick is available. Then I want to include the zwave nodes from my network.In the control panel I click on the action tab and the manage node. The node manager opens and then click on next 2x inclusion is started, put your device in inclusion mode.
The only way to put my stick in inclusion mode is to disconnect the stick from the usb port. I a do this and put the stick in inclusion mode and put it back in the usb port the stick goes out of inclusion. What am I doing wrong?

I rarely "include" from within Domoticz, I find it best to stop Domoticz, remove the stick and use the button on the stick to include the new device in situ, then re-insert the stick and restart Domoticz.

[rron]

Is that the best way to this ? This one is a spare stick and is complete empty. In my production I have one completly functional.Is it possibble to copy the file into the new one?

[mgugu]

Yes, at least for Aeotec (Zensys) components. I use this tool https://help.aeotec.com/support/solutio ... p-software for a long time to make my backups on a spare stick. Never problem

[heggink]

Hey rron,

When you include from zwavejs2mqtt, how close to the stick is the device you are trying to include? I have noticed in the past that being too far away leads to issues so the closer, the better but a few metres should work fine.

Also, many people have reported including through the stick itself (talking it out, including close to the device and reinserting). I have not done that myself so cannot confirm but others have. Once you have done that, you still need to rename and/or reconfigure in zwavejs2mqtt. What may help you is that I have configured the udev system to call a script when the stick gets inserted of removed where it stops and restarts the zwavejs2mqtt docker container. Let me know if you are interested. It's quite simple.

Finally, if you production stick is of the same type the there is a Windows utility that lets you copy the entire content of one stick onto the other making a complete backup (you export everything into a fine that you can then copy back at will when needed). As long as the security keys are the same, you should have an exact copy. I forgot what is called but a little googling will come a long way.

Sent from my SM-G980F using Tapatalk

[heggink]

Yes, at least for Aeotec (Zensys) components. I use this tool https://help.aeotec.com/support/solutio ... p-software for a long time to make my backups on a spare stick. Never problem

That's what I use as well. Great tool.

Sent from my SM-G980F using Tapatalk

[mgugu]

Yep, and its companion is zensys tool https://assistance.domadoo.com/article/ ... -2555.html to make all is not possible directly with OZW.

[rron]

Thanks for both your explanations. I will try to copy first. Both sticks are the same so that should work.
@ Herman, I also like the script from you. I will try this tomorrow, will be away today.

[heggink]

For those interested in restarting/stopping zwave/zigbee2mqtt on device removal/insert, here are a couple of sample scripts/configs that I use for my zzh and aeotec gen5 usb sticks (you need to change the vendor and product Id's to match your device using lsusb):

in /etc/udev/rules.d/99-some-filename-u-can-choose-yourself:

Code: Select all

SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", SYMLINK+="ttyUSB.zzh"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="ttyUSB.aeotec"
ACTION=="add", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SUBSYSTEM=="usb", PROGRAM="/usr/local/bin/add_aeotec.sh"
ACTION=="remove", ENV{ID_MODEL}=="0200", ENV{ID_VENDOR}=="0658", PROGRAM="/usr/local/bin/rem_aeotec.sh"
ACTION=="add", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", SUBSYSTEM=="usb", PROGRAM="/usr/local/bin/add_zzh.sh"
ACTION=="remove", ENV{ID_MODEL}=="7523", ENV{ID_VENDOR}=="1a86", PROGRAM="/usr/local/bin/rem_zzh.sh"

Then create an executable script (chmod +x) in /usr/local/bin/add_zzh.sh

Code: Select all

#!/bin/sh
LOCK=/tmp/lockfile_zzh

if [ -f $LOCK ]; then
   logger zzh lock exists
   exit 1
else
   touch $LOCK;
   logger zzh lock created
   # the actual command to run upon USB plug in
   sleep 2 && sudo docker restart zigbee2mqtt
   logger zzh added and zigbee2mqtt restarted
fi

And similarly for rem_zzh.sh:

Code: Select all

#!/bin/sh
LOCK=/tmp/lockfile_zzh
logger removing zzh lock
if [ -f $LOCK ]; then
   rm $LOCK
   sudo docker stop zigbee2mqtt
fi

Do something similar for any other stick you have (aeotec, rfxcom, ...).

[rron]

It's working now. I only get a failure message in domoticz:

Code: Select all

2021-12-12 15:18:24.900 Error: MQTT: MQTT_Discovery: Invalid/Unhandled data received! (Topic: 3/status, Message: {"time":1639318704896,"value":true,"status":"Asleep","nodeId":3}

[heggink]

You can ignore it

Sent from my SM-G980F using Tapatalk

[rron]

Ok, i will do this.