Re: [RFC][PATCH 0/4] Allow hexadecimal encoded pins

[Daniele Forsi <dforsi@gmail.com>]

2011/5/3 David Herrmann:
> On Tue, May 3, 2011 at 1:32 AM, Bastien Nocera wrote:
>> What are the necessary changes to be made in gnome-bluetooth?
>>
>> I'm guessing that we should add a "WIIMOTE" type of special casing in
>> the pin database, and pass the adapter address as per the above when a
>> PIN is requested.
>
> Exactly. If I click on PIN-type in gnome-bluetooth applet, then there
> are already several choices I can make. I'd recommend adding a new one
> with "use source address as PIN" and one with "use destination address
> as PIN".

yeah, automatically shown only when the selected device is a Wiimote

one issue when using the 1+2 way is that the Wiimote will forget the
pairing when it is turned off while the PC will remember it, so the
Wiimote won't be shown in the list of found devices and you need to
delete it before you can pair again

>> Is there any way to detect which "type" of pairing is made with the
>> Wiimote, eg. you say that button 1+2 will only work for temporary
>> connections. Can we detect this? Would pairing anyway work?
>
> I guess you mean that you wanna predict which PIN to use? No, I
> currently know no way to detect this. However, one may try the first
> pin and if that fails the second pin.

I think this is what the Wii does when in the "home" screen where you
are supposed to press 1+2 because it will find the remote also when
pressing the sync button (I have a Wiimote that I need to pair from
the home screen pressing sync because it doesn't wake up with 1+2)

-- 
Daniele Forsi