Skip to content

Unified firmware: runtime Bluetooth Proxy switch + Stable/Beta channel OTA#66

Open
bharvey88 wants to merge 2 commits into
betafrom
unified/firmware-channel
Open

Unified firmware: runtime Bluetooth Proxy switch + Stable/Beta channel OTA#66
bharvey88 wants to merge 2 commits into
betafrom
unified/firmware-channel

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Version: 26.7.12.1

Adds:

Fixes:

  • "Firmware Update" button upgraded from a bare perform(true) to the standard flow: apply_ota_source + a fixed manifest-fetch window before perform (same-version switches never flip update.is_available).

Breaks:

  • Nothing: the Type select keeps its cross-flash behavior; the proxy switch defaults off.

Supersedes #65.

Checks:

  • Documentation Updated
  • Build Number Incremented In Core.yaml

🤖 Generated with Claude Code

…l OTA

Rebuild of the earlier firmware-channel branch 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 both images; a
  "Bluetooth Proxy" switch (default off, persisted, re-applied at boot)
  starts/stops scanning at runtime. Always-on S3/8MB device - a clean
  proxy candidate; nothing changes until a user turns the switch on.
- Firmware Channel select (Stable/Beta) crossed with the existing
  Firmware Type select (WiFi/Ethernet) in apply_ota_source - a direct
  set_source_url swap over the four manifests, re-applied at boot
  (on_boot -100). No manifest-matching guard.
- Firmware Update button upgraded from bare perform(true) to the standard
  flow (apply_ota_source + fetch window before perform)
- http_request consolidated into Core.yaml with the proven buffer sizes
  (rx 5120 / tx 2048 for GitHub release redirects)
- beta-channel/ wrappers default the select to Beta; build-beta.yml
  publishes manifest-e.json + manifest-w.json (absolute URLs) to the
  rolling beta-fw pre-release
- version 26.7.12.1

Supersedes #65.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@coderabbitai

coderabbitai Bot commented Jul 12, 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: 55 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: b2a28ffe-17a6-4e7f-b90c-9ac1d66a37a1

📥 Commits

Reviewing files that changed from the base of the PR and between 93d9cce and f9f8af5.

📒 Files selected for processing (6)
  • .github/workflows/build-beta.yml
  • Integrations/ESPHome/Core.yaml
  • Integrations/ESPHome/R_PRO-1_ETH.yaml
  • Integrations/ESPHome/R_PRO-1_W.yaml
  • Integrations/ESPHome/beta-channel/R_PRO-1_ETH.yaml
  • Integrations/ESPHome/beta-channel/R_PRO-1_W.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch unified/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.

Add an empty encryption: key to the api: block so ESPHome/HA
provisions a per-device API key on adoption, matching MSR-1. Bump
firmware version to 26.7.14.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