Fix Apollo Firmware Version sensor showing unknown#65
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. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Version:
What does this implement/fix?
Fixes Apollo Firmware Version text sensor showing "unknown" in Home Assistant.
update_interval: neverso the lambda also fires periodically (every 60s) as a fallbackThe root cause is that ESPHome's template text sensor with
update_interval: neveronly publishes when explicitly triggered. Removing this allows the lambda to fire periodically as a fallback, ensuring the version is always reported.Same fix as ApolloAutomation/AIR-1#87
Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified: