[EDGE] 3rd Reality MK1 Keyboard as 10 button device

Devices & Integrations Community Created Device Types
41

Why do they make it so hard for themselves?

2 Likes
42

Maybe in preparation for a WWST device with 12 (13?) buttons. If 3rd Reality wants their 10-button device supported, they’ll have to jump through hoops.

Update:

Screenshot_20250501_204018_Samsung Internet
Screenshot_20250501_204018_Samsung Internet1200×1005 209 KB

43

I’m surprised they made a whole subdriver copy-pasting most of the code just to add the F1-F12 names in the profile, which could have been just labels instead of IDs.

Maybe they plan to add more features in the future. BTW it’s interesting the compliance document only has 10 endpoints instead of 12, but the website does indeed mention F1 to F12 are exposed to Matter.

Edit: Actually, it’s not most, it was just the component mapping, which would have not been necessary if it had labels and kept the button1… button12 IDs.

Yeah, no subdriver needed, the stock driver already handles buttons and does the mapping when endpoints are consecutive like in the MK. So no code was needed besides a small tweak to change the profile when the MK1 is detected and add labels for the keys as labels instead of IDs, like:

   - id: button2
     label: "F2"

Oh, wait, I see now. The keyboard must have a wrong Matter implementation and does report support for held and multiple presses when it doesn’t, since the subdriver has initial_press only hardcoded to true and only exposes the “pushed” event.

1 Like
44

My prototype device only has 10 buttons exposed to HA and Homekit. I was told 10 was the max for Matter buttons.

1 Like
45

I think I understand the need for the subdriver now, according to the Matter compliance document the keys support also long press and multiple presses when in reality (no pun intended) it only supports a single press.

<feature>Does the device support Momentary Switch LongPress?</feature>
<support>true</support>

<feature>Does the device support Momentary Switch MultiPress?</feature>
<support>true</support>

The subdriver is probably to ignore the wrong features reported by the keyboard. And if they’re indeed wrong, that leads to the next question, how did it get the certification?

2 Likes
46

Your keyboard should work with the stock Matter switch driver now.

The necessary sub-driver is in version 2025-05-27T19:00.