Page help

Status indicators (top strip)

• Dashboard — this browser tab's live connection to the backend. "Reconnecting" clears itself automatically; no action needed unless it's stuck for a while.
• Server — whether the backend and its database are responding normally.
• Radio mesh — the coordinator's connection to your tally hardware. Manage it from the Setup page.

Devices page

Each card is one device — a physical Tally Transceiver or an external connection — with its Inputs and Outputs listed underneath.

• Dot — on a virtual input, click to toggle it (it's a switch, and it stays where you put it). On outputs and device-owned inputs the dot is hold-to-test: the state is forced only while you hold the mouse down, and releasing puts it straight back to the truth (outputs recompute from their wiring; a device input returns to what the hardware/switcher last reported) — so a manual poke can never leave a tally stuck.
• Name — click to open the full editor: rename, change the logic gate, and wire it to other inputs/outputs. Hover to see a small pencil hint.
• Color swatch — click for a quick preset palette (red/green/ amber/blue/white) or a custom color picker.
• Pencil icon (card header) — device settings: rename, and for external connections, retarget host/port.
• Trash icon (card header) — delete the device, with a styled confirmation. It will re-register itself (unwired) if it contacts the server again.
• Category filter — narrow the page down to Tally, External, or Virtual devices; useful once you have a lot of cards.
• "Firmware vN available" pill — this app ships with the latest Tally Transceiver firmware, and each board reports the version it's running. The pill appears on any board running an older version; the board keeps working as-is (the app never sends it commands it can't understand). Click the pill to update: plug the board into this computer with a USB data cable, pick it from the list, and the app flashes it in about ten seconds — names, wiring and colors live on the server and survive the update untouched.

Device categories

Every device on the Devices page falls into one of three categories:

• Tally — physical radio-mesh hardware (Tally Transceivers) that register themselves automatically over the coordinator's radio link. You don't "add" these — they show up on their own the first time they power on.
• External — software/network integrations you add yourself from the Connections page (vMix, TSL, OBS; eventually ATEM/webhook).
• Virtual — logic points with no physical or external owner, for building intermediate wiring (e.g. a combined "any camera live" signal).

Matrix page

A routing grid: inputs down the side, outputs across the top. Click a cell to wire or unwire that pair. Click a row or column header to open that IO's full editor. Each axis has its own filter — one narrows the rows, the other the columns — so a large matrix dials straight down to the inputs and outputs you care about. The bands are per-device groupings, there to separate things visually.

Connections page

Add a software/network integration — vMix, TSL 3.1, or OBS Studio today, with more planned. Each one becomes a device on the Devices page (in the External category) with its own Inputs pre-created for you to wire up.

Setup page

• Coordinator — a read-only status line for the USB radio that talks to your tally hardware. Which serial port it uses is chosen on the setup screen shown before the app launches; to scan for it again or switch ports, use "Reconfigure Server & Hardware", which restarts the backend and reopens that screen.
• Radio — everything about the radios themselves. Radio network shows the identity of this system's mesh, so two GPI-Psychic systems in one venue stay separate, and opens a pairing window to let a brand-new Tally Transceiver join. Tally firmware updates a transceiver over USB — including a board that has never been set up.
• Security — asks anyone opening the dashboard from another machine for a username and password. This PC is never asked, on or off. You can also let the webhook URLs through without a sign-in, so a Stream Deck or script on another machine keeps working while the gate is on.
• Webhooks — flood protection — every input can be driven by bare on/off/toggle URLs (Stream Deck, Companion, scripts). This setting caps how fast those URLs can change each input; anything faster is merged rather than rejected — the first change applies instantly, in-between states are skipped, and the newest state always lands. Protects the radio link and database from a runaway script without ever dropping a deliberate press. Default: 20 changes/sec per input, plenty for any controller.
• Appearance — light/dark theme.
• Danger zone — bulk, irreversible database cleanup: clearing all virtual inputs/outputs, or unwiring everything at once.