[Feature Request] Clash widget (mihomo / Clash Meta, OpenClash, etc.)

[mdj2812]

Description

Homepage currently has no widget for Clash-compatible proxy cores. mihomo (formerly Clash Meta) is the core used by OpenClash on OpenWrt and many other router and self-hosted setups. It exposes a RESTful API via its external controller (port 9090 by default), documented at https://wiki.metacubex.one/api/.

I'd like a read-only service widget that shows:

• Mode (Rule / Global / Direct) — from GET /configs (mode)
• Active node in a strategy group — from GET /proxies (now of a Selector / URLTest / Fallback group; defaults to GLOBAL, configurable with a group option)
• Up / Down totals — from GET /connections (uploadTotal / downloadTotal)
• Optional extras: connection count, active-node latency (read from proxy history, without triggering delay tests), and core version

Example configuration:

widget:
  type: clash
  url: http://clash.host.or.ip:9090
  key: apisecret # optional, only needed if the API has a secret
  group: PROXY   # optional, strategy group to watch; default is GLOBAL
  fields: [mode, active, up, down] # optional, defaults to these four

Other

• The widget is named clash because it works with any Clash-compatible core — per the MetaCubeX naming policy, downstream projects unrelated to MetaCubeX must not use "mihomo" in their name.
• Example API output:
  • GET /configs → {"port": 7890, "mode": "rule", ...}
  • GET /proxies → {"proxies": {"GLOBAL": {"type": "Selector", "now": "DIRECT", "history": [{"delay": 123}]}, ...}}
  • GET /connections → {"connections": [...], "uploadTotal": 123456789, "downloadTotal": 987654321}
  • GET /version → {"meta": true, "version": "v1.18.0"}
• A complete, tested implementation is ready in PR Feature: clash service widget #6967 (closed pending this feature request) — happy to resubmit once this request shows enough support.