Controller not recognized when paired, but recognized when connected

[the-pieman]

I'm on PC running Windows 10 using BetterJoyForCemu version 5
I am having a very strange and infuriating issue.
When I connect my Joy Con to my PC via bluetooth, the Joy Con will either become "Connected" or "Paired". If the Joy Con is "Connected" but not paired, it will show up and be used by BetterJoy just fine, but if my PC decides to pair with the Joy Con, BetterJoy suddenly is no longer able to "see" that Joy Con. I have a screenshot for proof. The Left Joy Con is Connected and noticed by BetterJoy. The Right Joy Con is paired and is not noticed by BetterJoy.
As you can see, Progressive Scan is on, so BetterJoy is showing up-to-date information.

If this is not a bug with BetterJoy, please tell me how to connect a bluetooth device to my PC and prevent it from pairing with that device.

[the-pieman]

Here's the screenshot

[Davidobot]

This is not a BetterJoy related thing. Make sure your BT drivers are up-to-date. What kind of BT card are you using?

Also, if I may, why are you on version 5 if there are newer ones available?

[the-pieman]

I see no results when I try to update the bluetooth drivers for the joy con (either of them) and it says they're up-to-date so I can only assume they are up-to-date.

My wi-fi/bluetooth card is a FebSmart Wireless Dual Band N600

As for using version 5, that's the version I already had installed. I had it working fine before, and this is a new development. Though if this problem won't be fixed by a new version, I don't consider that a priority at the moment.

Update: I checked all my devices under the bluetooth drop-down and I did find a few drivers that could be updated. After a restart, the problem persists (Specifically that a 'paired' JoyCon is not recognized or responsive while a 'connected' one is)

[the-pieman]

Update: Tried using latest stable (non-alpha) version 6.3 and the problem seems to be worse as now even a "connected" joy con isn't noticed by the program.

[Davidobot]

Update: Tried using latest stable (non-alpha) version 6.3 and the problem seems to be worse as now even a "connected" joy con isn't noticed by the program.

That's because you don't have HIDGuardian enabled in 6.3, but do in v5

Update: I checked all my devices under the bluetooth drop-down and I did find a few drivers that could be updated. After a restart, the problem persists (Specifically that a 'paired' JoyCon is not recognized or responsive while a 'connected' one is)

I meant it in the sense that you should update your BT card drivers. This is definitely on that end

[the-pieman]

I checked all listed devices under the bluetooth drop-down and I did find a few drivers that could be updated. After a restart, the problem persists: Specifically that a 'paired' JoyCon is not recognized or responsive while a 'connected' one is, and I can't prevent pairing from occurring.

Also, it seems HIDGuardian is installed, unless I'm reading this incorrectly

[Davidobot]

I meant in the sense that you need to enable useHidGuardian in app settings for version 6

[the-pieman]

Is there a reason for that being the default? That a function is disabled?

[the-pieman]

Hmmm... I turned on the setting, but I get this at start. Yes, I am running it as admin.

[Davidobot]

Is there a reason for that being the default? That a function is disabled?

Yes, read the commit messages for details.

You shouldn't need to run the program as admin.

[the-pieman]

Okay, then if running as admin is not the solution, what is?

[the-pieman]

Any help on this? How do I turn on HIDGuardian, and what do I do to make my JoyCon connect to my PC properly?

[Davidobot]

The joycon connection is on the BT hardware end, little I can do there other than advise you to get another dingle (not an Intel one).

Regarding HidGuardian, it's all here https://github.com/Davidobot/BetterJoy/wiki/HIDGuardian-and-Steam-(Big-Picture)

[alexjbusch]

I had this same problem and went nuts trying to solve it, but I eventually figured something out that might be helpful to people. I was using this unity code for joycon support, and I noticed that I only ever had the "paired" problem if unity was open when I connected the controllers via bluetooth. If I closed unity, both controllers would say "connected", and then I could safely reopen unity without them paring.