Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
WalkthroughESPHome version bumped from 25.7.18.1 to 26.3.2.1 in the Core configuration. A character encoding change detected in the BME280 Temperature Offset unit_of_measurement field requires verification. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@Integrations/ESPHome/Core.yaml`:
- Line 145: The unit_of_measurement value contains a garbled character ("�C");
update the YAML key unit_of_measurement to use the correct degree Celsius symbol
(°C) instead of the replacement character so the UI displays temperatures
properly—locate the unit_of_measurement entry in the
Integrations/ESPHome/Core.yaml and replace the corrupted character with the
proper ° character.
Version: 26.3.2.1
Adds:
Version number update to Core.yaml
Fixes:
Breaks:
Checks:
Summary by CodeRabbit