3 releases 9 tags

RSS feed

• v0.3.1 0c98b4b790

  Compare

  v0.3.1 Stable

  r3pek released this 2026-08-13 15:21:42 +01:00 | 0 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

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads

  ---

  • mobius.zip
    0 downloads · 2026-08-13 15:21:44 +01:00 · 298 KiB
• v0.3.0 e9f329df13

  Compare

  v0.3.0 Stable

  r3pek released this 2026-08-10 01:38:26 +01:00 | 19 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

  • Source code (ZIP)
    1 download
  • Source code (TAR.GZ)
    0 downloads

  ---

  • mobius.zip
    0 downloads · 2026-08-10 01:38:27 +01:00 · 292 KiB
• v0.2.2 726c6117a8

  Compare

  v0.2.2 Stable

  r3pek released this 2026-08-07 15:24:14 +01:00 | 37 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

  • Source code (ZIP)
    1 download
  • Source code (TAR.GZ)
    1 download

  ---

  • mobius.zip
    0 downloads · 2026-08-07 15:24:15 +01:00 · 271 KiB