SPEEDTEST_SCHEDULE not firing (speedtest-tracker v1.14.5)
Posted by globaltarheel8
Setup: SparkBox, speedtest module enabled, container sb-speedtest (linuxserver/speedtest-tracker:1.14.5), host port 8765. Issue: SPEEDTESTSCHEDULE in .env appears to have no effect on actual test cadence. Steps taken: Confirmed SPEEDTESTSCHEDULE="0 " was set in /opt/sparkbox/.env. Ran sudo sparkbox restart speedtest to apply �� hit a container-name conflict from orphaned containers on first attempt (sb-speedtest name in use by a stale container), cleaned those up manually with docker rm -f. Got sb-speedtest running clean and healthy after restart. To verify scheduling actually works, changed SPEEDTESTSCHEDULE to "/2 " (every 2 min) and restarted the module again. Waited 5+ minutes — no new test runs fired. Container logs show only normal boot/migration lines, no reference to cron, scheduling, or the SPEEDTESTSCHEDULE var being read at all. Checked the speedtest-tracker web UI (port 8765) for a Settings → Scheduling page (expected since this app is normally configured that way) — no such page exists in this version/config. Conclusion: SPEEDTESTSCHEDULE doesn't appear to be wired to anything the container actually consumes in this image/version — no cron process visible in logs, no in-app scheduling UI to cross-check against. Manual "run now" from the UI works fine, so the app itself is healthy; it's specifically the scheduled/automatic run path that seems disconnected. Ask: Can someone confirm whether SPEEDTESTSCHEDULE is still correctly passed through to this image in the current compose file / entrypoint, or whether the scheduling mechanism changed in a recent speedtest-tracker version bump?
2 replies
Chris wrote:
You nailed it — this isn't anything you did wrong. I checked the current build, and that schedule setting genuinely isn't being handed to the speedtest container right now, so changing SPEEDTESTSCHEDULE in your .env has nothing on the other end reading it. That's exactly why your /2 test never fired and why there's no cron activity in the logs. The app itself is healthy (which is why 'run now' works fine) — it's only the automatic-schedule wiring that's missing. I've flagged this to Tom directly so he can wire it in properly; editing the compose yourself would just get overwritten on the next update, so it's not worth chasing on your end. I'll come back to this thread once the fix ships.
Chris wrote:
Keeping that promise: Tom shipped it today in v1.6.458, and your report is what closed it. You had it pinned exactly right — the schedule was never handed to the container, so nothing on the other end was reading it. It is passed through now, and a box with no value set defaults to hourly. Over SSH: sudo sparkbox upgrade — that is upgrade, not update. update only refreshes your apps' images and cannot move you onto a new release. Then sudo sparkbox restart speedtest. One thing before you do: your .env is still on the /2 test value you set, so put your real cadence back first or you'll be testing every two minutes.