I am currently experimenting with the Oculus Quest implementation package and Unity. I have some questions regarding the following points:
All my game and data retrieval methods run on Android on my Quest 3. I would like to find out during gameplay which devices are connected to the USB-C port (the only port it has) and also via Bluetooth.
By devices, I mainly mean batteries and haptic suits. For example, I want to know which batteries are being used when they are connected to my quest headset, and in case a user connects a haptic suit to the Quest 3, I also want to know in-game which haptic suit is being used.
In the case of data recollection with Unity and Android, you are requesting information that is on the external system of the headset, so this information cannot be obtained. From what you describe, I am assuming that you do not understand how haptic suits work. Haptic suits require their own software, so commonly on the market, they are all connected to a computer. The reason is that USB-C ports are not sufficient for these processes involving sound sources in games to trigger haptic sensations and bone tracking. The only tracking suits that are not haptic and are compatible with Android are SlimeVR, which works with OSC, and Mocopi. Another point you touch on is that you intuitively think your player will connect the haptic suit to their Quest, and magically it will work in your game. It is important to remember that each suit has its own SDK for implementation. If the game does not have the SDK, the game simply will not recognize anything.
As @Pendleton5564 mentioned, you can only access what the SDK allows you to access. I'm not sure which haptic suit you're using, but if it's the bHaptic TactSuit then what you can access can be found in thier documentation found here.
