It means that as a workaround a pin confirmation is asked on the client side. Just accepting the PIN is enough. No actual way to verify that pin has been implemented on the server side.
It is a step back compared to Buster and the auto accept policy, without having to verify and confirm a PIN.
Check regularly the state of this bug in order to get back to the desired behavior, or implement an actual PIN confirmation.
Apparently the version of bluez used in Bullseye (5.55) has a bug that prevents the
NoInputNoOutput
capacity to work. see: https://github.com/RPi-Distro/repo/issues/291It means that as a workaround a pin confirmation is asked on the client side. Just accepting the PIN is enough. No actual way to verify that pin has been implemented on the server side.
It is a step back compared to Buster and the auto accept policy, without having to verify and confirm a PIN.
Check regularly the state of this bug in order to get back to the desired behavior, or implement an actual PIN confirmation.
simple-agent
needs to be called with-c NoInputNoOutput
in https://github.com/pirateradiohack/Transistor/blob/master/stage2/04-pirate-radio/files/etc/systemd/system/bluetooth-agent.service