This is a screenshot of the situation:

Deleted: screenshotBLE.jpg 370 KB

	screenshotBLE.jpg 370 KB View Download

lukas.helebrandt@ Thanks for the issue.

Tested this issue on Windows 10 Surface Pro 4 machine on the reported version 69.0.3489.0 and the latest Canary 69.0.3493.0 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and enabled the flag #enable-experimental-web-platform-features.
2. Navigated to chrome://bluetooth-internals/#devices and checked if adapter is initialized, present, powered in the Adapter section.
2. Clicked on Devices and hit the start scan button.
4. Can observe that all the nearby bluetooth devices are shown.
Attached is the screen cast for reference.

Request you to retry the issue on new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..

Deleted: 863507.mp4 2.9 MB

	863507.mp4 2.9 MB View Download

Hello Susan, thanks for your comment.
I am using a surface pro 4 too, and this is the test:

Deleted: Configuración 17_07_2018 18_49_28.mp4 28.0 MB

Configuración 17_07_2018 18_49_28.mp4 28.0 MB Download

Sorry that my last comment was too laconic. 
- I did it with a new windows profile.
- My Surface Pro 4 has a Marvell AVASTAR Bluetooth Radio Adapter,version: 10.0.17134.1
- Chrome canary version 69.
- Flag Enabled.
Unfortunately I got the same results.

Susan, may I ask what Bluetooth driver do you have?

Thank you

I will attempt to reproduce on the Windows hardware I have access to as well.

There are known issues with Bluetooth LE support on Windows. The most critical is that devices are not visible to Chrome unless they have been paired. There is ongoing work to fix this and when that happens we will be taking Web Bluetooth out from behind the --experimental-web-platform-features flag.

To get a sneak preview of what this will look like run Chrome on Windows 10 with the --enable-features=NewBLEWinImplementation flag and try doing a scan. Note that this new implementation is incomplete and so Web Bluetooth apps may not work with it set.

Thanks for your comment reilly. Following your steps to have a preview I could find my device! However, as you said it can not be connected yet. just found.

Would you like to receive information of our device and website to be part of your tests?

What version of Chrome are you using to test with the new flag. The latest canary should be able to connect to the device.

Any update on whether connect works with the latest canary?

Sorry for my late reply, 

I tried with the latest version on canary: 70.0.3514.0 with the same settings as you mention in your video. Unfortunately, the result is not successful.

In the BLE dialog it appears the message: "could not find compatible devices"

Any idea of what I am doing wrong?

Thank you.

Deleted: screenshot.png 356 KB

	screenshot.png 356 KB View Download

Just to confirm, did you run Chrome with the --enable-features=NewBLEWinImplementation flag?

Hello Ortuno, good news!

Thanks for the heads up! I ran it with the -enable-features=NewBLEWinImplementation flag on and our Tokymaker it is actually working on create.tokylabs.com

I have a couple of questions:
 1.- Will this be compatible with previous versions of Windows?
 2.- Is there any visibility on when this will be implemented for all users?

Thank you very much for this awesome work!

If you need/want to do any further tests, we are happy to run them on our platform. In such case just mail me at hello@tokylabs.com

Cheers!

This new code relies on APIs which are not present in previous versions of Windows. Windows 10 is the first version with a fully capable Bluetooth Low Energy API.

I am eager to enable this flag for all users. There will be an update to the Web Bluetooth Intent to Ship thread on blink-dev@chromium.org when we are ready to officially launch support for Web Bluetooth on Windows.

I am closing this issue. Follow along on issue 579202 for updates on Web Bluetooth support on Windows.