fritzFluxDB¶

fritzFluxDB is a lightweight, container-friendly daemon that collects metrics from an AVM FRITZ!Box and writes them to InfluxDB v1, InfluxDB v2, or QuestDB. It also exposes call logs, router logs, VPN data, network hosts, connection information, system statistics, and supported smart-home metrics to the selected time-series backend.

Start here¶

The recommended deployment is Docker Compose with an existing database or one of the repository's backend-specific Compose examples:

cp .env.example .env
# Edit .env with your own FRITZ!Box and database values.
docker compose -f docker/docker-compose.influx2.yml up -d

The command above uses the repository's InfluxDB v2 stack. For a minimal application-only container, see Docker Compose. For the first configuration decision, read Backend overview.

Credentials stay local

The examples in this documentation use placeholders only. Keep .env, tokens, passwords, and exported database credentials outside Git and never paste them into issue reports.

What the daemon does¶

flowchart LR
    B[FRITZ!Box\nTR-064 + Lua] --> F[fritzFluxDB]
    F --> I[InfluxDB v1/v2]
    F --> Q[QuestDB]
    I --> G[Grafana]
    Q --> G

The daemon polls the FRITZ!Box asynchronously, buffers measurements, and flushes buffered data before a graceful shutdown when possible. The Docker image runs as a non-root user and uses Tini plus a watchdog entrypoint.

Documentation map¶

Installation — prerequisites and deployment choices.
Environment variables — complete runtime configuration.
Polling and data model — collection cadence and measurement naming.
InfluxDB and QuestDB — backend-specific setup.
Grafana dashboards — import and datasource requirements.
Architecture — code layout and runtime flow.

Current release metadata is in pyproject.toml; see the changelog for the latest released version and its notes. The project is independent open source software and is not affiliated with AVM GmbH.