Re: [web-bluetooth] status of start/stop notifications for chrome windows

@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

1) Pair the newly created peripheral: Windows-> Settings-> Bluetooth-> pair a device-> Heart Rate-> Insert pin.
2) Open Chrome Canary at URL: chrome://flags/#enable-Experimental-web-platform-features-> enable (if disabled)
3) Restart Chrome Canary to apply the changes (if point 2 was disabled)
4) Open Chrome Canary at URL: https://googlechrome.github.io/samples/web-bluetooth/notifications.html
5) Select Bluetooth Service: heart_rate
6) Select Bluetooth Characteristic: heart_rate_measurement
7) 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


-- 
GitHub Notification of comment by dmazzella
Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/387#issuecomment-366368740 using your GitHub account

Received on Friday, 16 February 2018 21:52:07 UTC