Setup wizard — the five steps

Welcome → USB flash → Fleet join → Zigbee → Go live. What each step checks and what 'debt' means.

Before you start: the Pi has booted and the dashboard answers (Flash the SD image and first boot), and you have the kit card, the kit devices and a USB data cable to hand. The wizard lives at #/setup. It remembers which step you are on, so you can close the browser and come back. Once the kit is commissioned, or once the hub or a probe has reported to this brain, the wizard parks itself: #/setup then shows Kit already commissioned (or Kit is live) and only Open Overview. Settings › System › Kit setup shows the phase, the commissioned state and any flash debt.

Shows how you are connected (Ethernet / LAN or Pi SoftAP) and lists the addresses the dashboard is reachable at. Two honesty notes are on this screen:

• The Pi hotspot is only for reaching the wizard. The hub's DSC-Setup-* hotspot is a separate fleet network.
• Ethernet later enables full update pulls; an offline bring-up is still a valid bring-up.

With the site profile on (it is by default in 9.8.9), this step also shows a card headed Where is the kit?: the site profile and the Getting started guide. The guide has five steps in order: Site, Spaces, Devices, Prove and Plants. Every count is read from the kit and nothing is assumed; a source that did not answer reads not known, never zero or complete. A step you skip stays open and is named, never hidden. Prove records whether a device showed a real reaction; a device that did not is saved as unproven, never as working. The same guide sits in Settings › System › Site profile.

Press Next: USB flash.

Flashes the baked firmware onto each kit device over a USB cable plugged into the Pi. One device at a time. The screen never turns green on a failure. The full steps, boot-mode tips and the fallback paths are on Flashing devices over USB. For a Sonoff plug, read the mains safety note there first: never open a plug while it is connected to mains.

1. Pick the Role (hub, control, pot1, pot2, then the Sonoffs). A role greyed out shows the reason instead of its size (for example missing or zero-byte file): the brain has no usable binary for it.
2. Plug the device into the Pi with a data cable and pick its Port. The list shows the USB chip when it can tell.
3. Press Flash. Watch the log; it ends with OK or FAILED and the reason.
4. Repeat for every device, then Next: Fleet join.

Skip (record debt) lets you move on without flashing a device. The skipped role is written to the kit's setup debt and shown again on Go live and on Settings › System › Kit setup until it is cleared.

The devices now need a network. The wizard lists the order:

1. Power the hub. A hub built for the Pi kit joins the Pi's own Wi-Fi network, DSC-Brain-XXXX (XXXX is unique to your card; setup shows the full name. Cards made before 9.9.0 use DSC-Brain), by itself. Only if it opens a DSC-Setup-XXXX hotspot (the factory setup portal, which is parked) follow Fleet Wi-Fi join.
2. Power the panel and the probes; they find the hub, register, and reboot onto the chosen network.
3. The Sonoff plugs join the Pi's own DSC-Brain-XXXX Wi-Fi network, using the name and password compiled into their firmware, so the Pi's hotspot must be running. They do not use your home Wi-Fi. A plug that cannot join opens its own DSC-<name> Fallback Hotspot.
4. The screen also lists the ETH01 bridge. The bridge is retired from the kit and not offered in USB flash; skip that line.

Press Next: Zigbee.

Reports whether the Zigbee radio is up or down / not detected. If SkyConnect is not plugged in it says so and shows no fake devices. Pairing and role binding happen under Settings › Devices › Zigbee (the Open Device settings button); the steps are on Zigbee, pairing and binding roles. You can bind sensors later, but Go live checks the radio: commissioning is refused while it is down.

A health list: brain, Mosquitto (the internal message bus), Zigbee radio, hub online, catalog (always the thin local copy, never blocking). Any setup debt is listed. Press Commission kit. The brain refuses, and the screen shows why, if the brain, Mosquitto or the Zigbee radio is not OK (a radio whose state is unknown counts as not OK), or if the hub is offline and its flash was not skipped. Otherwise it records the kit as commissioned, the dashboard opens Overview, and the wizard parks.

• Overview should show the hub heartbeat and the two tents.
• Kit › Inventory shows each device online and In service.
• If a device is missing, see Adding, replacing and retiring devices, Troubleshooting › Hub offline or not reporting or Probe dark or faulted.

Next: work through the steps above. Step 2 uses Flashing devices over USB, step 3 uses Fleet Wi-Fi join and step 4 uses Zigbee pairing; come back here for step 5, Go live. Once the kit is commissioned, continue with Tuya devices, cameras or the dashboard guide.

Guide contents  ·  Setup  ·  Troubleshooting  ·  Digital Stealth Care

DSC-Brain user guide · Setup wizard — the five steps · this page is edited on the site; the Notion original was retired after the mirror