[question] ZIPATO/WINTOP KEYPAD 0x0097-0x6131-0x4501 : Where I'm wrong ?

[candrea77]

Hi, I've migrated from OZW recently to zwavejs2mqtt using docker:latest update a@24th december .... currently the only device I cannot get to work on my new system is my Zipato Keypad.

By my point of view, seems that in the autodiscovery section, a device/class is missing preventing Domoticz/HomeAssistant to create the corresponding device in the Home Automation System.

VERSION AND SETTINGS

This is the zwavejs2mqtt version I'm using :

zwavejs2mqtt: 6.2.0
zwave-js: 8.9.1

This is my zwavejs2mqtt seetings :

STEP TO REPRODUCE

When I use keypad for unlock / lock operation, this is the results.

Reading ZWAVE log, I can see the operation of unlock and lock :

2021-12-26T15:37:37.051Z CNTRLR   [Node 067] [~] [Notification] notificationMode: "pull" [Endpoint 0] [internal]
2021-12-26T15:37:37.051Z DRIVER « [Node 067] [REQ] [ApplicationCommand]
2021-12-26T15:37:37.161Z DRIVER « [Node 067] [REQ] [ApplicationCommand]
2021-12-26T15:37:41.305Z CNTRLR   [Node 067] [~] [Notification] notificationMode: "pull" [Endpoint 0] [internal]
2021-12-26T15:37:41.305Z DRIVER « [Node 067] [REQ] [ApplicationCommand]
2021-12-26T15:37:41.323Z DRIVER « [Node 067] [REQ] [ApplicationCommand]

Reading mqtt log , I can see the update in domoticz/in mqtt section :

2021-12-26 15:36:22.541 DEBUG MQTT: Publishing to domoticz/in/67/113/0/Access_Control/Keypad_unlock_operation: { time: 1640532982541, value: { userId: 1 } } with options { qos: 1, retain: false }
2021-12-26 15:36:22.558 DEBUG MQTT: Publishing to domoticz/in/67/status: { time: 1640532982558, value: true, status: 'Awake', nodeId: 67 } with options { qos: 1, retain: false }
2021-12-26 15:36:23.594 DEBUG MQTT: Publishing to domoticz/in/67/status: { time: 1640532983593, value: true, status: 'Asleep', nodeId: 67 } with options { qos: 1, retain: false }
2021-12-26 15:36:26.283 DEBUG MQTT: Publishing to domoticz/in/67/113/0/Access_Control/Keypad_lock_operation: { time: 1640532986283, value: { userId: 1 } } with options { qos: 1, retain: false }
2021-12-26 15:36:26.301 DEBUG MQTT: Publishing to domoticz/in/67/status: { time: 1640532986301, value: true, status: 'Awake', nodeId: 67 } with options { qos: 1, retain: false }
2021-12-26 15:36:27.332 DEBUG MQTT: Publishing to domoticz/in/67/status: { time: 1640532987332, value: true, status: 'Asleep', nodeId: 67 } with options { qos: 1, retain: false }

In MQTT Explorer I can clearly see the infomation of the operation come through the MQTT prefix classes (in my case domoticz/in)

Also seems (but I'm a real newby ... so excuse me in case of wrong undesrstanding of how the system have to work) that binary sensor or any other kind of sensors for class 113/0/Access Control is not created in the MQTT Discovery operation. In the binary sensors tree of the MQTT Discovery, I can see only 113/0/Home Security with "cover status" (see image)

Where I made mistake ? How I've to do to complete the setup ?

[robertsLando]

Hi @candrea77 , If the problem is related to mqtt discovery please read this: https://zwave-js.github.io/zwavejs2mqtt/#/homeassistant/homeassistant-mqtt

I don't plan to keep it maintained ATM

[candrea77]

Hi @candrea77 , If the problem is related to mqtt discovery please read this: https://zwave-js.github.io/zwavejs2mqtt/#/homeassistant/homeassistant-mqtt

I don't plan to keep it maintained ATM

Hi robertsLando, in order to understand if Zipato device works correctly, I've setted up this environment ;

• 1 Docker container for ZWaveJS2MQTT
• 1 VM with HassOs

On the docker container, i've enabled the WebSocket and in HassOS I've enabled the ZWave integration with WebSocket pointing to the container.

Now in HassOS I've got the device for keypad (see image attached)

When I use the NFC tag, I get this Log :

2022-01-07T16:52:36.182Z SERIAL « 0x0110000400430a7105000000ff0606010129                              (18 bytes)
2022-01-07T16:52:36.182Z CNTRLR   [Node 067] [~] [Notification] notificationMode: "pull" [Endpoint 0] [internal]
                                   => "pull"
2022-01-07T16:52:36.182Z SERIAL » [ACK]                                                                   (0x06)
2022-01-07T16:52:36.183Z DRIVER « [Node 067] [REQ] [ApplicationCommand]
                                  └─[NotificationCCReport]
                                      notification type:   Access Control
                                      notification status: 255
                                      notification event:  Keypad unlock operation
                                      event parameters:
                                        userId: 0x01
2022-01-07T16:52:36.251Z SERIAL « 0x01080004004302840731                                              (10 bytes)
2022-01-07T16:52:36.252Z SERIAL » [ACK]                                                                   (0x06)
2022-01-07T16:52:36.252Z DRIVER « [Node 067] [REQ] [ApplicationCommand]
                                  └─[WakeUpCCWakeUpNotification]
2022-01-07T16:52:36.252Z CNTRLR « [Node 067] received wakeup notification
2022-01-07T16:52:36.254Z CNTRLR   [Node 067] The node is now awake.
2022-01-07T16:52:37.254Z CNTRLR » [Node 067] Sending node back to sleep...
2022-01-07T16:52:37.256Z SERIAL » 0x010900134302840825020f                                            (11 bytes)
2022-01-07T16:52:37.257Z DRIVER » [Node 067] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      2
                                  └─[WakeUpCCNoMoreInformation]
2022-01-07T16:52:37.258Z SERIAL « [ACK]                                                                   (0x06)
2022-01-07T16:52:37.264Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-01-07T16:52:37.264Z SERIAL » [ACK]                                                                   (0x06)
2022-01-07T16:52:37.265Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-01-07T16:52:37.327Z SERIAL « 0x0107001302000006ef                                                 (9 bytes)
2022-01-07T16:52:37.327Z SERIAL » [ACK]                                                                   (0x06)
2022-01-07T16:52:37.328Z DRIVER « [REQ] [SendData]
                                    callback id:     2
                                    transmit status: OK
2022-01-07T16:52:37.332Z CNTRLR   [Node 067] The node is now asleep.

I'm unable to get the Access Control in HassOS .... I'm missing something ?

[kpine]

Please check the HA docs for the integration. There is a section for Notification Events, even with an example using the Keypad operation events.

[candrea77]

Please check the HA docs for the integration. There is a section for Notification Events, even with an example using the Keypad operation events.

Thank you kpine ... you pointed me in the right direction and I've solved my problem

AUTOMATION FOR UNLOCK OPERATION

platform: event
event_type: zwave_js_notification
event_data:
  domain: zwave_js
  node_id: "your node id"
  command_class: 113
  command_class_name: Notification
  label: Access Control
  type: 6
  event: 6
  event_label: Keypad unlock operation

AUTOMATION FOR LOCK OPERATION

platform: event
event_type: zwave_js_notification
event_data:
  domain: zwave_js
  node_id: "your node id"
  command_class: 113
  command_class_name: Notification
  label: Access Control
  type: 6
  event: 5
  event_label: Keypad lock operation

Thank you very much to all of you guys!