Using a keypad with zwaveJS2Mqtt - adding NFC Tags

Hello everyone.

I have added my zipato keypad to my zwave network. Everything works so fine and I can. Lock and unlock it with a pin code. It is recognized as https://devices.zwave-js.io/?jumpTo=0x0097:0x6131:0x4501:0.28.
Even tags I haved added with the old integration work.

Has someone an idea to add new tags?

Have you found a solution for this ?

Unfortunately not. I use the PinCodes at the moment.

Thats to bad, are you able to add PinCodes ? if so how ?

I use ywaveJs2Mqtt, changed the topic. Sorry for my fault.
Still interested?

With the new version it is possible add new devices:

  1. Go to the Control Panel of Z-WaveJS to MQTT
  2. Go to the Keypad and open User Codes
  3. Press the home Button and add hold the new tag in front of it
  4. In the [XX-99-0-userCode-0] User Code (0) you find the ID of the TAG eg: 0x8fb45cf292500104
  5. Paste the ID into an empty config path eg: [XX-99-0-userCode-2] User Code (2)
  6. Enable [XX-99-0-userIdStatus-2] User ID status (2)

Now you can react on the events from the keypad eg:

{
    "event_type": "zwave_js_event",
    "data": {
        "type": "notification",
        "domain": "zwave_js",
        "node_id": 30,
        "home_id": 3342345011612,
        "device_id": "070a75bb1c67e3312301f10b18565d27",
        "label": "Keypad unlock operation",
        "parameters": {
            "userId": 6
        }
    },
    "origin": "LOCAL",
    "time_fired": "2021-03-09T17:33:42.254855+00:00",
    "context": {
        "id": "d6bfae099c73af7e2f2bafea9805b0fa",
        "parent_id": null,
        "user_id": null
    }
}

The trigger for the automation looks something like this:

platform: event
event_type: zwave_js_event
event_data:
  label: Keypad unlock operation
  parameters:
    userId: 1
1 Like

Thanks, that was the solution for me…

Hi Bibabuzi,

Can you tell me where i need to place this code plz, and where i can find home-id, device_id, userId, and context id ?

Thanks for your much appreciated help!

The code has to be placed in the zwave config of the keypad.

What I have pasted there was the information you get when you listen to the notification of the keypad. userId is the ID where you put the code in. So in the event you see which person entered his code.

Thx for the reply, i never do something like that, can you explain me step by step plz.

Regards,

yeah I try to make some pictures the next days

1 Like

Thx a lot, :pray:

Sorry. totally forgot it.

Here the pictures and the steps to do:

First click on the Z-wave JS Button on the left

Then find your keypad in the list:


The click on the keypad and open the dropdown:

There is the entry for usercode:

There you see list with all the possible users. You first have to enable the the entry a: User ID Status and click on the ‘send’ button. Then you can to the same at the User Code part and also click the send button.

And the with the developer tools you can listen to the event: zwave_js_notification

And the create the automation like my posts before. If you need any help just let me know and I apologise for being so late with my answer.
@dre93300

1 Like

Thx but this part is ok for me. I need to know how i can have acess to the id when i arm or disarm the alarm. I saw in the log the id is 6 when i arm, and 5 when i disarm but i don’t know how to create an entities with it?

That is the part I already posted:
userID inside the Parameters is the ID of the user who entered the code

Hi there,
Old post, but may be the only place where I can get some help. Trying to add new users with PIN (just one tag available for the moment), without any success. As soon as I set a user to “enabled” it switches instantly back to “available”. Any code I set is deleted instantly as well. First user has the RFID tag assigned and it works as expected. Any ideas? Thanks!

Which Z-Wave Integration/Addon do you use?

zwave-js. solved by re-interviewing the device. at least so it seems for now. thanks!

So for me my workflow looks like this:

  • set the User ID status on available
  • wake the keypad with the connected token by press home and hold the token in front of it
  • type in a usercode and press “send”
  • wake the keypad with the connected token by press home and hold the token in front of it

so my problem is that the keypad was allways sleeping and not taking any commands.

thanks. that was exactly my workflow, but it simply wasn’t working. as said earlier, re-interviewing the device seems to have solved it. it now works exactly the way you describe it (and as expected).

1 Like