Skip to content

Commit

Permalink
Add troubleshooting step for "Not connected" problems on Raspberry Pi. (
Browse files Browse the repository at this point in the history
#1670)

Disabling wifi on Raspberry- and Rock Pi can greatly improve the stability
of Bluetooth.
  • Loading branch information
denravonska authored Oct 19, 2024
1 parent 8073b41 commit c98883b
Showing 1 changed file with 27 additions and 0 deletions.
27 changes: 27 additions & 0 deletions docs/troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,33 @@ crash with an ``ImportError`` similar to::

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

----------
Linux Bugs
----------

Occasional "Not connected" errors on Raspberry Pi
=================================================

If you are using the built in WiFi/Bluetooth module on a Raspberry Pi and and are seeing occasional
"Not connected" errors, also manifesting as HCI error 0x3e and BlueZ error "Software caused
connection abort", when trying to connect to a device, it may be due to wifi interference on
the chip level.

As a test the wifi interface can be disabled using either

.. code-block:: shell
sudo rfkill block wlan
or

.. code-block:: shell
sudo nmcli radio wifi off
See `this <https://github.com/project-chip/connectedhomeip/issues/16178>`_ Matter issue
with similar problems on Raspberry Pi and other devices.

----------
macOS Bugs
----------
Expand Down

0 comments on commit c98883b

Please sign in to comment.