Changelog

What changed on Sticky and its website. Firmware version numbers are shown in each unit’s footer. Website changes appear separately and do not always need a device update.

Website ·

Online user manual and changelog

Firmware 17 ·

Editorial daily quotes and reactions

Running version 17 confirmed on both units; Taylor updated over USB and Liz updated remotely.

Firmware 16 ·

Message of the day

Firmware 15 ·

Dry wit message display

Firmware 14 ·

Personal quick replies

Website login and device credentials were deferred; this release did not add password protection.

Firmware 13 ·

Find my Sticky from the website

Replaced the temporary recovery builds with the regular website-controlled finder.

Firmware 12 · · Temporary recovery build

Chirps added to the temporary finder

Used while locating Taylor's misplaced Sticky. Superseded by the website finder in version 13.

Firmware 11 · · Temporary recovery build

Temporary Bluetooth finder

Bluetooth-only recovery build; version 12 added sound, and version 13 added website control.

Firmware 10 ·

Simpler Wi-Fi setup

Firmware 9 · Date not confirmed · Historical gap

Wi-Fi setup development

A version 9 publication record is not retained. Its exact date and standalone release contents cannot be confirmed; version 10 documents the finished setup improvements.

Firmware 8 ·

Weather and moon information

The owners confirmed the weather display on both units.

Firmware 7 ·

Shared Happy Hour list

The owners confirmed the feature on both units.

Earlier releases and development history

Firmware 6 · · Limited historical record

Intermediate build

  • A published version 6 artifact is retained between the automatic-update baseline and the Happy Hour release.

The available notes do not separately establish its user-facing changes. It is included for completeness rather than assigned an inferred feature list.

Firmware 5 ·

Automatic update production baseline

  • Established the shared public firmware and automatic signed online-update path for both units.
  • Preserved private device identity and Wi-Fi settings on each unit.
  • Both devices were subsequently confirmed running version 5 on 5 October.

The earlier version 4 validation established the update and recovery behavior; separate version 5 feature changes were not recorded.

Firmware 4 ·

Validated online update and recovery

  • Validated signed firmware installation through the website backend.
  • Confirmed that device identity, saved configuration, messaging and normal sleep survived the update.
  • Verified rejection of altered signatures or firmware and recovery when a new image failed its startup health check.

Firmware 3 · · Limited historical record

Update validation build

  • A version 3 publication artifact is retained from the online-update validation period.

The surviving records do not establish a separate feature list or a confirmed installation for this build.

Firmware 2 · · Test build

Rollback validation

  • Used to verify that an unconfirmed update rolls back after an interrupted startup.

The deliberate reset returned the test unit to version 1. This was a recovery test, not a regular feature rollout.

Firmware 1 ·

Initial numbered update baseline

  • Provided the existing messaging firmware and saved device configuration as the baseline for online-update testing.

Version 1 is identified in the rollback validation notes. A separate retained publication manifest is not available.

Early development ·

First working Sticky and messaging foundation

  • Established the working reTerminal Sticky e-paper display, Wi-Fi and secure message retrieval.
  • Added a low-power wake, fetch and sleep cycle with a retained message display.
  • Subsequent September work added device navigation, touch interaction, reply confirmation, stamps and message hearts; two-device messaging was validated on 25 September.

The initial display milestone was tagged v0.1. These development milestones predate the numbered online releases; the date shown starts this period.

Earlier history was reconstructed from development notes and retained publication records. Dates use those records where available. Missing records and test-only builds are labeled; publication alone does not confirm installation on a unit.