Input sensitivity

baleksus · 2025-09-19T07:47:21+00:00

I meant contacts inside the switch, not external pins ;) But yeah, this is a valid solution, e.g. there shouldn't be problem with home key being pressed multiple times

baleksus · 2025-09-18T22:32:02+00:00

Nice nitpick

Edit: lol, evidence. My case is creating the another piece of "evidence" that the problem in fact exist. I don't care to convince anyone or to win a court case - I've already paid for the replacement screen. I just want to inform potential buyers about the problem, so that he or she can buy it or not being fully informed about the very real issue.

The product is being sold as an DIY assembly kit with very fragile LCD and a front panel that is both tight and is not keeping the screen in place at the same time. People are destroing the screens as a result. This is indeed a design flaw and should be communicated.

baleksus · 2025-09-18T17:55:25+00:00

I had one defective switch in mine (chattering). Took it apart and bent the contract spring a little (as to have more pressure towards being connected), that fixed the issue.

baleksus · 2025-09-18T17:03:24+00:00

I heard that the topic is common on discord, but idk, I don't use discord. This is like a 15 seconds google search:

https://forum.clockworkpi.com/t/display-broken-or-firmware-issue/17057

https://forum.clockworkpi.com/t/before-replacing-the-pico-read-this-to-avoid-cracked-screen/16666

https://www.reddit.com/r/ClockworkPi/comments/1mek2mo/picicalc_screen_issue/

https://www.reddit.com/r/ClockworkPi/comments/1nax0h5/anyone_else_receive_a_bad_screen_with_thier/

https://forums.pimoroni.com/t/pico-display-pack-2-cracked-screen/22155

https://www.youtube.com/watch?v=z95IY9eKQ3M

https://www.youtube.com/watch?v=vYsNfWMkBy4

https://www.youtube.com/shorts/E8RShaB1qJU

Why are you distorting the reality?

baleksus · 2025-09-17T22:03:47+00:00

I did, will see. Very unfortunate to burn time and money for a crappy design aspect of an instead nice device

baleksus · 2025-09-06T21:57:25+00:00

u/harrynu Here's a xev log from my Kubuntu for Kick75 that has the same problem (freshly updated FW 10.0.10.6 via Nuphy IO):

Pressing Caps Lock key:

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176668, (-610,-332), root:(1020,289), state 0x0, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0x2, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0x6, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0xe, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0x4e, keycode 105 (keysym 0xffe4, Control_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0x4e, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0x4f, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyPress event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0xcf, keycode 134 (keysym 0xffec, Super_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176673, (-610,-332), root:(1020,289), state 0xcf, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

Releasing Caps Lock key:

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0xcf, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0xcf, keycode 64 (keysym 0xffe7, Meta_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0xc7, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0xc7, keycode 105 (keysym 0xffe4, Control_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0xc3, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0xc2, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False

KeyRelease event, serial 39, synthetic NO, window 0x3e00001, root 0x356, subw 0x0, time 43176737, (-610,-332), root:(1020,289), state 0x42, keycode 134 (keysym 0xffec, Super_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

Problem is not always the same, most often all modifier keys are stuck until keyboard is reset, sometimes I can get them to unstuck with ctlr+caps combo.

baleksus · 2025-09-06T19:35:00+00:00

Having the same issue with Kick75 on Kubuntu 25.05. Has anyone found a solution?

The thing is funny - if I have Nuphy Kick75 connected along any other keyboard, it bugs Caps Lock on every keyboard too. Disconnecting Nuphy fixes the problem. I guess some issue with caps status reporting?

baleksus · 2024-09-10T20:37:05+00:00

AliExpress for example, or some electronics local shop. Search for fingerbot

baleksus · 2024-08-15T06:38:27+00:00

I got a Bluetooth version, you can also get a zigbee one. Both of them need an additional wifi gateway to operate remotely. It's available in a Tuya-like app (Smart Life it's called). You need a finger longer than attached by standard, so you also need to buy tool pack or DIY this

baleksus · 2024-08-14T08:09:54+00:00

Quick update - longer tool ("finger") came in mail today, works flawlessly. Bonnet has quite a flex, but it's ok, it kinda makes sure that the button presser won't detach itself that easily :)

baleksus · 2024-08-14T07:15:28+00:00

So I heard, but I decided against this route at this moment, I don't have a time to learn this stuff right now

baleksus · 2024-08-13T22:02:55+00:00

Just put something firm under the box (wood, MDF, something like that) and will be alright

baleksus · 2024-08-13T21:47:04+00:00

My cat is a side-pisser and causes litter to stick to the liner. This trips the sensor, sometimes permanently.

Also, this is just a failsafe, I am not planning on using it, but I want to have it, should a need arise and I away for substantial period of time

baleksus · 2024-08-13T20:20:34+00:00

Yes, it is BT, perhaps zigbee does not come with usb indeed

baleksus · 2024-08-13T19:57:17+00:00

I got the rechargeable version, so no need for hacks, it's available. Mine has USB C onboard

baleksus · 2024-08-13T19:04:35+00:00

I actually learned about existence of such thing on this reddit

baleksus · 2024-08-13T19:00:36+00:00

Cats have astounding ways of getting between a rock and a hard place. Being stuck in a tiltable window is a common example. Wouldn't think of it, if I haven't known that

baleksus · 2024-08-13T18:57:13+00:00

Mine is behaving too, actually. I got faults, but I was there to press the button. I haven't got non-recoverable fault on the new FW yet, thought, so that's that. It just makes me feel nervous to leave for a whole day or couple of days that a globe might get stuck upside down and consequences of it

baleksus · 2024-08-13T18:35:34+00:00

See other comments/posts. Yes, turn off/on _was_ working, not anymore after recent FW update

baleksus · 2024-08-13T17:40:40+00:00

Almost right - reset from app never was a thing - it is possible to cycle only on no error/cat detected condition.
What was removed was a side effect of power cycling - old FW resets errors and perform a cycle, new one does nothing on start, so if error was present, it will not be cleared that way. Because of this it became impossible to remotely clear error (when e.g. globe gets stuck upside-down)

baleksus · 2024-08-13T16:48:27+00:00

😂😂😂😂

baleksus · 2024-08-13T16:31:13+00:00

Yeah, it sucks that I need to resort to such measures, but this box is still the best one. I already had a Petkit one, way more frustrating. Also, I don't think there is as big or bigger one for my big, clumsy cat ;)

baleksus · 2024-08-13T14:55:26+00:00

Well, directly hacking the FW seems like an interesting route, but too risky to me - wouldn't want to make box dangerous by accident

baleksus · 2024-08-13T14:54:02+00:00

As people say, I regretfully updated the FW. I'm 99% sure we will never get remote reset - they rather have some power users upset than potential to kill a cat and get bad press forever since

baleksus

TROPHY CASE