You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuation of issue #456 (I don't think I can reopen an issue unless I closed it myself? Sorry, I'm not too familiar with GitHub.)
Thank you for looking into it! It looks like that fixed the problem of detecting the wrong MacOS version (The [PAIRING OSX] No need to add entry for OS X before 10.7. message no longer appears), but unfortunately I still can't get my controller to pair. I suspect that it may have to do with the mac address of the controller being written to the com.apple.bluetooth.plist file in /Library/Preferences/ , is it possible that file it needs to be written to changed in recent MacOS versions? I'm thinking that because none of my other bluetooth devices are in that file, in fact, there's not much data there at all. Just a guess though, you would have a much better idea of what's causing the problem than I would.
One thing that I think is worth noting is the controller works well with the example scripts when it's plugged in over usb, the issue is just pairing over bluetooth.
Here is a video of me trying to pair the controller to my Mac, in case you notice anything strange there.
Log from terminal:
bryce@Bryces-Air build % sudo ./psmove pair
Password:
Connected controllers: 1
[PSMOVE WARNING] Magnetometer in 04:76:6e:0f:0a:18 not yet calibrated.
PSMove #1 connected via USB.
[PAIRING OSX] Detected: macOS 13.1
[PAIRING OSX] Entry for 04-76-6e-0f-0a-18 already present.
Pairing of #1 succeeded!
Controller address: 04:76:6e:0f:0a:18
Calibration data available and saved.
bryce@Bryces-Air build %
The text was updated successfully, but these errors were encountered:
thp
changed the title
(Continuation of #456 ) Unable to pair on M1 Mac, Ventura
Pairing broken on macOS Ventura
Dec 12, 2022
Hey Thomas, I just came across something that might be worth looking into related to this problem. I dug around a bit and noticed that all of my bluetooth devices had their information and mac addresses stored in different files like /Users/bryce/Library/com.apple.bluetooth.services.cloud/CachedRecords/DeviceRecord/01:23:45:67:89:10
I am still not even sure if this is what should be looking for in order to help get this issue solved. I would like to help however I can, I just don't know what I should be doing. If you can tell me how to can help you best, I'd be more than happy to do whatever!
Continuation of issue #456 (I don't think I can reopen an issue unless I closed it myself? Sorry, I'm not too familiar with GitHub.)
Thank you for looking into it! It looks like that fixed the problem of detecting the wrong MacOS version (The
[PAIRING OSX] No need to add entry for OS X before 10.7.
message no longer appears), but unfortunately I still can't get my controller to pair. I suspect that it may have to do with the mac address of the controller being written to thecom.apple.bluetooth.plist
file in/Library/Preferences/
, is it possible that file it needs to be written to changed in recent MacOS versions? I'm thinking that because none of my other bluetooth devices are in that file, in fact, there's not much data there at all. Just a guess though, you would have a much better idea of what's causing the problem than I would.One thing that I think is worth noting is the controller works well with the example scripts when it's plugged in over usb, the issue is just pairing over bluetooth.
Here is a video of me trying to pair the controller to my Mac, in case you notice anything strange there.
Log from terminal:
The text was updated successfully, but these errors were encountered: