Speedtest.net Smart-Home-Integration, kostenlos und Open Source
Measure your internet speed on a schedule using Speedtest.net servers.
Veröffentlicht von guim31
- Geräte
- Version 1.0.2
- Erfordert Gladys >=4.86.0
- ★ 0
Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.
Measure your internet connection on a schedule, straight from Gladys, using the worldwide network of Speedtest.net servers. Every run feeds four sensors you can chart on your dashboard and use in scenes:
| Sensor | Unit | What it tells you |
|---|---|---|
| Download | Mbit/s | How fast data reaches your home |
| Upload | Mbit/s | How fast data leaves your home |
| Ping | ms | Reaction time of the connection (lower is better) |
| Jitter | ms | Stability of that reaction time (lower is better) |
Typical uses: keep an eye on what your ISP actually delivers, get notified by a scene when the download rate drops below what you pay for, or detect that a backup line (4G failover…) has taken over.
How a test works
The integration talks directly to Speedtest.net infrastructure — no account, no API key, no Ookla software installed. By default it probes the closest servers, keeps the healthiest one, then measures latency, download and upload (about 25 seconds in total). You can pin a specific server instead: press List nearby servers to see IDs, and paste one into the Server ID field.
Things to know
- A test saturates your connection while it runs. Results are also slightly conservative on very fast lines, since the measurement shares CPU with the sandbox limits Gladys applies to integrations.
- A test transfers real data — several hundred MB per run on a fast line. If your plan has a data cap, increase the interval between tests or disable automatic tests and use the manual button only.
- Scheduled tests follow the Interval between tests setting (default: one test per hour). The Run a speed test now button works at any time.
Dashboard widget
With Gladys 5.1 or later, the integration adds an Internet speed widget to the dashboard editor (Add a widget → Speedtest.net). It shows:
- four live tiles — download, upload, ping and jitter — following the sensors as soon as a test publishes them;
- a history chart of two of them: Chart picks Download and upload (default) or Ping and jitter, History window the last 24 hours, the last week (default) or the last month;
- when the last test ran and the Speedtest.net server it used (operator and city), and Test in progress while one runs;
- a Run a test button. The result shows as a notification when the test ends (about half a minute). Tapping it while a test already runs does not start another one.
Good to know:
- The tiles and the chart read the device sensors: add the device to Gladys (Integrations → Speedtest.net → Discovery) for them to fill.
- The date and server of the last test are kept by the integration: right after an update or a restart, before any test ran, the widget says so while the tiles still show the last values Gladys recorded.
- Chart intervals and the long-term history follow your Gladys settings for device history (data retention).
Troubleshooting
- Results lower than the official app: increase Parallel connections (fast lines fill better with 6–8) or Measurement time.
- Test fails: the closest server may be down — pin a different Server ID, or clear the field to let auto-selection skip unhealthy servers.
This integration is an independent community project, not affiliated with or endorsed by Ookla. Speedtest® is a trademark of Ookla, LLC.
Konfigurationseinstellungen
Diese Einstellungen fragt Speedtest.net in seinem Konfigurationsbildschirm in Gladys ab.
| Einstellung | Typ | Pflichtfeld | Beschreibung |
|---|---|---|---|
| How it works | section | Nein | A test saturates your connection for about 25 seconds and can transfer several hundred MB per run: mind your data cap when choosing the interval. Results are stored as four sensors (download, upload, ping, jitter) you can chart and use in scenes. |
| Run tests automatically | boolean | Nein | When disabled, tests only run through the manual button below. |
| Interval between tests (s) | number | Nein | Seconds between automatic tests. 3600 = one test per hour. |
| Server ID (optional) | string | Nein | Leave empty to auto-select the closest healthy server. Use the "List nearby servers" button to find IDs. |
| Parallel connections | number | Nein | TCP connections per direction. More connections fill fast links better. |
| Measurement time per direction (s) | number | Nein | Longer measurements are steadier but transfer more data. |
So installierst du Speedtest.net in Gladys
- Öffne in Gladys Integrationen: Speedtest.net erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
- Klicke auf Installieren. Gladys lädt das Docker-Image (
ghcr.io/guim31/gladys-speedtest:1.1.0) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration). - Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
- Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/guim31/gladys-speedtest.
Speedtest.net benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.
Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.
Über externe Integrationen
Speedtest.net ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von guim31 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.
- Alle externen Integrationen durchsuchen
- Die nativen Integrationen entdecken, die in Gladys eingebaut sind
- Deine eigene externe Integration bauen und veröffentlichen
- Quellcode auf GitHub — Quelle dieser Dokumentation