Repository navigation
firmware: valar-core v0.3.1 (verified TLS for the GitHub update) -> v2.12.2 - #52
Merged
Merged
Conversation
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>
1 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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
v0.3.1tag gives a config byte-identical to the local-include builds tested on hardware, on both boards.verify_ssl, the new entity + itsIdleat boot, and the OTA events. The stepper block is identical; the rest islogger.logkey-order noise.text_sensorFirmware Update (diagnostic); CHANGEDesphome:on_boot 600.Hardware
Idle→Downloading…→0…100%→Installed - restarting; checksum matched; rebooted into the release-0x2700, certificate verification failed); nothing downloaded; firmware unchanged; no restart; the page showed the reasonIdle→Downloading…→0…100%→Installed - restarting; checksumabecdd17…(VAL3100 release file); 17 s; rebooted into the releaseDocs: user guide troubleshooting + quick reference; firmware README.
🤖 Generated with Claude Code