New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

status of start/stop notifications for chrome windows #387

Closed
dmazzella opened this Issue Feb 14, 2018 · 16 comments

Comments

Projects
None yet
9 participants
@dmazzella
Copy link

dmazzella commented Feb 14, 2018

What about the status of implementation about startNotifications/stopNotifications for use event on characteristicvaluechanged in chrome for windows?

Where i can read about this?

Thanks and regards,
Damiano.

@beaufortfrancois

This comment has been minimized.

Copy link
Member

beaufortfrancois commented Feb 15, 2018

@cco3 may be able to help there.

@dmazzella dmazzella changed the title status of start/stop notification for chrome windows status of start/stop notifications for chrome windows Feb 15, 2018

@cco3

This comment has been minimized.

Copy link

cco3 commented Feb 16, 2018

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.

@dmazzella

This comment has been minimized.

Copy link

dmazzella commented Feb 16, 2018

@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

@cco3

This comment has been minimized.

Copy link

cco3 commented Feb 16, 2018

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.

@dmazzella

This comment has been minimized.

Copy link

dmazzella commented Feb 19, 2018

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?

@dmazzella

This comment has been minimized.

Copy link

dmazzella commented Mar 2, 2018

news about this?

@gfwilliams

This comment has been minimized.

Copy link

gfwilliams commented Mar 2, 2018

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.

@brianz

This comment has been minimized.

Copy link

brianz commented Mar 2, 2018

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.

@cco3

This comment has been minimized.

Copy link

cco3 commented Mar 2, 2018

Sorry, planning on taking another look soon.

@vshymanskyy

This comment has been minimized.

Copy link

vshymanskyy commented Mar 28, 2018

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

@jsiebert

This comment has been minimized.

Copy link

jsiebert commented Apr 18, 2018

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...

@dmazzella

This comment has been minimized.

Copy link

dmazzella commented May 14, 2018

@cco3 news about this?

@cco3

This comment has been minimized.

Copy link

cco3 commented May 14, 2018

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.

@motivado

This comment has been minimized.

Copy link

motivado commented May 28, 2018

Hi, are there any news on the topic?

@reillyeon

This comment has been minimized.

Copy link
Contributor

reillyeon commented May 28, 2018

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.

@reillyeon reillyeon closed this May 28, 2018

@dmazzella

This comment has been minimized.

Copy link

dmazzella commented Aug 20, 2018

Solved. now work on windows!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment