Re: Entering the PIN of a device?

[Fabrice DELENTE <delentef@gmail.com>]

> There was no CC ;) CC is enough of course.

Strange, mutt showed me a CC though...

> No, don't! The user shouldn't care what protocols are used. I just
> wanted to notify you that using rfcomm won't work here.

Ok, ok, won't do :^)

> This is exactly what should happen, yes. No PIN as BlueZ generates
> it for you.

I guess it hasn't, because when I try simple-agent hci0 $WIIMOTE, it
asks for a PIN?

> Did the device show up in /sys/bus/hid/devices ? Did you check
> dmesg? I think you got the device connected successfully, it just
> doesn't do anything useful without configuration ;)

Well nothing showed in /sys/bus/hid/devices, nor in dmesg. The only
thing I had was in /var/log/messages, after trying the simple-agent
hci0 $WIIMOTE thing:

Feb 14 19:11:11 slick dbus-daemon: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.65" (uid=0 pid=17775 comm="/usr/bin/python) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.9" (uid=0 pid=1930 comm="/usr/sbin/bluetoothd))

> You may also want to have a look at
> https://wiki.archlinux.org/index.php/XWiimote This is a short
> summary of the current state of the xwiimote drivers.  The
> user-space part is still under development so you might want to look
> at cwiid instead.

Will do. I thought cwiid was abandonned, and replaced by the kernel
driver?

Thanks again!

-- 
F. Delente