Conversation
Merge main into beta to resync them
Exposes the device's current IP address as a diagnostic text sensor in Home Assistant, making it easier to identify devices on the network.
Exposes the running ESPHome version and the Apollo firmware version as diagnostic text sensors in Home Assistant, making it easy to verify what firmware is installed without checking the ESPHome dashboard.
ESPHome renamed `services`/`service` to `actions`/`action` in newer versions. Updates the play_buzzer API entry to use the current syntax. BREAKING CHANGE: Any Home Assistant automations or scripts that call play_buzzer as a service must be updated to use the new action syntax.
…io options - Replace deprecated board name with explicit variant/flash_size spec (esp32c3 + 4MB) — removes need for platformio_options flash_mode override - Enable web server version 3 (modern UI) across all device YAMLs - Remove platformio_options board_build.flash_mode: dio from all device YAMLs - Remove legacy BLE on_connect/on_disconnect wifi hooks from PLT-1.yaml and PLT-1B.yaml
[esphome] Modernise board spec, web server v3, remove legacy options
[version] Add ESPHome and Apollo firmware version sensors
[wifi_info] Add entity_category diagnostic to IP address sensor
Implements the same pattern as MSR-2 PR #56 to allow users to adjust the LTR390 light sensor polling frequency without reflashing. Uses an interval component workaround since ESPHome update_interval is not templatable on sensor platforms. - Add ltr390_last_update global to track last sensor update time - Add LTR390 Update Interval number input (1-300s, default 60s, CONFIG) - Set LTR390 update_interval to never (disables automatic polling) - Add 1s interval component that triggers sensor update when configured interval has elapsed
…ble-update-interval Add configurable update interval for LTR390 sensor
Bump version to 26.3.2.1
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. Removed component.update from reportAllValues scripts.
The text sensor component sets up at priority 800 (HARDWARE), so publishing at the same priority races with component init. Move to priority 600 so the component is ready when publish fires.
Adding logger.log before text_sensor.template.publish to debug why the publish isn't working at priority 500.
Add text_sensor.template.publish for apollo_firmware_version to PLT-1_Minimal, PLT-1B, PLT-1B_Minimal, PLT-1_BLE, and PLT-1B_BLE. Remove debug log from PLT-1.
Fix Apollo Firmware Version sensor showing unknown
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 14 minutes and 29 seconds. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ 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 |
2 participants
Version: 26.3.2.1
What does this implement/fix?
Merges beta into main for the 26.3.2.1 release. Changes include:
esp32c3board variant +flash_size: 4MB, web server v3 across all device YAMLs, remove legacy platformio options and BLE on_connect/on_disconnect wifi hooks (breaking: board spec change)play_buzzerrenamed fromservicetoaction(breaking: existing HA automations calling this service will need updating)wifi_infoplatformTypes of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified: