From: "Проклов Александр Валерьевич" <ProklovAV@mail.zabtrans.ru>
To: linux-bluetooth@vger.kernel.org
Subject: Problem with StopDiscovery() via dbus-send
Date: Fri, 24 Aug 2018 09:58:05 +0800 [thread overview]
Message-ID: <5B7F662D.5010903@mail.zabtrans.ru> (raw)
Hello All,
Thanks for your work. Since version bluez-5.50 start-stop discovery work
from command line and scripts:
#bluetoothctl scan on
#bluetoothctl scan off
(see mail-list "Problem with StopDiscovery() via dbus-send")
--------------------------------------------
My next task is to do pair with device from bash script. I tried several
ways:
1. #bluetoothctl pair 11:22:33:44:55:66 does not work because the agent
is not created.
2. Make agent via Dbus:
#dbus-send --system --print-reply --type=method_call --dest=org.bluez
/org/bluez org.bluez.AgentManager1.RegisterAgent
objpath:/org/bluez/agent1 string:KeyboardOnly
the command works, but I do not see in Dbus /org/bluez/agent1 created.
3. Make agent via bluetoothctl:
[bluetooth]#agent on
the command works, but I do not see in Dbus agent path!.
May be possible to set a default pin code via /etc/bluetooth/main.conf
if it is available, do not make a request for a pin from the command
line? I think that then #bluetoothctl pair 11:22:33:44:55:66 will be
able to work fine.
---------------------
Best regards,
Aleksandr Proklov
next reply other threads:[~2018-08-24 1:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 1:58 Проклов Александр Валерьевич [this message]
2018-08-24 8:19 ` Problem with StopDiscovery() via dbus-send Luiz Augusto von Dentz
2018-08-24 14:36 ` Luiz Augusto von Dentz
2018-08-26 23:58 ` Проклов Александр Валерьевич
2018-08-27 7:24 ` Luiz Augusto von Dentz
2018-08-28 2:41 ` Проклов Александр Валерьевич
2018-09-06 0:43 ` Проклов Александр Валерьевич
2018-10-29 5:47 ` Non intheractive request pin-code Проклов Александр Валерьевич
2018-11-01 3:44 ` Serial communication over BT using the DBus API Проклов Александр Валерьевич
-- strict thread matches above, loose matches on Subject: below --
2017-09-15 3:25 Problem with StopDiscovery() via dbus-send Проклов Александр Валерьевич
2017-09-15 6:27 ` Luiz Augusto von Dentz
2017-09-15 8:35 ` Проклов Александр Валерьевич
2017-09-15 8:46 ` Luiz Augusto von Dentz
2017-09-18 2:50 ` Проклов Александр Валерьевич
2017-09-18 6:53 ` Luiz Augusto von Dentz
2017-09-18 8:59 ` Проклов Александр Валерьевич
2017-09-19 23:58 ` Проклов Александр Валерьевич
2017-09-25 1:26 ` Проклов Александр Валерьевич
2017-07-25 23:51 Проклов Александр Валерьевич
2017-07-26 8:05 ` Luiz Augusto von Dentz
2017-07-27 0:50 ` Проклов Александр Валерьевич
2017-07-27 11:33 ` Luiz Augusto von Dentz
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=5B7F662D.5010903@mail.zabtrans.ru \
--to=proklovav@mail.zabtrans.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.