Migration Guide

Migration Guide

Room Card To Area Card

Orbit Room Card has been renamed to Orbit Area Card.

New configs should use:

type: custom:orbit-area-card

Existing configs using:

type: custom:orbit-room-card

continue to work through a legacy alias.

Editor Migration

When an old Room Card config is opened in the visual editor, the editor migrates:

type: custom:orbit-room-card

to:

type: custom:orbit-area-card

It also migrates:

room_name: Lounge

to:

area_name: Lounge

Navigation Migration

Older Area/Room Card configs may use:

navigate:
  navigation_path: /dashboard-main/lounge

This still works as a legacy fallback.

New configs should use:

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

The visual editor writes navigation through tap_action.

Main Icon Migration

Area Card now supports icon source selection:

main_entity_icon_source: area

Options:

• area
• entity
• custom

If custom icon config exists, the editor can preserve custom mode. If no custom icon config exists, it prefers Area when an area is configured, otherwise Entity when a main entity is configured.

Interaction Migration

Actions now live in a native-style Interactions section in the editor.

Unset actions use card defaults.

Use:

action: none

only when you intentionally want to disable an interaction.

Compatibility Summary

Old	New
custom:orbit-room-card	custom:orbit-area-card
room_name	area_name
navigate.navigation_path	tap_action.navigation_path with action: navigate