• 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 | 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