Fix: publish firmware version once on boot instead of polling#50
Fix: publish firmware version once on boot instead of polling#50
Conversation
Per ESPHome dev feedback: the version is a compile-time constant, so publish it once on_boot rather than using a lambda with periodic updates.
|
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 (3)
✨ 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 |
Move text_sensor.template.publish for apollo_firmware_version from priority 900 to separate priority 500 block in both R_PRO-1_ETH and R_PRO-1_W variants.
|
confirmed working! |
2 participants
Summary
text_sensor.template.publishon bootupdate_interval: neverback to the sensor definition since the value is a compile-time constantPer ESPHome developer feedback: there's no need to poll a constant value every 60s — just publish it once at boot.