Using latest Chrome, on Windows, I cannot get the web demo to work.

The device is found in the pairing stage, and appears to pair successfully.
However, after this point, nothing else happens.

Chrome Console Log (Blank line between each entry):

THREE.WebGLRenderer 90

OBJLoader: 194.5078125ms

Uncaught (in promise) DOMException: GATT operation failed for unknown reason.

ControllerBluetoothInterface.js:160 Error: NetworkError: Failed to execute 'writeValue' on 'BluetoothRemoteGATTCharacteristic': GATT Server is disconnected. Cannot perform GATT operations. (Re)connect first with `device.gatt.connect`.

Any steps I've missed, or has a chrome update changed something?

Linux Version 66.0.3359.181 (Official Build) (64-bit)
Windows Version 66.0.3359.181 (Official Build) (32-bit)
both fail with the following error:
ControllerBluetoothInterface.js:154 Uncaught TypeError: Cannot read property 'writeValue' of null
at ControllerBluetoothInterface.runCommand (:152:44)
at ControllerDisplay.onClickDeviceActionButton (:320:50)
runCommand @ ControllerBluetoothInterface.js:154
onClickDeviceActionButton @ ControllerDisplay.js:319

I've been unable to 'downgrade' chrome due to dependency issues.

Any ideas?

I managed to make it work under macOS/OS X 10.12.6.

It is necessary to activate the API by entering this address into the address bar chrome://flags/#enable-experimental-web-platform-features and then ticking the "Experimental Web Platform features" to enable it.

I've just tested it out and saw how the home button resets the position of the controller to zero in the demo.

I found that the demo here on Github works but not the one from your website.

Cheers,

-Scott

Hi. I'm asking if it would be possible to change the license to MIT. GPL is great, I fully support it, but some libraries and implementations like this will have a greater set of use cases if compatible with MIT.

Hello, Great work!
I am author of first attempt and it is very interesting how you approached this problem.
I was sure that these three values are ready to use orientation but I was not able to figure out how to decode them. They change very consistently as you rotate GearVR around and also make other rotations.

Perhaps you can take a look and we can get consistent rotation from that ?

Thank you for the excellent reverse engineering.

I'm considering turning this into a reusable library to be able to include in future projects (including user js allowing me to try to use this with Google Slides). (Thanks to Best buy for selling these super cheap)

In your experience, can the pairing be automatic between page refreshes, or does it need to be manually performed each time?

Any input you can provide towards my possible efforts is appreciated. The demo worked perfectly on latest chrome stable on Android 10 on a Pixel 3 XL as of today.

Maybe using React Native, and this library?
https://github.com/Polidea/react-native-ble-plx