Add Firmware Channel switching and serve the end-user image for OTA#36
Add Firmware Channel switching and serve the end-user image for OTA#36bharvey88 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 (8)
✨ 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 |
32cb182 to
ba6998e
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; Firmware Update button force-installs and prevents deep sleep for the download duration. - BTN-1_Minimal.yaml (the adopted end-user config) gains the managed update system so fielded devices can keep updating after leaving the improv image. - build.yml now serves BTN-1_Minimal.yaml at firmware/; BTN-1.yaml (improv + BLE) moves to firmware-factory/ for the web installer only. - build-beta.yml publishes beta builds to a rolling beta pre-release. - update component id renamed firmware_update -> update_http_request to match the other Apollo repos. 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)
ba6998e to
4fd3a37
Compare
|
Superseded by #37, which is this branch rebuilt on the unified pattern MSR-1 shipped as 26.7.9.1: same channel select and image flip, plus the http_request buffer fixes (rx 5120 / tx 2048) this predates, boot-time channel re-apply, the pre-OTA BLE disable removed (ESPHome's OTA quiesces BLE itself), and min_version raised to the update-system floor. |
…l OTA Rebuild of the earlier firmware-channel port on the pattern MSR-1 shipped as 26.7.9.1 (ApolloAutomation/MSR-1 #100/#103/#104): - NEW: bluetooth_proxy + esp32_ble_tracker compile into every image; a "Bluetooth Proxy" switch (default off, persisted, re-applied at boot) starts/stops scanning at runtime. On this deep-sleep battery button the proxy pairs with "Prevent Sleep" for continuous use. - Firmware Channel select (Stable/Beta) + apply_ota_source doing a direct set_source_url swap from ota_stable_manifest/ota_beta_manifest subs; 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) - BTN-1_Minimal gains the managed-update machinery and takes over Pages firmware/ for OTA/adoption; the improv image moves to firmware-factory/ (installer page repointed) - beta-channel/ wrapper defaults the select to Beta; build-beta.yml publishes the manifest (absolute URLs) to the rolling beta-fw pre-release - min_version 2025.11.0 (update-system floor); version 26.7.12.1 Supersedes #36. 🤖 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.BTN-1_Minimal.yaml(the adopted end-user config) gains the managed update system, and CI serves it atfirmware/;BTN-1.yaml(improv + BLE) moves tofirmware-factory/for the web installer only. Fielded devices leave the improv image on their next update.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.Both images config-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