Integración domótica Speedtest.net, gratuita y de código abierto
Measure your internet speed on a schedule using Speedtest.net servers.
Publicado por guim31
- Dispositivos
- Versión 1.0.2
- Requiere Gladys >=4.86.0
- ★ 0
La documentación de esta integración la escribe su autor y, por ahora, solo está disponible en inglés.
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.
Parámetros de configuración
Estos son los parámetros que Speedtest.net te pide en su pantalla de configuración en Gladys.
| Parámetro | Tipo | Obligatorio | Descripción |
|---|---|---|---|
| How it works | section | No | 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 | No | When disabled, tests only run through the manual button below. |
| Interval between tests (s) | number | No | Seconds between automatic tests. 3600 = one test per hour. |
| Server ID (optional) | string | No | Leave empty to auto-select the closest healthy server. Use the "List nearby servers" button to find IDs. |
| Parallel connections | number | No | TCP connections per direction. More connections fill fast links better. |
| Measurement time per direction (s) | number | No | Longer measurements are steadier but transfer more data. |
Cómo instalar Speedtest.net en Gladys
- En Gladys, abre Integraciones: Speedtest.net aparece en el catálogo junto a las integraciones nativas, con una insignia de comunidad.
- Haz clic en Instalar. Gladys descarga la imagen Docker (
ghcr.io/guim31/gladys-speedtest:1.1.0), la ejecuta en un entorno aislado del núcleo y genera la interfaz de la integración (dispositivos, descubrimiento y configuración). - Abre la pantalla de Configuración de la integración, rellena los parámetros y guarda.
- También puedes instalarla directamente desde la URL de su repositorio: https://github.com/guim31/gladys-speedtest.
Speedtest.net requiere Gladys >=5.1.0. El catálogo de Gladys se actualiza cada hora, así que una nueva versión está disponible como máximo una hora después de publicarse.
¿Todavía no usas Gladys? Es gratuito y de código abierto: sigue la guía de instalación para empezar.
Sobre las integraciones externas
Speedtest.net es una integración externa: una integración comunitaria empaquetada como contenedor Docker y publicada en GitHub. Gladys la instala con un clic y la ejecuta en un entorno aislado del núcleo. La publica y mantiene guim31, no el equipo principal de Gladys.
- Explorar todas las integraciones externas
- Descubrir las integraciones nativas incluidas en Gladys
- Crear y publicar tu propia integración externa
- Código fuente en GitHub — fuente de esta documentación