Skip to content

Add Firmware Channel switching and serve the end-user image for OTA#36

Open
bharvey88 wants to merge 1 commit into
betafrom
firmware-channel
Open

Add Firmware Channel switching and serve the end-user image for OTA#36
bharvey88 wants to merge 1 commit into
betafrom
firmware-channel

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Version: 26.7.7.1

What does this implement/fix?

Same Stable/Beta firmware switching as CAST-1 (naming per ApolloAutomation/CAST-1#43):

  • Firmware Channel select (Stable/Beta) sets the OTA manifest URL via a new apply_ota_source script. Stable = GitHub Pages (main branch builds), Beta = rolling beta pre-release assets.
  • Firmware Update button force-installs the selected channel's firmware. It re-applies the manifest URL first (so a just-switched channel is fetched before forcing) and temporarily disables BLE during the download to free heap for TLS (no-op on non-BLE images). It also prevents deep sleep for the download duration.
  • Updates now serve the end-user image: BTN-1_Minimal.yaml (the adopted end-user config) gains the managed update system, and CI serves it at firmware/; BTN-1.yaml (improv + BLE) moves to firmware-factory/ for the web installer only. Fielded devices leave the improv image on their next update.
  • build-beta.yml (new): pushes to beta build the end-user image(s) and publish them to a rolling beta pre-release with manifests rewritten to absolute URLs.
  • update component id renamed firmware_update -> update_http_request to match the other Apollo repos.

Both images config-validated on ESPHome 2026.6.4. Not yet tested on hardware.

Types of changes

  • Bugfix (fixed change that fixes an issue)
  • New feature (thanks!)
  • Breaking change (repair/feature that breaks existing functionality)
  • Dependency Update - Does not publish
  • Other - Does not publish
  • Website of github readme file update - Does not publish
  • Github workflows - Does not publish

Checklist / Checklijst:

  • The code change has been tested and works locally
  • The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

  • Added/updated documentation for the web page

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@bharvey88, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8af75d23-514a-4d6c-980f-d4893c33a65d

📥 Commits

Reviewing files that changed from the base of the PR and between 6b097fa and 4fd3a37.

📒 Files selected for processing (8)
  • .github/workflows/build-beta.yml
  • .github/workflows/build.yml
  • Integrations/ESPHome/.gitignore
  • Integrations/ESPHome/BTN-1.yaml
  • Integrations/ESPHome/BTN-1_Minimal.yaml
  • Integrations/ESPHome/Core.yaml
  • Integrations/ESPHome/beta-channel/BTN-1_Minimal.yaml
  • static/index.html
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch firmware-channel

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@bharvey88 bharvey88 force-pushed the firmware-channel branch 2 times, most recently from 32cb182 to ba6998e Compare July 8, 2026 16:58
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)
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