TigerScale V3 v3.1.2

v3.1.2

An update started from the scale's own screen now reports itself like any other,
and a failed update no longer stops the scale looking for the next one.

Fixed

• An update launched from the touchscreen was invisible to everything else.
  The screen called the updater directly with its own progress callback and never
  touched the shared status, so the web interface, the local API and Studio all
  reported "idle, 0%" for the entire two minutes. It now publishes the same
  phases and the same percentage as an update started from the web interface, so
  a client cannot tell which one started it.
• One failed update disabled update checking until the next reboot. The
  automatic check required the status to read exactly idle, and a failure
  leaves it reading error — which is kept on purpose, so the interface can say
  what went wrong. The check now stands down only while an update is genuinely
  running. Failing and then never looking again is the opposite of what you want.

Updating

Over the air from Settings > Update, or over USB with
bash scripts/flash.sh --fs. Both keep your WiFi credentials, TigerTag session
and calibration.