Wintop MINI KEYPAD RFID - issue with event lock/unlock

Configuration Z-Wave
1

Hello,

I would like to submit a problem that I cannot solved:

I would like to use my Z-wave zipato (Wintop) RFID keyboard in HA.
This one worked perfectly in my old system (JEEDOM + OpenZwave)

I use it in HA with zwave-js-ui ( V8.21.0 - zwave-js: V11.5.0)

The condition below allows me to recover, for example, the lock event:

node_id: 29
event_label: Keypad lock operation
domain: zwave_js
command_class: 113
command_class_name: Notification
label: Access Control
type: 6
event: 5

When I used the TAG, it works.
But the same event is repeated at regular intervals (28613 - a little less than 8 hours) without action on the Tag reader.

I tried changing the battery, excluding it and re-including it, without success.

Does anyone have an idea of ​​the origin of this problem?

THANKS

2

I also have this device, and have been using it without issue in HA for nearly three years. However, this week I noticed the same issue that you seem to be reporting here. It is repeating the last event, leading the alarm to arm or disarm inappropriately. I haven’t timed the intervals, but I thought it was at 12 hour intervals. Maybe I was wrong at it was at 8 hour intervals.

I changed the batteries to check that. I also removed the batteries for a day, and can confirm that the event was not repeated when the device was powered off.

I am a bit stumped. It would appear to be an issue with the device itself, but I can’t explain it happening suddenly to both of us at about the same time.

3

A bit more info. First, it looks like this has been happening to me for more than 30 days, which is as long as I have events recorded for.

During this period, it usually repeats events twice a day at approx 4am and noon, (with an 8 hour gap) or once per day at 6am. There are some days when it repeats at 6:20am and 2:20pm (also an 8 hour gap).

I auto-disarm my alarm at 6.30am, which probably masked this problem, and I only started noticing it this week because we were out a lot and the alarm started disarming itself while we were away.

How does this compare with what you are seeing?

Here are the timestamps during the last 30 days that I’ve seen this behavior:

5 July 2023     04:25:31
5 July 2023     12:25:15

6 July 2023     04:24:49

7 July 2023     04:24:28

8 July 2023     04:24:14
8 July 2023     12:24:09

9 July 2023     02:24:08

10 July 2023    06:24:01
10 July 2023    14:23:53

11 July 2023    06:23:36
11 July 2023    14:23:31

13 July 2023    06:23:04
14 July 2023    06:22:38
15 July 2023    06:22:09
16 July 2023    06:21:42
17 July 2023    06:21:16
18 July 2023    06:20:53
19 July 2023    06:20:18
20 July 2023    06:19:51
21 July 2023    06:19:16
22 July 2023    06:18:46
23 July 2023    06:18:07
24 July 2023    06:17:33
25 July 2023    06:16:56
26 July 2023    06:16:26
27 July 2023    06:15:51
28 July 2023    06:15:31

29 July 2023    06:15:05 
29 July 2023    11:26:25

30 July 2023    04:18:04

31 July 2023    04:17:26

1 August 2023   04:16:40 
1 August 2023   12:16:35 

2 August 2023   04:16:16
2 August 2023   11:34:31
4

I think I’m going to deal with this problem by ignoring the event unless a motion sensor detects a person in the room where the keypad is.

5

I started encountering this same issue 5 days ago. I’ve been using Home assistant for about a year and the alarm is rarely used as there’s usually someone home but whenever we do it’s armed/disarmed via the RFID keypad and I’ve encountered no previous automatic disarming issues.
I set up overnight automatic arming/disarming about 2 weeks ago, scheduled via sunset/sunrise, and all was fine until 5 days ago when it started disarming itself hours ahead of schedule.

I’ve just been digging through the Z-Wave JS UI logs and I noticed the same pattern ‘Keypad unlock operation’ notification events are firing every 8 hours. I’ve only got logs going back to the day the issue started happening, which leads me to believe that was the day I updated my ZW JS UI container image (I hadn’t updated it for months before that).

Unfortunately there’s no differentiator between an expected RFID unlock event and these periodic ones so I’m going to have to do similar to you and apply more checks in the automation for disarming for now.

6

may i ask you how you’ve been able to re-include the keypad again?!

Since Zwave js 2.1 i’m not able to exclude or include the keypad again. Nothing happens after clicking the tamper button, batteries are new.

7

Hello Sean, I’m new to HA. I come from Vera where this keypad was fully supported. same principles, more or less, including text scripts. I understand I have to define the event ‘some where’ and add an ‘and’ condition to it (if sensor is triggered) to cope with this problem. I’m aware this is a pure noob question. Where do you enter the definition of the event? Of course the node-id will be different…
(node-id 29 and so on)

this is one of the challenges for moving away from Vera. Another one is the zwave scenecontrollers (quad or dual switches from aeotec)
br
Olivier

8

You can use a zwave_js_notification event type as an automation trigger, and set the node ID etc in the event data that is filtered for. Here’s some screen shots of the recent automation in my system.

1000046738
10000467381080×2118 167 KB

1000046739
10000467391080×1631 65.7 KB

1000046740
10000467401080×1666 64.2 KB

9

Oh, and you can use the “events” section in the Developer Tools screens to monitor events and figure out the node ID, command class etc.

10

Hello Sean.
I don’t get any event out, when listening to zwave_js_notification. I do get text when using logging silly or a bit less directly on the device info. But not on de event bus.
I suppose a configuration either in yaml configuration file or on the device self.
Suppose still missing something…
best regards
Olivier