v0.5.3 — Integration brand icon + logo

Added

• Bundled brand images at custom_components/evse_hub/brand/ (icon.png, icon@2x.png, logo.png, logo@2x.png).
• Home Assistant 2026.3+ serves these locally via /api/brands/integration/evse_hub/* — no external CDN roundtrip.
• Also unblocks the previously-failing HACS brands validation check (last one on Validate CI).

Preview

Requires

• Home Assistant 2026.3.0 or newer for local brand serving.
• Older versions still fall back to CDN (which is empty for this integration until a home-assistant/brands PR lands).

v0.5.2 — One-click install (baked-in Geely AppSecrets)

Changed

• One-click install: Geely client-side AppSecrets are now shipped as defaults, so the integration works right after HACS install — no env vars to set up first.
• Override chain is unchanged: env vars → $EVSE_HUB_SECRETS_FILE → /config/.evse_hub_secrets.json → baked-in default.
• These are client-fixed signing parameters (same for every Geely Galaxy app install), not per-user credentials. Same category as client_id values other HA integrations hard-code.

Migrating from 0.5.1

Nothing to do. If you'd previously set GEELY_*_SECRET env vars or the JSON file, they still take precedence.

v0.5.1 — Provider-agnostic token sensors + EN docs

v0.5.1 — Token sensors → TokenBundle, English docs, new-provider template

v0.5.0 — Multi-provider architecture

v0.5.0 — Multi-provider architecture

Major refactor: geely-charger-ha renamed to evse-hub-ha, HA domain
renamed to evse_hub. Introduces a Provider SPI + unified data models
so future vendors can be added by writing a single provider//
package.

Highlights:

• Provider ABC + @register_provider registry
• Unified Equipment / ChargeStatus / TokenBundle / Health / Versions
• switch / sensor / binary_sensor entities are now provider-agnostic
• Config flow picks provider first (auto-skipped when only one is bundled)
• docs/PROVIDER-GUIDE.md contributor guide
• tests/ + CI on push/PR

Breaking:

• HA integration domain changed geely_charger -> evse_hub
• Existing 0.4.0 users must re-add the integration once after upgrade