I have improved this a bit in v6.613 alpha, previously it was not clear that using the system settings basically means it will reset to these system settings every time BTT reinitializes the mouse.
This alpha also adds multiple extra safeguards for preventing reconnect issues - I have however only tested it with one mouse so far.
Sounds good and since the last regular update, the BTT settings are being applied much faster when reinitialising the mouse!
Thanks for clarifying, it seems to work now with Automatic and settings are not being reset anymore.
Just to pick this back up, I'm still having reconnection issues after the computer sleeps and I have to reset BTT to get the MX Master 3 buttons working as intended again (thumb button, for instance, always reverts to window switching the two latest windows rather than launching mission control, which is how I have it set in the configuration).
I'm running the latest alpha (currently 6.687, although I have only just installed it) and I have the mouse speed set as automatic.
Interestingly, after a wake event, I notice the slow pointer until I recognise that BTT reinstates some control - but sometimes it manages to regain control of the pointer speed without the mission control shortcut working, almost as if it's half recognised the mouse but not fully. I have the mouse name set as a partial name in case I use a different Master 3 that I own, but choosing the full name from the dropdown list doesn't seem to make a difference:
Are there any other settings I can apply that might resolve the need to restart BTT after a wake? I've tried power cycling the mouse instead but that doesn't work as reliably as restarting BTT, which is actually quicker.
Thanks!
I haven't seen any wake issues on my machines for quite a while, if you still encounter them I would need more specific logs from your system. You can enable Logitech debug logging via this terminal command:
osascript -e 'tell application "BetterTouchTool" to set_user_defaults key "BTTLogitechDebugEnabled" numberValue 3'
Then after the issue happens again, go to "Help => Export Basic Debug Logs" and send the result to andreas@folivora.ai, maybe I can see anything special that is happening.
Ok, thanks. I've set up the debug logging and will try to remember to send the logs if I see the issue repeat itself.