Connect controls straight to protocols you already run — an MQTT broker or a plain HTTP API — with no MeshSocket bridge and zero server code, or to an on-device local store (Local Store) with no network at all. MeshSocket stays the power path (dynamic content, rooms, E2EE, readback); sources are the zero-setup path.
Symbol
point.3.connected.trianglepath.dotted
Docs
Docs complete
Fields
8 fields, each with what it does.
Fields
Field
Type
Default
What it does
typetype
choiceone of 3
—
What kind of source this is
Picks whether the source talks to an MQTT broker, an HTTP API or the on-device local store.
mqtta broker the phone subscribes to and publishes on
httpan API the phone polls and sends requests to
locala database stored on the phone with no network
urlurl
text
—
The broker address
Sets where the phone dials the MQTT broker; mqtt:// is plain and mqtts:// is encrypted.
baseURLbaseURL
text
—
The web address paths start from
Sets the address that relative sync and action paths of an HTTP source are added to.
usernameusername
text
—
The broker login name
Sends this username when the phone connects to the MQTT broker.
passwordpassword
text
—
The broker password
Sends this password to the MQTT broker, filled in from the Keychain when you write a secret placeholder.
clientIdclientId
text
—
The name the phone gives the broker
Sets the MQTT client id; a random one is made when it is left out.
headersheaders
object
—
Extra info sent with web requests
Adds these HTTP headers to every poll and request of the source, such as an Authorization header.
intervalinterval
number1–3600step 1
5
How often to check
Sets the seconds between polls for HTTP syncs that do not set their own, 1 to 3600.
Examples
3 examples, each one a control you can paste into a layout.
A layout declares named sources at the top level; controls bind them through the
same standardized connection block (Sync / Toggle expand) they use for
MeshSocket. Every control's inputs and outputs are transport-independent: what a
Unit accepts or a Border thickness emits is defined by the control, and method
just picks the wire.
Credentials go in as {{secret:name}} placeholders, not literal values: the
phone fills them in from its Keychain when it dials the broker or sends the
request, and the JSON never carries them. By default a secret may only be sent
to the hosts of the layout's declared sources; secrets[].hosts changes that
for one secret. See Secrets.
When a layout has exactly one source of a kind, sync/action entries may omit
source — it resolves automatically. With several, name the one you mean.
MQTT
Subscribe a topic and bind the payload — the entire connection block of the
control is:
Payloads parse naturally: JSON objects work with filter/valuePath
exactly like MeshSocket frames; bare 23.5 / true / ON payloads become
number / bool / string values directly (leave valuePath empty).
String payloads publish raw bytes (ON, not "ON"); objects publish as JSON.
mqtt:// is plain TCP (default port 1883), mqtts:// is TLS (default 8883).
QoS 0 publish; inbound QoS 1 is acknowledged. The client auto-reconnects with
backoff and reports state to the connection console.
HTTP polling
Poll any JSON endpoint on an interval and extract a value:
url (absolute) or path (against the source's baseURL).
Controls polling the same URL at the same interval share one request — a
page of gauges over one status endpoint costs one poll.
The response body is JSON; filter and valuePath behave exactly as in
Sync. Special receivers work too: point a Card padding at an array endpoint,
a Title at a numeric one.
A layout may use MeshSocket, MQTT, HTTP, and Sensors together — each sync
entry picks its own method. A control with several sync entries takes whichever
delivered last.
What the header shows
The connection dot in the header stands for the layout's MeshSocket relay link.
A layout that pulls through sources gets one extra glyph beside the dot per
pipe — a poll cycle (↻) for each HTTP host, a fan-out mark for each MQTT
broker — each in its own health color: yellow while the first poll or the
broker dial is in flight, green once data is arriving, red after a failed poll
or a dropped session, grey for a source nothing is bound to. A layout with no
relay at all takes the pipes' aggregate color for the dot instead of the idle
grey, so an HTTP-fed dashboard never reads as "Not connected". Tapping the dot
or a glyph opens the connection hub, whose Data Pipes box lists every pipe
with its host, cadence or topic count, and state.
Notes
Sources live and die with the layout: leaving it disconnects the broker and
stops all polling.
MQTT needs a declared source (the broker address); HTTP syncs with an absolute
url work with no sources block at all.
Diagnostics (connects, failures, reconnects) land in the connection console
like MeshSocket's.
A request that needs a secret the phone does not have, or may not send to
that host, is not sent; the pipe shows needs secret <name> or
secret <name> not allowed for host <h> (Secrets).
Local store
"type": "local" declares an on-device database instead of an external endpoint:
typed collections of records the layout's controls read with sync and write
with action, no server or network involved. The keys (namespace,
collections, views, weekStartsOn), the field types, the JSON query stages,
the tokens and the write ops are all documented in Local Store.
A local source appears in the header's Data Pipes as Local; it is grey until a
control binds it, green while serving, and red with the reason after a schema or
write error.