Repository navigation
Release 26.10.12.1 - Reduce DB Reporting fix, BLE proxy default, ESPHome 2026.10 build fix - #100
Conversation
When Reduce DB Reporting was on, the DPS310 pressure sensor only reported on a >= 5.0 hPa change. Barometric pressure normally drifts 1-3 hPa a day, so the reading could freeze for hours and look like a dead sensor. Give the reduce-gated ambient sensors (pressure, ESP temp, LTR390 light/UV) a delta-OR-hourly-heartbeat floor, and publish the first post-boot reading so a value always shows on boot. Lower the pressure delta to 0.5 hPa and move the DPS310 poll to 60s. Radar filters and the toggle-off path are unchanged. Fixes #70 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Fix Reduce DB Reporting freezing DPS310 pressure and ambient sensors
The Bluetooth Proxy switch does restore from flash, but the _OFF half of RESTORE_DEFAULT_OFF decides the boot where nothing is stored yet, which is the first boot after the switch shipped. MSR-2_BLE.yaml inherited that mode from Core, so legacy BLE devices that had always proxied came up with the proxy off after updating. Core now reads the mode from a bluetooth_proxy_restore_mode substitution defaulting to RESTORE_DEFAULT_OFF, and MSR-2_BLE.yaml overrides it to RESTORE_DEFAULT_ON, the same override pattern the file already uses for its OTA manifest URLs. The unified image is unchanged and a user's saved choice still wins on every later boot. Refs #92 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Re-dated for the merge day per versioning policy. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Keep Bluetooth Proxy on for legacy BLE builds
ESPHome 2026.8.0 replaces rgb_order/is_rgbw/is_wrgb with a single channel_colors key on esp32_rmt_led_strip (esphome#18474).
`channel_colors` only exists from ESPHome 2026.8.0 (esphome#18474), but these YAMLs still declared an older min_version. Devices adopted through the ESPHome dashboard track this repo at HEAD with no pinned ref, so on an older ESPHome the next recompile fails with "Unknown option channel_colors" pointing into a file the user never wrote, instead of a clear version error. ESPHome merges remote packages and checks min_version in the preload phase, before component schemas load, so the bump produces the right message. No firmware change: min_version is validation-only and emits no code, so the compiled binary is unaffected. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Replace deprecated rgb_order with channel_colors
🤖 Generated with [Claude Code](https://claude.com/claude-code)
# Conflicts: # Integrations/ESPHome/Core.yaml
Fix OTA manifest lambda for ESPHome dev
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe ESPHome configurations update reduced sensor reporting, Bluetooth proxy restore behavior, firmware and LED settings, OTA URL typing, and the minimum supported ESPHome version. ChangesESPHome configuration
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix · Severity of issue fixed: Medium Suggested reviewers: Merge Risk: ⚪ Minimal · up to No actionable issue is established; the release is mergeable after normal build and validation checks. Pre-merge checks |
|
Version: 26.10.12.1
What does this implement/fix?
Merges beta into main for the 26.10.12.1 release. Changes include:
_BLEdevices that had always proxied keep proxying after the update (Keep Bluetooth Proxy on for legacy BLE builds #93)rgb_orderoption withchannel_colors, which requires ESPHome 2026.8.0+ (Replace deprecated rgb_order with channel_colors #96)Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified:
Summary by CodeRabbit