Restore 22 pages + 23 images deleted by mistake in 3b9277a (2026-07-30)
Commit 3b9277a ("Binary ops: one format, no version framing") was pushed from
an incomplete working copy of the wiki: alongside its intended 11-line edit to
Canvas-Ops-Reference.md it recorded deletions of every page not in that copy --
22 pages (Home, Quick-Start, Provisioning, Calibration, FAQ, Hardware, ...) and
23 screenshots. _Sidebar.md still linked all of them, so 22 of 28 nav links 404'd.
Restored verbatim from 3b9277a's parent. Additions only; the 8 pages that
evolved since 2026-07-30 are left at their current content.
Binary ops: one format, no version framing
Accuracy sweep: twelve MCP tools (FAQ), no armv7 image (Home Assistant), settings mirror is local-primary (Multiple Displays), caps field is named_colors not named_colours (Writing Apps, Compatibility), HTTP frame-push is ~40 fps since fw 3.0.1 (Writing Apps)
Docs update for companion 2.9.x: quiz app type, channels/quizzes on the Matrix panel (canvas_art + Show on Matrix toggle), new apps (Stock Graph, Movie Quotes, Weather Panel, Scoreboard, HA Dashboard, Aquarium), firmware 3.1 delta frames + named atlases, smart-refresh cadence; new panel screenshots
mDNS names carry the board id: splitflap-gw-xxxxxx.local
Firmware 3.11 gives the SplitFlap Gateway the suffixed hostname the
Matrix Gateway always had (plain splitflap-gw collides the moment a
second gateway joins the LAN). Every page that named the old address
now shows the suffixed form and says where to find yours: the boot log
and the router's device list.
Two gateways, two names — plus Provisioning and Calibration get their own pages
SplitFlap Gateway drives real modules; Matrix Gateway draws a simulated
wall on an LED matrix. The Gateway and Matrix-Portal-Gateway pages are
renamed (redirect stubs left at the old names), 21 pages re-worded, and
both diagrams regenerated with the new labels — the configurations
diagram also aligns all seven Modules boxes on one row.
New: Module provisioning (the full process — the SplitFlap Gateway's
Provision tab and bare-metal provision.py in detail, splitflap-os's
built-in equivalent acknowledged without detail) and Module calibration
(the CALIBRATION_GUIDE ported: the three quantities, the golden order,
nudge vs exact offset, per-flap tuning, the wizard and whole-board pass,
the control reference). Linked from the sidebar's Build-it section,
Home, Module-Firmware and the SplitFlap Gateway tab tour.
The companion has its own app library — the csader relationship, stated honestly
The ecosystem graphic claimed the companion 'runs the splitflap-os app
library (csader)'; it ships its OWN library and speaks the splitflap-os
plugin format. Regenerated, and the framing aligned across the wiki:
splitflap-os is an acknowledged alternative content engine (A/B/E/F);
apps written for it drop in and run here — that inbound direction stays
a hard contract; apps written here MAY run there, without the injected
helpers and unoptimized, with no guarantees. Compatibility's goal
paragraph now says exactly that.
Also: Writing-Apps documents the grown get_weather surface (sky tokens,
days=N forecast + hourly, air=True with labels and canonical bands), and
Built-in Apps gains the countdown's per-unit colour-bar panel and the
weather app's forecast/AQI/UV/pollen in their rows.
Wiki: correct the splitflap-os feature grid; give Vestaboard + MCP their own pages
Feature grid — I built it from splitflap-os's README, which undersells it. Rebuilt
from the code (csader/splitflap-os main, with feat/app-triggers, feat/schedules and
feature/custom-char-map all merged in):
- Event triggers, schedules and quiet hours: splitflap-os HAS these. Was "—", now ✅
for every splitflap-os configuration.
- Flap sets: splitflap-os reads each module's flap count and character set from the
firmware and encodes against them, so a non-64 reel works — but it can't *write*
one. Split the row into "custom character set" and "flap count other than 64", both
✅ (web UI) only where the Universal Firmware meets the gateway, ⚠️ for sfOS.
- REST API: it has Flask endpoints for its own UI but no documented API. Now ⚠️.
- Localization: verified against upstream main — no language/locale settings there.
Left as "—" with a footnote saying so; i18n exists in forks.
Vestaboard + MCP are companion features, not Home Assistant features. They now have
their own pages, and the HA page links to them instead of owning them:
- Vestaboard-API: enabling it, the endpoints (GET returns {"message": [[…]]}, POST
201, 401 is plain text), the {"text": …} extension, ha-vestaboard and rest_command.
- MCP-Server: the eleven tools, why read-before-write matters, connecting Claude Code
and Desktop, and worked examples of what you can ask for.
Both are linked from the Companion's new "Ways to drive it from outside" section.
Wiki: flaps & character sets page, WiFi/mDNS setup, HA install steps, real screenshots
- New page "Flaps & Character Sets": the N command, the 64-flap budget, and
validated 64-flap starter sets for 12 locales (each exactly 64 unique CP1252
glyphs) — framed as a suggestion, not a prescription. Linked from the sidebar,
the Home TOC, the feature grid, Module Firmware and the Companion's
localization section.
- Gateway: full first-boot WiFi flow via the fallback AP, and a "Finding it on
your network" section — mDNS is best-effort, so document finding the IP from
the router/serial and using that everywhere (incl. GATEWAY_URL). Same for the
Matrix Portal, whose AP is named after its hostname.
- Home Assistant: step-by-step install for both the App (repository URL, the two
channels, gateway_url, sidebar) and the HACS integration (custom repository of
type Integration, restart, config flow against the *companion's* URL), plus a
full options table. Mirrored as a condensed step 6 in the Quick Start.
- Correct the calibration-compatibility claim: the gateway's Calibration tab
issues only original-protocol commands (c o s t g w h d) against
original-layout EEPROM fields, so it works fully on the original firmware. The
only version gate in the gateway UI is the flap-set editor (v31+).
- Swap the mocked-up screenshots for real ones rendered from the actual UIs with
fake data; drop ha-device.png; de-boastify a few lines; fix four dead anchors.
Hardware: modules mount on a DIN rail with pogo-pin contacts, not point-to-point wiring
The bus description said the modules were daisy-chained with a two-wire pair. In Adam's
design there is no wiring between modules at all: each clips onto a DIN rail, and four pogo
pins on its underside contact a conductor rail carrying 12 V, GND and the two RS-485
signals — mounting a module is connecting it. Fixed in Hardware (prose, diagram, module
parts list, what-you-need table), Quick Start, and the FAQ glossary.
Comprehensive combined wiki for the whole SplitFlap ecosystem
Ties together all the projects — hardware (Adam G Makes), Universal Firmware, Gateway,
Matrix Portal Gateway, Companion (+ HA add-on and HACS integration), and splitflap-os — into
one guided flow from parts to a message on the wall, with optional steps clearly marked.
Pages: Home (ecosystem + TOC), Quick Start (end-to-end, two paths), Hardware, Module
Firmware, Gateway, Matrix Portal Gateway, Companion, Home Assistant (five surfaces), Using
splitflap-os, FAQ & Glossary, plus a sidebar. Includes made-up-data UI mockups (ecosystem
diagram, companion Apps tab, gateway Modules tab, HA device).