@cco3 may be able to help there.

At the device level, subscribe has an implementation (I've not tested it), but unsubscribe does not.
crbug.com/735828
However, this may be covered up by the web bluetooth layer (i.e., maybe unsubscribe functionally works there). I'd have to do more testing to see.

@cco3, I am using for testing the latest version of Chrome version 66.0.3349.0 (official Build) Canary (64 bit).

A quick way to verify that the expected events from the "characteristicvaluechanged" listener are not received:

1. Open the application for iOS: LightBlue

2. Create a virtual peripheral: Heart Rate

3. Select the peripheral you just created for enable it: Heart Rate

4. Pair the newly created peripheral: Windows-> Settings-> Bluetooth-> pair a device-> Heart Rate-> Insert pin.

5. Open Chrome Canary at URL: chrome://flags/#enable-experimental-web-platform-features-> enable (if disabled)

6. Restart Chrome Canary to apply the changes (if point 2 was disabled)

7. Open Chrome Canary at URL: https://googlechrome.github.io/samples/web-bluetooth/notifications.html

8. Select Bluetooth Service: heart_rate

9. Select Bluetooth Characteristic: heart_rate_measurement

10. Start Notifications

The output is:

Live Output

Requesting Bluetooth Device...
Connecting to GATT Server...
Getting Service
Getting Characteristic...
> notifications started

And nothing else.

From Chrome with the Bluetooth Web extension polyfill (Web Bluetooth polyfill 0.4.0-Windows 10 web Bluetooth API polyfill)
The output is:

Live Output

Requesting Bluetooth Device...
Connecting to GATT Server...
Getting Service
Getting Characteristic...
> notifications started
> 0x00 0x78
> 0x00 0x78
> 0x00 0x78
> 0x00 0x78
> 0x00 0x64
> 0x00 0x64
> 0x00 0x64
> 0x00 0x50
> 0x00 0x50
> 0x00 0x50
> notifications Stopped

Can you give me some feedback?

Best regards and thanks,
Damiano

Thanks for testing! I'm guessing that the notification subscription as it exists in Chrome on Windows was probably implemented and working for some other feature in Chrome. At the moment, I'm not sure what it will take to get it working for Web Bluetooth.

At the moment, I'm not sure what it will take to get it working for Web Bluetooth.

when do you think you can take a look?

news about this?

It'd be really good to get this fixed - it's so close to being usable right now, but virtually everything relies on notifications to get data back.

I'm also very interested in this. I'm currently developing a Web Bluetooth app with a custom device which sends notifications. Having native support for Windows would be a huge 👍 . I'd be more than willing to do some testing.

Sorry, planning on taking another look soon.

Works fine on all platforms except... Windows! :)

Are there any news on this issue? I'm currently writing an article about the Espruino Platform and wanted to show how to use Google Chrome and Web Bluetooth for their IDE. Doesn't work though...

@cco3 news about this?

Sorry, I don't have any news here and I'm no longer actively working on Web Bluetooth, but the web bluetooth team is still aware of the issue and we are still pursuing Windows support.

Hi, are there any news on the topic?

Asking about this over and over again serves no purpose other than annoying the developers involved.

Since this issue tracker is for the Web Bluetooth specification and not its implementation in Chrome I am closing this issue. Please follow Chromium issue 507419 for updates on Chrome's Windows implementation.

Solved. now work on windows!