Skip to content

v1.6.0

Choose a tag to compare

@twodrops twodrops released this 10 Nov 10:11
· 1 commit to main since this release

v1.6.0

Fixed

  • Sensors no longer go unavailable after a single failed speed test. Previously, any failed test attempt — including a backend rate-limiting you (most noticeably with the Ookla CLI backend, which throttles if tested too often) — would immediately flip every sensor (download, upload, ping, server name, etc.) to "unavailable", even though the last successful reading was still perfectly good. Sensors now tolerate a handful of failures in a row, continuing to show the last known values, and only go unavailable once failures genuinely pile up (5 in a row) — the same point you'd already get a "repeated test failures" notification.

New

  • New sensor: "Consecutive Test Failures" (sensor.pace_..._consecutive_test_failures). Shows how many speed tests have failed in a row, with the most recent error message as an attribute. Unlike the other sensors, it stays available even during an outage, so you always have somewhere to check what's going wrong.

Docs

  • Added a troubleshooting section explaining this behavior and the Ookla rate-limiting case specifically.