Navigation card

Who it’s for

Dashboard builders who want a home screen that leads somewhere. A tenant landing page usually needs a handful of large, obvious entry points — Devices, Assets, Alarms — and this card is one of them: a labelled, icon-bearing button that opens a platform page.

What it does

The Navigation card renders one button that navigates to a relative path inside the platform. Configured with the title Devices, the devices_other icon and the path /devices, it draws a 2.5×2 tile that opens the device list when clicked.

• One tile, one destination — the whole card is the target, so it works as a large touch target on wall displays and tablets.
• The path is relative to the platform, so the same card behaves correctly regardless of the host name the dashboard is opened under.
• Titles accept the platform’s translation tokens, which lets one dashboard serve users in several languages without a card per language.
• Any Material or MDI icon can front the card, which is what makes a row of them scannable.
• The Navigation card reads no data and shows no state: it is a link, so a tile that also has to display a live count belongs on the Entity count card with a click action.

How to set up

Data keys

The Navigation card takes no data keys — it navigates, it does not read. The default configuration carries a leftover demo datasource, which can be removed.

Destination

Setting	Default	Effect
Title	{i18n:device.devices}	The caption on the card; accepts a plain string or an {i18n:...} translation token
Icon	devices_other	The symbol above the caption
Navigation path	/devices	Relative platform path opened on click

Take the path from the browser’s address bar while standing on the destination page, keeping everything after the host — that is exactly what belongs here.

How to customize

• To point the card somewhere else — change Navigation path to the relative path of the target page.
• To caption it in the user’s language — set Title to an {i18n:...} token instead of literal text.
• To change the symbol — set Icon to any Material or MDI name.

Tips

• Give related cards icons from the same family and let the captions carry the difference. A landing page is scanned by shape first, and icons chosen individually rarely read as one set.
• Check the path as a user with the least privilege who will see the dashboard. The card renders identically whether or not the viewer may open the destination, so the permission problem only appears at the moment someone clicks.