-
Notifications
You must be signed in to change notification settings - Fork 2k
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
GDBus.Error:org.bluez.Error.Failed: le-connection-abort-by-local (36) #26118
Comments
@sprabhaa @bzbarsky-apple Any updates on this error yet? I face the same issue. Any potential solutions? |
Any way to fix this? I have the same issue. TH Fall2023 Sha: 3f84bff5
|
The Raspberry Pi running the chip tool must have WiFi turned off, otherwise it will cause serious interference to the BLE. You can discover the matter device, but cannot successfully establish the BLE connection. The error log is as you can see. If your Raspberry Pi‘s Wi-Fi is indeed on, please use nmcli or rfkill to turn it off, and then try to commission some matter device , you may see the success rate is almost 100%. Raspberry Pi Wi-Fi on
Wi-Fi offubuntu@ubuntu:
|
Reproduction steps
step 1: Flashed all-cluster-app in esp32-c3.
step2 : When it is in Advertise mode , we start wifi commissioning using " ./chip-tool pairing ble-wifi 0x7283 wifi-SSID wifi-password 20202021 3840 "
And getting Getting "GDBus.Error:org.bluez.Error.Failed: le-connection-abort-by-local (36)" error.
Attached complete log.
connected_home_ip_logs.txt
Query: Sometimes when we do blue tooth daemon stop and start this error is not seen, but it does not resolve the issue 100%. Kindly let us know what could be the root cause for this issue.
Bug prevalence
4 out of 5 trials.
GitHub hash of the SDK that was being used
20de612
commit 20de612 (HEAD -> master, origin/master, origin/HEAD)
Author: manjunath-grl 102359958+manjunath-grl@users.noreply.github.com
Date: Fri Feb 24 11:03:10 2023 +0530
Platform
raspi
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: