How to add a new RFID tag to a Zipato Mini Keypad

jaepetto · February 28, 2019, 3:54pm

I’m currently trying to add a new RFID tag to a Zipato Mini Keypad.

According to this post, I should:

2: Add RFiD tags and/or codes

Once the device is correctly included the network, close the cover of the device.

It should show up as ‘Schlage Link Mini Keypad RFID’, select it and then “Current Values” on the left.

On the device, press home then place the RFiD tag close to the face of the device (within one second).

You should see “Enrollment Code” change to a 10 value hex. Copy this number and paste into “Code 1”.

Press submit. Now press home again placing the RFiD close and you should see Code 1 is set.

To set keypad code, the process is the same, with the numbers being simply 0x31, 0x32, 0x33 and 0x34 for 1, 2, 3 and 4 respectively. You must press “Enter” after the last key press.

Since most of the menus have changed concerning the zwave, I tried the following:

Press the home button on the keypad
Once the led (after 1 sec) turn red, present the tag in front of the keypad
Look at the zwave logs

2019-02-28 16:32:32.208 Detail, Node013, Received: 0x01, 0x14, 0x00, 0x04, 0x00, 0x0d, 0x0e, 0x63, 0x03, 0x00, 0x00, 0x8f, 0x17, 0x7c, 0x18, 0x3d, 0x50, 0x01, 0x04, 0x00, 0x00, 0x18
2019-02-28 16:32:32.208 Detail,
2019-02-28 16:32:32.208 Info, Node013, User Code Packet is 10
2019-02-28 16:32:32.208 Detail, Node013, Refreshed Value: old value=56a706d0, new value=7004261c, type=raw
2019-02-28 16:32:32.208 Detail, Node013, Changes to this value are not verified
2019-02-28 16:32:32.208 Info, Node013, Received User Code Report from node 13 for User Code 0 (Available)
2019-02-28 16:32:32.208 Detail, Node013, Notification: ValueChanged
2019-02-28 16:32:32.277 Detail, Node013, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0d, 0x02, 0x84, 0x07, 0x7f
2019-02-28 16:32:32.277 Detail,
2019-02-28 16:32:32.277 Info, Node013, Received Wakeup Notification from node 13
2019-02-28 16:32:32.277 Info, Node013, Node 13 has been marked as awake
2019-02-28 16:32:32.277 Detail, Node013, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=13): 0x01, 0x09, 0x00, 0x13, 0x0d, 0x02, 0x84, 0x08, 0x25, 0x3d, 0x7e
2019-02-28 16:32:32.277 Detail, Node013, Notification: Notification - Node Awake
2019-02-28 16:32:32.298 Detail,
2019-02-28 16:32:32.298 Info, Node013, Sending (WakeUp) message (Callback ID=0x3d, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=13): 0x01, 0x09, 0x00, 0x13, 0x0d, 0x02, 0x84, 0x08, 0x25, 0x3d, 0x7e
2019-02-28 16:32:32.306 Detail, Node013, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-02-28 16:32:32.306 Detail, Node013, ZW_SEND_DATA delivered to Z-Wave stack
2019-02-28 16:32:32.412 Detail, Node013, Received: 0x01, 0x07, 0x00, 0x13, 0x3d, 0x00, 0x00, 0x0b, 0xdd
2019-02-28 16:32:32.413 Detail, Node013, ZW_SEND_DATA Request with callback ID 0x3d received (expected 0x3d)
2019-02-28 16:32:32.413 Info, Node013, Request RTT 114 Average Request RTT 374
2019-02-28 16:32:32.413 Info, Node013, Node 13 has been marked as asleep
2019-02-28 16:32:32.413 Detail, Expected callbackId was received
2019-02-28 16:32:32.413 Detail, Expected reply was received
2019-02-28 16:32:32.413 Detail, Message transaction complete
2019-02-28 16:32:32.413 Detail,
2019-02-28 16:32:32.413 Detail, Node013, Removing current message
2019-02-28 16:32:32.413 Detail, Node013, Notification: Notification - Node Asleep
Go the zwave configuration
select the Z-Wave Node Management
Select the keypad node
In the Node User Codes, select code slot: code 1
In the Node User Codes, paste the value passed in the logs: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0d, 0x02, 0x84, 0x07, 0x7f
click on set user code
press the home button again on the keypag
wait for the led (1 sec) and present the RFID tag

Unfortunately, the zwave log are still the same and the RFID tag is not recognized

What am I doing wrong?

jaepetto · February 28, 2019, 11:24pm

I was using the wrong tool. Instead of using the zwave configuration provided by Home Assistant, the procedure had to be done with OZWCP.

Conveniently, an add-on exists to use directly from HA: New Add-on: Open ZWave Control Panel (OZWCP)

The github repository can be found here: https://github.com/jkeljo/hassio-addons

denisvic · July 20, 2020, 10:52pm

Can you tell me more about your solution, I’m stucked with this device that worked well with other solutions.

tremebundo · November 28, 2020, 12:48pm

Do you remember how to save the enrollment codes into the codes?

nila · February 18, 2022, 5:20pm

Here are my notes and How-to for Z-waveJS and the Zipato (Wintop) Keypad with alarm activation rfid tag - Online manual

Z-Wave Include/Exclude: Press and hold the tamper for 1 seconds and release

Add tags: (in my examples 179 is my Z-Wave node ID)
Press [Home], wait 1 sec
Place tag over the [Enter] - Tag ID will be written in Usercode v1 → “[179-99-0-userCode-0] User Code (0)”
Copy Usercode/Tag ID to “[179-99-0-userCode-XXX] User Code (XXX)” - Where XXX is a number between 1-255
Remember to set the “[179-99-0-userIdStatus-XXX] User ID status (XXX)” to Enabled.

Test:
Developer tools → Events
Listen to events
Event to subscribe to: zwave_js_notification
Press Start listening

Implementation: (I use Alarmo HACS integration, and have created a special user with code: SecretPIN)

alias: 'Alarm: Set alarm arm/disarm'
description: Set alarm armed or disarmed
trigger:
  - platform: event
    event_type: zwave_js_notification
    event_data:
      node_id: 179
      event: 5
    id: Armed
  - platform: event
    event_type: zwave_js_notification
    id: Disarmed
    event_data:
      node_id: 179
      event: 6
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id: Armed
        sequence:
          - service: alarmo.arm
            data:
              entity_id: alarm_control_panel.alarmo
              mode: away
              code: SecretPIN
      - conditions:
          - condition: trigger
            id: Disarmed
        sequence:
          - service: alarmo.disarm
            data:
              entity_id: alarm_control_panel.alarmo
              code: SecretPIN
    default: []
mode: single

tremebundo · February 18, 2022, 8:55pm

Thanks a lot.
I will try when I have time.

marc.forn · March 12, 2022, 5:39pm

How you did it to get this on zwave_js_notification event? I do not have this event to filter. The only information I can get is through logs and I get this:

2022-03-12T17:05:46.735Z SERIAL « XXXXXXXXXXXXXXXXXXXXXXXX                      (22 bytes)
2022-03-12T17:05:46.743Z CNTRLR   [Node 041] [User Code] userCode[0]: metadata updated              [Endpoint 0]
2022-03-12T17:05:46.745Z CNTRLR   [Node 041] [~] [User Code] userIdStatus[0]: 0 => 0                [Endpoint 0]
2022-03-12T17:05:46.748Z CNTRLR   [Node 041] [~] [User Code] userCode[0]: "2222" => "1111"         [Endpoint 0]
2022-03-12T17:05:46.751Z SERIAL » [ACK]                                                                   (0x06)
2022-03-12T17:05:46.753Z DRIVER « [Node 041] [REQ] [ApplicationCommand]
                                  └─[UserCodeCCReport]
                                      user id:   0
                                      id status: Available
                                      user code: 1111
2022-03-12T17:05:46.779Z SERIAL « sfsdfsdfsdfsdfsdfsdfdsfds

upwind_anderl · August 26, 2023, 11:03am

aaaah… how did you get Zipita on ZWave_JS working
I freak out and have been trying for days

I don’t find any user_id information and also i’m not able to listen to zwave_*
the only chance is to check the logfiles and there are only **** at usercode.

Any hints on how to setup zipato with zwave_js???