Breitbandmessung.de

A self-hosted script that automates the German Federal Network Agency's Breitbandmessung.de speed tests on a schedule so home network users can collect…

  • Home Automation
  • Network Services
  • Other
  • Productivity
  • Tools & Utilities
A self-hosted script that automates the German Federal Network Agency's Breitbandmessung.de speed tests on a schedule so home network users can collect regular connection-speed evidence.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

13/100 Low

Maintained
0last commit 1106 days ago
Popular
165 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 39 days ago

GitHub stars
5
Open issues
2
Last commit
2023-11-11
Activity
stale

Checked 10 days ago - source: GitHub (shneezin/breitbandmessung-node)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Configuration Create a config directory and a config.cfg file. Set timezone to your IANA timezone, crontab to a cron schedule such as 0 */2 * * * for every two hours, run_once, and run_on_startup. Also create a messprotokolle directory where result files are stored. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I change how often the measurement runs?

Edit the crontab value in config.cfg to the desired cron expression. The default schedule runs every 2 hours.

Where do measurement results go, and how should I persist them in Docker?

Create a messprotokolle directory for the measurement results. Mount that directory to /export when running the container.

How is the measurement timezone configured?

Set timezone in config.cfg using a tz database timezone name. The default timezone is UTC.

How do I combine the individual CSV files?

Run merge.sh to merge the CSV files into one. You can also download merge.sh and execute it with bash.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads