Skip to content

firmware: valar-core v0.3.1 (verified TLS for the GitHub update) -> v2.12.2 - #52

Merged
daniel-frenkel merged 1 commit into
mainfrom
fix/core-v0.3.1-verify-tls
Nov 17, 2026
Merged

daniel-frenkel merged 1 commit into
mainfrom
fix/core-v0.3.1-verify-tls

Conversation

@daniel-frenkel

@daniel-frenkel daniel-frenkel commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

What

Bumps valar-core and scheduling from v0.2.0 → v0.3.1 on both boards. v0.3.1 is Valar-Systems/valar-motion#10, the fix for valar-motion#9:

  • Verified TLS for "Update Firmware (GitHub)", using the CMN certificate bundle that was already in every build: +144 B.
  • New "Firmware Update" diagnostic: Idle / Downloading N% / Installed - restarting / Failed: <why>. Firmware unchanged.

v0.2.0 → v0.3.0 only turned stepper constants into substitutions whose defaults equal the old literals.

Verification

  • Resolved config: resolving against the real v0.3.1 tag gives a config byte-identical to the local-include builds tested on hardware, on both boards.
  • Full resolved-config diff vs v2.12.1: only verify_ssl, the new entity + its Idle at boot, and the OTA events. The stepper block is identical; the rest is logger.log key-order noise.
  • Gate: ADDED text_sensor Firmware Update (diagnostic); CHANGED esphome:on_boot 600.
  • Flash: VAL3000 1,217,354 B (66.3 %), VAL3100 1,318,340 B (71.8 %), +≈3.1 KB.

Hardware

  • VAL3000, success: verified update; the page showed Idle → Downloading… → 0…100% → Installed - restarting; checksum matched; rebooted into the release
  • VAL3000, failure (a build trusting only a throwaway CA): refused at the TLS handshake (-0x2700, certificate verification failed); nothing downloaded; firmware unchanged; no restart; the page showed the reason
  • VAL3100, success (this branch's build, ESP32-C6): verified update; the page showed Idle → Downloading… → 0…100% → Installed - restarting; checksum abecdd17… (VAL3100 release file); 17 s; rebooted into the release

Docs: user guide troubleshooting + quick reference; firmware README.

🤖 Generated with Claude Code

Bumps valar-core + scheduling from v0.2.0 to v0.3.1 on both boards.
v0.3.1 = valar-motion #10: http_request verify_ssl on (the CMN CA bundle
was already compiled in; +144 B), and a "Firmware Update" diagnostic that
shows Downloading N% / Installed - restarting / Failed: <why>. Firmware
unchanged. Fixes valar-motion #9 for Ropener.

v0.2.0 -> v0.3.0 only parameterized stepper constants with defaults equal
to the old literals; the resolved stepper block is identical. Full
resolved-config diff vs v2.12.1, both boards: only verify_ssl, the new
entity + its Idle at boot, and the http_request OTA events (rest is
logger.log key-order noise). Gate: +1 diagnostic entity, on_boot 600.

Docs: user guide troubleshooting + quick reference, firmware README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@daniel-frenkel
daniel-frenkel merged commit 680e3bc into main Nov 17, 2026
3 checks passed
@daniel-frenkel
daniel-frenkel deleted the fix/core-v0.3.1-verify-tls branch November 17, 2026 17:21
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