Unlike USB devices, the removable device capability is never used to generate container IDs for Bluetooth devices. Therefore, a container ID for Bluetooth devnodes and services is always based on the MAC address value. Starting with Windows 7, the operating system considers Bluetooth services to be functional device interfaces, and groups these services together with the Bluetooth devnodes for a device.Īll Bluetooth devices must include a MAC address.
However, these services are effectively functional device instances, because they provide specific functionality and enable communication with the Bluetooth device. These services are not installed as Windows PnP devices and therefore do not have associated devnodes. This container ID is supplied by the Bluetooth bus driver for each Bluetooth device node ( devnode) that is enumerated for a physical device.īluetooth devices frequently implement Bluetooth-specific services. The Bluetooth bus driver uses the MAC address as a seed value to generate a unique container ID for the device. You can also get the version number of LMP on a connected Bluetooth device by its MAC address.For a Bluetooth device that is connected to the computer, the device's media access control (MAC) address is used to generate a container ID for the device. In our example, HCI number 0圆 corresponds to Bluetooth version 4.0. On Ubuntu Linux, open a console and run the command: hciconfig -aĭetermine the Bluetooth version according to the table. You can also use the deprecated hciconfig and hcitool utilities to get Bluetooth info.
Run the following command to display the MAC addresses of your Bluetooth adapters and their versions: btmgmt info | awk 'BEGIN' In order to install this package, run the command: sudo apt install bluez In Ubuntu and Debian distros you can use tools from the bluez package to manage Bluetooth devices and connections. In this article, we’ll look at how to find out the version of the Bluetooth adapter on a Linux computer or laptop.
0 kommentar(er)
