1.1.0

Fluval BLE v1.1.0

v1.1.0 removes hold_connection and the whole "hold Bluetooth connection"
concept: a second, confusing connection-policy knob with no real use case.
Connection policy is now the base's connect-on-demand only.

Highlights

• The hold_connection option and the Bluetooth connection switch are
  gone. There is no more "hold the link open permanently" mode to
  configure or toggle. Home Assistant always connects on demand - for
  commands and for the Schedule Guardian's periodic checks - and releases
  the connection again after the active connection window, leaving the
  fixture's single BLE slot free for the Fluval app the rest of the time.
  There is nothing to do in the app itself: the link is simply released
  once Home Assistant is done with it.
• The active connection window option is unchanged. 0 still means a
  persistent connection (upstream behaviour, unrelated to the removed
  hold_connection flag); 30–600 seconds still means a finite idle
  window. If you had hold_connection turned on, your fixture now connects
  on demand instead - set the active connection window to 0 if you want
  the lowest possible command latency at the cost of locking the Fluval app
  out permanently.

Upgrade notes

The switch.<device>_bluetooth_connection entity disappears from your
installation on upgrade; remove any automation or dashboard card that
referenced it. If you relied on hold_connection for the lowest possible
command latency, set the active connection window to 0 instead - the
same persistent-connection behaviour, without the second knob.

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
  connection-policy simplification by @nphil.