On Tue, Dec 10, 2013 at 8:39 PM, valent.turkovic@xxxxxxxxx <valent.turkovic@xxxxxxxxx> wrote: > Hi, > on OpenWrt latest version of bluez-utils is still 3.36 and when I add > pin_helper to hcid.conf file I see this error when starting hcid > daemon: > > # hcid -n > hcid[1063]: Bluetooth HCI daemon > hcid[1063]: Unknown option 'pin_helper' line 26 > > > Should bluez-utils 3.36 have support for pin_helper by default? I have > checked source code of OpenWrt and can't find any patch that disables > pin_helper. > > What could the issue here? Ah, I was already searching day ago for this issue an by Murphy's Law as soon as email was send I found an answer: "the "pin_helper" option is only valid with bluez-libs-2.x & bluez-utils-2.x and below. Thats what is causing the service to fail to start up. Bluez-3.X has replaced pin helpers with passkey agents such as kbluetoothd and bluez-gnome, the bluez-utils also comes with an command line agent passkey-agent. " Can anybody please point me in the direction of documentation that explains how to use passkey agents on bluez-utils 3.x and later? I saw that BlueZ website had wiki but that it is no longer available. -- 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
