ORG.BLUEZ.AGENTMANAGER(5) | Linux System Administration? | ORG.BLUEZ.AGENTMANAGER(5) |
NAME¶
org.bluez.AgentManager - BlueZ D-Bus AgentManager API documentation
INTERFACE¶
- Service
- org.bluez
- Interface
- org.bluez.AgentManager1
- Object path
- /org/bluez
Methods¶
void RegisterAgent(object agent, string capability)¶
The object path defines the path of the agent that will be called when user input is needed and must implement org.bluez.Agent(5) interface.
Every application can register its own agent and for all actions triggered by that application its agent is used.
It is not required by an application to register an agent. If an application does chooses to not register an agent, the default agent is used. This is on most cases a good idea. Only application like a pairing wizard should register their own agent.
An application can only register one agent. Multiple agents per application is not supported.
Possible capability values:
- ""
- Fallback to "KeyboardDisplay".
- "DisplayOnly"
- "DisplayYesNo"
- "KeyboardOnly"
- "NoInputNoOutput"
- "KeyboardDisplay"
Possible errors:
void UnregisterAgent(object agent)¶
Possible errors:
void RequestDefaultAgent(object agent)¶
Special permission might be required to become the default agent.
Possible errors:
October 2023 | BlueZ |