Skip to content

fix(native): drop ctt-lcd pin back to 0.4.0 (0.4.1 was never released) - #49

Open
meelyn-pandit wants to merge 1 commit into
web-wifi-manual-entryfrom
fix/ctt-lcd-pin-0.4.0
Open

fix(native): drop ctt-lcd pin back to 0.4.0 (0.4.1 was never released)#49
meelyn-pandit wants to merge 1 commit into
web-wifi-manual-entryfrom
fix/ctt-lcd-pin-0.4.0

Conversation

@meelyn-pandit

Copy link
Copy Markdown
Contributor

Problem

install-native.sh fetches prebuilt armhf binaries by release tag and never compiles on the station. f9b6743 bumped the ctt-lcd pin to 0.4.1, but no ctt-lcd-v0.4.1 release was ever cut — the latest published is ctt-lcd-v0.4.0 (2026-06-23). So every OTA on this branch 404s:

[install-native] INFO  ctt-lcd: fetching 0.4.1 (have: 0.4.0)
curl: (22) The requested URL returned error: 404
[install-native] WARN  ctt-lcd: download failed (.../ctt-lcd-v0.4.1/ctt-lcd-0.4.1-armhf); keeping existing binary, will retry next OTA

Non-fatal by design, but it recurs on every update forever. Observed on both a v3.0 and a v3.3 board.

The bump carried no code

Diffing the 0.4.0 release commit (63cccc5) against f9b6743 across the ctt-lcd source and its PCF8574 LCD chip driver:

$ git diff --stat 63cccc5 f9b6743 -- native/src/ctt-lcd/ native/lib/ctthw/chips/lcd_pcf8574.*
 native/src/ctt-lcd/VERSION | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Only the VERSION file. Every earlier ctt-lcd bump (0.1.0 → 0.4.0) shipped real source changes; this one didn't.

f9b6743's message credits the bump to a boot splash "Booting up...", but the splash string is " CTT Sensor Station" at both versions (added back at 0.3.0, 6404902) — so no such change is present in the tree.

Fix

Point the pin back at the release that matches the source, rather than cutting an identical binary under a new number.

Verified this tree's ctt-lcd source is identical to the published ctt-lcd-v0.4.0 tag:

$ git diff --stat ctt-lcd-v0.4.0 -- native/src/ctt-lcd/ native/lib/ctthw/chips/lcd_pcf8574.*
(no output)

So the 0.4.0 binary already installed on the fleet is the correct build for this source — no station needs a new download, and install-native will report ctt-lcd already at 0.4.0 and stop warning.

Notes for review

  • Base is web-wifi-manual-entry. f9b6743 exists only on this branch (git branch -r --contains f9b6743origin/web-wifi-manual-entry alone), so the bad pin never reached lts_26_07.iso and no station outside this branch was affected.
  • If a boot-splash change was actually intended, this is the wrong fix for the underlying issue — the change should land as a real source commit and then be released as 0.4.1. Worth a word with f9b6743's author. This revert makes that gap visible rather than masking it behind a permanent OTA warning; the alternative (cutting a ctt-lcd-v0.4.1 release from identical source) would have silenced the warning while leaving the missing change unnoticed.
  • CHANGELOG.md needs no update — it never referenced 0.4.1.

🤖 Generated with Claude Code

f9b6743 bumped ctt-lcd 0.4.0 -> 0.4.1, but no ctt-lcd-v0.4.1 release was ever
cut. install-native.sh fetches prebuilt armhf binaries by release tag and never
compiles, so every OTA on this branch 404s on

  releases/download/ctt-lcd-v0.4.1/ctt-lcd-0.4.1-armhf

and warns "keeping existing binary, will retry next OTA" — forever. Observed on
both a v3.0 and a v3.3 board.

The bump carried no code: diffing the 0.4.0 release commit (63cccc5) against
f9b6743 over native/src/ctt-lcd/ and the PCF8574 LCD chip driver shows only the
VERSION file changing. Every earlier ctt-lcd bump (0.1.0 -> 0.4.0) shipped real
source changes; this one didn't. f9b6743's message credits the bump to a boot
splash "Booting up...", but the splash string is " CTT Sensor Station" at both
versions (added back at 0.3.0), so no such change is present.

Rather than cut an identical binary under a new number, point the pin back at
the release that matches the source. Verified: this tree's ctt-lcd source is
identical to the published ctt-lcd-v0.4.0 tag, so the 0.4.0 binary already
installed on the fleet is the correct build for it.

If a boot-splash change was actually intended, it should land as a real source
commit and then be released as 0.4.1 — this revert makes that gap visible
instead of masking it behind a permanent OTA warning.

Note: the pin only ever existed on web-wifi-manual-entry, not lts_26_07.iso, so
no station outside that branch was affected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant