After pairing a DS3 controller the mac address of the BT dongle and the DS3 controller should match. Re-inserting the DS3 controller seems to give different mac addresses each time, but never the same as the BT dongle.
Pairing does work.
Here's a screenshot of the mac addresses after pressing the "Pair" button:

@rickgaiser Is this happening with original ds3? On which console model?
This problem occurred with older commits but I fixed it in latest (looks like not totally). Commands for setting/reading mac address can't be issued with led-rumble cmd (needs some delay between?) so simple fix was to disable led-rumble cmd (which is called together with pad data request) before calling mac cmd. You can disable led-rumble cmd fully by commenting out line 203 in src/pad.c and see if that helps.
From my test on console SCPH-50004 with latest OPL I have no problem at all (with original and fake ds3s). It only happens if ds3 was reconnected really fast.
I test with an original ds3 controller (CECHZC2E). I tested on SCPH-30004, 77004 and 90006. The problem is consistent on all models. I have compiled the latest OPL version.
I also tried the latest Beta release. It's r1027 (no git hash?!), so it does not have the latest ds34 additions. That version does show the mac address correctly, but has a slow gui response when using BT.
I also tried commenting out line 203 (ds34usb_set_rumble(pad->port, 0, 0)), but it has no effect.
@rickgaiser Could you test this build:
OPNPS2LD-0.9.3+.1008-Beta-c8205b0-dirty.ZIP
I have CECHZC2E ds3 also and only sometimes opl shows wrong mac address (when pairing and fast reconnecting). With fake one no problem at all.
I tried the build on an SCPH-90006, with 2 different ds3 controllers (CECHZC2E and CECHZC2U). The result is the same :-(.
It's hard to guess what may be wrong. Have you tried to pair controller without bt dongle connected to ps2?
What kind of BT-Dongle do you have @rickgaiser?
Do you have another BT-Dongle you can try it with?
AFAIR the code hasn't been changed since then, but I thought I'd ask... Is this still happening?
If I remember correctly, this happened to me as well (in a similar fashion)!
I had to press 'pair' a second time and when I pressed that OSD-Field again and again for a few times, it wouldn't change anymore and afterwards worked.
AFAIR the code hasn't been changed since then, but I thought I'd ask... Is this still happening?
If I remember correctly, this happened to me as well (in a similar fashion)!
I had to press 'pair' a second time and when I pressed that OSD-Field again and again for a few times, it wouldn't change anymore and afterwards worked.
I haven't worked on it for a long time but there is commit on my repo with minor changes. You could check it if issue still exist. It may be caused also by damaged cable or port.
Would you mind making a PR on the ifcaro-repo? ;)
This PR might help, because I also have this problem:


Tested with SL-7410-TTBK & CECHZC1E on OPL 1386.
Have not seen this issue last time I used and I forgot this issue was still open, so closing it.
From what I remember there weren't any changes recently in\to PADEMU...
Anyway a photo from v1.0.0-rc1:

I've tested this using v1.0.0-rc1 with 2x DS4 controllers and it worked fine. But then this issue must be somewhere in the details. I'll reopen this issue and make sure to test it with DS3 also.
Sorry, I forgot to mention that I tried to pair DS3 with a bluetooth adaptor.
Pressing pair twice seems to "fix" this issue, AFAIK.
I tried it more than two (2) times and nothing seems to be fixed (at least with DS3).
With DS4 I have no issues, but with DS3 I see more issues:
Something seems to go wrong in communicating with DS3 controllers via USB. The MAC seems almost random, as if the data is received wrong.