0.3.7

• Fix Fallback groups silently losing automatic switching: selecting a node pins it in
  Mihomo (fixed), and there was no way to undo that from Home Assistant. Fallback and
  pinnable URLTest selectors now offer ↺ Auto, which clears the pin, and expose
  fixed/pinned_node attributes.
• Create proxy groups marked hidden: true in the core config as disabled entities.
  Already registered entities keep their current enabled state.

Clash Controller 0.3.6

Changelog

0.3.6

• Publish the companion Mihomo Control card v17 with corrected diagnostic status,
  stable fallback telemetry and a primary-route check in Ping All.
• Keep the Python integration behavior unchanged from 0.3.5. The standalone card
  still needs to be installed as a separate Lovelace resource.

0.3.5

• Require Home Assistant administrator access for proxy API mutations, core restarts and connection closures. Keep read-only API and connection queries available to read-only users.
• Preserve explicit HTTPS URLs during setup.
• Reject supplied connection filters that contain no keywords.
• Give colliding group/provider names distinct, stable Home Assistant entity IDs while retaining existing IDs when a registered entity identifies its name.
• Reuse recent group-delay probes and locate groups from the coordinator's current data.
• Report Netflix status as unknown when redirected to login or when catalog access cannot be verified.
• Run tests on pushes to main and validate version tags before publishing a release.

Clash Controller 0.3.5

Changelog

0.3.5

• Require Home Assistant administrator access for proxy API mutations, core restarts and connection closures. Keep read-only API and connection queries available to read-only users.
• Preserve explicit HTTPS URLs during setup.
• Reject supplied connection filters that contain no keywords.
• Give colliding group/provider names distinct, stable Home Assistant entity IDs while retaining existing IDs when a registered entity identifies its name.
• Reuse recent group-delay probes and locate groups from the coordinator's current data.
• Report Netflix status as unknown when redirected to login or when catalog access cannot be verified.
• Run tests on pushes to main and validate version tags before publishing a release.

Clash Controller 0.3.4

Clash Controller 0.3.4 fixes latency checks for proxy-provider nodes that Mihomo includes in group options but omits from its direct /proxies endpoint. When the direct node delay returns 404, the service locates a containing group and reads that exact node's delay from the group response. It retains the exact-name handling from 0.3.3.

Clash Controller 0.3.3

Clash Controller 0.3.3 preserves exact group and node identifiers in latency checks, including leading and trailing spaces. Empty or whitespace-only targets still fail validation.

The private Home Assistant dashboard update is deployed separately as Lovelace resource v10. It reports Ping All failures accurately, keeps open selectors during telemetry updates, refreshes only changed UI sections, and shows the live integration status and fresher telemetry timestamp.

Clash Controller 0.3.2

Fix the memory sensor staying at 0 MB on Mihomo controllers whose /memory stream starts with a zero-valued WebSocket frame. When HTTP memory streaming is available, the integration reads the second HTTP sample and uses it if positive.

The local Lovelace dashboard also keeps proxy menus open across Home Assistant state refreshes and raises them above neighboring cards; that local /config/www/clash-dashboard.js file is deployed separately.

Clash Controller 0.3.1

Based on upstream Clash Controller v0.3.0, preserving its features and compatibility.

Fixes HTTP 400 when selecting a Mihomo proxy node whose configured name starts or ends with whitespace. Proxy group and node names are sent exactly as configured.

For this Home Assistant instance, the local dashboard reads the installed version from the HACS update entity and is updated separately in /config/www/clash-dashboard.js.

Clash Controller 0.2.3

The Mihomo Control dashboard now shows the installed Clash Controller integration version beside Proxy control. The version is exposed by the integration and updates when Home Assistant loads the new integration code. The footer no longer presents a stale Mihomo core version as the integration version.

Clash Controller 0.2.2

Changelog

0.2.2

• Preserve exact proxy group and node names when changing a selector. This fixes HTTP 400 errors when configured node names contain leading or trailing whitespace.