fritzFluxDB v1.2
fritzFluxDB 1.2
Docker Image: docker pull giiibates/fritzfluxdb:1.2
Available Tags
giiibates/fritzfluxdb:1.2(multi-arch: linux/amd64, linux/arm64)giiibates/fritzfluxdb:1.2-amd64giiibates/fritzfluxdb:1.2-arm64giiibates/fritzfluxdb:latest
Security Scan Results
| Architecture | Status | Findings |
|---|---|---|
| amd64 | ✅ No HIGH/CRITICAL vulnerabilities found | trivy-findings-amd64 |
| arm64 | ✅ No HIGH/CRITICAL vulnerabilities found | trivy-findings-arm64 |
| run | workflow details | Actions Run |
Scanned with Trivy for HIGH and CRITICAL severity vulnerabilities (unfixed CVEs ignored).
Changelog
NewQuestDB support. QuestDB can now be used as storage backend alongside InfluxDB v1/v2 — configured viaQUESTDB_*variables and a ready-to-usedocker-compose.questdb.yml.NewThe database backend is now selected with a singleDB_TYPEvariable (influxdb_v1,influxdb_v2orquestdb). Invalid values are rejected with a clear error instead of silently falling back to InfluxDB v1.INFLUXDB_VERSIONkeeps working but is deprecated.NewThe database hostname may now be a full URL (e.g.https://influx.example.combehind a reverse proxy) — protocol and port are detected automatically. Port443always enables TLS.NewCredentials and tokens are no longer sent over unencrypted HTTP to remote hosts by default. For trusted home networks this can be allowed explicitly withINFLUXDB_ALLOW_PLAINTEXT_CREDENTIALS=true(orQUESTDB_…); the bundled compose files set this for their internal network.NewUnraid app template with separate, clearly grouped settings for InfluxDB v1/v2 and QuestDB.NewPer-database Docker Compose bundles (docker-compose.influx1.yml,docker-compose.influx2.yml,docker-compose.questdb.yml) including database service, healthcheck and log rotation.NewLOG_LEVELenvironment variable controls log verbosity (INFOby default,DEBUG,WARNINGorERROR). Can also be set with the-lCLI flag.NewFritzBox serial number is now used as the InfluxDB measurement / QuestDB table name with afritzbox_prefix (e.g.fritzbox_AA1234567890).FixQuestDB dashboards now show the same user metrics as the InfluxDB dashboards, including home automation heating, call log details, VPN address fields, MyFritz hostname and current DSL download/upload values.FixMissing FritzBox fields are pre-created in QuestDB so dashboards no longer abort withInvalid columnjust because an optional value has never been written.FixThe duplicate FritzBox quick-filter has been removed from the QuestDB dashboards; call log tables are fully restored.FixConfiguration errors now stop the container immediately with a clear message instead of triggering pointless restart loops — a broken configuration cannot be fixed by retrying.FixA configured but emptyQUESTDB_HOSTNAMEno longer forces the daemon into QuestDB mode and no longer breaks InfluxDB setups (affected the Unraid template).FixFritzOS lab/beta versions with build suffixes (e.g.7.62-123456) are now recognised correctly instead of disabling services.FixThe FritzBox Lua client now useshttpxlike the rest of the application — the implicit dependency onrequestsis gone.FixImproved error messages: hostname, port and credential problems are reported individually and precisely at startup.FixTimezone suffix in Fritz!Box time responses (e.g.+02:00) no longer causes a log warning during timezone auto-detection.FixQuestDB column names containing dots (e.g. WLAN802.11metrics) are now sanitised automatically — dots are replaced with underscores before writing.FixCable-specific services (e.g. cable channel info) are no longer logged as warnings on DSL devices — the message is suppressed after the first discovery pass.