Add Firmware Channel switching and serve end-user images for OTA#69
Add Firmware Channel switching and serve end-user images for OTA#69bharvey88 wants to merge 1 commit into
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (13)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
49010d9 to
aa8c238
Compare
Same feature as CAST-1 and AIR-1 (ApolloAutomation/AIR-1#107): - Firmware Channel select (Stable/Beta) sets the OTA manifest URL via a new apply_ota_source script keyed by a per-variant variant_slug substitution ("" / "-b"); Firmware Update button force-installs and prevents deep sleep for the download duration. - The Minimal yamls (the adopted end-user configs) gain the managed update system, and their device identity is aligned with the improv images (apollo-plt-1 / apollo-plt-1b) since they become the images fielded devices update onto. - build.yml now serves the Minimal images at firmware/ and firmware-b/; the improv images move to *-factory/ for the web installer only. - build-beta.yml publishes beta builds of both variants to a rolling beta pre-release. - update component id renamed firmware_update -> update_http_request to match the other Apollo repos. The BLE variant yamls also gain the managed update system (they inherit the Firmware Update button and apply_ota_source from Core.yaml, so they must define update_http_request for CI to pass). Beta-channel builds compile thin beta-channel/ wrapper yamls so the Firmware Channel select defaults to Beta on firmware obtained from the beta channel (fresh flashes only; stored choices still win). Version: 26.7.8.1 🤖 Generated with [Claude Code](https://claude.com/claude-code)
aa8c238 to
50d943b
Compare
|
Superseded by the unified rebuild (see the new PR referencing this one): same channel select, variant_slug manifests, and image flip, plus the http_request buffer fixes this predates, boot-time channel re-apply, the pre-OTA BLE disable removed per MSR-1 #103, the _BLE on_boot mapping-vs-list merge fix, and min_version raised to the update-system floor. |
…l OTA
Port of the pattern MSR-1 shipped as 26.7.9.1 (ApolloAutomation/MSR-1
#100/#103/#104), replacing the earlier firmware-channel branch:
- bluetooth_proxy + esp32_ble_tracker compile into every image; a
"Bluetooth Proxy" switch (default off, persisted) starts/stops scanning
at runtime, re-applied at boot (on_boot -300). On this deep-sleep device
the proxy pairs with "Prevent Sleep" for continuous use. The _BLE build
split is retired: _BLE yamls stay compilable but their update entities
point at the standard manifests (they were never published), so
self-built _BLE devices converge onto the unified image.
- Firmware Channel select (Stable/Beta) + apply_ota_source doing a direct
set_source_url swap from per-variant ota_stable_manifest/ota_beta_manifest
subs (${variant_slug} keeps PLT-1 vs PLT-1B on their own manifests); the
channel is re-applied at boot (on_boot -100)
- Firmware Update button holds prevent_deep_sleep for the download and
re-arms sleep on the not-started path; no pre-OTA BLE disable (ESPHome's
OTA quiesces BLE itself)
- http_request consolidated into Core.yaml with the proven buffer sizes
(rx 5120 / tx 2048 for GitHub release redirects)
- _BLE variants' on_boot converted to list form so Core's on_boot entries
merge instead of being replaced
- Minimal images take over Pages firmware/ and firmware-b/ for OTA and
adoption; improv images move to firmware-factory/ and firmware-b-factory/
(installer page repointed)
- beta-channel/ wrappers default the select to Beta; build-beta.yml
publishes manifest.json + manifest-b.json (absolute URLs) to the rolling
beta-fw pre-release
- min_version 2025.11.0 (update-system floor); version 26.7.12.1
Supersedes #69.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
1 participant
Version: 26.7.7.1
What does this implement/fix?
Same Stable/Beta firmware switching as CAST-1 (naming per ApolloAutomation/CAST-1#43):
apply_ota_sourcescript. Stable = GitHub Pages (main branch builds), Beta = rollingbetapre-release assets.firmware//firmware-b/; the improv images move to*-factory/for the web installer only. Per-variant manifests are keyed by avariant_slugsubstitution ("" / "-b"). The Minimal images' device identity is aligned with the improv images (apollo-plt-1/apollo-plt-1b) since they become the images fielded devices update onto (Minimal builds were never published before, so nothing fielded is renamed).betabuild the end-user image(s) and publish them to a rollingbetapre-release with manifests rewritten to absolute URLs.firmware_update->update_http_requestto match the other Apollo repos.All four configs validated on ESPHome 2026.6.4. Not yet tested on hardware.
Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified:
🤖 Generated with Claude Code