Skip to content

Home Assistant integration (labelle-web-hacs, separate repo) #22

Description

@szrudi

What

A Home Assistant HACS integration that connects to a running Labelle Web server over the network, so users can print labels from automations / dashboards. Lives in a separate repo (`labelle-web-hacs`, not yet created) — the labelle-web server stays standalone and HA is just a network client.

Why

  • Common use case: print labels triggered by HA automations (package-on-doorbell, scheduled chore stickers, asset tagging for inventory).
  • Labelle Web already runs as a long-lived service on a Pi; exposing it via HA is a natural extension that doesn't require any new on-device hardware.
  • The relevant HTTP surface already exists: `/api/printers`, `/api/preview`, `/api/print`, `/api/batch-print`, `/api/health` (for connectivity monitoring).

Scope

On the HA side (new repo)

  • HACS-compatible custom component, Python.
  • Config flow: user enters the Labelle Web server URL; validate via `GET /api/health`.
  • Services:
    • `labelle.print_label` — accepts widgets + settings, POSTs to `/api/print`.
    • `labelle.preview` — returns a PNG preview as a binary attachment / camera entity image.
    • (Optional) `labelle.batch_print` — streams progress via SSE, surfaces as a long-running task.
  • Entities (one set per printer):
    • Sensor: online / offline (from `/api/health` + `/api/printers` polling).
    • Button: quick-print a preconfigured label template.
  • Lovelace card (optional, can be a follow-up): text input + template picker + preview + print button.

On this side (labelle-web)

  • Probably nothing required — the API is already sufficient. Worth double-checking once the HACS side is being built that:
    • `/api/health` is enough for HA's connectivity monitoring.
    • CORS allows the HA origin if HA ever calls the API from the browser side.
    • Auth: currently zero auth (LAN-only assumption). If HA is exposed to the internet, the HACS integration would need to pass credentials — but adding auth to labelle-web is a separate, larger discussion.

Reference

Owner

Nobody yet. The labelle-web server is ready to be consumed; just needs someone with HA-integration experience to write the HACS side.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions