Recently, the environment for using BLE on desktop PCs has been prepared. This time, we will talk about making Web Bluetooth available on Ubuntu 20.04.
「Implementation Status」 https://github.com/WebBluetoothCG/web-bluetooth/blob/master/implementation-status.md
「Linux is partially implemented and not supported. The chrome://flags/#enable-experimental-web-platform-features flag must be enabled.」
There is. Also,
「Linux: Requires Kernel 3.19+ and BlueZ 5.41+ installed. Read How to get Chrome Web Bluetooth working on Linux. Note that Bluetooth daemon needs to run with experimental interfaces if BlueZ version is lower than 5.43: sudo /usr/sbin/bluetoothd -E」
There was also. Previously, when I tried it on Ubuntu16.04, the version of BlueZ was low and it didn't work. Well, I wonder if it will work this time ...
Now, https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetooth_API According to it, firefox is not supported.
Originally, when you try to pair, the following dialog will appear.
This site has been confirmed to appear on Google Chrome on Windows 10 and Android, but not on Google Chrome on Linux.
First, let's check bluez.
$ sudo apt install bluez Loading the package list...Done Creating a dependency tree Reading status information...Done bluez is already the latest version(5.53-0ubuntu3)is. The following packages were installed automatically but are no longer needed: libfprint-2-tod1 libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib python2 python2-minimal python2.7 python2.7-minimal To remove this'sudo apt autoremove'Please use. upgrade:0 pieces, new installation:0, deleted:0 pieces, pending:11 pieces.
It was already in. The version is also 5.53, so there seems to be no problem.
chrome://flags Open and #enable-experimental-web-platform-features To Enabled.
It was convenient to be able to access directly with the following URL.
With Google Chrome, you can now use Web Bluetooth by itself.
I also tried it on Chromium. chrome://flags/#enable-experimental-web-platform-features Go to and enable it as above. After restarting the browser, I tried it and it was OK.