OK, those are button events (KEY:F23 KEY:F24 in your video) as well as touchscreen event (ABS:MT_POSITION_X/Y on your photo). As long as you have these in your whitelist that is all normal up to here...
The version below changes the on-screen debug display to a debuglog.txt file to be found in .addons/miniclock/debuglog.txt (logs only if debug=1 is set in config file)
ithe logfile looks like
Code:
[1564039443 ABS:MT_TRACKING_ID 1]
[1564039443 ABS:MT_TOUCH_MAJOR 1]
[1564039443 ABS:MT_WIDTH_MAJOR 1]
[1564039443 ABS:MT_POSITION_X 935]
-- whitelist match --
-- cfg_delay = '1 1 1' --
-- clock update Thu Jul 25 09:24:05 CEST 2019 --
-- clock update Thu Jul 25 09:24:06 CEST 2019 --
-- clock update Thu Jul 25 09:24:07 CEST 2019 --
MiniClock debug event:
[1564039461 KEY:F1 1]
-- whitelist not matched - negative 1 --
MiniClock debug event:
[1564039462 KEY:F1 1]
-- whitelist not matched - negative 2 --
MiniClock debug event:
[1564039472 KEY:F1 1]
-- whitelist not matched - negative 3 --
-- cooldown start, Thu Jul 25 09:24:33 CEST 2019 --
-- cooldown end, Thu Jul 25 09:25:03 CEST 2019 --
so this was me touching the touchscreen (MT_POSITION_X event), followed by updating clock x3 (due to delay = 1 1 1 setting), followed by three times magnet sensor (me testing with fridge magnet), after 3 negative events in a row there's a 30 second cooldown due to 'cooldown=3 30' setting.
this log will grow, uh, rather big over time. and although it prints times and dates, it might still be hard to corelate the log to real events if you don't remember when you pressed the keys ^^;
so if you notice miniclock misbehaving maybe you could note down the time or something then see if anything is in the log for that time frame
PS: oh, I see it actually misprints the BTN_TOUCH as 0x14a, gotta fix that (but unless you were trying to use BTN_TOUCH in the whitelist, that's not your issue)
PPS: edit - fixed in 20190725_b_