> the only thing that makes this a better proposition is Logitechs Flow software
Not sure if you've tried Flow but personally, in my experience of using it (on Mac), I would not recommend it at all.
Their hardware is very good (I have an MX Keys keyboard and MX Master 3 mouse) but the software is buggy and doesn't live up to its marketing promises; especially Flow. To the degree that it somewhat devalues the otherwise well built hardware devices.
Flow is not very reliable for me. It wouldn't be quite so bad but Logitech have a very strange design flaw in their Flow implementation which compounds the software issues; the MX Keys keyboard has 3x dedicated device buttons to allow you to manually switch between host computers, but this does not sync with the mouse - which has its own button on the underside.
When you switch between computers via software using Flow (when it works), it moves both mouse and keyboard at the same time. But when Flow flakes out, as it often does, you have to revert back to using the dedicated button on the keyboard AND turn your mouse upside down and click the switch button multiple times to also switch it to the new host.
It seems to be madness that they have designed a matching pair of keyboard and mouse, with this advertised "multiple host" capability, and yet the very obvious feature of switching both keyboard AND mouse together, to the same host via the dedicated keyboard keys is absent.
Here's a 2 year old Logitech forum post about this issue with 674 upvotes:
https://support.logi.com/hc/en-us/community/posts/3600507556...
And another 2 year old post with 275 votes:
https://support.logi.com/hc/en-us/community/posts/3600493206...
Logitech say its "difficult to implement" and yet there are a number of workarounds on GitHub that people have come up with to fix this behaviour. Knowing that the Flow software has full control over which host the keyboard and mouse are assigned to, having the software/driver automatically switch both devices when the dedicated button is pressed on the keyboard seems like it should not be difficult to implement.
I'm now using macOS' new Universal Control feature instead which is a good reliable implementation of what Flow tried to achieve. Switching between my Macs has been 100% reliable since using Universal Control. The downside is the special functions of the MX Master mouse do not carry over to the second Mac (scroll wheel behaviour is different and difficult to control, dedicated buttons don't work). So there are a different set of compromises. I now plan to look at hacking up something that uses a combination of Universal Control and some custom messages sent to the keyboard/mouse to have them switch hosts based on when Universal Control switches hosts.