HTTPS only #īecause this experimental API is a powerful new feature added to the web, it is made available only to secure contexts. To understand the security tradeoffs, I recommend the Web Bluetooth Security Model post from Jeffrey Yasskin, a software engineer on the Chrome team, working on the Web Bluetooth API specification. The trial has successfully ended in January 2017. In order to get as much feedback as possible from developers using the Web Bluetooth API in the field, Chrome has previously added this feature in Chrome 53 as an origin trial for Chrome OS, Android, and Mac. See MDN's Browser compatibility table for more information.įor Linux and earlier versions of Windows, enable the #experimental-web-platform-features flag in about://flags. This means you should be able to request and connect to nearby Bluetooth Low Energy devices, read/ write Bluetooth characteristics, receive GATT Notifications, know when a Bluetooth device gets disconnected, and even read and write to Bluetooth descriptors.
BLUETOOTH STACK SERVICE WINDOWS 10
This article assumes you have some basic knowledge of how Bluetooth Low Energy (BLE) and the Generic Attribute Profile (GATT) work.Įven though the Web Bluetooth API specification is not finalized yet, the spec authors are actively looking for enthusiastic developers to try out this API and give feedback on the spec and feedback on the implementation.Ī subset of the Web Bluetooth API is available in Chrome OS, Chrome for Android 6.0, Mac (Chrome 56) and Windows 10 (Chrome 70). The Web Bluetooth API aims to change this and brings it to web browsers as well. Until now, the ability to interact with Bluetooth devices has been possible only for platform-specific apps. What if I told you websites could communicate with nearby Bluetooth devices in a secure and privacy-preserving way? This way, heart rate monitors, singing lightbulbs, and even turtles could interact directly with a website. Read and write to Bluetooth descriptors.