Skip to content

Dashboards & scenes

If you connect smart-home and productivity integrations, Personal Agent gives you a full Home-Assistant-style control surface over your entities: dashboards to see and operate them, scenes to snapshot and re-apply states, and a logbook of everything that changed.

Entities live on the Knowledge page

Dashboards, scenes and workflows all operate on the same entities that make up the assistant's memory. Creating entities and helpers, organizing them into areas and floors, and inspecting their state and history all happen on the Knowledge page — see Memory & entities. This page is about displaying and controlling them.

Every entity is controllable through one pipeline: a dashboard card, a workflow and the assistant itself all act on it the same way, and changes appear live across every open view.

Dashboards

A dashboard is a board of cards. Each dashboard appears as its own entry in the sidebar, and you can have as many as you like — one per room, one for work, a glance board for your phone.

Managing dashboards

Manage dashboards (in the account menu) is where you create and organize boards — distinct from editing what's on a board, which you do on the board itself. From here you can:

  • Create a dashboard and choose how it starts:
    • Empty — a blank board you fill yourself;
    • Generated from your entities — auto-built views grouped by domain;
    • Generated by areas — one view per area (room).
  • Rename it, change its icon, and set its URL path for a short link.
  • Set one as the default on this device (the board you land on).
  • Choose whether each shows in the sidebar.
  • Delete a board.

Auto-generated dashboards keep updating themselves as your entities change — until you take control, which freezes the current layout into a fixed configuration you can edit freely.

Editing a dashboard

Open a board and click Edit. Editing is non-destructive (full undo/redo) and covers:

  • Views — the tabbed pages of a dashboard. Each view is laid out as either Sections (titled, resizable columns of cards) or a free Grid, and the view type can be sections, masonry, panel (one full-width card) or main-column-plus-sidebar. Views can be hidden from the tab bar or marked as a subview (reachable only by navigation, with a back button).
  • Cards — added from a searchable card picker with live previews, then arranged by drag-and-resize. You can duplicate, cut/copy/paste, and move cards between views and dashboards.
  • Badges — compact status chips shown along the top of a view.
  • Conditions — show a card, section or badge only when a condition holds: an entity state, a numeric range, the screen size (so a board adapts to phone vs desktop), the time, or a combination with and / or / not.
  • Per-card layout — width, height and aspect ratio, in a simple or precise grid mode.
  • Tap and hold actions — what a card does when tapped: toggle, navigate, open a URL, perform an action, show more-info, or nothing — optionally behind a confirmation.
  • Visual or YAML — edit any card either through its form or as YAML, and edit the whole board as raw YAML when you want full control.

Card types

There's a broad card set. The main families:

  • Read-outs — entity, entities list, glance, sensor, gauge, statistic, history, statistics graph, logbook, calendar, agenda, weather forecast, map, clock/date-time, markdown (which also renders Mermaid diagrams), picture and iframe.
  • Controls — tile, toggle, button, light, thermostat, humidifier, select, number, counter, scene, media control, alarm panel and to-do list.
  • Pictures & registry — picture-elements and picture-glance (interactive overlays on an image), picture-entity, plus area and device cards.
  • Layout & logic — grid, horizontal/vertical stacks, heading, conditional, entity- filter (a list that fills itself by matching entities), and an "auto" card that picks a sensible card for an entity's domain.

Dashboards in chat

Custom chat modes can pin a dashboard's cards into the chat's side panel, so the controls and readouts you need for a task sit right next to the conversation.

Scenes

A scene captures the current state of a set of entities so you can re-apply it later with one tap. On the Scenes page (in the account menu): create a new scene, name it, pick the entities to capture, and the scene stores their current values. Later, Activate restores them all at once — a one-click "movie night" or "leaving home".

Logbook

The Logbook (in the account menu) is a reverse-chronological feed of recent entity state changes — what changed, from which state to which, and when. Filter it by integration to focus on a single domain. It's the quickest way to answer "what just happened?" across your connected things.