On Tue, May 3, 2011 at 2:27 PM, Daniele Forsi <dforsi@xxxxxxxxx> wrote: > 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 I don't get this. If the wiimote is listed as paired, why would you want to see it in the list of found devices? The wiimote is already listed as paired so simply reestablish the pairing by connecting to the wiimote via DBus bluez.Input api. >>> 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) With 1+2 buttons only the dest-address works as PIN (I checked this). However, with "sync" button both addresses may work. I will check this later... Anyway, this would simplify the wiimote handling significantly. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
