Some other properties did work for me: $ dbus-send -print-reply=literal -system -dest=org.bluez /org/bluez/hci0/dev_E4_0C_E6_59_B6_FC .Get string:'org.bluez. Received Signal Strength Indicator of the remoteīut that didn't work for me: $ dbus-send -print-reply=literal -system -dest=org.bluez /org/bluez/hci0/dev_E4_0C_E6_59_B6_FC .Get string:'1' string:'RSSI'Įrror .InvalidArgs: No such property 'RSSI'

I think you may also be able to use BlueZ's DBus RSSI property of the 1 interface : int16 RSSI (You have the code for that command at ).

$ sudo btmgmt conn-info -t 2 E4:0C:E6:59:B6:FCĬonnection Information for E4:0C:E6:59:B6:FC (LE Random) Note that when using btmon you do not have to connect to get the rssi of a BLE device.įor connected devices you can use btmgmt conn-infoĮ.g. The results displayed on the monitor should be similar to this: > HCI Event: LE Meta Event (0x3e) plen 12Įvent type: Scan response - SCAN_RSP (0x04) RSSI (Received Signal Strength Indicator) For Bluetooth, it is the strength of the beacon’s signal as seen on the receiving device, e.g. Run btmon in the background then scan for Bluetooth Low Energy devices: #./btmon & static void cmd_rssi(int dev_id, int argc, char **argv)įor Bluetooth Low Energy, I only know one way to do this, and that is using the #btmon command. If you want to see the actual C code to achieve this, take a look at the bluez tools/hcitool.c file, under the cmd_rssi function. If you want to achieve this from the command line, try: #hcitool rssi AA:BB:CC:DD:EE:FF However, you have to be connected to get the rssi of a device. On Linux, the way to do this is with the hcitool command.

Bt rssi