Re: [Bluez-users] How do I reset a pairing?

Marcel Holtmann
2006-08-30T09:52:35Z

Hi Bearcat,

> Ok, the passkey-agent runs. But i get errors. Here's what i'm doing:
>
> 1. Switch to root.
> 1. put headset into paring mode.
> 2. run "btsco 00:0D:44:4F:37:72"
> 3. run "passkey-agent 0000 00:0D:44:4F:37:72"
>
> I get "Can't get on system bus" from passkey-agent. Is dbus misconfigured?

might be. You can however use "passkey-agent --default 0000" to be on
the safe side. There is a difference between the default passkey agent
and the application specific passkey agent.

> I know dbus is running. The "00:0D:44:4F:37:72" is the address of my
> headset. "0:07:61:1C:9F:D3" is the address of my hub. I've tried that as
> well. I've also tried encapsulating the 0000 with quotes in case it is a
> string. I am running passkey-agent as root.

Not needed to run it as root.

> What am i doing wrong. Is there a way to create the file
> in /var/lib/bluetooth\00:07:61:1C:9F:D3 by hand? What should the file be
> called and what should it contain.

You can use /var/lib/bluetooth/00:07:61:1C:9F:D3/pincodes and add a line
with "00:0D:44:4F:37:72 0000" this will make the need of a passkey agent
for that specific remote device obsolete.

> I am very confused by the configuration of all this. I have seen documentation
> that states that i need:
>
> 1. passkey "0000" in my hcid.conf file

No. This PIN code is only for incoming connections.

> 2. a /etc/bluetooth/passkeys/default file.

This is Debian specific crap and has to go away anyway.

> 3. A script to be called in the config file

No longer supported as of 3.x releases.

> 4. and now a passkey agent.

That is of course the preferred way and the distribution should make it
work nicely for you. Especially since bluez-gnome now contains a really
good example for a passkey agent.

Regards

Marcel