Hi,
I don't know if you've found a solution. I just identified the culprit after months of having this problem : it's the blued daemon. You have to restart it to get the mouse to work again. I've devised a small script, that I compiled as an app and leave on my desktop to kill blued, so when the mouse starts misbehaving I just double click on it.
In order not to type the password every time I created a keychain element named BluedScript that contains my administrator password. The first part of the script just gets the password from that entry. You'll need to create the entry too.
If you've found another solution, please tell me, this is not really perfect !
Here it is in case it helps :
o
on getPW(keychainItemName)
do shell script "security 2>&1 >/dev/null find-generic-password -gl " & quoted form of keychainItemName & " | awk '{print $2}'"
return (text 2 thru -2 of result)
end getPW
set MyResponse to "Error"
set app_name to "blued"
set the_pid to (do shell script "ps ax | grep " & (quoted form of app_name) & " | grep -v grep | awk '{print $1}'")
if the_pid is not "" then
set MyResponse to do shell script ("kill -9 " & the_pid) password getPW("BluedScript") with administrator privileges
if MyResponse = "" then
display notification "Bluetooth Reset"
else
display notification "ERROR : " & MyResponse
end if
end if
