Smart Appliance Card

Features

• One card, smart-appliance-card, and its compact version smart-appliance-mini-card (a detail button unfolds the full card)
• 13 appliance types, each with its own illustration animated by what it is doing: drum turning, laundry tumbling, water spraying, oven glowing, coffee pouring, hood drawing air, frost on a fridge in super mode…
• Type detected from the appliance (its programs, its model or its entities), or set with kind
• The appliance's brand next to its title: its logo (Bosch, Siemens, Neff, Gaggenau, Miele, Samsung, LG, Whirlpool, KitchenAid), or a badge with its initial on the header icon for the others (Constructa, Maytag…); main buttons in the brand's colour
• Status with colour, progress bar, finish time and time left, the program step when the integration reports it (spinning, drying…)
• Program picker and Start (when remote start is enabled), Pause / Resume, Stop with a confirmation tap, whatever the integration offers
• Program options before starting, and the settings of appliances without programs (super modes, fan stage…)
• Temperatures of fridges, freezers and wine cabinets, and of ovens while cooking
• Door state, salt and rinse aid alerts, coffee machine bean container, water tank and drip tray alerts
• A reminder chip when a program has finished and the door hasn't been opened since ("Finished 25 minutes ago, door still closed")
• Energy per cycle: with an energy meter on the appliance (or a smart plug's, set as entities.energy), This cycle: 0.6 kWh while a program runs, then Last cycle: 0.9 kWh, with its cost when a price is set
• A click on a chip (door, temperature, alert…) opens the more-info dialog of its entity
• Visual editor in the dashboard UI (no YAML needed)
• English, French, German, Spanish, Serbian (Cyrillic and Latin), Italian, Dutch, European Portuguese, Polish, Romanian, Danish, Swedish, Bulgarian, Russian, Ukrainian, Hungarian, Slovak, Czech, Slovenian, Latvian and Greek, follows the Home Assistant language
• Light and dark theme compatible
• Single file, no dependencies, ready for the Marketplace

Supported integrations

Air conditioners, purifiers and robot vacuums are left out: they have their own cards.

Appliance types#

Each type is detected by itself; kind is the value to set when it can't be (a Matter appliance whose entities don't give it away, for instance).

Prerequisites

• Home Assistant 2024.8 or later with one of the supported integrations set up
• To start a program from Home Assistant, Remote start (or the integration's equivalent) must be enabled on the appliance itself (the card shows a hint when it isn't)

Configuration

Visual editor#

Add the card from the dashboard (Add card → Smart Appliance Card). The first supported appliance is picked automatically; change it with the Appliance field, then set the name, icon and the sections to show. Appliance type and Brand are only needed when the integration doesn't give them away. The Entities (advanced) panel lets you force any entity if auto-detection picks the wrong one. Options left at their default are not written to the YAML.

Minimal#

type: custom:smart-appliance-card
device_id: bad11e7fd00845a2fb485b38c97cf675

type: custom:smart-appliance-card
entity: sensor.washing_machine_operation_state

Mini cards#

type: custom:smart-appliance-mini-card
device_id: bad11e7fd00845a2fb485b38c97cf675

The mini card shows the appliance, its state, the program, the progress and finish time, the alerts, and round Start / Pause / Resume and power buttons. The detail button (top right) unfolds the full card with every option; a click anywhere else on the page folds it back. It takes the same options as the full card, which apply once unfolded, plus zoom. At its default size in a Sections view (6 columns), the round buttons sit under the text and the status pill shows only its coloured dot, the state being written above the program.

Use either device_id (what the visual editor writes) or entity (any entity of the appliance). With neither, the card uses the first supported appliance it finds (of the kind given, if any).

Full options#

type: custom:smart-appliance-card
device_id: 5c3a4c7f80e0aa935477ebca6e7b915b
name: Washing machine
kind: washer
brand: maytag
show_program: true
show_options: true
show_controls: true
show_alerts: true
show_power: true
show_energy: true
language: en
entities:
  operation_state: sensor.washing_machine_operation_state
  selected_program: select.washing_machine_selected_program
  active_program: select.washing_machine_active_program

Options reference#

Entity overrides#

Keys accepted under entities:

Every other switch and select of the device is shown as a program option (or as a setting, on appliances without programs).

Legacy card types#

home-connect-dishwasher-card, home-connect-washer-card, home-connect-dishwasher-mini-card and home-connect-washer-mini-card are kept so that existing dashboards keep working. They are the same card with the appliance type fixed; new dashboards should use smart-appliance-card.

How it works

The card reads the entity registry to list the entities of the chosen device and tells its integration from them. It then matches each role by its translation key, then by its entity ID (English and French slugs), then by its attributes (a door's device class, a timestamp…). Program and option labels use Home Assistant's own translations.

The appliance type comes from what the integration says about the device (Miele's model, LG's device type), else from its Home Connect programs, else from the entities only one kind of appliance has (a fridge's setpoints, a hood's fan stage). Each integration's states are folded into one set (ready, delayed start, running, paused, action required, finished, error), and when the integration reports the current step (rinse, spin, drying…), the card shows it instead of "Running". Commands go through what each integration offers: buttons (Home Connect, Miele, Matter, SmartThings dishwashers) or an operation select (SmartThings, LG ThinQ). The progress is computed from the elapsed and remaining times, or from the finish time and total duration, when the integration has no percentage.

Home Connect only sends program options when the selected program changes, so after a Home Assistant restart they all stay unavailable. The card then shows them greyed out with a Load options button, which switches to another program and back to load them. While someone turns the dial on the appliance (Remote control off), Home Assistant can't read the options: the card says so and disables the button until remote control is back. It never reloads them by itself, since that changes the program on the appliance. If loading fails, the original program is restored.

With Home Connect, Start selects the chosen program on the Active program entity, which is how that integration starts a program. Appliances sometimes reject a start for a moment (BadRequest, WrongOperationState): the card then retries once after 3 seconds, and if it fails again shows a short message in the card instead of Home Assistant's raw error (the technical detail is in its tooltip). Stop asks for a second tap within 3 seconds.

Some appliances can't be turned off remotely: after a first refusal, the card says so and keeps the power button disabled while the appliance is on (until the page is reloaded); turning it on still works. The power button and the option pills send an explicit turn on or turn off from the state shown, and stay disabled until the appliance answers, so a quick second click can't undo the first.

Support

If you find this project useful, you can support its development:

Features

• show_title and show_subtitle options (also in the visual editor) hide the header's title and its subtitle, separately, for a card placed under a section heading of its own (asked in juju35/ha-vehicle-card#72).

Features

• Home Connect hob: a hob on the built-in Home Connect integration is now detected. It has no program and its device model is the VIB, so it is told apart by its event sensors: it is the only appliance with both the favorite keys (also on hoods) and the preheat / alarm clock events (also on ovens). Thanks @FredM67 (#79, #80).

Improvements

• Energy per cycle: with energy_price (per kWh) or energy_price_entity (a price sensor: current tariff, Tempo…), the chip adds the cycle's cost in Home Assistant's currency (This cycle: 0.58 kWh · ≈ €0.12). Both in the editor (full card), 22 languages.

Maintenance

• No code change: released again to check the installation from the Marketplace.

Features

• Energy per cycle: with an energy meter among the appliance's entities (device_class: energy, Miele, SmartThings, LG ThinQ…) or one set as entities.energy (a smart plug), a chip shows This cycle: 0.6 kWh while a program runs and Last cycle: 0.9 kWh once it ended (within 24 h). Worked out from the recorder's history of the operation state and the meter, read again when the state changes and every 5 minutes while a cycle runs; a meter that drops (Miele's per-program one) counts as a reset. show_energy (default true) in the editor; 22 languages.

Fixes

• Translations: the cards are defined once the page's language file has arrived (at most 1.5 s; Home Assistant builds a card when its element gets defined), so the first render is already translated instead of English then redrawn; until a language file is in, a missing text reads the English one wherever the card has no fallback of its own.