Skip to content

Ship the switch card with the integration #32

Closed

Description

@eizedev

The HACS review of hacs/default#12989 asks to ship the card inside the integration: the card works with this integration only (it reads managed_switch/ports and this integration's entities), so it should not be a separate HACS dashboard repository (hacs/default#12992 was closed for that reason).

Plan:

  • Move the card's source from eizedev/managed-switch-card into card/, with its history (git subtree add)
  • Build it into custom_components/managed_switch/www/managed-switch-card.js; CI checks that the committed bundle matches a fresh build
  • The integration serves the file and loads it in the frontend on setup, with its version in the URL
  • Docs: card page, README, AGENTS.md, CONTRIBUTING.md, CHANGELOG; a note for users who installed the card on its own
  • Release 0.6.0, re-request the HACS review
  • Archive eizedev/managed-switch-card with a pointer here; move its open issues

Refs #6

Activity

  1. eizedev commented on Nov 2, 2026

    @eizedev
    OwnerAuthor

    Done in #33, released in v0.6.0. HACS review re-requested on hacs/default#12989. Left: archive eizedev/managed-switch-card after eizedev/managed-switch-card#13 is merged; its issue #8 is now #37. README without the custom repository route: #35.

  2. eizedev commented on Nov 2, 2026

    @eizedev
    OwnerAuthor

    Done. The card ships with v0.6.0 (#33) and loads as a frontend module without a dashboard resource; checked on a production instance after the update. eizedev/managed-switch-card points here (eizedev/managed-switch-card#13) and is archived, eizedev/brand notes it (eizedev/brand#8), its open issue is #37. HACS review re-requested on hacs/default#12989; README follow-up in #35.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions