I unfortunately missed a small but important step in the first post
Once reloading the udev rules, you'll also want
udevadm trigger to put the new one into effect.
Quote:
Originally Posted by kbarni
We tried to debug my issue with Clint and Sighery, it's a problem with the authentication using the pairing process. The keyboard asks for a pairing confirmation that doesn't show up in the ace_bt_cli interface.
|
I do think there's still a possibility of pairing devices that require a PIN -- I don't personally have any to test with, though.
If anyone else wants to test -- once you run
pair <addr> you can then run
pin 0000 while the pairing is still in progress and it hasn't timed out. (The output is confusing because it writes over the prompt, but running the
pin is only possible after a pairing address has been set internally.)