inputexec VS input-leap

I recently put something together similar to this, to switch between my personal PopOS/Windows machine and my work Macbook Pro.

I used one of these manual USB switchers, (https://sabrent.com/products/usb-sw30), and connected it's switch to a Raspberry Pi 4B via GPIO (4B is overkill by wanted hardwired network). There's a small separate keyboard (which will later be a macro keypad of some sort), connected to the Pi. Using inputexec (https://github.com/rbarrois/inputexec) to detect keypresses and then firing off a specific script to send a network request to the LG TV I use as a monitor to switch the source, and then set the GPIO connected to the USB switcher to high or low to switch the keyboard/mouse to the other machine.

I can also turn on/off the TV using the same WebOS API (and Wake-on-lan) as used during the source switch. A Kasa smart outlet also gets toggled to turn on/off a BenQ ScreenBar Halo (https://www.benq.com/en-us/lighting/monitor-light.html).

So with 4 different keypresses, I can switch to Work, to Personal, turn off monitor and light, and turn on monitor and light.

There is an actively developed fork https://github.com/input-leap/input-leap, however that fork is still undergoing heavy development and recommends sticking with Barrier until they're able to release v3.0.0 which they expect rather soon.

barrier is basically a dead project now. The active members of the project forked it and are going to release when ready but

https://github.com/input-leap/input-leap

Keep an eye on that for anything new

There's a new fork of barrier called input leap (not to be confused with the leap motion), https://github.com/input-leap/input-leap with work on getting Wayland support in shape. Not sure how far the support is atm, but the gnome 45 release notes mentioned "Wayland support for Input Leap" (https://release.gnome.org/45/)

Wayland tracker issue, https://github.com/input-leap/input-leap/issues/109

I wonder if I would be better off just buying a LG monitor without the Smart KVM, and instead using Barrier (or, Input Leap, which seems to be maintained actively compared to Barrier https://github.com/input-leap/input-leap)

Could also be worth mentioning that Barrier is basically unmaintained at this point so you'll probably never get Wayland support there. The maintainers (apparently the owner of the debauchee/barrier dropped off the face of the earth) of Barrier forked it and migrated to input-leap (issue with details if interested) which is where all development is presently, although they haven't made a release yet.