Skip to content

Troubleshooting

Andrew Blackburn edited this page Jun 28, 2026 · 1 revision

Troubleshooting

Card Does Not Update After Installing

Refresh the browser or reload Home Assistant frontend resources.

For manual installs, check that the resource points to:

/local/orbit-cards.js

and that the resource type is JavaScript module.

Old Room Card Still Works

This is expected.

custom:orbit-room-card remains registered as a legacy alias for custom:orbit-area-card.

Open the card in the visual editor and save it to migrate the config to the new Area Card type.

Navigation Path Is Missing From The Editor

Navigation is now configured through the Interactions section as the card tap_action.

Use:

tap_action:
  action: navigate
  navigation_path: /dashboard-main/lounge

Legacy navigate.navigation_path configs still work as a fallback.

Theme Colours Do Not Appear

Reload themes in Home Assistant, then refresh the dashboard editor.

The picker reads colours from the active Home Assistant theme. Theme-provided colours are marked with T.

Local Icons Do Not Appear

Create:

/config/www/icons/manifest.json

Example:

[
  "motion_detected.svg",
  "motion_on.svg",
  "motion_off.svg"
]

Then refresh the editor.

SVG Icon Colours Look Wrong

Orbit Cards recolour inline SVG icons by default.

To preserve a multi-colour SVG, set the matching override to false:

main_entity_icon_svg_color_override: false
button1_icon_svg_color_override: false
curve_button1_icon_svg_color_override: false

Add To Dashboard Preview Clicks

In Home Assistant's add-card picker, clicking a card preview should add the card. Inside the Orbit visual editor, preview interactions remain testable.

If preview clicks behave oddly, refresh the frontend resources and make sure only one copy of orbit-cards.js is registered.

Clone this wiki locally