dbus2mqtt 0.4.4__tar.gz → 0.5.1__tar.gz

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/release-drafter.yml

@@ -27,7 +27,7 @@ autolabeler:
   - label: enhancement
     branch:
       - '/feature\/.+/'
-  - label: fix
+  - label: bugfix
     branch:
       - '/fix\/.+/'
     title:
@@ -46,6 +46,6 @@ version-resolver:
       - feature  # patch until we are on 1.x
       - enhancement  # patch until we are on 1.x
   default: patch
-change-template: '* $TITLE (#$NUMBER)'
+change-template: '* $TITLE (#$NUMBER) by @$AUTHOR'
 template: |
   $CHANGES

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/ci.yml

@@ -19,9 +19,10 @@ jobs:
           - "3.11"
           - "3.12"
           - "3.13"
+          - "3.14"
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
 
       - name: Install uv
         uses: astral-sh/setup-uv@v6

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/deploy-docs.yml

@@ -12,7 +12,7 @@ jobs:
       contents: write
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0
       - name: Configure Git Credentials

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/docker-dev.yml

@@ -10,6 +10,7 @@ name: docker-dev
       - '.pre-commit-config.yaml'
       - 'README.md'
       - 'renovate.json'
+      - 'mkdocs.yaml'
   workflow_dispatch:
 
 jobs:
@@ -19,7 +20,7 @@ jobs:
       packages: write
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Install uv
         uses: astral-sh/setup-uv@v6

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/docker-stable.yml

@@ -19,7 +19,7 @@ jobs:
       versions_matrix: ${{ steps.supported_release_versions.outputs.versions_matrix }}
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0
 
@@ -46,7 +46,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Docker meta
         id: meta

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/pre-commit.yml

@@ -13,7 +13,7 @@ jobs:
   pre-commit:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
 
       - name: Install uv
         uses: astral-sh/setup-uv@v6

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/publish.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           persist-credentials: false
 

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.github/workflows/trivy.yml

@@ -18,10 +18,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Run Trivy vulnerability scanner
-        uses: aquasecurity/trivy-action@0.32.0
+        uses: aquasecurity/trivy-action@0.33.1
         with:
           image-ref: ghcr.io/jwnmulder/dbus2mqtt:latest
           format: 'sarif'

dbus2mqtt-0.5.1/.markdownlint.json

@@ -0,0 +1,4 @@
+{
+  "MD013": false,
+  "MD033": false
+}

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/.pre-commit-config.yaml

@@ -33,7 +33,7 @@ repos:
           - --strict
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.12.10
+    rev: v0.12.12
     hooks:
       - id: ruff
         args:
@@ -42,16 +42,22 @@ repos:
           - I
 
   - repo: https://github.com/astral-sh/uv-pre-commit
-    rev: 0.8.13
+    rev: 0.8.15
     hooks:
       - id: uv-lock
 
   - repo: https://github.com/RobertCraigie/pyright-python
-    rev: v1.1.404
+    rev: v1.1.405
     hooks:
       - id: pyright
 
-  - repo: https://github.com/fpgmaas/deptry
-    rev: "0.23.1"
+  - repo: local
     hooks:
       - id: deptry
+        name: deptry
+        entry: uv run deptry .
+        language: python
+        additional_dependencies:
+          - uv
+        always_run: true
+        pass_filenames: false

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dbus2mqtt
-Version: 0.4.4
+Version: 0.5.1
 Summary: General purpose DBus to MQTT bridge - expose signals, methods and properties over MQTT - featuring jinja based templating, payload enrichment and MPRIS / BlueZ / Home Assistant ready examples 
 Project-URL: Documentation, https://jwnmulder.github.io/dbus2mqtt
 Project-URL: Source, https://github.com/jwnmulder/dbus2mqtt
@@ -17,6 +17,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Home Automation
 Requires-Python: >=3.10
 Requires-Dist: apscheduler>=3.11.0
@@ -27,7 +28,6 @@ Requires-Dist: jinja2-ansible-filters>=1.3.2
 Requires-Dist: jinja2>=3.1.6
 Requires-Dist: jsonargparse>=4.38.0
 Requires-Dist: paho-mqtt>=2.1.0
-Requires-Dist: pydantic>=2.11.3
 Requires-Dist: python-dotenv>=1.1.0
 Requires-Dist: pyyaml>=6.0.2
 Description-Content-Type: text/markdown
@@ -51,7 +51,7 @@ This makes it easy to integrate Linux desktop services or system signals into MQ
 
 **dbus2mqtt** is considered stable for the use-cases it has been tested against, and is actively being developed. Documentation is continuously being improved.
 
-Initial testing has focused on MPRIS integration. A table of tested MPRIS players and their supported methods can be found here: [Mediaplayer integration with Home Assistant](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player/)
+Initial testing has focused on MPRIS integration. A table of tested MPRIS players and their supported methods can be found on [Mediaplayer integration with Home Assistant](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player.html)
 
 ## Getting started with dbus2mqtt
 
@@ -94,7 +94,6 @@ MQTT__USERNAME=
 MQTT__PASSWORD=
 ```
 
-
 ### Install and run dbus2mqtt
 
 ```bash
@@ -102,136 +101,25 @@ python -m pip install dbus2mqtt
 dbus2mqtt --config config.yaml
 ```
 
-
-### Run using docker with auto start behavior
-
-To build and run dbus2mqtt using Docker with the [home_assistant_media_player.yaml](https://github.com/jwnmulder/dbus2mqtt/blob/main/docs/examples/home_assistant_media_player.yaml) example from this repository.
-
-```bash
-# setup configuration
-mkdir -p $HOME/.config/dbus2mqtt
-cp docs/examples/home_assistant_media_player.yaml $HOME/.config/dbus2mqtt/config.yaml
-cp .env.example $HOME/.config/dbus2mqtt/.env
-
-# run image and automatically start on reboot
-sudo docker pull jwnmulder/dbus2mqtt
-sudo docker run --detach --name dbus2mqtt \
-  --volume "$HOME"/.config/dbus2mqtt:"$HOME"/.config/dbus2mqtt \
-  --volume /run/user:/run/user \
-  --env DBUS_SESSION_BUS_ADDRESS="$DBUS_SESSION_BUS_ADDRESS" \
-  --env-file "$HOME"/.config/dbus2mqtt/.env \
-  --user $(id -u):$(id -g) \
-  --privileged \
-  --restart unless-stopped \
-  jwnmulder/dbus2mqtt \
-  --config "$HOME"/.config/dbus2mqtt/config.yaml
-
-# view logs
-sudo docker logs dbus2mqtt -f
-```
+See [setup](https://jwnmulder.github.io/dbus2mqtt/setup.html) for more installation options and configuration details.
 
 ## Examples
 
-More dbus2mqtt examples can be found here: [examples](https://jwnmulder.github.io/dbus2mqtt/examples/).
-The most complete one being [MPRIS to Home Assistant Media Player integration](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player/)
-
-## Configuration reference
-
-dbus2mqtt leverages [jsonargparse](https://jsonargparse.readthedocs.io/en/stable/) which allows configuration via either yaml configuration, CLI or environment variables. Until this is fully documented have a look at the examples in this repository.
-
-### MQTT and D-Bus connection details
-
-```bash
-# dbus_fast configuration
-export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
-
-# dbus2mqtt configuration
-MQTT__HOST=localhost
-MQTT__PORT=1883
-MQTT__USERNAME=
-MQTT__PASSWORD=
-```
-
-or
-
-```yaml
-mqtt:
-  host: localhost
-  port: 1883
-  subscription_topics:
-    - dbus2mqtt/#
-```
-
-### Exposing dbus methods
-
-```yaml
-dbus:
-  subscriptions:
-    - bus_name: org.mpris.MediaPlayer2.*
-      path: /org/mpris/MediaPlayer2
-      interfaces:
-        - interface: org.mpris.MediaPlayer2.Player
-          mqtt_command_topic: dbus2mqtt/org.mpris.MediaPlayer2/command
-          methods:
-            - method: Pause
-            - method: Play
-```
-
-This configuration will expose 2 methods. Triggering methods can be done by publishing json messages to the `dbus2mqtt/org.mpris.MediaPlayer2/command` MQTT topic. Arguments can be passed along in `args`.
+More dbus2mqtt examples can be found in the [examples](https://jwnmulder.github.io/dbus2mqtt/examples/index.html) section.
+The most complete one being [Mediaplayer integration with Home Assistant](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player.html)
 
-Some examples that call methods  on **all** bus_names matching the configured pattern
+## Exposing dbus methods, properties and signals
 
-```json
-{
-    "method": "Play",
-}
-```
+See [subscriptions](https://jwnmulder.github.io/dbus2mqtt/subscriptions.html) for documentation on calling methods, setting properties and exposing D-Bus signals to MQTT. When configured, D-Bus methods can be invoked by publishing a message like
 
 ```json
 {
-    "method": "OpenUri",
-    "args": []
+    "method": "Play"
 }
 ```
 
-To specifically target objects the properties `bus_name` and/or `path` can be used. Both properties support wildcards
-
-```json
-{
-    "method": "Play",
-    "bus_name": "*.firefox",
-    "path": "/org/mpris/MediaPlayer2"
-}
-```
-
-### Exposing dbus signals
-
-Publishing signals to MQTT topics works by subscribing to the relevant signal and using flows for publishing
-
-```yaml
-dbus:
-  subscriptions:
-    - bus_name: org.mpris.MediaPlayer2.*
-      path: /org/mpris/MediaPlayer2
-      interfaces:
-        - interface: org.freedesktop.DBus.Properties
-           signals:
-             - signal: PropertiesChanged
-
-      flows:
-        - name: "Property Changed flow"
-          triggers:
-            - type: on_signal
-          actions:
-            - type: mqtt_publish
-              topic: dbus2mqtt/org.mpris.MediaPlayer2/signals/PropertiesChanged
-              payload_type: json
-```
-
-## Flows
-
-A reference of all supported flow triggers and actions can be found on [Flows](https://jwnmulder.github.io/dbus2mqtt/flows/)
+## Flows and Jinja based templating
 
-## Jinja templating
+For more advanced use-cases, dbus2mqtt has support for flows and Jinja2 based templates. A reference of all supported flow triggers and actions can be found on [flows](https://jwnmulder.github.io/dbus2mqtt/flows/index.html)
 
-TODO: Document Jinja templating, for now see the [MPRIS to Home Assistant Media Player integration](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player/) example
+Jinja templating documentation can be found here: [templating](https://jwnmulder.github.io/dbus2mqtt/templating/index.html)

dbus2mqtt-0.5.1/README.md

@@ -0,0 +1,91 @@
+# dbus2mqtt
+
+**dbus2mqtt** is a Python application that bridges **DBus** with **MQTT**.
+It lets you forward Linux D-Bus signals and properties to MQTT topics, call D-Bus methods via MQTT messages, and shape payloads using flexible **Jinja2 templating**.
+
+This makes it easy to integrate Linux desktop services or system signals into MQTT-based workflows - including **Home Assistant**.
+
+## Features
+
+* 🔗 Forward **D-Bus signals** to MQTT topics.
+* 🧠 Enrich or transform **MQTT payloads** using Jinja2 templates and additional D-Bus calls.
+* ⚡ Trigger message publishing via **signals, timers, property changes, or startup events**.
+* 📡 Expose **D-Bus methods** for remote control via MQTT messages.
+* 🏠 Includes example configurations for **MPRIS** and **Home Assistant Media Player** integration.
+
+## Project status
+
+**dbus2mqtt** is considered stable for the use-cases it has been tested against, and is actively being developed. Documentation is continuously being improved.
+
+Initial testing has focused on MPRIS integration. A table of tested MPRIS players and their supported methods can be found on [Mediaplayer integration with Home Assistant](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player.html)
+
+## Getting started with dbus2mqtt
+
+Create a `config.yaml` file with the contents shown below. This configuration will expose all bus properties from the `org.mpris.MediaPlayer2.Player` interface to MQTT on the `dbus2mqtt/org.mpris.MediaPlayer2/state` topic.
+
+```yaml
+dbus:
+  subscriptions:
+    - bus_name: org.mpris.MediaPlayer2.*
+      path: /org/mpris/MediaPlayer2
+      interfaces:
+        - interface: org.freedesktop.DBus.Properties
+          methods:
+            - method: GetAll
+
+      flows:
+        - name: "Publish MPRIS state"
+          triggers:
+            - type: object_added
+            - type: schedule
+              interval: {seconds: 5}
+          actions:
+            - type: context_set
+              context:
+                mpris_bus_name: '{{ dbus_list("org.mpris.MediaPlayer2.*") | first }}'
+                path: /org/mpris/MediaPlayer2
+            - type: mqtt_publish
+              topic: dbus2mqtt/org.mpris.MediaPlayer2/state
+              payload_type: json
+              payload_template: |
+                {{ dbus_call(mpris_bus_name, path, 'org.freedesktop.DBus.Properties', 'GetAll', ['org.mpris.MediaPlayer2.Player']) }}
+```
+
+MQTT connection details can be configured in that same `config.yaml` file or via environment variables. For now create a `.env` file with the following contents.
+
+```bash
+MQTT__HOST=localhost
+MQTT__PORT=1883
+MQTT__USERNAME=
+MQTT__PASSWORD=
+```
+
+### Install and run dbus2mqtt
+
+```bash
+python -m pip install dbus2mqtt
+dbus2mqtt --config config.yaml
+```
+
+See [setup](https://jwnmulder.github.io/dbus2mqtt/setup.html) for more installation options and configuration details.
+
+## Examples
+
+More dbus2mqtt examples can be found in the [examples](https://jwnmulder.github.io/dbus2mqtt/examples/index.html) section.
+The most complete one being [Mediaplayer integration with Home Assistant](https://jwnmulder.github.io/dbus2mqtt/examples/home_assistant_media_player.html)
+
+## Exposing dbus methods, properties and signals
+
+See [subscriptions](https://jwnmulder.github.io/dbus2mqtt/subscriptions.html) for documentation on calling methods, setting properties and exposing D-Bus signals to MQTT. When configured, D-Bus methods can be invoked by publishing a message like
+
+```json
+{
+    "method": "Play"
+}
+```
+
+## Flows and Jinja based templating
+
+For more advanced use-cases, dbus2mqtt has support for flows and Jinja2 based templates. A reference of all supported flow triggers and actions can be found on [flows](https://jwnmulder.github.io/dbus2mqtt/flows/index.html)
+
+Jinja templating documentation can be found here: [templating](https://jwnmulder.github.io/dbus2mqtt/templating/index.html)

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/docker/Dockerfile.dev

@@ -20,7 +20,7 @@ RUN --mount=type=cache,target=/root/.cache/uv \
     --mount=type=bind,source=pyproject.toml,target=pyproject.toml \
     uv sync --frozen --no-install-project --no-dev
 
-ADD src/ pyproject.toml uv.lock README.md /app
+ADD src/ pyproject.toml uv.lock README.md /app/
 RUN --mount=type=cache,target=/root/.cache/uv \
     uv sync --frozen --no-dev
 

dbus2mqtt-0.5.1/docs/assets/favicon.svg

@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 35 47" role="img" aria-label="dbus2 MQTT logo">
+  <defs>
+    <style>
+      .word {
+        font-family: Inter, Roboto, system-ui, -apple-system, Segoe UI, Arial, sans-serif;
+        font-size: 64px;
+        font-weight: 600;
+        fill: #1F2937;
+      }
+      .num {
+        font-family: Inter, Roboto, system-ui, sans-serif;
+        font-size: 64px;
+        font-weight: 700;
+        fill: #7B1FA2;
+      }
+    </style>
+  </defs>
+
+  <!-- <text x="0" y="50" class="word">dbus</text> -->
+  <text x="0" y="46" class="num">2</text>
+  <!-- <text x="0" y="105" class="word">MQTT</text> -->
+</svg>

dbus2mqtt-0.5.1/docs/assets/logo-dark-img.svg

@@ -0,0 +1,11 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 80">
+
+  <!-- Connection (angular polyline) behind, vertical in the middle of the dots -->
+  <polyline points="20,40 50,10 50,70 80,40" stroke="#1F2937" stroke-width="10" fill="none" stroke-linecap="round" stroke-linejoin="round"/>
+
+  <!-- DBus node in purple -->
+  <circle cx="20" cy="40" r="14" fill="#7B1FA2"/>
+
+  <!-- MQTT node in purple -->
+  <circle cx="80" cy="40" r="14" fill="#7B1FA2"/>
+</svg>

dbus2mqtt-0.5.1/docs/assets/logo-dark-text.svg

@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 180 110" role="img" aria-label="dbus2 MQTT logo">
+  <defs>
+    <style>
+      .word {
+        font-family: Inter, Roboto, system-ui, -apple-system, Segoe UI, Arial, sans-serif;
+        font-size: 64px;
+        font-weight: 600;
+        fill: #1F2937;
+      }
+      .num {
+        font-family: Inter, Roboto, system-ui, sans-serif;
+        font-size: 64px;
+        font-weight: 700;
+        fill: #7B1FA2;
+      }
+    </style>
+  </defs>
+
+  <text x="0" y="50" class="word">dbus</text>
+  <text x="143" y="50" class="num">2</text>
+  <text x="0" y="105" class="word">MQTT</text>
+</svg>

dbus2mqtt-0.5.1/docs/assets/logo-light-img.svg

@@ -0,0 +1,11 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 80">
+
+  <!-- Connection (angular polyline) behind, vertical in the middle of the dots -->
+  <polyline points="20,40 50,10 50,70 80,40" stroke="#FFFFFF" stroke-width="10" fill="none" stroke-linecap="round" stroke-linejoin="round"/>
+
+  <!-- DBus node in purple -->
+  <circle cx="20" cy="40" r="14" fill="#BE90FF"/>
+
+  <!-- MQTT node in purple -->
+  <circle cx="80" cy="40" r="14" fill="#BE90FF"/>
+</svg>

dbus2mqtt-0.5.1/docs/assets/logo-light-text.svg

@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 180 110" role="img" aria-label="dbus2 MQTT logo">
+  <defs>
+    <style>
+      .word {
+        font-family: Inter, Roboto, system-ui, -apple-system, Segoe UI, Arial, sans-serif;
+        font-size: 64px;
+        font-weight: 600;
+        fill: #FFFFFF;
+      }
+      .num {
+        font-family: Inter, Roboto, system-ui, sans-serif;
+        font-size: 64px;
+        font-weight: 700;
+        fill: #BE90FF;
+      }
+    </style>
+  </defs>
+
+  <text x="0" y="50" class="word">dbus</text>
+  <text x="143" y="50" class="num">2</text>
+  <text x="0" y="105" class="word">MQTT</text>
+</svg>

dbus2mqtt-0.5.1/docs/developer/index.md

@@ -0,0 +1,56 @@
+# Developer guide
+
+## Specifications
+
+Generic DBus specifications:
+
+* [D-Bus Tutorial](https://dbus.freedesktop.org/doc/dbus-tutorial.html)
+* [D-Bus Specification](https://dbus.freedesktop.org/doc/dbus-specification.html)
+
+## Running from source
+
+```bash
+uv run main.py --config config.yaml
+```
+
+## Activate Python virtual env
+
+```bash
+uv sync
+source .venv/bin/activate
+```
+
+## Linting
+
+```bash
+# run pre-commit linters
+uv run pre-commit run --all-files
+
+# setup pre-commit to automatically run linters via git hooks
+uv run pre-commit install
+```
+
+## Publishing and subscribing to MQTT messages
+
+Multiple MQTT client exist that can be used for testing, e.g.
+
+* [MQTT Explorer](https://mqtt-explorer.com/)
+* [github.com/RISE-Maritime/mqtt-cli](https://github.com/RISE-Maritime/mqtt-cli)
+
+### Using mqtt-cli
+
+```bash
+source .env
+
+mqtt() {
+  uvx --from mqtt-cli mqtt \
+    --host "$MQTT__HOST" \
+    --user "$MQTT__USERNAME" \
+    --password "$MQTT__PASSWORD" \
+    "$@"
+}
+
+mqtt --help
+mqtt subscribe --topic 'dbus2mqtt/#'
+mqtt publish -t dbus2mqtt/org.mpris.MediaPlayer2/command -m '{ "method": "Play" }'
+```

{dbus2mqtt-0.4.4 → dbus2mqtt-0.5.1}/docs/examples/bluez.md

@@ -5,8 +5,6 @@ hide:
 
 # Bluez
 
-## Introduction
-
 This configuration file demonstrates how to use dbus2mqtt to bridge D-Bus events from BlueZ (the official Linux Bluetooth protocol stack) to MQTT topics. It subscribes to relevant D-Bus signals and properties for both the Bluetooth adapter (`hci0`) and all Bluetooth devices managed by BlueZ. The configuration defines flows that:
 
 * Monitor property changes and object lifecycle events (added/removed) for the Bluetooth adapter and devices.

dbus2mqtt-0.5.1/docs/examples/connman-config.md

@@ -0,0 +1,20 @@
+---
+hide:
+  - toc
+---
+
+# Connman (WIP)
+
+Using dbus2mqtt, you can control you network configuration using connman through mqtt topics.
+
+## Setup activities
+
+Trying out this example
+
+```bash
+uv run dbus2mqtt --config docs/examples/connman-config.yaml
+```
+
+## Features
+
+This configuration is a passthrough of the D-BUS architecture of connman. refer to connman D-BUS API.