Repository navigation
Troubleshooting and FAQ
The resource is not loaded. Check Settings › Dashboards › ⋮ › Resources (/local/maquette-card.js, type
JavaScript module), then reload the page with the cache cleared (Ctrl+F5, or close and reopen the companion app).
The browser still has the previous file. Reload without cache; for a manual install, change the resource URL
(?v=2). ⚙ Settings (top of the dialog) and the console banner show the version actually loaded.
2023.9 or later, as declared to HACS (the card uses Home Assistant's state formatting, hass.formatEntityState). Valves
(valve.* in a cover widget) need 2024.1, where the domain appeared. The card also relies
on the entity, device and area registries and on Home Assistant's state formatting. Browsers: Chrome / Edge 111+,
Safari 16.4+, Firefox 121+.
Older Home Assistant versions do not list custom dashboard strategies. Add the card to any dashboard instead (Add card › Maquette), preferably in a view of type Panel.
It is shown only to administrators, not in the card picker preview, not while the dashboard itself is in edit mode
(click Done), and not when editor: false is set. To get it back, open the card in the code editor and remove
editor: false.
The dashboard card changed since you opened the editor (another browser, another tab, the YAML editor). Choose Export my plan to keep a copy, then Overwrite with my plan or Cancel.
Dashboards in YAML mode cannot be written by the frontend. Use Export / import, copy the YAML and paste it into your dashboard file.
- Not saved: reopen the editor in the same browser, a draft is offered (Resume).
- Saved, then regretted: Export / import › Previous versions (the last five, in this browser).
- After a clean-up: Plans before clean-up.
Some rooms have fewer than three valid points, or some walls, openings, badges or texts have no valid coordinates (often after hand-editing the YAML). Fix them in YAML before saving if you want to keep them.
The text must be a Maquette plan (type: custom:maquette-card), with lists where lists are expected. Plans written with
the former French keys (pieces, murs…) from development versions are refused: convert them to the English keys
first (CHANGELOG › Former French keys).
They are looked up in the room the opening borders: give the room its Home Assistant area (or name it like the area).
Entities already on the plan are skipped. Use the suggestions of the opening panel, or pick the entity by hand.
Use a Panel view; check margin; very large furniture or texts far from the rooms extend the frame.
With a mouse, they appear when the pointer is over the plan. interaction.lock_view: true hides them.
It has no temperature, it is outside: true or a sub-area, or temperature_tint: false is set. Check that the sensor
state is a number (or use temperature_attribute).
Its contact is unavailable or unknown.
Check the active rule: without threshold, only on, open, playing, heating… count.
For a thermostat use active_attribute: hvac_action, for a plug active: <power sensor> with threshold.
It is painted only on rooms with outside: true. The editor's Ambience panel warns when there are none.
It is drawn in the editor only while the Ambience and animations panel is open.
Their direction comes from their latitude / longitude and the Home Assistant home location; check ambience.north
(the direction of north on your drawing).
animation_level: reduced or none; the system "reduce motion" setting also stops loops. Animations pause when the
card is off screen.
Inside a card, rows show values only (no toggles, no Activate button). Put scenes, scripts and buttons in a side panel
or a room's panel, or use room actions.
The service is sensitive (unlock, open a garage door, disarm, run a script…) or the element has confirm: true. The
dialog names the real service and entities; see Security.
power is converted to watts from its unit (W, kW or MW; no unit = W) and compared with threshold (50 W by default).
Check that the sensor has a unit and that threshold is in watts.
stat needs an entity with long-term statistics (a state_class of total or total_increasing). Otherwise use four
entities (day, week, month, year).
The lock widget never sends a code: operate it from its more-info.
maquette-card : unknown key « … » (ignored): a typo or a key that does not exist. The Reference lists
every key.
Yes: open the card in the dashboard's code editor, or use Export / import. Coordinates are in cm, y downwards.
Use one card per floor, each with its own id, in separate views or side by side.
No. It only reads your entities and calls the services described in Entities.
Yes. The card makes no request outside your Home Assistant (see Privacy).
Not in 0.1.0. Trace the rooms with the editor; Clean up the plan helps when the drawing is a bit off ("Round to 5 cm" is offered for traced plans).
In the issues of the repository.