Skip to content

Enable API encryption#86

Merged
bharvey88 merged 2 commits into
ApolloAutomation:betafrom
bharvey88:fix/api-encryption
Jul 14, 2026
Merged

Enable API encryption#86
bharvey88 merged 2 commits into
ApolloAutomation:betafrom
bharvey88:fix/api-encryption

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Version: 26.7.14.1

What does this implement/fix?

Adds an empty encryption: key to the api: block so ESPHome/Home Assistant provisions a per-device API key at adoption, matching MSR-1 and the rest of the fleet. Bumps the firmware version to 26.7.14.1.

Note: freshly flashed devices provision the key seamlessly at adoption. Already-adopted devices will need the auto-generated key entered in Home Assistant after the OTA (a re-adopt) before the API reconnects.

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

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)
@bharvey88 bharvey88 added the new-feature New feature label Jul 14, 2026
@coderabbitai

coderabbitai Bot commented Jul 14, 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: 22 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: 7e0119fd-3d3e-41ab-81cd-b97b6f17afe3

📥 Commits

Reviewing files that changed from the base of the PR and between 64b884b and 8fe7883.

📒 Files selected for processing (1)
  • Integrations/ESPHome/Core.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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 merged commit 8e7ecc7 into ApolloAutomation:beta Jul 14, 2026
12 checks passed
@bharvey88 bharvey88 mentioned this pull request Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-feature New feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant