Open afauch opened 6 years ago
Note: This is when running the same exact code.
We were able to workaround by providing additional logic to search for the MAC address in multiple formats; yet, the HoloLens is still facing unique connection/reading issues even after the device has been selected.
The Windows IoT Core Version might have something to do with this?
When running on Desktop (resulting in successful data stream):
When looping through on Hololens:
Key difference:
Desktop BluetoothLEDevice.DeviceID format:
BluetoothLE#BluetoothLE44:85:00:a0:7f:e3-f0:f6:60:6a:fc:de
HoloLens BluetoothLEDevice.DeviceID format:
\\?\BTHLEDevice#{00001801-0000-1000-8000-00805f9b34fb}_f0f6606afcde#8&172376d9&7&0008#{6e3bb679-4372-40c8-9eaa-4509df260cd8}