Migrating to Z-Wave JS : Benext Tag Reader

[memyself]

I am trying to migrate away from the old Z-Wave system to the well maintained Z-Wave-JS-UI. I have 2 Domoticz devices, one near the power meter for P1 information and a BeNext Tag Reader. Another one with the rest of the devices. Reason for this : the BeNext does not have the range to reach the other Domoticz machine.

After reading a lot, I decided to try and install Z-Wave-JS-UI on the Domoticz with the Tag Reader. I did note Tag Readers and Security Panels are not (yet) supported (https://www.domoticz.com/wiki/MQTT#Add_ ... Gateway.22).

After installing the needed software like Mosquitto, it all ran fine. Z-Wave-JS-UI did find the Tag Reader. Clicking the link to the database, the device is also supported : https://devices.zwave-js.io/?jumpTo=0x0 ... 0x0101:0.0.

Domoticz then sees two MQTT switches. One "Battery Low" and one "CurrentValue¨. Entering the alarm code does not have any result. I do not use tags with the device.

Am I doing something wrong or is the documentation correct stating Tag Readers and Security Panels are not supported?

[waltervl]

I suppose in the group of developers nobody had these kind of devices. So if you make a GitHub issue with the config and state topics of these new devices the developers can try to implement these in beta.

[gizmocuz]

@memyself

could you join us in Slack (MQTT Auto Discovery channel)

https://join.slack.com/t/domoticz/share ... G2dBSOTRwg

Could you post there the config topic+payload? You can use "MQTT Explorer" for this

[memyself]

Thank you for responding!

Installed a new Ubuntu machine to use Snap. It is 20.04 LTS, and installed the Snap version. I did shut down Domoticz, fired up the Zwave broker and directed MQTT Explorer to it. I have no idea where to look for a config topic or payload, but this is the output it shows:



For the record, the overview:



Domoticz has 10+ seperate devices listed:



If I know what to look for, I will add a slack account to post it.

[ben92]

hi,

is there any news ? same problem here

zwavejs logs :
11:05:02.930 SERIAL « 0x01100004000e0a710500ff00ff0605010198 (18 bytes)
11:05:02.932 SERIAL » [ACK] (0x06)
11:05:02.933 CNTRLR [Node 014] [~] [Notification] alarmType: 0 => 0 [Endpoint 0]
11:05:02.934 CNTRLR [Node 014] [~] [Notification] alarmLevel: 255 => 255 [Endpoint 0]
11:05:02.935 DRIVER « [Node 014] [REQ] [ApplicationCommand]
└─[NotificationCCReport]
notification type: Access Control
notification status: 255
notification event: Keypad lock operation
event parameters:
userId: 0x01
11:05:02.937 CNTRLR [Node 014] [Notification]
type: Access Control
event: Keypad lock operation
userId: 1
11:05:02.948 SERIAL « 0x01080004000e0284077c (10 bytes)
11:05:02.949 SERIAL » [ACK] (0x06)
11:05:02.950 DRIVER « [Node 014] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
11:05:02.951 CNTRLR « [Node 014] received wakeup notification
11:05:02.952 CNTRLR [Node 014] The node is now awake.
11:05:03.954 CNTRLR » [Node 014] Sending node back to sleep...
11:05:03.961 SERIAL » 0x010900130e028408240041 (11 bytes)
11:05:03.962 DRIVER » [Node 014] [REQ] [SendData]
│ transmit options: 0x24
│ callback id: 0
└─[WakeUpCCNoMoreInformation]
11:05:03.963 SERIAL « [ACK] (0x06)
11:05:03.969 SERIAL « 0x0104011301e8 (6 bytes)
11:05:03.970 SERIAL » [ACK] (0x06)
11:05:03.970 DRIVER « [RES] [SendData]
was sent: true
11:05:03.974 CNTRLR [Node 014] The node is now asleep.
11:05:29.298 SERIAL « 0x01100004000e0a7105000000ff0606010164 (18 bytes)
11:05:29.299 SERIAL » [ACK] (0x06)
11:05:29.300 CNTRLR [Node 014] [~] [Notification] alarmType: 0 => 0 [Endpoint 0]
11:05:29.302 CNTRLR [Node 014] [~] [Notification] alarmLevel: 255 => 0 [Endpoint 0]
11:05:29.303 DRIVER « [Node 014] [REQ] [ApplicationCommand]
└─[NotificationCCReport]
notification type: Access Control
notification status: 255
notification event: Keypad unlock operation
event parameters:
userId: 0x01
11:05:29.306 CNTRLR [Node 014] [Notification]
type: Access Control
event: Keypad unlock operation
userId: 1
11:05:29.315 SERIAL « 0x01080004000e0284077c (10 bytes)
11:05:29.316 SERIAL » [ACK] (0x06)
11:05:29.317 DRIVER « [Node 014] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
11:05:29.318 CNTRLR « [Node 014] received wakeup notification
11:05:29.319 CNTRLR [Node 014] The node is now awake.
11:05:30.320 CNTRLR » [Node 014] Sending node back to sleep...
11:05:30.327 SERIAL » 0x010900130e028408240041 (11 bytes)
11:05:30.327 DRIVER » [Node 014] [REQ] [SendData]
│ transmit options: 0x24
│ callback id: 0
└─[WakeUpCCNoMoreInformation]
11:05:30.329 SERIAL « [ACK] (0x06)
11:05:30.335 SERIAL « 0x0104011301e8 (6 bytes)
11:05:30.335 SERIAL » [ACK] (0x06)
11:05:30.336 DRIVER « [RES] [SendData]
was sent: true
11:05:30.342 CNTRLR [Node 014] The node is now asleep.

[ben92]

jeedom can do it : https://community.jeedom.com/t/zipato-m ... s/94827/53

domoticz no ?