For a long time I’ve been using Logitech G604 with “Works on Keyboards with Same Type as Used for Recording" applied to all my remaps, and it works great - as expected.
However, I recently bought a second Logitech G604 so that I can always have it in my backpack and not be packing / unpacking it everytime I am out. My expectation was that the second G604 would be treated as “Same Type” after all it is the exact same model, but bettertouch tool is not activating. And yes, the second G604 has been properly configured with the right onboard profile using Logitech G-Hub.
I have tested and indeed if I reconfigure the trigger using either G604, it will work on one mouse but not the other.
If “"Works on Keyboards with Same Type as Used for Recording" is behaving as expected, then I would like to see a third option be made available. I think the options should be:
Works on all keyboards
Works on the keyboard used for recording
Works on keyboards of the same model as used for recording
Alternatively, there could be a “Works on selected devices” and then just have a list of devices with a checkbox next to them. This may be a superior option as it would make it possible to know what device the trigger is assigned to.
I even tried remapping once more, but it still only works on the mouse that recorded the trigger.
Looking at System Info, they do share the same name and further share the same exact information for everything else (except for Version and Location ID):
Yes! Sorry I should’ve mentioned that. This is a mouse with a ton of buttons. In order to be able to have them be identified properly by BTT, I need to:
Map buttons to keyboard shortcuts in Logitech G-Hub
Assign the profile to the mouse’s onboard memory
Configure BTT using the “Keyboard” section.
It is hacky, but works perfectly both when using the Receiver and also Bluetooth.
Ah I see, this is the mouse I'm currently working with @asphy to get the native support in BTT working properly:
I think I can add a product id only check for keyboard type, that should resolve your issue - but it might make sense to switch away from G-Hub once this works well in BTT itself.
