• v0.3.4 88967b59b7

    v0.3.4
    All checks were successful
    Release / test-1 (push) Successful in 5m6s
    Release / test (push) Successful in 0s
    Release / hacs (push) Successful in 42s
    Release / hassfest (push) Successful in 1m43s
    Release / validate (push) Successful in 0s
    Validate / hacs (push) Successful in 41s
    Validate / hassfest (push) Successful in 1m51s
    Test / test (push) Successful in 4m2s
    Release / release (push) Successful in 48s
    Stable

    r3pek released this 2026-08-18 11:46:42 +01:00 | 153 commits to main since this release

    • Fixed a device's name sometimes staying stuck as "Mobius device
      (SERIAL)" even after it started working again.
    • Fixed the firmware version sensor showing "Unknown" for
      AquaIllumination-brand devices (AI Prime, AI Axis, and similar).
    • Now requires python-mobius 0.4.4 (still auto-installed, nothing to
      do manually), for its own fixes to the device model list and to the
      lunar-phase light intensity calculation.
    Downloads
  • v0.3.3 4300fc9e75

    v0.3.3
    All checks were successful
    Release / test-1 (push) Successful in 4m38s
    Release / test (push) Successful in 0s
    Release / hacs (push) Successful in 48s
    Release / hassfest (push) Successful in 1m54s
    Release / validate (push) Successful in 0s
    Validate / hacs (push) Successful in 51s
    Validate / hassfest (push) Successful in 2m23s
    Test / test (push) Successful in 4m31s
    Release / release (push) Successful in 1m7s
    Stable

    r3pek released this 2026-08-14 19:30:40 +01:00 | 159 commits to main since this release

    • Fixed some sensors (motor speed, flow rate, light intensity,
      calibration, and similar) sometimes showing "Unavailable" forever
      after a reboot, for one or two devices on a tank, even though
      everything else about that device kept updating normally. Caused by
      a relayed (non-gateway) device's own very first read sometimes
      failing right after startup -- often because Home Assistant's own
      Bluetooth cache isn't fully warmed up yet at that exact moment. That
      first read now gets a couple of quick retries, and, as a backstop,
      Mobius periodically checks for and fills in any sensors that still
      ended up missing.
    Downloads
  • v0.3.2 2f79014dd0

    v0.3.2
    All checks were successful
    Release / hacs (push) Successful in 44s
    Release / hassfest (push) Successful in 1m39s
    Release / validate (push) Successful in 0s
    Release / test-1 (push) Successful in 3m57s
    Release / test (push) Successful in 0s
    Validate / hacs (push) Successful in 37s
    Validate / hassfest (push) Successful in 1m44s
    Test / test (push) Successful in 4m11s
    Release / release (push) Successful in 50s
    Stable

    r3pek released this 2026-08-14 14:46:27 +01:00 | 161 commits to main since this release

    • Fixed relayed devices (anything reached through a gateway, not
      directly over BLE) sometimes getting stuck failing every single
      update for extended periods, even though the gateway itself and
      every other device on the tank kept working fine the whole time. If
      a device keeps failing to relay through its current gateway, a
      different gateway now gets tried automatically instead of needing a
      manual reload to recover.
    • Fixed a device occasionally going missing from Home Assistant's own
      Bluetooth cache for a long stretch, even while still nearby and
      broadcasting. Mobius now periodically checks its own gateway is
      still visible there and asks Home Assistant to do a quick active
      scan if not, rather than only finding out reactively once something
      actually failed to connect.
    • Now requires python-mobius 0.4.3 (still auto-installed, nothing to
      do manually) and won't automatically move to its next minor version
      even once one exists, to avoid a python-mobius change breaking
      Mobius before a matching update here has actually been tested
      against it.
    Downloads
  • v0.3.1 0c98b4b790

    v0.3.1
    All checks were successful
    Release / test-1 (push) Successful in 6m51s
    Release / test (push) Successful in 0s
    Test / test (push) Successful in 5m36s
    Validate / hacs (push) Successful in 44s
    Release / release (push) Successful in 1m5s
    Validate / hassfest (push) Successful in 1m45s
    Stable

    r3pek released this 2026-08-13 15:21:42 +01:00 | 174 commits to main since this release

    • Fixed the "Discovered at" sensor, which could show confusing,
      out-of-order values. It's now a "last seen" attribute on the mesh
      address sensor instead, updating about every 30 seconds.
    • Fixed gateway failover getting stuck bouncing between the same two
      devices forever on a tank with more than two, never trying the
      others.
    • A tank now checks and refreshes its own connection info (which
      device to reconnect through, addresses) about once a minute instead
      of every 12 hours, so a device that couldn't be reached comes back
      much sooner once it's reachable again.
    • Fixed newly-added devices sometimes never showing up in Home
      Assistant, even though they were clearly nearby and broadcasting.
    • Removing a device (or a whole tank) now also tells Home Assistant to
      forget it was seen before, so re-adding the same physical device
      later isn't silently blocked.
    • Now requires Home Assistant 2026.7.0 or newer.
    • Added a lot more detail to debug logging (Settings > Devices &
      Services > Mobius > Enable debug logging) -- connection attempts,
      gateway elections and failovers, and mesh scans are all covered now,
      to make it much easier to see what's going on if something isn't
      connecting.
    • The diagnostics download now also shows whether Home Assistant
      itself currently sees each device over Bluetooth, separately from
      what Mobius has cached -- useful for telling "Mobius's own cached
      info is stale" apart from "Home Assistant hasn't seen this device
      recently" when nothing's connecting.
    • Most sensors now have a proper icon instead of the generic default.
    Downloads
  • v0.3.0 e9f329df13

    v0.3.0
    Some checks failed
    Release / release (push) Failing after 9m30s
    Validate / hacs (push) Successful in 36s
    Validate / hassfest (push) Successful in 1m44s
    Test / test (push) Successful in 8m4s
    Stable

    r3pek released this 2026-08-10 01:38:26 +01:00 | 193 commits to main since this release

    • Devices can now be added as a full tank instead of one at a time.
      When a new device is found, Mobius checks whether it's part of a
      bigger setup and offers to add every device on that tank at once.
      Devices in the same tank are grouped together under one hub in the
      device list.
    • The "add tank" screen now lists the actual devices found, and lets
      you name the tank right there.
    • A newly found device that belongs to a tank you've already set up
      gets added to it automatically -- no need to set it up separately.
    • Mobius now periodically double-checks which devices are actually on
      each tank. If a device turns up on a different tank you've already
      set up (for example, after moving it to another aquarium), it gets
      moved there automatically. A device that just goes quiet is left
      alone, though -- it's not removed.
    • Fixed a real bug where a tank could fail to load at all if even one
      of its devices was temporarily unreachable, even after a restart.
      Now the tank loads as long as at least one device responds; a
      device that's still unreachable just shows unavailable instead of
      blocking the whole tank.
    • Setting up a tank now only needs to connect to one device, not one
      per device -- Mobius learns where the rest are from that single
      connection instead. Faster setup, less Bluetooth traffic.
    • Added Mesh address, Discovered at, and Mesh prefix diagnostic
      sensors.
    • Added a "Gateway device" sensor showing which device is currently
      relaying for the rest of a tank, by name.
    • Added support for Home Assistant's built-in diagnostics download
      (Settings > Devices & Services > Mobius > your tank > Download
      diagnostics), useful if you ever need to report an issue.
    • Various reliability and under-the-hood fixes.

    After upgrading: your existing Mobius devices will show as failed.
    This is expected -- remove them and Home Assistant will find them again
    automatically, this time offering to add each tank as a whole. Do this
    after upgrading, not before, so rediscovery happens under the new
    version from the start.

    Downloads
  • v0.2.2 726c6117a8

    v0.2.2
    Some checks failed
    Release / release (push) Failing after 14m57s
    Validate / hacs (push) Successful in 58s
    Validate / hassfest (push) Successful in 3m6s
    Test / test (push) Successful in 14m11s
    Stable

    r3pek released this 2026-08-07 15:24:14 +01:00 | 211 commits to main since this release

    • Requires python-mobius>=0.3.1 for a real, high-impact fix in
      that library: Brightness (the schedule's master dimmer channel) was
      never being applied to any other channel at all -- every channel,
      moonlight included, was being interpolated and returned without ever
      being scaled by Brightness. Found via real hardware testing: a light
      showing ~1% in the app's own display came back as ~25% from this
      integration's sensors at the same moment. No code changes needed on
      this side -- LightChannelIntensitySensor (and everywhere else that
      reads current_intensities) already just displays whatever
      python-mobius computes, so this integration picks up the corrected
      values automatically once the dependency is upgraded. Confirmed by
      actually installing the fixed python-mobius into this project's own
      test environment and running the full suite against it (98/98 still
      passing), not just assumed compatible from reading the change.

    • Fixed two real hassfest findings, caught once its CI check actually
      started running.
      manifest.json's keys weren't in hassfest's
      required order (domain, name, then alphabetical) -- reordered.
      Added CONFIG_SCHEMA = cv.config_entry_only_config_schema(DOMAIN):
      hassfest requires any integration implementing async_setup to define
      one of CONFIG_SCHEMA/PLATFORM_SCHEMA/PLATFORM_SCHEMA_BASE (or a
      helper equivalent); this integration is config-entry-only (no YAML
      configuration.yaml support at all), so
      config_entry_only_config_schema is the correct one -- confirmed via
      real behavior testing that it doesn't raise if someone configures it
      via YAML anyway, it logs a clear error and creates a Home Assistant
      Repairs issue instead, which is the actual intended, more
      user-friendly handling. 2 new tests.

    Downloads