Skip to content

1.2.0

Choose a tag to compare

@townsmcp townsmcp released this 29 Jul 09:15
· 29 commits to main since this release
e35ca0c

v1.2.0 — Connection resilience & Bluetooth proxy docs

Fixed

  • Sensors no longer flap to unavailable on every failed poll. Any transient
    read failure — a failed GATT connection or an all-zero/invalid frame, not just a
    device that's out of range — is now treated as a miss and passed through the
    soft-fail grace window. Previously only "not found" errors were tolerated, so on
    a weak link (where the BM6 is seen but the connection fails) the sensors
    flipped straight to unavailable.

Changed

  • Last-good readings are now held through up to 5 consecutive misses / 15
    minutes
    (was 3 / 5 min) before the sensors go unavailable.
  • BLE connections now make up to 4 attempts via bleak-retry-connector (was the
    default 3), improving success on marginal signal.
  • Resilience tunables are surfaced as constants in custom_components/bm6/const.py
    (DEFAULT_FAILURES_BEFORE_UNAVAILABLE, DEFAULT_STALE_AFTER_SECONDS,
    BLEAK_CONNECT_MAX_ATTEMPTS).

Added

  • docs/bluetooth-proxy.md — a full guide to giving the BM6 a reliable
    connection, covering both an ESP32 + ESPHome proxy (with sample YAML) and a
    Raspberry Pi proxy, plus why Shelly plugs can't do the job.
  • README Reliability & Bluetooth range section and a Credits block.

Maintenance

  • Removed a leftover debug log line and an unused method from bm6_connect.py;
    normalised the success-event firing.
  • README licence badge now points at this fork.
  • Dependabot no longer runs on pip/requirements.txt (Home Assistant ignores it
    at runtime and pins the Bluetooth stack itself); GitHub Actions updates kept.

Upgrade notes

  • No configuration changes required — update via HACS and restart Home Assistant.
  • For a BM6 at marginal signal strength, a Bluetooth proxy near the vehicle
    remains the real fix. See docs/bluetooth-proxy.md.