Skip to content

1.0.1

Choose a tag to compare

@nphil nphil released this 05 Sep 09:28
· 26 commits to main since this release

Fluval BLE v1.0.1

v1.0.1 fixes the exact failure v1.0.0's Schedule Guardian could otherwise
hide: a permanently held Home Assistant connection locking the Fluval app
out of a fixture that only accepts one BLE central at a time.

Highlights

  • hold_connection now defaults to off (connect-on-demand). Home
    Assistant connects only when it needs to - for commands and for the
    guardian's periodic checks - and disconnects again after the active
    connection window, leaving the fixture's single BLE slot free for the
    Fluval app the rest of the time. Turn the Bluetooth connection switch
    on (or set the hold_connection option) if you'd rather hold the link
    open permanently for the lowest possible command latency.
  • Guardian supervision no longer stops when the connection isn't held.
    Previously, turning hold_connection off made every guardian check report
    "paused" without even attempting BLE traffic - silently disabling
    supervision the moment anyone used the connection switch as documented.
    The guardian now only pauses when expected_mode is explicitly set to
    Unsupervised; with the new default it keeps checking and correcting on its
    normal schedule, connecting on demand like everything else.
  • Guardian status starts at "unknown", not "ok". The status sensor now
    accurately reports that no check has run yet instead of claiming things
    are fine before the guardian has looked.
  • Stopped calling the deprecated device_registry.async_get_device(), which
    Home Assistant Core 2026.8+ logs a warning for; the integration now prefers
    the config-entry-scoped async_get_device_by_identifier() when the running
    Home Assistant provides it.

Upgrade notes

Existing installations pick up the new hold_connection default (off) on
upgrade unless you already changed it - if you specifically want Home
Assistant to keep holding the connection open, turn the Bluetooth
connection
switch back on, or set hold_connection in Configure. No
other action is required.

If a fixture behaves differently after upgrading, include its exact model,
Home Assistant version, downloadable Fluval BLE diagnostics, and relevant
logs in a GitHub issue.

Credits

  • Original integration structure and BLE work by
    @mrzottel.
  • Continued development, product support, and protocol work by
    @MrMooreUK.
  • Schedule Guardian, connection-sharing controls, and this release's
    connect-on-demand default by @nphil.