Web bluetooth StartNotification throwing NotSupported error
Reported by
moorthy...@gmail.com,
Jan 11
|
|||
Issue descriptionChrome Version : 71.0.3578.98 URLs (if applicable) :https://googlechrome.github.io/samples/web-bluetooth/notifications-async-await.html (Used custom service & characteristic identifier) What steps will reproduce the problem? (1) Input A&D Medical weighing machine's (https://medical.andonline.com/product/premium-wireless-weight-scale/uc-352ble?commerce_product=4) service and characteristic identifier in the notification sample. Service UUID - 23434100-1fe4-1eff-80cb-00ff78297d8b Character UUID - 23434101-1fe4-1eff-80cb-00ff78297d8b (2) Click on Start Notification What is the expected result? Should be able to successfully enable notification What happens instead? Got error at start notification step- "NotSupportedError: GATT operation failed for unknown reason" - Screenshot attached Please provide any additional information below. Attach a screenshot if possible. Able to connect to this device and establish notification using bluez package. Attached the chrome and platform (Mac 10.14.2) log. Tested in both windows and mac and found issue in both platform.
,
Jan 14
Thanks for filing the issue... As per comment #0, looks like this requires Premium Wireless Weight Scale device to be purchased for testing which is not possible as of now. Requesting Blink>Bluetooth team to look into it for help in triaging further. @Reporter: Can you please provide any alternate way to test this issue by using other Bluetooth device.
,
Jan 16
(6 days ago)
James to take a look at the logs.
,
Jan 17
(5 days ago)
@phanindra: Unfortunately I couldn't reproduce this issue with any other devices. Other devices which I'm testing are connecting without any issues. As i noted earlier, i'm able to connect to the weigh scale device in a custom python app which uses bluez package (bluez_5.46-0ubuntu3_armhf.deb) to connect. Also tested with nRF Connect for Android (https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en) and it works fine. I'm facing this issue only when trying to connect using web bluetooth api. Please let me know if you need any additional logs which might be helpful to debug this issue.
,
Today
(7 hours ago)
I looked into the logs and there is not enough information there. The next step would be to get the packet log from macOS. Here is a link with instructions on how to get those logs for us(https://www.chromium.org/developers/how-tos/file-web-bluetooth-bugs). |
|||
►
Sign in to add a comment |
|||
Comment 1 by phanindra.mandapaka@chromium.org
, Jan 12