v0.2.16 — why did the dish restart?

Starlink updates its firmware overnight, and the only sign was a short uptime the
next morning. DishWatch now says when the current boot began and, when it can
tell, why.

In the app

The Observed section has a new Boot line, for example:

• Boot ≈02:39 · firmware update 2026.10.09 → 2026.10.21
• Boot ≈02:39 · likely firmware update (one was pending)
• Boot ≈02:39 · restart requested via DishWatch
• Boot ≈Nov 6 14:02

The dish never reports why it restarted, so DishWatch works it out from what it saw
just before:

• Firmware update: the version changed across one restart.
• Restart requested: you restarted it from the app or with sl reboot just before.
• Likely firmware update: the dish said an update was waiting, but the version
  didn't change. A power cut while an update is waiting looks the same, hence
  "likely".
• Time only: anything else, such as a power cut, unplugging, or several restarts
  while DishWatch wasn't looking. These look alike from outside, so it doesn't guess.

The time has a ≈ because it is estimated from the dish's uptime. A boot before
today shows its date.

Labels start from the first restart after you install this version. The boot
already running when you upgrade shows its time only.

In the terminal

• sl dash shows the same Boot line under Observed.
• The Firmware row shows the version, plus the update state while an update
  is in progress. It used to show only update IDLE.
• sl events logs a FIRMWARE old → new line when the version changes.