zwavejs2mqtt

[mgugu]

Oké I thought that with autodiscovery the devices were put in the new stick

disappointing because now I have to manually include them again.

Why not using the stick with devices inside ? So no need to re-pair and you can come back to OZW if necessary.

[JuanUil]

Did that indeed, and now system in getting info.
Takes a lot of time?

[mgugu]

It depends on the number of devices, can take some time. Be patient...

[ksacca]

I was not sure if you wanted to keep your existing stick, or use the new one (that's why I asked). I just remembered our discussion from a few days ago, and wanted to be sure which stick you used. Of course you can keep the old stick so you don't have to include new devices!

[JuanUil]

Thnx all system is gathering info now I have 39 devices and 5 have completed now. running 30 minutes now.
I am impressed, switches appear with the old node number included, really nice.
Again thank you for all the help!

[JuanUil]

Is it normal that interviewing is taking such a long time?
39 nodes total 5 completed running more than 1 hour.

[ksacca]

It can take quite some time, depending on the size and quality of your zwave network. Did you check the remaining nodes if they are battery devices? If yes, they will need to be woken up by pressing the button on the device. If not, you can always restart your container and see what happens.

[JuanUil]

woke up the battery nodes
still sticking with 5 devices completed
running 2 hours now

[ksacca]

If possible, try to disconnect the device from mains power (unplug if possible, or turn off the fuse for a few seconds if built into the wall). Had to do the same for a fibaro double switch 2. Sometimes it can help to start the inclusion process (3x click on the button).

[JuanUil]

Just to let you know guys, everything is working oké now.
Did a complete new install and working like charm!
Thnx for all the help.

Just one other question:
I have a Nodon wallswitch. It is seen by zwjs but there are no switches made.
It should at least have 4 switches.
Anybody experience with this wallswitch?

[ksacca]

I don't have any experience with Nodon, but I have something similar (aeotec wallmote quad).

For the devices to appear in domoticz, you will first have to trigger each button on the remote. So press each button once and you should see the devices in domoticz. If the nodon supports double/triple click and hold/release, you will have to trigger those manually too for them to appear in your devices.

[JuanUil]

To bad, In the ozw it worked that way.
Now I only get a battery state device.
Even after allowing new sensors for 5 minutes.
Also in the log I see no activities around the switch.

[ksacca]

When I first tested a few months ago, my wallmote didn't create switches either. With an older version of domoticz, it created utility sensors (found in the utility tab of domoticz). To be sure, go to Setup -> Devices, press a button on your wall switch and sort by "Last Seen" so the most recent is on top. Maybe a device of a different type is created.

If it's not there, you could install MQTT Explorer, connect it to your broker and check the zwave topic if you see any messages when you press the button. Topics where a message is received will flash, so it should be fairly easy to spot. If you see the messages, you can inspect what was sent.
Normally you should also be able to see each button within the zwavejs UI (if you expand the view of your device), and you should be able to see a change when pressing a button.

I also check the zwavejs device database, and could not find any nodon devices (https://devices.zwave-js.io/). But if it's recognized, it should work I suppose.

[JuanUil]

Tried to install the explorer with snapd but get an error.

Code: Select all

pi@pi:~ $ sudo snap install mqtt-explorer
error: snap "mqtt-explorer" is not available on stable for this architecture (armhf) but exists on
       other architectures (amd64).
pi@pi:~ $

Are there anywhere instructions on how to install? I couldn't find it with google

[ksacca]

MQTT Explorer has a visual interface, and you should install it on your computer, not on your pi. You can download it from http://mqtt-explorer.com/.
You could indeed subscribe to the topic from the command line using mosquitto_sub if you know the exact topic for the device, but I would not recommend this.

[JuanUil]

Found this after a restart in my log:

Code: Select all

2022-10-21 12:34:18.245 Status: MQTT: discovered: Wallswitch/Wallswitch_scene_state_scene_001 (unique_id: zwavejs2mqtt_0xd4b25b25_69-91-0-scene-001)
2022-10-21 12:34:18.346 Status: MQTT: discovered: Wallswitch/Wallswitch_scene_state_scene_002 (unique_id: zwavejs2mqtt_0xd4b25b25_69-91-0-scene-002)
2022-10-21 12:34:18.446 Status: MQTT: discovered: Wallswitch/Wallswitch_scene_state_scene_003 (unique_id: zwavejs2mqtt_0xd4b25b25_69-91-0-scene-003)
2022-10-21 12:34:18.547 Status: MQTT: discovered: Wallswitch/Wallswitch_scene_state_scene_004 (unique_id: zwavejs2mqtt_0xd4b25b25_69-91-0-scene-004))

and in the explorer also traffic is noticed where scene 1 is button 1 and so on.
Any idea on how to get switches in domoticz now?

[JuanUil]

So I have made a group in domotcz.
in activating devices I added switch 1
In devices I added a light.

When I press button 1 the bulb only switches on but never off.

[JuanUil]

All of the sudden 4 switches appeared so problem solved!!!

[JuanUil]

After a week struggling, everything works perfect now for allready 2 days.
How have we ever lived with the terrible ozw.
Late response, no correct feedback, crashes a.s.o.
Thnx to all developers!!!

[mgugu]

After a week struggling, everything works perfect now for allready 2 days.
How have we ever lived with the terrible ozw.
Late response, no correct feedback, crashes a.s.o.
Thnx to all developers!!!

Hello Juanuil, happy to see that everything works fine.
I do not share that opinion, i think you are exaggerating the weakness of OZW a bit.
For me OZW has a lot of positive points like a wonderfull graphical GUI, integrated in domoticz, for network, neighbours and groups, high stability and reliability (I have more than 50 connected devices working for years and the few troubles I got were due to the nodes and not to OZW itself).
Today I use both OZW and zwave-js in parallel, and I reserve zwave-js for new devices mainly due to the fact OZW is now deprecated.
In favor of zwave-js I woud say improved facilities for device management and troubleshouting.