Describe the bug
I created an automation to put the computer to sleep 10 seconds after the Logitech MX Ergo trackball is turned off. Unfortunately, for some reason BTT does not see that the device is disconnected. Surely this is not the script's fault, because the script itself works, and replacing the script with another action does not trigger it either. I tried setting the trigger with both the name and MAC address - it didn't help.
Edit: It doesn’t work with any Bluetooth device. I checked with Logitech MX Ergo and Microsoft Number Pad.
weird. Could you check whether in the newest BTT log in ~/Library/Application Support/BetterTouchTool/Logs" you find entries that begin with "connected bt name" or "disconnected bt name" ?
Now I see and you are right, while earlier I used the information that is written out in the System Report. Today, this device has a different address, and I guess that's not possible. This is weird
MBP M1 Pro with Sonoma 14.4. (also didn't work with 14.3.1)
I want an automation that switches the source of my displays as soon as I switch my Logitech MX Master 3S or MX Keyboard to another PC. Both are connected via Blueetooth to my Mac (not via the BOLT dongle).
The MX Master 3S (as well as the keyboard) has 3 preset buttons on the bottom to switch between different PCs. When I press that button, the BT connection gets disconnected, what is also shown in the BT settings of macOS.
But unfortunately the disconnection does not trigger an action.
In the example a HUD message should be displayed when the mouse is disconnected.
The same issue is also when I try to trigger an action when a device is connected.
Try to remove the vendor id & product id, it seems kind of random whether they are made available to BTT or not. Matching for only the address should be the best option. I did some reading on this topic and it looks like the address should never change. (I have been testing it mostly with the MX Master 3)
In your case the logs also don't seem to contain any disconnected messages, right? Only the connect events seem to trigger.
Is BTT already launched when the device is connected? (It registers the disconnect event once a device connects, in the next alpha I'll add an additional disconnect event registration when BTT starts)