You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you connect your phone to the pi and then re-install your phone / forget the device / anything that makes the bluetooth data inconsistent between the pi and the phone makes the pi completely unconnectable.
Connections and their data are stored in /var/lib/bluetooth/<BT-Adapater-Mac>/<device-id> and /var/lib/bluetooth/<BT-Adapter-Mac>/cache/<device-id>, but don't seem to be removed / replaced with new data from the device.
That results in the error message "Couldn't pair with becuase of an incorrect PIN or passkey".
Removing the above directories and then running sudo systemctl restart bluetooth makes the pi reconnectable.
It's possible to replace the keys using bluetoothctl. But idk how to properly integrate it. Maybe it could be stuck into the reconnect script. #7
bluetoothctl
# remove old keys
remove <device-id>
scan on
# wait for 5 secs
# requires device to be broadcasting it's id AKA Searching for new devices
scan off
trust <device-id>
connect <device-id>
The text was updated successfully, but these errors were encountered:
Once you connect your phone to the pi and then re-install your phone / forget the device / anything that makes the bluetooth data inconsistent between the pi and the phone makes the pi completely unconnectable.
Connections and their data are stored in
/var/lib/bluetooth/<BT-Adapater-Mac>/<device-id>
and/var/lib/bluetooth/<BT-Adapter-Mac>/cache/<device-id>
, but don't seem to be removed / replaced with new data from the device.That results in the error message "Couldn't pair with becuase of an incorrect PIN or passkey".
Removing the above directories and then running
sudo systemctl restart bluetooth
makes the pi reconnectable.It's possible to replace the keys using bluetoothctl. But idk how to properly integrate it. Maybe it could be stuck into the reconnect script. #7
The text was updated successfully, but these errors were encountered: