Core concepts
Routix Dash is built from a handful of ideas. Once you know them, everything else in this guide makes sense.
| Concept | What it is |
|---|---|
| Data source | Where data comes in — an HTTP source with an Actions / Transformers pipe, an HTTP stream that stays open, a Video source for a camera, an MQTT subscription, a WebSocket/SSE feed, or a Timer source. |
| Connection | A shared MQTT or WebSocket link that one or more sources or destinations can reuse. |
| Data section | One screen of your dashboard — you swipe between sections. |
| Data piece | One cell in the dashboard grid: one or more components. Optional root data source; components inherit it unless you pick another. You can group components so they move and scale together. Save a group to Grouped from the data piece editor to reuse it on other data pieces. Your saved groups can be renamed, edited, exported, or deleted; built-in groups cannot. Plus in the data piece editor opens the library on Components. Save to library on a data piece keeps the whole data piece under Data pieces, so Add data piece can reuse it. |
| Transformer | Something that reshapes data as it moves along — JSONPath, Simple expression, Lua, or JavaScript. |
| Data destination | Where data goes out — an HTTP request, an MQTT publish, or a WebSocket message. |
| Tap action | Something that runs when you tap a data piece or a component — refresh, send HTTP / MQTT / WebSocket, trigger a destination, ask you something, open a link, and so on. If the data piece has tap actions turned on, the tap runs those and does not reach components. |
| ENV variable | Reusable text you store once — a host, a token, a shared string — and insert as env.my_key. See ENV variables. |
Data sources, data destinations, connections, data sections, data pieces, custom screens, custom bottom sheets, and components each have a Data setting for your own notes or data. See Components.
One source, many data pieces
A single data source can power many data pieces, across different sections. Set it as the data piece root source so every component starts from it; override the source on a component when that component needs different data.
Three places for transformers
A chain of transformers can run in three places:
- On the source — cleans up the data once, before it's stored.
- On the data piece — reshapes the root source value for this data piece. Components with Inherited on and the same source start from this result. The data piece has no Inherited switch.
- On a component — shapes the display for that one component when Inherited is off.
See Data transformers and Incoming data flow. In transformer and tap action lists, swipe a row right to left to delete it.
Errors follow the same path as data
A network error enters the source's transformers as ctx.error. The source's Lua transformer can clear it for every component using that source; after that, each component gets its own copy, and that component's Lua can clear it only for itself. Connection health stays on the status dot and in the connection log.
A transformer that throws an error is a different thing — it stops the rest of that chain of transformers.
Connections are shared
MQTT and WebSocket connections (broker or device address, TLS, login) are set up once and reused by multiple sources and destinations. Routix Dash keeps a connection open for as long as anything still needs it.
Your configuration lives on your device first
Your whole setup — sections, data pieces, sources, destinations, connections, transformers, tap actions, and variables — is saved on your device, encrypted. Export and named snapshots need Pro. The last good configuration is backed up automatically. See Settings and configuration safety.