Typical setup flow

Follow this order when building a new dashboard from scratch.

Throughout the app — in sources, destinations, connections, transformers, tap actions, and variables — swipe a row right to left to delete it.

1. Add connections (if you're using MQTT or WebSocket)

Set up your MQTT connections and WebSocket connections before adding sources that need them. Configure the broker or device address, port, TLS, login, and protocol options once — many sources and destinations can share the same connection.

Open from the menu: MQTT connections, WebSocket connections.

If several sources or connections will share a host or a token, store it under ENV variables first (menu → Data → ENV variables), then insert {{ env.my_key }} in those fields. See ENV variables.

2. Create your data sources

Add a data source for each stream you want to watch:

On HTTP and Timer, set Trigger to Auto (periodic) or Manual; an HTTP stream and a Video source use Keep connected instead. On every type except HTTP and Video, add source transformers if you want to clean up the JSON early. On HTTP, add extra actions in the Actions / Transformers pipe instead.

3. Add a section and data pieces

Create at least one data section, then add data pieces to it. A data piece can have an optional root data source; components inherit it unless you pick another source on that component.

While Edit layout is on, tap Add at the top of the home screen, then Add section, Add data piece, Add data source, or Add data destination. Add data piece asks Wizard or Manually:

On a Fixed grid, the data piece then opens in the data piece editor. On a Resizable grid, it is added right away and Edit layout turns on; the new data piece is selected, so tap its menu button for more while Edit layout is on. An empty data piece already includes a Label at the top (bold Header) and a Data source activity bar (last-updated time and status dot).

Tap Ask AI on the home screen to open the AI assistant so it can add data pieces for you.

When you select a component that shows text, Component has Text size, Text color, Font, Bold, and Italic next to each other. Highlight editor has size, color, and font only. On Label, Badge, Button, and Data source last activity label, Word wrap puts long text on the next line instead of scrolling it or cutting it with an ellipsis.

To reuse a layout from several data pieces, open Custom screens from the menu (Data) and design Vertical screen and Horizontal screen. Set a Default root data source while designing. Then add Open screen → Custom screen and pass keys such as source or room there. If a key is missing, labels show <room>. To zoom one data piece, add Open screen → Data piece full screen. See Tap actions.

4. Set up tap actions (optional)

If a component should refresh data, ask for input, or send a command, add tap actions on that component — or on the data piece so a tap on the whole card runs them. If the data piece has tap actions turned on, taps do not reach components. A group with tap actions on also keeps the tap from reaching components inside it. See Tap actions.

5. Add data destinations (optional)

For sending an MQTT publish or a WebSocket message, use a reusable destination when several data pieces should share topics or events, or MQTT send / WebSocket send on this component only. For HTTP, use a destination or HTTP request on the component. Destination URL, topics, events, body, and Text to send can include {{ value?.field }} or {{ env.my_key }} when the tap runs.

6. Protect your work

Once the dashboard works the way you want:

See Settings and configuration safety.

The fastest possible first dashboard

To get something on screen with one HTTP API:

  1. Add one section.
  2. Tap Ask AI and ask the assistant to add an HTTP data piece for your URL.
  3. Open the dashboard and check that the value updates.