Open abmantis opened 11 months ago
I just noticed this on journalctl:
Oct 06 02:19:40 kiwi bluetoothd[770018]: src/device.c:new_auth() No agent available for request type 2
Oct 06 02:19:40 kiwi bluetoothd[770018]: device_confirm_passkey: Operation not permitted
I guess we need #1100 ?
I guess we need #1100 ?
Yes.
@abmantis , as a workaround, you could attempt to register the authentication agent you need for your device using bt-agent from the bluez-tools package as outlined in this doc https://technotes.kynetics.com/2018/pairing_agents_bluez/.
@abmantis , as a workaround, you could attempt to register the authentication agent you need for your device using bt-agent from the bluez-tools package as outlined in this doc https://technotes.kynetics.com/2018/pairing_agents_bluez/.
Interesting. Thanks! I will look into that option.
I'm having this issue suddenly too trying to tether and the above works... but on fedora and i have no idea what bleak does...
bluetoothctl -v
) in case of Linux: 5.69Description
client.pair()
fails withbleak.exc.BleakDBusError: [org.bluez.Error.AuthenticationFailed] Authentication Failed
, unlessbluetoothctl
is running, or the Gnome Control Center bluetooth page is open.What I Did
I added the Idasen Desk integration to HA, and after some issue reports from users, I was able to reproduce it locally with the following:
Logs
Without
bluetootctl
running:With
bluetoothctl running
: