-
Notifications
You must be signed in to change notification settings - Fork 0
Saving layouts
Drag devices into place, optionally use Tidy layout, then press Save layout. Saving includes positions, orientation, grouping, link-label visibility, detailed/map-only view and whether the magnifier is enabled.
On an editable storage dashboard, Save layout writes this card's configuration through Home Assistant's dashboard save mechanism. The arrangement is then available in other browsers using that dashboard.
When working in the card editor's preview, Save layout sends the positions to the matching editor draft. Press the editor's Save button to apply that draft to the dashboard.
A save requires the card to be identified uniquely. Use a unique layout_id for otherwise identical cards. Unsupported dashboard modes, generated dashboard strategies or failed dashboard writes produce a save error.
Save layout stores the active hub’s settings and positions in the integration configuration. These settings are shared across browsers and remain separate from dashboard cards. Saving panel settings requires an administrator.
Use the toolbar’s Copy / Paste from clipboard menu to transfer display settings and map positions between dashboard cards and sidebar panels. Copy includes the title, theme mode, automatic refresh, detailed view, device-list visibility, link labels, link status, magnifier, orientation, area grouping, map height and node coordinates.
Paste validates and saves the settings to the destination. Its hub, layout identity and dashboard placement stay unchanged. Sidebar panels retain automatic height. Save remains the last toolbar button.
If clipboard reading is blocked, Paste uses the last successful Wiser Copy in the current browser tab session. If no copy is available, a text box opens for manual paste followed by Save. Paste is unavailable in the card editor preview.
- Arrange the map and choose Copy from the toolbar menu.
- Open your existing card YAML.
- Merge the copied fields, replacing existing fields with the same names.
- Keep the destination card’s
typeandhub, then apply the dashboard changes.
The clipboard contains a settings fragment, not a complete card. It includes the title and display settings as well as layout_data, but omits type and hub. Avoid duplicate YAML keys. Use the generated coordinates rather than inventing node IDs.
When a map loads, a compatible layout_data object in the card configuration takes priority over browser-saved coordinates. Browser storage is a fallback when no compatible configured layout exists. If neither is available, the card uses an automatic layout.
While the map is already running, refresh preserves current positions, including unsaved dragging, and the current viewport.
Browser layout identity includes dashboard path, hub, card name and layout_id, with separate layouts for orientation and area grouping. Changing any of those may select a different local layout. Clearing browser site data removes local layouts but does not remove coordinates saved in dashboard configuration.
To replace an arrangement, use Tidy, adjust positions and save again. Removing layout_data alone can reveal an older browser fallback.
Successful Copy and Save actions show brief confirmations beside their buttons. Failures show an error. A browser copy may have been stored even if the dashboard save failed, so a layout that survives locally is not proof that it was saved for other browsers. Use Copy and merge the YAML if dashboard saving is unavailable.