zwavejs2mqtt

[heggink]

That should do it.

Sent from my SM-G980F using Tapatalk

[heggink]

I already created the PR based on what I saw implemented for the zigbee2mqtt plugin.
H

[AllesVanZelf]

with those 2 lines the error disappears and the connection is made.
I also had to set the 192.168.x.x lan ip-address in ZwaveJS2MQTT instead of localhost or 127.0.0.1. This is because docker can by default not access host computer direct.
Thank you Heggink and Moroen! I will experiment further.

[heggink]

That's correct. Inside a container, localhost (127...) is the container and not the host system running the container.

Sent from my SM-G980F using Tapatalk

[Derik]

Great work guys!!!

What are the supported devices?

[heggink]

Zwavejs2mqtt supports more devices than any other system I know. The plugin supports the device types listed on the plugin page. Have a look. In case more types are needed, these can be added by virtue of a config file but the base is pretty functional already.

Sent from my SM-G980F using Tapatalk

[JuanUil]

Looks good guys!!!
Will also try it after my holidays.

[AllesVanZelf]

I switched to zwavejs2mqtt. (switch off Openzwave. Start ZwaveJS2MQTT via systemd. )(Mosquitto, ZwaveJS2MQTT and domoticz are running on the same server)
It took a lot of time to gather all the information from the zwave devices. Still not all devices are investigated/discoverd (rotating icon). Especially the battery powered.

I renamed the devices to the same name they had under openzwave, to minimize the changes I have to make on ZwaveJs. But some devices like dimmers and shuttered are working in another way. They have an ON/Off switch and a slider, instead of just one devices under OpenZwave. This could be very usefull in scripts. I changed my DzVents script using these. I can switch and slide devices by hand in Domoticz. This all is promising
But ..

A lot of actions are not triggered, or excecuted from DzVents. Actions that where working for years on OpenZwave.
Although The devices have the same name, they where not triggered to action. Like Lights that where not switched off later in the evening. Or lights that should switch on when there is movement on a sensor.

Does anyone recognize this on ZwaveJs? Is there a specific cause for this, or solution?
I will test later (when my laptop is working again).

[heggink]

Did you restart domoticz after switching off ozw? I found that dzvents can get upset if new devices are created with the same name as devices within a plugin that is not active.

For me, all scripts work fine so there is no distinct behaviour from the new plugin causing a malfunction.

Sent from my SM-G980F using Tapatalk

[IanDury]

Awesome!!! Many kudos to @moroen and @heggink for creating this plugin. I did a big bang migration of my 52 Zwave devices and it is working very well for me. Big performance gain when switching on/off a group of lights which could take multiple seconds with OZW, even after a healed network. Now it takes less than a second.

Some observations:

• Had the same issue with dzVents as @AllesVanZelf. The log complained about not being able to switch disabled devices. Apparently if you just disable your OZW controlled hardware and add the Zwave-MQTT plugin using the same device names this will cause confusion for dzVents. After deleting the OZW controller and restarting Domoticz, dzVents works fine.

• Zwave+ motion sensors use the notification command class. The plugin does not seem to support this yet. I had to add the controller to the 4th association group for "backwards compatibility" (Motion BC, binary sensor).

• CO2 device type appears to be not yet supported with the plugin.

[AllesVanZelf]

Thank you @IanDury

• Had the same issue with dzVents as @AllesVanZelf. The log complained about not being able to switch disabled devices. Apparently if you just disable your OZW controlled hardware and add the Zwave-MQTT plugin using the same device names this will cause confusion for dzVents. After deleting the OZW controller and restarting Domoticz, dzVents works fine.

I will try another name then, to make it possible to switch back.

• Zwave+ motion sensors use the notification command class. The plugin does not seem to support this yet. I had to add the controller to the 4th association group for "backwards compatibility" (Motion BC, binary sensor).

I do not understand what you mean by this. Could you explain this to me? How do you "add the controller to the 4th association group"?

[heggink]

Hey IanDury,

52 devices big bang migrated, impressive , wow!

In terms of your comments:

• the notification command class (113) should be supported so let's look into that. I am 1 release behind master in which moroen replaced built-in classes with configurable classes. If you look at the device_types.yml, you can see that there are 3 definitions (mappings) for the 113 class: acces_control/door_state, smoke_alarm/alarm_status and smoke_alarm/sensor_status. It may be that your specific type is not defined. It should be fairly simple to add to the file.

• CO2: that may well be missing since I don't have one and neither does moroen. Again, should be relatively simple top add.

when you install the plugin, in the tools folder, you will find a utility called mqtt-snooper.py. This will allow you to see what mqtt messages are sent by your devices and, therefore, how to configure the device_types.yml. You may neet to trigger zwavejs to send all the device messages.

Let me know how that goes.

EDIT: when you add devices and have them working, please either do a pull request on github or describe the additions in an issue and log that. That way, we can keep expanding with any missing devices.

Herman

[IanDury]

Thanks @heggink,

Will further investigate how to modify device_types.yml when I have more time and contribute if I'm succesfull. If I set the zwavejs2mqtt log level to Debug I see this:

Code: Select all

2021-08-16 13:18:20.730 DEBUG MQTT: Publishing to zwave/31/113/0/Home_Security/Motion_sensor_status: {
  time: 1629119900729,
  value: 8,
  nodeName: 'MS Trap',
  nodeLocation: ''
} with options { qos: 1, retain: true }
2021-08-16 13:18:20.731 INFO ZWAVE: Node 31: value updated: 113-0-Home Security-Motion sensor status 0 => 8

Node 31 is a Fibaro FGMS-001-ZW5 motion sensor.

@AllesVanZelf, To enable the binary sensor command class on this device I've added the following groups next to lifeline:

Screenshot from 2021-08-16 15-32-39.png (29.56 KiB) Viewed 1728 times

[heggink]

Thanks @heggink,

Will further investigate how to modify device_types.yml when I have more time and contribute if I'm succesfull. If I set the zwavejs2mqtt log level to Debug I see this:

Code: Select all

2021-08-16 13:18:20.730 DEBUG MQTT: Publishing to zwave/31/113/0/Home_Security/Motion_sensor_status: {
  time: 1629119900729,
  value: 8,
  nodeName: 'MS Trap',
  nodeLocation: ''
} with options { qos: 1, retain: true }
2021-08-16 13:18:20.731 INFO ZWAVE: Node 31: value updated: 113-0-Home Security-Motion sensor status 0 => 8

Node 31 is a Fibaro FGMS-001-ZW5 motion sensor.

@AllesVanZelf, To enable the binary sensor command class on this device I've added the following groups next to lifeline:


Screenshot from 2021-08-16 15-32-39.png

I think adding the below at the bottom of the 113 section in device_types.yml should do it (ie just before the /128/:):

Code: Select all

  Home_Security/Motion_sensor_status:
    DeviceType: 244
    Enabled: true
    Primary_device: true
    SubType: 62
    SwitchType: 8
    Type: DeviceType
    nValue: 1
    sValue: OnOff

[IanDury]

@heggink, I did as you suggested. The devices are added when a motion is triggered but no motion events are passed on to Domoticz. The "Last Seen" gets never updated. I tried changing SubType from 62 to 73 but that did not help.

Below the logs when a motion starts and ends after 10 seconds. Notice the line that I prefixed with question marks which shows nValue: 0 sValue Off. Shouldn't that be the opposite when a motion starts?

mqtt-snooper:

Code: Select all

19:48:20 zwave/31/113/0/Home_Security/Motion_sensor_status b'{"time":1629136100201,"value":8,"nodeName":"MS Trap","nodeLocation":""}'
19:48:31 zwave/31/113/0/Home_Security/Motion_sensor_status b'{"time":1629136111020,"value":0,"nodeName":"MS Trap","nodeLocation":""}'

Domoticz log:

Code: Select all

2021-08-16 19:48:20.202 ZW: (ZW) Pushing 'ReadEvent' on to queue
2021-08-16 19:48:20.227 (ZW) Processing 'ReadEvent' message
2021-08-16 19:48:20.227 ZW: (ZW) Received 124 bytes of data
2021-08-16 19:48:20.227 ZW: (ZW) 30 7a 00 31 7a 77 61 76 65 2f 33 31 2f 31 31 33 2f 30 2f 48 0z.1zwave/31/113/0/H
2021-08-16 19:48:20.227 ZW: (ZW) 6f 6d 65 5f 53 65 63 75 72 69 74 79 2f 4d 6f 74 69 6f 6e 5f ome_Security/Motion_
2021-08-16 19:48:20.227 ZW: (ZW) 73 65 6e 73 6f 72 5f 73 74 61 74 75 73 7b 22 74 69 6d 65 22 sensor_status{"time"
2021-08-16 19:48:20.227 ZW: (ZW) 3a 31 36 32 39 31 33 36 31 30 30 32 30 31 2c 22 76 61 6c 75 :1629136100201,"valu
2021-08-16 19:48:20.227 ZW: (ZW) 65 22 3a 38 2c 22 6e 6f 64 65 4e 61 6d 65 22 3a 22 4d 53 20 e":8,"nodeName":"MS.
2021-08-16 19:48:20.227 ZW: (ZW) 54 72 61 70 22 2c 22 6e 6f 64 65 4c 6f 63 61 74 69 6f 6e 22 Trap","nodeLocation"
2021-08-16 19:48:20.227 ZW: (ZW) 3a 22 22 7d .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. :""}
2021-08-16 19:48:20.227 ZW: (ZW) Pushing 'onMessageCallback' on to queue
2021-08-16 19:48:20.227 (ZW) Processing 'onMessageCallback' message
2021-08-16 19:48:20.227 ZW: (ZW) Calling message handler 'onMessage' on 'module' type object.
2021-08-16 19:48:20.227 ZW: (ZW) onMessage called: Verb: PUBLISH
2021-08-16 19:48:20.227 ZW: (ZW) zwave/31/113/0/Home_Security/Motion_sensor_status
2021-08-16 19:48:20.228 ZW: (ZW) updateDevice called with topic: zwave/31/113/0/Home_Security/Motion_sensor_status and payload b'{"time":1629136100201,"value":8,"nodeName":"MS Trap","nodeLocation":""}'
2021-08-16 19:48:20.228 ZW: (ZW) zwave/31/113/0/Home_Security/Motion_sensor_status
2021-08-16 19:48:20.228 ZW: (ZW) Updating unit 61 as device /31/113/0/Home_Security/Motion_sensor_status of type Home_Security/Motion_sensor_status with {'time': 1629136100201, 'value': 8, 'nodeName': 'MS Trap', 'nodeLocation': ''}
2021-08-16 19:48:20.228 ZW: (ZW) Updating with typedef: {'DeviceType': 244, 'Enabled': True, 'Primary_device': True, 'SubType': 73, 'SwitchType': 8, 'Type': 'DeviceType', 'nValue': 1, 'sValue': 'OnOff'}
???????? 2021-08-16 19:48:20.228 ZW: (ZW) nValue: 0 sValue: Off
021-08-16 19:48:23.033 ZW: (ZW) Pushing 'onHeartbeatCallback' on to queue
2021-08-16 19:48:23.084 (ZW) Processing 'onHeartbeatCallback' message
2021-08-16 19:48:23.084 ZW: (ZW) Calling message handler 'onHeartbeat' on 'module' type object.
2021-08-16 19:48:23.084 ZW: (ZW) onHeartbeat called
2021-08-16 19:48:23.084 ZW: (ZW) Pushing 'WriteDirective' on to queue
2021-08-16 19:48:23.084 (ZW) Processing 'WriteDirective' message
2021-08-16 19:48:23.084 ZW: (ZW) Sending 2 bytes of data
2021-08-16 19:48:23.084 ZW: (ZW) c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2021-08-16 19:48:23.085 ZW: (ZW) Pushing 'ReadEvent' on to queue
2021-08-16 19:48:23.135 (ZW) Processing 'ReadEvent' message
2021-08-16 19:48:23.135 ZW: (ZW) Received 2 bytes of data
2021-08-16 19:48:23.135 ZW: (ZW) d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2021-08-16 19:48:23.135 ZW: (ZW) Pushing 'onMessageCallback' on to queue
2021-08-16 19:48:23.135 (ZW) Processing 'onMessageCallback' message
2021-08-16 19:48:23.135 ZW: (ZW) Calling message handler 'onMessage' on 'module' type object.
2021-08-16 19:48:23.135 ZW: (ZW) onMessage called: Verb: PINGRESP
021-08-16 19:48:31.022 ZW: (ZW) Pushing 'ReadEvent' on to queue
2021-08-16 19:48:31.049 (ZW) Processing 'ReadEvent' message
2021-08-16 19:48:31.049 ZW: (ZW) Received 124 bytes of data
2021-08-16 19:48:31.049 ZW: (ZW) 30 7a 00 31 7a 77 61 76 65 2f 33 31 2f 31 31 33 2f 30 2f 48 0z.1zwave/31/113/0/H
2021-08-16 19:48:31.049 ZW: (ZW) 6f 6d 65 5f 53 65 63 75 72 69 74 79 2f 4d 6f 74 69 6f 6e 5f ome_Security/Motion_
2021-08-16 19:48:31.050 ZW: (ZW) 73 65 6e 73 6f 72 5f 73 74 61 74 75 73 7b 22 74 69 6d 65 22 sensor_status{"time"
2021-08-16 19:48:31.050 ZW: (ZW) 3a 31 36 32 39 31 33 36 31 31 31 30 32 30 2c 22 76 61 6c 75 :1629136111020,"valu
2021-08-16 19:48:31.050 ZW: (ZW) 65 22 3a 30 2c 22 6e 6f 64 65 4e 61 6d 65 22 3a 22 4d 53 20 e":0,"nodeName":"MS.
2021-08-16 19:48:31.050 ZW: (ZW) 54 72 61 70 22 2c 22 6e 6f 64 65 4c 6f 63 61 74 69 6f 6e 22 Trap","nodeLocation"
2021-08-16 19:48:31.050 ZW: (ZW) 3a 22 22 7d .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. :""}
2021-08-16 19:48:31.050 ZW: (ZW) Pushing 'onMessageCallback' on to queue
2021-08-16 19:48:31.050 (ZW) Processing 'onMessageCallback' message
2021-08-16 19:48:31.050 ZW: (ZW) Calling message handler 'onMessage' on 'module' type object.
2021-08-16 19:48:31.050 ZW: (ZW) onMessage called: Verb: PUBLISH
2021-08-16 19:48:31.050 ZW: (ZW) zwave/31/113/0/Home_Security/Motion_sensor_status
2021-08-16 19:48:31.050 ZW: (ZW) updateDevice called with topic: zwave/31/113/0/Home_Security/Motion_sensor_status and payload b'{"time":1629136111020,"value":0,"nodeName":"MS Trap","nodeLocation":""}'
2021-08-16 19:48:31.050 ZW: (ZW) zwave/31/113/0/Home_Security/Motion_sensor_status
2021-08-16 19:48:31.050 ZW: (ZW) Updating unit 61 as device /31/113/0/Home_Security/Motion_sensor_status of type Home_Security/Motion_sensor_status with {'time': 1629136111020, 'value': 0, 'nodeName': 'MS Trap', 'nodeLocation': ''}
2021-08-16 19:48:31.050 ZW: (ZW) Updating with typedef: {'DeviceType': 244, 'Enabled': True, 'Primary_device': True, 'SubType': 73, 'SwitchType': 8, 'Type': 'DeviceType', 'nValue': 1, 'sValue': 'OnOff'}
2021-08-16 19:48:31.050 ZW: (ZW) nValue: 0 sValue: Off

[IanDury]

Got it working. In api/devices.py I've added " or val == "8"

Code: Select all

        elif typedef["sValue"] == "OnOff":
            val = str(payload["value"])
            if val == "True" or val == "22" or val == "8":
                sValue = "On"
                nValue = 1
            else:
                sValue = "Off"
                nValue = 0

I think this code should be more generic following the rule:
# sValue 'OnOff' "On" if value > 0 else "Off"

[heggink]

Great, good work. Please suggest the change on GitHub. As said, to some degree, it's still work in progress. Our aim was to have a solid base functionality in order to prevent breaking changes.
Did you also get the CO sensor to work?

Sent from my SM-G980F using Tapatalk

[IanDury]

Thanks. Sure, I will create a pull request after some decent testing to not break the solid base

CO2 is also recognized. Just wondering why all my previously excluded nodes ( /28, /32, /33) are still being send through zwavejs2mqtt? In the Control Panel they are not present any more.

CO2.PNG (12.08 KiB) Viewed 1692 times

[heggink]

Do you have the retain flag on in the mqtt settings of zwavejs2mqtt? If so, mqtt caches the last message on the topic it received and will resend it every time the plugin subscribes again.

Best to switch it off and also putge the queued messages from mqtt.

Sent from my SM-G980F using Tapatalk

[AllesVanZelf]

@AllesVanZelf, To enable the binary sensor command class on this device I've added the following groups next to lifeline:

I tried to add group motion etc. But no success. The line is not added at all. I see a message:

Code: Select all

 Success zwave api call getAssociations [
{ endpoint: 0, groupId: 1, nodeId: 1, targetEndpoint: undefined },
[length]: 1
]

But still I only see the lifeline here. What do I miss?

Edit: I had to wake up the device!
Adding these endpoints to the group of the device in ZwaveJS2Mqtt did the trick to get the Fibaro motion sensors to work again!