One of the problems with the early Raspberry Pi models was the lack of on-board connectivity. Ethernet aside, if you wanted to connect to a wireless network, you needed to use one of the USB ports, and in hub-less situations, this was a port you could be using for other purposes. The same was true for Bluetooth.
While the Raspberry Pi Model B+ The Raspberry Pi B+ Is Here. What's Changed? The Raspberry Pi B+ Is Here. What's Changed? Read More and Raspberry Pi 2 5 Things Only a Raspberry Pi 2 Can Do 5 Things Only a Raspberry Pi 2 Can Do The latest edition of the pint-sized computer is awesome. So awesome, in fact, that there's 5 things you can only do on a Raspberry Pi 2. Read More brought extra USB ports, the best solution could only be built-in Bluetooth and Wi-Fi, something we finally got with the Raspberry Pi 3, released in early 2016.
But how do you set up wireless networking and Bluetooth on the Raspberry Pi 3?
Wireless and Bluetooth on the Raspberry Pi 3
The Raspberry Pi 3 The Raspberry Pi 3: Faster, Better, with Wi-Fi and Bluetooth The Raspberry Pi 3: Faster, Better, with Wi-Fi and Bluetooth Today, the Raspberry Pi foundation announced the release of the Raspberry Pi 3. It's the most significant update to the popular line of low-cost computers yet. Read More comes with some nice new features, and the new wireless and Bluetooth component is arguably the most impressive. Have you spotted it yet?
You’ll find it along the short edge of the Pi where the microSD card is inserted. This small, white oblong chip antenna will connect you to your wireless router, as well as enable you to connect a Bluetooth keyboard or other device to the Pi.
However, this component is delicate. Take care when installing the Raspberry Pi 3 into a case, as the position of the chip antenna can result in it being caught. Also, thick, darker plastic (and denser) cases can block the signal to and from the chip antenna, making the device useless.
Time to set it up!
Configure Wireless Networking on the Raspberry Pi 3
To get started with the Raspberry Pi 3, you’ll need to connect it to your router with an Ethernet cable to get updates and configure Wi-Fi. Once hooked up and booted, you can plug in a keyboard or connect via SSH or VNC VNC, SSH and HDMI: Three Options for Viewing Your Raspberry Pi VNC, SSH and HDMI: Three Options for Viewing Your Raspberry Pi The Raspberry Pi is a remarkable little computer, but it can be time consuming to set it up and connect it to your monitor. Read More to run an update in the terminal.
sudo apt-get update
sudo apt-get upgradeYou’ve then got two options for setting up a wireless connection. It might seem easier to boot into the GUI, but really it’s more straightforward to do it in the command line. You should already have your SSID name, but if not, use
sudo iwlist wlan0 scanThis will reveal the SSID in the line “ESSID”. Next, open wpa_supplicant.conf:
sudo nano /etc/wpa_supplicant/wpa_supplicant.confYou’ll need to add or edit the following:
network={
ssid="SSID"
psk="WIFI PASSWORD"
}Press CTRL+X to exit and save, pressing Y and Enter to confirm. Wireless connectivity should start immediately; if not, use
sudo ifdown wlan0
sudo ifup wlan0…to restart wireless. You could also simply enter sudo reboot.
If you prefer to use the GUI, right-click the Ethernet icon in the panel (two computer monitors) and select the wireless networking option. Then all you need to do is select the correct SSID and add the password. You should now be online, and be able to disconnect the Ethernet cable!
Configure Bluetooth on the Raspberry Pi 3
To configure Bluetooth, you’ll need to begin with the update and upgrade commands, as above. Next, install the Bluetooth package:
sudo apt-get install bluetooth-piIf you prefer, you can install bluez instead, which bluetooth-pi installs along with other tools.
sudo apt-get install bluez bluez-firmwareAt this stage, everything is installed for activating Bluetooth from the command line
To get started configuring your Pi’s Bluetooth, run
bluetoothctlA host of options are available with this. Type help to see them.
For Bluetooth to work, it needs to be enabled, discoverable and capable of discovering devices.
We use three commands to do this:
power on
agent on
scan on
In this screen, you can see the Raspberry Pi has detected my Ubuntu phone. A connection can be made by entering connect, followed by the MAC address. You don’t need to connect though – you can use Bluetooth scanning as a presence detection for DIY smart home systems Make An Auto-Locking Office Door with Smartphone Proximity Sensor Make An Auto-Locking Office Door with Smartphone Proximity Sensor We'll be setting up a Raspberry Pi with a Bluetooth adapter to be on the lookout for when your smartphone is out of range, and snap a relay into action to lock the door. Read More .
Connect to Bluetooth in the GUI
If you prefer to setup your Raspberry Pi Bluetooth connections in X, you can, as long as the blueman software is installed.
sudo apt-get install bluemanYou’ll need to restart the Pi:
sudo rebootNotice how we can now be more verbal with the Pi; previously this command would have been sudo shutdown -r (which still works).
With the Pi now rebooted and the X desktop environment loaded, open Menu > Preferences > Bluetooth Manager. Nearby discoverable devices will be listed, so right-click and select Connect to begin the pairing/trust process.
Bluetooth is up and running!
When Bluetooth Fails
Although the setup is straightforward, should your hardware not be working correctly, it won’t be immediately apparent. I’ve been, um, blessed with a Raspberry Pi 3 that was defective (either due to a manufacturing fault, which is unlikely, or a fault that occurred when the device was installed in the case, again, pretty unlikely), and found that while setting up wireless networking is a complete no-go if the chip antenna is damaged, Bluetooth appears to be working.
I can’t tell you how bizarre and frustrating it is to run sudo service bluetooth status (see above) and find that all seems well with Bluetooth, only to find a couple of commands later the whole thing is pretty much out of order. With wireless and Bluetooth failing to work correctly, I’ve essentially got a very hi spec Raspberry Pi 2! Still, it’s ideal for running OSMC…
Ready to give Raspberry Pi 4 a try Why Everyone Should Try the Raspberry Pi 4: New Features and Impressive Specs Why Everyone Should Try the Raspberry Pi 4: New Features and Impressive Specs Interested in buying the Raspberry Pi 4? Here's what's new, as well as why three versions of the Raspberry Pi 4 are available. Read More ? Here’s why you should and what features you can expect.
Explore more about: Bluetooth, Raspberry Pi, Wi-Fi.
Just nudging this thread awake again...
I've been bouncing around from site to site trying to get this working. Not sure if I have a damaged pi or what the problem is. Pretty much every one (obviously) has the same basic instructions and I've followed them to a T. Rechecked my steps. Rechecked everything again, (rinse & repeat)...but I still can't connect.
Wireless says it's working on the pi after setup but when I unplug the ethernet cable, I get nothing and my wired connection in my network list goes dark with no replacing wireless connection.
I appear to have the same problem with Bluetooth, although it did say it was connected to my PC at the end of the setup but then the connection disappeared.
I now get this in my service status:
Mar 04 03:17:08 octopi bluetoothd[680]: Starting SDP server
Mar 04 03:17:08 octopi bluetoothd[680]: Bluetooth management interface 1.14 initialized
Mar 04 03:17:08 octopi bluetoothd[680]: Sap driver initialization failed.
Mar 04 03:17:08 octopi bluetoothd[680]: sap-server: Operation not permitted (1)
Mar 04 03:56:11 octopi bluetoothd[680]: a2dp-sink profile connect failed for "MyPC": Protocol not available
Mar 04 03:56:11 octopi bluetoothd[680]: a2dp-source profile connect failed for "MyPC": Protocol not available
Mar 04 03:56:36 octopi bluetoothd[680]: a2dp-sink profile connect failed for "MyPC": Protocol not available
Mar 04 03:56:36 octopi bluetoothd[680]: a2dp-source profile connect failed for "MyPC": Protocol not available
Mar 04 04:03:02 octopi bluetoothd[680]: a2dp-sink profile connect failed for "MyPC": Protocol not available
Mar 04 04:03:02 octopi bluetoothd[680]: a2dp-source profile connect failed for "MyPC": Protocol not available
I don't even know what this means and probably says the answer right there but I don't know how to fix it. I'm now drinking copious amounts of rum (medicinally-for my nerves from dealing with this issue of course) and this is just getting harder so I'm calling it quits for tonight. Maybe tomorrow I can look at this again through hangover fogged eyeballs and it will become clear (doubt it), or some kind soul will have the answer for me and become my brand new favoritest person in the whole world.
I'm using a Pi3 and have installed both bluetooth and Wifi. Wifi works fine and bluetooth works 100% with BUT ONLY if wifi is switched off. With wifi on bluetooth disconnects from the keyboard sporadically - bluetooth keboard is pure frustration unless wifi is off.
That sounds very annoying. Is yours a recent device or an older Pi3?
The Pi3 was purchased 11/2016. The bluetooth keyboard works fine as long as wifi is off. wifi on results in frequent and random disconnects that require the keyboard to be switched on/off to reestablish connection. Others have reported this problem as well.
Yeah, I've heard of others having the issue, wondered if it was a batch problem.
R-pi3b, trying to access wirelessly via a Mac computer.
Ran through the setup instructions as described above to try to access the pi , but I'm not showing the Pi connected to my router unless I plug the ethernet cable in. No Wifi.
If I connect the ethernet cable, the pi does seem to see my network: when I try "ssh pi@octopi.local" i am connected to the pi. Issuing the "sudo iwlist wlan0 scan" command does show my network, with info on signal strength.
When I disconnect the Ethernet cable, I can no longer connect to my pi, and checking the router DHCP list there is no connection from my pi (it shows up as octopi.local when the Ethernet cable is connected).
Any thoughts?
Have you tried a full update, or a fresh install? Possible the Wi-Fi driver isn't installed.
I finally figured it out. I had edited the SSID and password using the Mac's TextEdit program. It turns out this program substitutes a different kind of quotation mark than the ones the Pi is looking for if you type the quotes in by hand, or even if you edit the text right next to them (the wrong quotation marks appeared "curly"). I could not figure out how to get my Mac to type the correct kind of quotes. I ended up copying the correct type of quotation marks from an unedited part of the file and pasting them in around the SSID and password in place of the curly quotation marks that had appeared.
I've since found out you can turn off this annoying behavior in TextEdit: Go to the TextEdit menu and choose Preferences. Select "Plain Text", and turn off "Smart Quotes" & "Smart Dashes"
Good advice, great to see you've sorted it out!
Tried using a 'Microsoft Designer Mouse' - this will pair but a message we get is there are no services for this device. Bluetooth BLE devices have a problem connecting. Tried with Ubuntu Mate, Windows 10 IOT and Jessie. Not much use contacting Microsoft - they are not interested, their BB is full of people with this problem even with Windows 10 grrrrrrrrrrrrrrrrr
Ahh, that's sad to hear -- always seems the way with the Microsoft support forums.
I just went through the process for setting up the Wi-Fi and all went well. It took a few seconds for the Wi-Fi connection to show up but then I was immediately able to disconnect the ethernet cable. I didn't try the Bluetooth set up because I don't have a Bluetooth device but will bookmark this for later.
Thank you for the easy to follow instructions!
Gary
Happy to help Gary, thanks!
Every time I try to connect my phone, the terminal says "Failed to connect: org.bluez.Error.Failed" and on my pi is says that I have "no usable services" on my device
I cant connect to any wifi on rpi3b using ubuntu mate. Simply the SOs dont detect any wifi networks, while my cellphone detects 18.
How does it fair with Raspbian? Checking that will determine whether you've got a suspect wireless radio.
That sounds like a BT driver issue, *or* the BT hardware has failed. My first Pi3 had working BT and Wi-Fi for about a day before it stopped working. You should probably contact the vendor to arrange a replacement.