Skip to content

Skippable Home Assistant first-run setup wizard + global HA connection status indicator #30

Open
1 of 2 issues completed
edge-mining/frontend
#15

Description

@riccardoaran

Home Assistant is expected to be the primary (and initially the only) external service supported by Edge Mining. Since the HA connection is fundamental for core features (energy monitoring, miner control via smart plugs, etc.), we should guide users to connect HA as the first step when opening Edge Mining for the first time.

At the same time, this setup must be skippable so users can explore the UI without configuring anything yet.

In addition, the UI should always expose a clear, global indication of whether Home Assistant is connected or not (green/red), with quick access to connection details.

See the sub-issues for details.

Activity

  1. riccardoaran commented on Jan 21, 2026

    @riccardoaran
    MemberAuthor
    Image

    In the bottom-right corner.

  2. markoceri commented on Jan 24, 2026

    @markoceri
    Collaborator

    This requires the state to be provided by a Core API (edge-mining/core#65)

  3. riccardoaran commented on Jan 26, 2026

    @riccardoaran
    MemberAuthor

    Is it something that @sebailfico you can do?

  4. markoceri commented on Mar 24, 2026

    @markoceri
    Collaborator

    Added visualization of the connection status with external services (Home Assistant). The colors change based on the status.

    I've also added the app version (core and frontend) to the same bar.

    Image
  5. GitGab19 commented on Mar 24, 2026

    @GitGab19
    Member

    Where did you add this? Without a PR mentioning this issue, it's very hard to know what's going on.

  6. linked a pull request that will close this issue UI Refactoring Proposal #15on Mar 24, 2026
  7. markoceri commented on Mar 24, 2026

    @markoceri
    Collaborator

    PR edge-mining/frontend#15 partially closes this issue for the part regarding the status indicator.

  8. riccardoaran commented on Apr 9, 2026

    @riccardoaran
    MemberAuthor

    This issue was getting too broad, so I've split it into 2 sub-issues to keep things more manageable.

    @markoceri could you please review the 2 sub-issues and check whether they can be closed as completed or if there's still work to be done?

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions