Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add troubleshooting step for "Not connected" problems on Raspberry Pi. #1670

Merged
merged 2 commits into from
Oct 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Loading