Skip to content

Releases

Dashhaus 0.4.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 01:58
6ec1f2a

Orb and Field now each install on their own from the Home Assistant Marketplace, under their own names, and each one
lists itself in Settings → Dashboards → Add dashboard. The Dashhaus download is gone: this release adds no file to
it, so move to Orb or Field with the steps below. On npm, @dashhaus/bundle and @dashhaus/dashboard are gone too:
each skin's package ships its own file, and the dashboard framework is now @dashhaus/core/lovelace.

Upgrading

From the Dashhaus download in the Marketplace:

  1. Install Orb or Field (or both) from its page:
    krystosterone.github.io/dashhaus/orb/ or
    krystosterone.github.io/dashhaus/field/.
  2. Reload the browser tab.
  3. Go to Settings → Dashboards → Add dashboard and pick the skin.
  4. Delete the Dashhaus dashboard, any Home (Orb) or Home (Field) dashboard the old setup card made, and the
    setup card itself.
  5. Remove the Dashhaus download.

A dashboard you wrote yourself on Orb's or Field's card (custom:dashhaus-orb, custom:dashhaus-field) keeps
working once that skin is installed.

From npm, deploying from the command line:

  1. Replace @dashhaus/bundle with the skins you deploy:
    npm uninstall @dashhaus/bundle && npm install @dashhaus/orb@^0.4.0 @dashhaus/deploy@^0.4.0 (add
    @dashhaus/field@^0.4.0 for Field).
  2. In dashboard.config.mjs, replace bundle: fileURLToPath(bundlePath) with files: [resourceFile], importing
    resourceFile from @dashhaus/orb/resource or @dashhaus/field/resource. A dashboard can now name a skin's
    strategy instead of a card, strategy: { type: "custom:orb-dashboard" }, and follow the skin as it updates.
  3. Deploy, then delete the old /local/dashhaus/dashhaus.js under Settings → Dashboards → Resources, since it
    defines the same cards.

If you call @dashhaus/deploy from code, resolveBundle is now resolveFiles, which returns one target per file, and
deploy() returns { resources, dashboards } instead of { version, resource, dashboards }.

If you build a skin, drop @dashhaus/dashboard from its package.json, move @dashhaus/core to ^0.4.0, and change
each import: @dashhaus/dashboard becomes @dashhaus/core/lovelace, and @dashhaus/dashboard/skin, /card,
/schema, /layout and /conformance become @dashhaus/core/lovelace/skin, /card, /schema, /layout and
/conformance.

Full notes: spec/releases/0.4.0.md

Dashhaus 0.3.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 02:16
014c516

One breaking change for Orb YAML: cards no longer take a color of their own, so delete color from your cards and
set the dashboard's accent instead. New in Orb and Field: a guest Wi-Fi card with the network's name, its code and a
join QR code. Lights and covers Home Assistant reports as unknown, such as RF blinds, now say Unknown and can be driven.

Full notes: spec/releases/0.3.0.md

Dashhaus 0.2.1

Choose a tag to compare

@github-actions github-actions released this 05 Nov 02:12
26f2403

A patch release. A skin made with npm create dashhaus-skin now builds to exactly one file, without the empty
style.css and the CSS warnings beside it. Every package is now published from this repository's GitHub Actions, with
an npm provenance attestation naming the commit it was built from.

Full notes: spec/releases/0.2.1.md

Dashhaus 0.2.0

Choose a tag to compare

@Krystosterone Krystosterone released this 04 Nov 21:45
c2c25ad

The first public release of Dashhaus: Home Assistant dashboards drawn in React.

  • Two finished skins, Orb and Field. Install them from the Home Assistant Marketplace (or HACS), then press Create on the setup card; no terminal needed.
  • The headless hooks under them, @dashhaus/core, to draw your own.
  • create-dashhaus-skin to start a skin of your own.

Full notes: spec/releases/0.2.0.md