Bluetooth passthrough Kinivo BTD-400

[skeeveo]

So - I can get bluetooth passthrough to work by forcing dolphin to use the adapter as instructed, however, despite the compatibility list saying so, it does not remember pairings and the red "sync" button has to be pressed and the button manually pressed on dolphin every single time, which is annoying.

Things I noticed:

After pairing the controller and resetting, pressing 1+2 will flash it very quickly on and off once. Just pressing the A button or similar doesn't work either.

The bluetooth lists itself as CSR 8510 A10 (Generic bluetooth,) which I find odd. In either case, the pairing should still work.

For now, I am using the hotkey to sync them, but I would rather it just -worked-, any ideas?

[leolam]

The reason why the Wiimote LEDs flash for much less time after you've paired is because the Wiimote is actively trying to connect to the game/Dolphin, but the emulated software is blocking the connection.

Quote:The bluetooth lists itself as CSR 8510 A10 (Generic bluetooth,) which I find odd. In either case, the pairing should still work.

No. You need an adapter which remembers link keys, or at the very least, allows link keys to be written. Fwiw, I myself have two "CSR 8510 A10" adapters: one of them remembers Wiimotes perfectly, the other one is unable to store even a single link key.

[skeeveo]

(01-12-2017, 02:25 AM)leolam Wrote: The reason why the Wiimote LEDs flash for much less time after you've paired is because the Wiimote is actively trying to connect to the game/Dolphin, but the emulated software is blocking the connection.

No. You need an adapter which remembers link keys, or at the very least, allows link keys to be written. Fwiw, I myself have two "CSR 8510 A10" adapters: one of them remembers Wiimotes perfectly, the other one is unable to store even a single link key.

Is there any reason why the Kinivo BTD-400 is not being listed as a Kinivo BTD-400? It definitely is one - it has the same formfactor. But the device ID is the CSR. Have you had similar problems with that? I was having difficulty installing the driver - would it default to CSR's VID/PID as a result?

[leolam]

I don't know. I've never had this problem because there's no need to install anything else on Linux. But I can't see why installing the WinUSB driver would change your device VID/PID… Was the device ID different before using Zadig?

[skeeveo]

(01-12-2017, 08:56 AM)leolam Wrote: I don't know. I've never had this problem because there's no need to install anything else on Linux. But I can't see why installing the WinUSB driver would change your device VID/PID… Was the device ID different before using Zadig?

Actually I meant the actual driver itself, I know windows 10 "automatically" installs it, but it would start,then fail halfway through. It's always been the same VID/PID, before and after zadig

Interestingly, Zadig also had an error and crashed, but after restarting the program, it looked like winusb successfully installed, which seemed right, considering the bluetooth passthrough works but the device pairing doesn't at all.

I am going to contact Kinivo and see if the VID/PID is supposed to be that, but according to the bluetooth passthrough compatibility chart, it should be different.