New issue
Advanced search Search tips

Issue 904100 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 902241
Owner: ----
Closed: Nov 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

BT: Root robot does not display its name in selection dialog before inspection

Reported by dauml...@gmail.com, Nov 10

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce the problem:
1. Power on the Root robot (www.rootrobotics.com).
2. Call Bluetooth.requestDevice()

What is the expected behavior?
The robot should be listed as ROOT

What went wrong?
It is listed as Unknown Device

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.77  Channel: stable
OS Version: 10.0
Flash Version: 

I know that this is a bit specific already...
Using chrome://bluetooth-internals/#devices, the Root robot is listed correctly after clicking Inspect.

Here is the developer's reply:

I'm not very knowledgeable about Web Bluetooth but I can comment some more on the robot's BLE implementation.

The advertising packet is 22 bytes long and contains the UART service UUID:

Byte 0: Length = 2
Byte 1: AD type = flags
Byte 2: General Mode
Byte 3: Length = 17
Byte 4: 128-bit UUID following
Bytes 5 to 20: UART service UUID
The scan response packet is 24 bytes long and contains the device name and dynamic service data:

Byte 0: Length = 5
Byte 1: AD type = Complete local name
Bytes 2 to 17: Device name
Byte 18: Length = 5
Byte 19: AD type = Service data
Bytes 20 to 21: 16-bit UUID
Bytes 22 to 23: Service data
After connection the device name is available via a Root robot BLE protocol command or under the Generic Access service (UUID: 0x1800) and Device Name characteristic (UUID: 0x2A00).

More info re the protocol here: https://github.com/RootRobotics/root-robot-ble-protocol

Hope this helps.
 
I don't know if it works in Chrome for Mac OS. My Chromebook (Asus C100PA) with Chrome 79 does not list the device at all.
Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Needs-Triage-M70 TE-Hardware-Dependency
The issue needs to be tested using "Root robot". As ET-team doesn't have the above device to test the issue. Hence, adding label TE-Hardware-Dependency.

Thanks...!!
Mergedinto: 902241
Status: Duplicate (was: Unconfirmed)
Thank you for reporting this issue. It looks like it is a duplicate of  issue 902241  for which there is a patch in progress.

Sign in to add a comment