Forum Discussion
Bluetooth HID device paring issue
We are currently developing a Quest 2-based mix-reality game using Unreal Engine. One of the critical features of this game is to allow the customer to use a physical control unit we build explici...
Working on a similar challenge here. Our device actually connects with the headset initially, and the controls work in the main menus (D-pad, select and back buttons, etc), but then after that initial connection, the when reconnecting a 2nd time with the same piece of hardware, although the device shows that it's paired/connected, the control input have no more effect. Even "forgetting" the device and re-pairing after restarting the headset does not correct the issue. But using a new hardware unit (new MAC/UUID) seems to work the first time only. We don't have this issue on Android phones or Windows computers. No such issue with other OTS 3rd party bluetooth gamepads,, so we suspect something is missing in our HID profile/report descriptor, and the Quest 2 is blacklisting our device. A factory reboot of the headset and test should confirm/support this theory but we have not tried this yet. We'll also be trying connection directly via USB-C port next to try and narrow down the cause.
Did you manage to find the solution? It has been 3 weeks since I emailed developer.support@oculus.com and have never got a response.
Still working on it. We'll let you know what works/doesn't work.