Configuration and editor

Profiles, overrides and effective configuration

A profile contains a complete dashboard. A device references one profile and may store an override. It follows RFC 7396: objects merge recursively, arrays are replaced in full, and null removes a key. Provider bindings are stored separately and are never resolved to secrets.

{
  "schema_version": 1,
  "theme": "dark",
  "tabs": [
    {
      "id": "overview",
      "title": "Overview",
      "columns": 2,
      "widgets": [{"id": "clock", "type": "clock"}]
    }
  ]
}

JSON and visual editor

JSON is always the default view. The code editor provides syntax highlighting, line numbers, tab indentation and immediate syntax validation. Separate views show the profile draft, device override and read-only effective configuration. Saving a profile creates a draft; only Publish validates references, creates a monotonic revision and deploys it. Saving a device override immediately publishes and deploys its merge patch. Missing providers block publishing. Temporarily missing HA entities produce warnings.

The visual editor changes complete profiles. It exposes the real theme fields for colors, radius, scale, padding and gap as well as tabs, grid positions, spans and common native widget types. Widgets can be created, reordered and deleted. Fields that are not shown and complex blocks remain unchanged. Device overrides are RFC 7396 merge patches and therefore stay in the JSON editor; their merged result is visible on the right.

Preview

Select a device to use its last reported physical and usable pixel size, activity content area, orientation, density, density DPI, font scale and known insets. The preview converts dp and sp with those values and scales proportionally into the browser. Portrait and landscape can be switched deliberately. Offline devices use their last data; the generic tablet is explicitly not device-specific.

The preview uses current HA states, the actual widget family, tab order, explicit rows and columns, spans, cell heights and theme values. auto_entities is resolved by the same server-side compiler used for deployment to Android. It still remains an approximation because Android and browser font and media engines differ. The native device is authoritative. The header links directly to the complete widget documentation with all JSON codes.

Revisions and rollback

Twenty immutable revisions are retained. A rollback does not rewrite history; it republishes the chosen content as a newer revision. If the app rejects a configuration, its last valid configuration stays active and HA shows the unacknowledged revision.