linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "W.P." <laurentp@wp.pl>
To: linux-bluetooth@vger.kernel.org
Subject: Re: pairing device in text mode
Date: Fri, 01 Jul 2011 11:38:39 +0200	[thread overview]
Message-ID: <4E0D959F.5050201@wp.pl> (raw)
In-Reply-To: <20110701084439.GA6461@dell.ger.corp.intel.com>

Użytkownik Johan Hedberg napisał:
> On Fri, Jul 01, 2011, W.P. wrote:
>   
>> How can I do this in text mode?
>>     
>
> You can pair with "simple-agent hci0 <remote address>". To simply create
> a new device object without pairing you can use "test-device create
> <remote address>". Once you've created the object you can connect HID to
> the device with "test-input connect <remote address". To make it
> possible for the remote device to connect back to you later without user
> interaction do "test-device trusted <remote address> yes". simple-agent,
> test-input and test-device can be found under the test subdirectory in
> the source tree.
>
>   
[root@laurent-home test]# test-device create 00:1A:40:01:AE:09
New device (/org/bluez/2269/hci0/dev_00_1A_40_01_AE_09)

But:
[root@laurent-home test]# test-input connect 00:1A:40:01:AE:09
Traceback (most recent call last):
  File "/usr/bin/test-input", line 40, in <module>
    input.Connect()
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in
__call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in
__call__
    **keywords)
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 630,
in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.Failed: Connection
refused (111)

linkkeys not added.

What should I do / check?
> That doesn't make any sense. A PIN is a mandatory input parameter to the
> pairing process with any Bluetooth 2.0 or older device. Or do you mean
> to say that the mouse doesn't require pairing at all?
>
>   
It does require pairing. But in Win$ I simply choose option "without
security code", as said in manual.

W.P.

  reply	other threads:[~2011-07-01  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  8:18 pairing device in text mode W.P.
2011-07-01  8:44 ` Johan Hedberg
2011-07-01  9:38   ` W.P. [this message]
2011-07-01  9:55   ` W.P.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E0D959F.5050201@wp.pl \
    --to=laurentp@wp.pl \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).