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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 2 commits into from
Oct 19, 2024
Merged

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

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e5ff67e
Add troubleshooting step for "Not connected" problems on Raspberry Pi.
denravonska Oct 18, 2024
6cd945f
Clarify Raspberry Pi WiFi/Bluetooth issue.
denravonska Oct 19, 2024
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
View file
Open in desktop
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 a Raspberry Pi and are seeing occasional "Not connected" errors,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this is using the built-in WiFi and Bluetooth on the newer RPis? Probably would be helpful to clarify that in the text.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If what I'm suspecting is correct you're right, it shouldn't affect USB connected radios as they don't use the same chip. I'll see if it can be rephrased.

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