Can you confirm that this worked in Chrome 66? What were the old characteristics? What are the new ones?

@Ricardo Cabello confirmed it worked back in March. I am unsure how long it
has been since it stopped working. The old characteristics are that the
event handler is called every time the device moves or a button is pushed
and returns data array values of the type accessed in the code. The new
characteristics is that the event handler is never called and when I poll
the data manually, there is no array of values, only a single 16-bit int.

Also, I can confirm this code works on the Android build of Chrome 67.

Correction: I noticed it no longer worked back in March, I do not know when was the last time it worked.

Adding "TE-Hardware-Dependency" as we don't have the mentioned Daydream Controller in order to test and confirm the issue, hence requesting some one from respective team to have a look into this and help in further triaging it.

Thanks!

Thanks for the additional detail. I'll find someone with a controller and compare behavior between Android and macOS.

I've confirmed that the controller works with Chrome on Android but not Chrome on macOS. It appears that while the app can find the expected characteristic on the device no events are fired for the 'oncharacteristicvaluechanged' event when interacting with the controller.

I've also confirmed that the controller does not generate any events when connected to an Android device which it has not previously paired to with the Daydream app. I don't know anything about the protocol this device supports but it is possible there is some setup process which it must go through first.

bitllama@, can you confirm this is the case for you as well (find a new controller or new phone to test with)?

This appears to be an issue with the Daydream controller and not Chrome.