unpairing and re-pairing dualsense over bluetooth breaks device hiding

[snack0verflow]

I am having this problem where if I pair the controller with a different device and pair it back to windows hidhide doesn't work, I can see the device shown in windows controller settings

[nefarius]

This is per design of Windows, if you unpair and repair a device, the Instance ID (that HidHide uses to uniquely identifies the device) changes and the match configured within HH no longer works. There is no way around this, I'm afraid.

Cheers

[nefarius]

I assume te ID changed but somehow the UI associates the same name to the previous state? The CLI output would shed light on what's actually stored in the drivers setting and if this is a UI issue.

[snack0verflow]

What command's output would be useful for you from the cli when this happens the next time?

[nefarius]

cd "C:\Program Files\Nefarius Software Solutions e.U\HidHideCLI"
PS C:\Program Files\Nefarius Software Solutions e.U\HidHideCLI> .\HidHideCLI.exe --dev-list
--dev-hide "HID\VID_054C&PID_0CE6&MI_03\a&c9e84b2&0&0000"

[Kanuan]

The CLI shows the old ID instance. If you make it list the currently present devices the same controller will have a different ID

With the issue occurring, this is how my DS4v2 as it appears when the "list connected devices" command is used (--dev-gaming)

HID\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002054c_PID&09cc\9&1a03a06a&18&0000

ANd this is how it appears when the "list HidHide's blacklist" command is used (--dev-list)

HID\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002054c_PID&09cc\9&1a03a06a&17&0000

[nefarius]

So the driver is fine, it is supposed to hold the old value, the UI is mixing it up for whatever reason, hm... 🤔