Repository navigation
Releases
Releases · townsmcp/BM6
1.3.4 — Installs from the release package
1.3.4 — Installs from the release package
Changed
- The Marketplace (formerly HACS) now installs and updates BM6 from the signed release
package (bm6.zip) attached to each release, instead of downloading the repository
source. The package carries the release's version number, so Home Assistant shows
exactly the version you installed, and each release now counts how often it was
downloaded. - README: new badges for users, downloads, release and beta versions, stars, open issues
and validation status. The HACS badge now correctly says Custom: this fork is added
as a custom repository.
Upgrade notes
- No configuration changes required. Update via the Marketplace (HACS on Home Assistant
2026.10 and older) and restart Home Assistant.
Also included if you're upgrading from 1.3.2 — from 1.3.3
Fixed
- The BM6 sometimes sends a frame reading 0 V but with a real temperature.
This used to be accepted, then rejected as implausible, so the whole update
was lost. Any frame below the voltage floor (5 V) is now treated as empty: the
integration keeps waiting on the same connection and asks again, so the real
reading still comes through on that update.
1.3.3
1.3.3 — Fewer missed readings
Fixed
- The BM6 sometimes sends a frame reading 0 V but with a real temperature.
This used to be accepted, then rejected as implausible, so the whole update
was lost. Any frame below the voltage floor (5 V) is now treated as empty: the
integration keeps waiting on the same connection and asks again, so the real
reading still comes through on that update.
Upgrade notes
- No configuration changes required. Update via HACS and restart Home Assistant.
1.3.2 — Discovery fix, icon and translations
1.3.2 — Discovery fix, icon and translations
Fixed
- Home Assistant no longer offers unrelated Bluetooth devices as new BM6 monitors.
Discovery now only matches devices carrying a BM6 manufacturer signature;
anything else is ignored.
Added
- The integration now has its own icon (Home Assistant 2026.3 or later).
- The preferred Bluetooth scanner option and the new "not a BM6" message are
translated into all 28 supported languages.
Changed
- Corrected translations across all languages (German, Polish and others had
machine-translation errors). - README: corrected language flags and the translation issue link.
Upgrade notes
- No configuration changes required. Update via HACS and restart Home Assistant.
- Any old "new BM6 found" prompts disappear after the restart. Devices you
previously chose to ignore can stay as they are.
1.3.1 — Connection hardening
v1.3.1 — Connection hardening
Fixed
- A lost response or an unresponsive Bluetooth proxy can no longer leave a BM6
connection open. Every step of a read now has a time limit, and the connection
is always released afterwards, so an ESPHome proxy's connection slot is freed
and the next poll retries. Previously a hung disconnect could block all later
polls through that proxy until it was restarted. - A dropped connection is detected straight away while waiting for the BM6's
reply, rather than waiting out the full timeout.
Changed
- Added an overall time limit on each update; a timeout is treated like any other
missed read, so the last good value is held briefly before sensors go
unavailable. - Time limits are configurable in
const.py(BM6_RESPONSE_TIMEOUT,
BM6_EXCHANGE_TIMEOUT,BM6_CLEANUP_TIMEOUT,BM6_UPDATE_TIMEOUT).
Upgrade notes
- No configuration changes required. Update via HACS and restart Home Assistant.
1.3.0
1.2.0
v1.2.0 — Connection resilience & Bluetooth proxy docs
Fixed
- Sensors no longer flap to
unavailableon 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.
Updated all Dependabot changes
What's Changed
- Bump softprops/action-gh-release from 2.2.1 to 3.0.0 by @dependabot[bot] in #10
- Bump actions/checkout from 4.2.1 to 6.0.3 by @dependabot[bot] in #8
- Bump sigstore/gh-action-sigstore-python from 3.0.0 to 3.4.0 by @dependabot[bot] in #6
New Contributors
- @dependabot[bot] made their first contribution in #10
Full Changelog: 0.1.0...0.1.1
0.1.0 - First release
Full Changelog: https://github.com/townsmcp/BM6/commits/0.1.0
First release. https://github.com/Rafciq/BM6 and https://github.com/bsrotten/BM6 merged