Skip to content

Commit c98883b

Browse files
authored
Add troubleshooting step for "Not connected" problems on Raspberry Pi. (#1670)
Disabling wifi on Raspberry- and Rock Pi can greatly improve the stability of Bluetooth.
1 parent 8073b41 commit c98883b

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

docs/troubleshooting.rst

+27
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,33 @@ crash with an ``ImportError`` similar to::
118118

119119
To fix the error, change the name of the script to something other than ``bleak.py``.
120120

121+
----------
122+
Linux Bugs
123+
----------
124+
125+
Occasional "Not connected" errors on Raspberry Pi
126+
=================================================
127+
128+
If you are using the built in WiFi/Bluetooth module on a Raspberry Pi and and are seeing occasional
129+
"Not connected" errors, also manifesting as HCI error 0x3e and BlueZ error "Software caused
130+
connection abort", when trying to connect to a device, it may be due to wifi interference on
131+
the chip level.
132+
133+
As a test the wifi interface can be disabled using either
134+
135+
.. code-block:: shell
136+
137+
sudo rfkill block wlan
138+
139+
or
140+
141+
.. code-block:: shell
142+
143+
sudo nmcli radio wifi off
144+
145+
See `this <https://github.com/project-chip/connectedhomeip/issues/16178>`_ Matter issue
146+
with similar problems on Raspberry Pi and other devices.
147+
121148
----------
122149
macOS Bugs
123150
----------

0 commit comments

Comments
 (0)