Raspberry Pi Stack Exchange is a question and answer site for users and developers of hardware and software for Raspberry Pi. It only takes a minute to sign up.
Sign up to join this community
I am running a headless Raspberry PI 3, and I want it to automatically accept pairings from any device.
I saw this answer in an identical question:
Automatically accepting Bluetooth connections on a Pi 3
But it seems to be a bit outdated and some of the used commands don't seem to exist.
I am running the 2016-05-27-raspbian-jessie.img OS image.
Since bluetooth-agent command doesn't exist on Jessie, the modern way is to pipe relevant commands to bluetoothctl. Based on this SO question, the following script should enable automatic pairing without manual pin entry:
sudo bluetoothctl <<EOF
power on
discoverable on
pairable on
agent NoInputNoOutput
default-agent
EOF
hciconfig hci0 piscan and hciconfig hci0 sspmode 1
hciconfig hci0 class 0x400100. After this I cannot connect RFCOMM socket without prior pairing.
I was facing the same issue and found this method to work (RasPi 3, Model B, Raspbian 9 Stretch)
I am using Raspberry Pi as an IoT EDGE Device and needed it to accept Bluetooth Pair Requests without intervention. I have an Android App that communicates text information to the Pi via Bluetooth and my problem statement needed any Android device to connect.
Firstly, I am not running any separate Bluetooth Agents (No Blueman, infact I had to remove it)
Edited the .bashrc file at
sudo nano /home/pi/.bashrc
Added two commands to this at the end
sudo hciconfig hci0 piscan
sudo hciconfig hci0 sspmode 1
piscan makes Raspberry Pi Bluetooth discoverable
sspmode 1 enables 'Secure Simple Pairing' which is the same type of method used by your Bluetooth Earphones or Speakers (basically devices that don't have a display where you can confirm PIN). And since these commands are in .bashrc they run at boot.
Run Bluetooth Script. Pair. Although there is a pop-up asking me to confirm, I can communicate messages to and from the Pi with my app
Note : hci0 may not be the same throughout, could be hci1, hci2 please check by running hciconfig on your CLI
This is almost like a contraption, and I am not sure if there are any unknown repercussions, but it works. Any improvements are appreciated
hciconfig hci0 up just in case the Bluetooth is feeling down that day.
I just used a fresh install of 2016-09-23-raspbian-jessie-lite.img to try it without any additional updates. No apt-get update no apt-get install bluez-utils or anything. This single command makes the Pi discoverable and pairable. Without an agent to control who can connect, it just lets anyone:
sudo hciconfig hci0 piscan
One simple way is Just to remove the Blueman if you have installed it by using
sudo apt remove blueman
And remove the Bluetooth logo from the top menu by right click and remove.
And install bluedot using
sudo pip3 install bluedot
for more about bluedot click here
import time
from bluedot.btcomm import BluetoothServer
import os
import bluetooth
def data_received(data):
print(data)
s.send(data)
os.system('bluetoothctl discoverable on && bluetoothctl agent NoInputNoOutput')
time.sleep(2)
s = BluetoothServer(data_received)
Now In Android phone go to Bluetooth settings and pair raspberry Pi
And if you will send data it will print on the terminal you can check it's working or not by using this application if you didn't develop your own.
I have to make clear some terminology:
I am currently working on a project which involves bluetooth pairing in Linux - note that the server you want to connect (defined as bluetooth server - i.e MUST HAVE the "Just works" (aka NoInputNoOutput) capability in order to work. "Just works" means exactly that - the pairing is in the simplest form: does not require authorization/pin/confirmation etc (Hence No Input No Output)
Now, due to the explaination above, automatic pairing becomes a relative term: automatic in relation to what?
In conclusion, it depends on the capability of the bluetooth device you want to connect to (you are the client, again).
I banged my head to the wall for a long time until I realized this and I was trying to autopair something that is not autopairable.
the device you want to connect... that would not be the RPi I'll guess - but what type of device is it?; perhaps some insight into what exactly "Just works" is?
sudo apt install bluez-tools
sudo bt-agent -c DisplayOnly -p pins.txt
pins.txt:
00:00:00:00:00:00 *
* *
You may take a peek at the source code of EcoDroidLink. It accepts Bluetooth connections without the need to log in.
EDIT: By popular demand, here are code excerpts of the edl_agent
module that makes this happen.
# - automate the agent for running on a headless Pi - to answer pair and connection requests without a blocking query
import dbus
import dbus.service
import dbus.mainloop.glib
import bluezutils
BUS_NAME = 'org.bluez'
AGENT_INTERFACE = 'org.bluez.Agent1'
AGENT_PATH = "/test/agent"
bus = None
device_obj = None
dev_path = None
def set_trusted(path):
props = dbus.Interface(bus.get_object("org.bluez", path),
"org.freedesktop.DBus.Properties")
props.Set("org.bluez.Device1", "Trusted", True)
def dev_connect(path):
dev = dbus.Interface(bus.get_object("org.bluez", path),
"org.bluez.Device1")
dev.Connect()
class Rejected(dbus.DBusException):
_dbus_error_name = "org.bluez.Error.Rejected"
class Agent(dbus.service.Object):
exit_on_release = True
def set_exit_on_release(self, exit_on_release):
self.exit_on_release = exit_on_release
@dbus.service.method(AGENT_INTERFACE,
in_signature="", out_signature="")
def Release(self):
printlog("Release")
if self.exit_on_release:
mainloop.quit()
@dbus.service.method(AGENT_INTERFACE,
in_signature="os", out_signature="")
def AuthorizeService(self, device, uuid):
printlog("AuthorizeService (%s, %s)" % (device, uuid))
authorize = "yes" #ask("Authorize connection (yes/no): ")
if (authorize == "yes"):
return
raise Rejected("Connection rejected by user")
@dbus.service.method(AGENT_INTERFACE,
in_signature="o", out_signature="s")
def RequestPinCode(self, device):
printlog("RequestPinCode (%s)" % (device))
set_trusted(device)
return "0000" #ask("Enter PIN Code: ")
@dbus.service.method(AGENT_INTERFACE,
in_signature="o", out_signature="u")
def RequestPasskey(self, device):
printlog("RequestPasskey (%s)" % (device))
set_trusted(device)
passkey = "0000" #ask("Enter passkey: ")
return dbus.UInt32(passkey)
@dbus.service.method(AGENT_INTERFACE,
in_signature="ouq", out_signature="")
def DisplayPasskey(self, device, passkey, entered):
printlog("DisplayPasskey (%s, %06u entered %u)" %
(device, passkey, entered))
@dbus.service.method(AGENT_INTERFACE,
in_signature="os", out_signature="")
def DisplayPinCode(self, device, pincode):
printlog("DisplayPinCode (%s, %s)" % (device, pincode))
@dbus.service.method(AGENT_INTERFACE,
in_signature="ou", out_signature="")
def RequestConfirmation(self, device, passkey):
printlog("RequestConfirmation (%s, %06d)" % (device, passkey))
confirm = "yes" #ask("Confirm passkey (yes/no): ")
if (confirm == "yes"):
set_trusted(device)
return
raise Rejected("Passkey doesn't match")
@dbus.service.method(AGENT_INTERFACE,
in_signature="o", out_signature="")
def RequestAuthorization(self, device):
printlog("RequestAuthorization (%s)" % (device))
auth = "yes" #ask("Authorize? (yes/no): ")
if (auth == "yes"):
return
raise Rejected("Pairing rejected")
@dbus.service.method(AGENT_INTERFACE,
in_signature="", out_signature="")
def Cancel(self):
printlog("Cancel")
Raspbian - Jessie
sudo apt-get install expect
xxxxx.sh
#!/usr/bin/expect -f
set prompt "#"
spawn sudo bluetoothctl
sleep 1
expect -re $prompt
sleep 1
send "agent NoInputNoOutput\r"
sleep 2
expect "Agent registered"
send "default-agent\r"
expect -re $prompt
sleep 3
interact
expect eof
bluetoothctl is inferior to calling hciconfig hci0 piscan and hciconfig hci0 sspmode 1
bluetooth-agent, but I am not sure.