Domoticz

Posted: **Tuesday 28 September 2021 10:24**

I need some help because the Vision ZD2102-5 door and windows sensor are not reporting the actual status. The ZwaveJS to MQTT panel is indication the open/close status but it will not be mentioned by the Domoticz GUI. Any ideas? All switches and Motion sensors are reporting quite well.

Posted: **Friday 08 October 2021 19:53**

Hi updated Domoticz to beta 2021.1 with build 13689 and installed Zwavejs2mqtt (docker) describe here : https://github.com/moroen/ZWave-MQTT-plugin

Beause I am using the latest beta I do not need the plugin installed, correct me if I am wrong.

Because I using an Security key in Domoticz I think I have to use the same key in the Zwavejs2mqtt GUI in the field : S0_legacy

What about the other 3 fields for S2 do I have to use the same S0 key over there or just one of the fields, which one?

Do I have to restart Domoticz every time if I change something in the Zwave2mqtt GUI?
Do I have to configure something under Hardware (Domoticz)?

Thanks

Posted: **Friday 08 October 2021 20:30**

You still would need a MQTT broker like Mosquito https://www.domoticz.com/wiki/MQTT

Posted: **Friday 08 October 2021 21:12**

Just read this, a commit from a few days ago.
https://github.com/zwave-js/zwavejs2mqt ... 463d1a3b34
Attention to: "I don't plan to keep it maintained in the future."

Posted: **Saturday 09 October 2021 0:46**

For now, it works really well. Let's see about that future. Maybe someone can help build native support for zwavejs2mqtt. If not then we can always revert to the plugin. It looks like both HA and zigbee2mqtt support the autodiscovery. If people use it with zwavejs2mqtt, maybe someone else is willing to maintain.

Choices...

Sent from my SM-G980F using Tapatalk

Posted: **Saturday 09 October 2021 0:55**

EddyG wrote: ↑Friday 08 October 2021 21:12 Just read this, a commit from a few days ago.
https://github.com/zwave-js/zwavejs2mqt ... 463d1a3b34
Attention to: "I don't plan to keep it maintained in the future."

Owch, one door opens, another closes, then both doors close lol

Posted: **Saturday 09 October 2021 9:06**

Already have an MQTT server running because of zigbee2mqtt and because in my case OpenZwave is not stable I want to switch to Zwavejs2mqtt maybe but it is not clear what is the best way to proceed for now?
Installed already an broker (mosquitto) and now also zwavejs2mqtt but how to integrate?
I tough is just filling in S0 or S2 and restart Domoticz, without the plugin, I am confused now?

Posted: **Saturday 09 October 2021 9:11**

I don't understand your question but moved from ozw to zwavejs2mqtt myself. Send me a PM and I will try to help

Sent from my SM-G980F using Tapatalk

Posted: **Saturday 09 October 2021 10:08**

solarboy wrote:
EddyG wrote: ↑Friday 08 October 2021 21:12 Just read this, a commit from a few days ago.
https://github.com/zwave-js/zwavejs2mqt ... 463d1a3b34
Attention to: "I don't plan to keep it maintained in the future."
Owch, one door opens, another closes, then both doors close lol

Not sure what you mean with that. There are different mqtt based systems that support autodiscovery where zwavejs2mqtt and zigbee2mqtt are the ones with the biggest device support. Both offer autodiscovery as well as native home assistant integration. One of them, zwavejs2mqtt, intends to not maintain autodiscovery in "the future"but the rest have not expressed anything in that direction. IF the developer of zwavejs2mqtt stops maintenance on autodiscovery (and only that piece) THEN that could be an issue BUT that does not mean that it will not work anymore, just that it's not maintained by that developer. And maybe someone else will pick that up since it's open source after all.

Personally, I don't think it's a worry since I hardly extend my zwave stuff and mostly add zigbee services so maintenance is not required at all as long as nothing is desupported (of which there is no mention). But that may not be workable for other people.

Sent from my SM-G980F using Tapatalk

Posted: **Saturday 09 October 2021 20:16**

And if Domoticz will also support MQTT autodiscovery there is a bigger user group for autodiscovery so perhaps the zwavejs2mqtt maintainers will reconsider their decision...

Posted: **Monday 11 October 2021 15:31**

First mistake I made both OZW and Zwavejs2mqtt was running so I stopped OZW
Now If I use mosquitto_sub -h 192.168.2.57 -q 1 -v -u mqtt_user -P Just4testing -t homeassistant/#
I see :

Code: Select all

homeassistant/56/50/0/value/66817 {"id":"56-50-0-value-66817","nodeId":56,"commandClass":50,"commandClassName":"Meter","endpoint":0,"property":"value","propertyName":"value","propertyKey":66817,"propertyKeyName":"Electric_A_Consumed","type":"number","readable":true,"writeable":false,"label":"Electric Consumption [A]","ccSpecific":{"meterType":1,"rateType":1,"scale":5},"stateless":false,"unit":"A","list":false,"value":0.03,"lastUpdate":1633958282042,"nodeName":"","nodeLocation":""}
homeassistant/55/50/0/value/66561 {"id":"55-50-0-value-66561","nodeId":55,"commandClass":50,"commandClassName":"Meter","endpoint":0,"property":"value","propertyName":"value","propertyKey":66561,"propertyKeyName":"Electric_V_Consumed","type":"number","readable":true,"writeable":false,"label":"Electric Consumption [V]","ccSpecific":{"meterType":1,"rateType":1,"scale":4},"stateless":false,"unit":"V","list":false,"value":236.27,"lastUpdate":1633958282460,"nodeName":"","nodeLocation":""}
homeassistant/55/50/0/value/66817 {"id":"55-50-0-value-66817","nodeId":55,"commandClass":50,"commandClassName":"Meter","endpoint":0,"property":"value","propertyName":"value","propertyKey":66817,"propertyKeyName":"Electric_A_Consumed","type":"number","readable":true,"writeable":false,"label":"Electric Consumption [A]","ccSpecific":{"meterType":1,"rateType":1,"scale":5},"stateless":false,"unit":"A","list":false,"value":0.78,"lastUpdate":1633958283146,"nodeName":"","nodeLocation":""}

But no devices are discovered in Domoticz, why not?
Settings in the GUI are :

: BROM_08 2021-10-11 15.20.gif (33.87 KiB) Viewed 1788 times

Under : Z-Wave : I have my /dev/ttyUSB-ZWAVE to my USB stick and under "S0 Legacy" my key I used under OZW

Under : Home Assistant : I have selected MQTT Discovery I tried it also with WS Server or both

Do I have to do also something in Domoticz what do I forget or wrong?
How is autodiscovery working under Domoticz?

Posted: **Monday 11 October 2021 15:55**

Do you also see the config message when you check the mqtt server with MQTT-Explorer ?

Posted: **Monday 11 October 2021 16:20**

@jvdz the same as with mosquitto_sub depends on what I select in the GUI under Gateway.

Are my settings ok, have set my prefix to homeassistant? Maybe it has to be Domoticz/homeassistant or something else?

Posted: **Monday 11 October 2021 16:25**

I have payload type as JSON Time-Value.
You also want to switch retain off since that will keep the last message in the mqtt broker (so old message will continue to exist after you deleted a device recrearting that device until you manually delete the message).

your autodiscovery prefix can be anything as long as you use the same in domoticz and zwavejs. I would just use something like homeassistant or zwaveauto or ...

Posted: **Monday 11 October 2021 16:27**

have you installed mqtt explorer? That is a lot easier to see all broker messages than mosquitto_sub.
Also, do all your devices now show up correctly in zwavejs?

If your devices are all correctly in zwavejs, check if all devices are sent to the broker on the autodiscovery topic you configured

if they are all there as well, domoyticz should pick them up.

Posted: **Monday 11 October 2021 16:44**

brommetje wrote: ↑Monday 11 October 2021 16:20 @jvdz the same as with mosquitto_sub depends on what I select in the GUI under Gateway.

Are my settings ok, have set my prefix to homeassistant? Maybe it has to be Domoticz/homeassistant or something else?

We know when you tell us which MQTT message you see for homeassist.... so do you see config messages there as well as the shown message is only a status update message.
Also do you see discovery messages in the domoticz log?

Posted: **Tuesday 12 October 2021 13:17**

heggink wrote: ↑Saturday 09 October 2021 10:08
solarboy wrote:
EddyG wrote: ↑Friday 08 October 2021 21:12 Just read this, a commit from a few days ago.
https://github.com/zwave-js/zwavejs2mqt ... 463d1a3b34
Attention to: "I don't plan to keep it maintained in the future."
Owch, one door opens, another closes, then both doors close lol
Not sure what you mean with that.
Sent from my SM-G980F using Tapatalk

To clarify, I am still on an old version of Domoticz (possibly like many others) due to the Openzwave 1.6 issues including lack of development going forward. I was very interested in the zwave2mqtt plugin you had proposed but I thought I would wait a couple of months to see how it all panned out, and then the mqtt autodiscovery developments proposed for the new versions of Domoticz appeared to supersede the need for the plugin which is fantastic for users such as myself who are heavily invested in zwave (when I started with Domoticz Zigbee was pretty much absent). Now with the news that the developers of zwave2mqtt do not intend to maintain the code and as present I have not heard of anyone else taking up the mantle, my comment was a light-hearted way of expressing my (perhaps unique and naive) feelings regarding zwave (on any platform).

Posted: **Tuesday 12 October 2021 15:03**

We know when you tell us which MQTT message you see for homeassist.... so do you see config messages there as well as the shown message is only a status update message.
Also do you see discovery messages in the domoticz log

First mistake I made was that you you have to fill in the Auto Discovery Prefix: under Hardware and MQTT client setup in my example I use : zwave
In domoticz.log I see

Code: Select all

2021-10-12 14:38:23.255  Status: MQTT-DOPEY: discovered: Overloop_Rook/Overloop_Rook_temperature_air (unique_id: zwavejs2mqtt_0xff3b0602_61-49-0-Air_temperature)
2021-10-12 14:38:23.256  Status: MQTT-DOPEY: discovered: Overloop_Rook/Overloop_Rook_smoke_alarm (unique_id: zwavejs2mqtt_0xff3b0602_61-113-0-Smoke_Alarm-Sensor_status)
2021-10-12 14:38:23.258  Status: MQTT-DOPEY: discovered: Overloop_Rook/Overloop_Rook_alarm_status (unique_id: zwavejs2mqtt_0xff3b0602_61-113-0-Smoke_Alarm-Alarm_status)
2021-10-12 14:38:23.360  Status: MQTT-DOPEY: discovered: Overloop_Rook/Overloop_Rook_heat_sensor_status (unique_id: zwavejs2mqtt_0xff3b0602_61-113-0-Heat_Alarm-Heat_sensor_status)
2021-10-12 14:38:23.362  Status: MQTT-DOPEY: discovered: Overloop_Rook/Overloop_Rook_cover_status (unique_id: zwavejs2mqtt_0xff3b0602_61-113-0-Home_Security-Cover_status)
2021-10-12 14:38:23.364  Status: MQTT-DOPEY: discovered: Overloop_Rook/Overloop_Rook_hardware_status (unique_id: zwavejs2mqtt_0xff3b0602_61-113-0-System-Hardware_status)
2021-10-12 14:38:24.480  Status: MQTT-DOPEY: discovered: ZW117_Slaapkamer/ZW117_Slaapkamer_rgb_dimmer (unique_id: zwavejs2mqtt_0xff3b0602_52-51-0-currentColor)
2021-10-12 14:38:25.293  Status: MQTT-DOPEY: discovered: PowerPlug DC/PowerPlug DC_switch (unique_id: zwavejs2mqtt_0xff3b0602_55-37-0-currentValue)
2021-10-12 14:38:25.294  Status: MQTT-DOPEY: discovered: PowerPlug DC/PowerPlug DC_electric_kwh_value (unique_id: zwavejs2mqtt_0xff3b0602_55-50-0-value-65537)
2021-10-12 14:38:25.294  Status: MQTT-DOPEY: discovered: PowerPlug DC/PowerPlug DC_electric_w_value (unique_id: zwavejs2mqtt_0xff3b0602_55-50-0-value-66049)
2021-10-12 14:38:25.395  Status: MQTT-DOPEY: discovered: PowerPlug DC/PowerPlug DC_electric_a_value (unique_id: zwavejs2mqtt_0xff3b0602_55-50-0-value-66817)
2021-10-12 14:38:25.395  Status: MQTT-DOPEY: discovered: PowerPlug DC/PowerPlug DC_electric_v_value (unique_id: zwavejs2mqtt_0xff3b0602_55-50-0-value-66561)
2021-10-12 14:38:26.305  Status: MQTT-DOPEY: discovered: nodeID_56/nodeID_56_switch (unique_id: zwavejs2mqtt_0xff3b0602_56-37-0-currentValue)
2021-10-12 14:38:26.306  Status: MQTT-DOPEY: discovered: nodeID_56/nodeID_56_electric_kwh_value (unique_id: zwavejs2mqtt_0xff3b0602_56-50-0-value-65537)
2021-10-12 14:38:26.307  Status: MQTT-DOPEY: discovered: nodeID_56/nodeID_56_electric_v_value (unique_id: zwavejs2mqtt_0xff3b0602_56-50-0-value-66561)
2021-10-12 14:38:26.308  Status: MQTT-DOPEY: discovered: nodeID_56/nodeID_56_electric_a_value (unique_id: zwavejs2mqtt_0xff3b0602_56-50-0-value-66817)
2021-10-12 14:38:26.408  Status: MQTT-DOPEY: discovered: nodeID_56/nodeID_56_electric_w_value (unique_id: zwavejs2mqtt_0xff3b0602_56-50-0-value-66049)
2021-10-12 14:38:55.152  Status: MQTT-DOPEY: discovered: nodeID_64/nodeID_64_switch (unique_id: zwavejs2mqtt_0xff3b0602_64-37-0-currentValue)
2021-10-12 14:38:55.254  Status: MQTT-DOPEY: discovered: nodeID_64/nodeID_64_electric_v_value (unique_id: zwavejs2mqtt_0xff3b0602_64-50-0-value-66561)
2021-10-12 14:38:55.355  Status: MQTT-DOPEY: discovered: nodeID_64/nodeID_64_electric_w_value (unique_id: zwavejs2mqtt_0xff3b0602_64-50-0-value-66049)
2021-10-12 14:38:55.455  Status: MQTT-DOPEY: discovered: nodeID_64/nodeID_64_electric_kwh_value (unique_id: zwavejs2mqtt_0xff3b0602_64-50-0-value-65537)
2021-10-12 14:38:55.556  Status: MQTT-DOPEY: discovered: nodeID_64/nodeID_64_electric_a_value (unique_id: zwavejs2mqtt_0xff3b0602_64-50-0-value-66817)

And domoticz creates devices all alway as a switch and for example not as an smoke device.
How and when Domoticz detects something is really depending on what you fill in in the Zwavejs GUI tried several options but it doesn't look better.
I installed MQTT-explorer it is still confusing how it works

: BROM_10 2021-10-12 14.43.gif (23.46 KiB) Viewed 1748 times

In the Zwavejs2MQTT GUI still a lot off zwave devices not recognized like an "Fibaro FGMS001 ZW5 motion sensor" and still showen as unknown product after 2 hours of collecting.
What do I have to set On and what do I have to set OFF in the GUI of zwavejs2mqtt?
It is working but not workable.
No plugin installed because I am using 2021.1 build 13689 I think?

Posted: **Tuesday 12 October 2021 20:27**

Are your autodiscovery prefix and mqtt prefix different? They cannot be the same as that would create issues.

If you find that some devices are not working then best to report these through either GitHub or slack (better). There is a specific channel on slack to report these. Let me know if I should send you an invitation.

Sent from my SM-G980F using Tapatalk

Posted: **Tuesday 12 October 2021 20:30**

In terms of the zwavejs2mqtt settings, if you use the exact same settings as defined in the python plugin then everything should be fine. Zwavejs2mqtt has tremendous support for devices, probably better than OZW.

Sent from my SM-G980F using Tapatalk

Domoticz

zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt

Re: zwavejs2mqtt