Dev Kit Setup
Your kit arrives assembled, tested, and already flashed. From the box to your own words glowing on the panel is about five minutes, and everything happens in your browser — no app, no account, no cloud.
Step 1 — Power it on
Plug the panel into the included 5V USB-C supply. The panel announces its setup hotspot: JOIN ME → DEVMATRIX-XXXX (the Xs come from your board's serial).
Step 2 — Join the setup hotspot
- On your phone, join the DEVMATRIX-XXXX Wi-Fi network the panel is showing.
- A setup page opens by itself. If it doesn't, browse to 192.168.4.1.
- The page scans and lists your networks live. Pick your 2.4 GHz network, type the password, and watch it join in real time — no blind reboot-and-hope.
Step 3 — Open the Console
After joining, the panel itself shows the last step: WIFI CONNECTED · LAST STEP: OPEN DMX-XXXX.LOCAL IN YOUR BROWSER. Open that address — it's the Console, served by the device itself: live status, apps, a 64×32 paint canvas, brightness, updates, and settings. The phone that ran setup is already signed in.
Step 4 — Your first app, 30 seconds
Console → Apps → Messages → type your words → PUT IT ON THE PANEL. They're saved, enabled, and showing. From the same page you can turn on flights from your own ADS-B receiver, install live weather layouts, or run 1,000+ community Pixlet apps.
Step 5 — Pair your other browsers
On any other phone or laptop, open the panel's address and tap Pair. The panel shows a 6-digit code; type it into that browser and it's in. Reading the panel is the proof it's your device — nothing to write down, and a lost browser never means starting over.
Step 6 — Updates, and the floor under everything
Firmware updates upload from the Console's Deploy page and install over the air — the previous version stays in a second slot on the board. If an experiment ever goes truly sideways, double-press the board's reset button and it mounts as a USB drive you can drag known-good firmware onto. There is always a way back.
Going deeper — your device, my docs
The panel serves its own quick guide (Console → Guide), so the instructions survive an internet outage. The complete owner's manual — recovery and re-flash to default, MQTT and Home Assistant details, and the REST API — is right here: flighttrackerled.com/devkit/manual. Building the open firmware yourself lives with the source: request source access.
This is a self-serve developer product by design: the setup guide, the built-in Guide, and the manual are the support. I add real support capacity only if demand requires it.