WearDash turns one YAML file into glanceable dashboards and watch tiles: buttons, sliders, live graphs and camera snapshots, wired to Home Assistant, Android TV or any REST API.
Apple Watch - coming soon
How it works
One install on the watch. After that, changes reach it without a cable.
Wear OS 3 or later. The app is standalone: nothing to install on the phone.

The watch shows a one-time code. Type it here and pick a config. Nothing to type on the watch.
Drag & drop blocks onto a live watch preview, or start from a ready-made config: TV remote, Home Assistant, weather. YAML stays available.
Each publish creates a version. Secrets are entered on the web and end-to-end encrypted; our servers only see ciphertext.
Connectors
Three connectors at launch, mixable in a single dashboard.
Native remote protocol: d-pad, apps and voice search straight from the watch. Pairs like the official remote.
works with Shield, Chromecast, Sony, TCL…Point at an entity, call a service: one line per source, one line per action. The shorthand keeps the YAML short.
entity: fan.living_roomTemplated URLs, headers and bodies against anything that speaks HTTP, behind a self-signed cert, a private CA or mutual TLS. Secrets stay out of the config.
Authorization: Bearer {{secrets.token}}Features
Build screens by drag & drop on a round watch preview, from example screens and blocks. No YAML required; the code view stays one click away.
Any screen becomes a tile, one swipe from the watch face, sliders and graphs included.
Show, hide and recolor components from live state, like conditional cards on your wrist.
Set a fan speed by dragging, read a 24-hour temperature curve drawn on the watch.
Doorbell or entrance cam, refreshed on a schedule; tap to reload.
The last config is cached on the watch, so it stays usable without network.
Speak into the watch and the recording is posted to the endpoint you choose, Whisper or n8n or your own. A separate mic drives Android TV search.
Wear OS cannot install a certificate authority, so WearDash handles TLS per host: a self-signed cert to trust once, a private CA, or a client certificate for mutual TLS.

actions: tv_left: { type: atv, key: DPAD_LEFT } tv_ok: { type: atv, key: DPAD_CENTER } tv_right: { type: atv, key: DPAD_RIGHT } screens: - id: remote label: TV root: type: column children: - type: row children: - { type: button, label: "◀", action: tv_left, size: 38 } - { type: button, label: "OK", action: tv_ok, size: 38 } - { type: button, label: "▶", action: tv_right, size: 38 }
The editor
Every block you drop renders on a round watch preview, including the tile view, since tiles don’t scroll.
The visual editor reads and writes one YAML file. The code view is one click away: copy it, diff it, keep it in git.
Tokens are typed on the web and end-to-end encrypted with a key derived from the pairing code. Our servers cannot read them.
Three ready-made configs: Android TV remote, Home Assistant home, full demo.
On the watch
Your screens, one list
Arc, slider, live state
Pairing in one short code$ git clone https://github.com/weardash/selfhost $ docker compose up -d # → https://your-server:3001 # pairing relay + YAML editor, in memory only
Open source
The watch pairs through your server. Configs and secrets are end-to-end encrypted either way; self-hosting removes even the encrypted transit.
A YAML editor with the exact rules of this one: errors block sending, warnings flag likely mistakes. The JSON Schema ships with it.
One command: docker compose up -d. The relay runs in memory, so nothing is stored and nothing needs backing up.
Pricing
No subscription: Premium is a one-time unlock on Google Play.
One purchase, from the watch.
Install the app, link the watch with a short code, then compose in the editor.