DSC-BRAIN USER GUIDE · TROUBLESHOOTING
Cannot reach the dashboard
Address checks, hotspot vs LAN, .local resolution, the two-minute restart window, and SSH checks.
Do this first: wait (five minutes after a first boot, two after a restart), then open the address for your network from the table below and reload. It worked when the dashboard opens on the Overview desk. If not, go to Still nothing.
● verified for 9.0.0 · firmware train 8.2.0.0
● first mirrored 2026-09-15
Check the address
| You are on | Try |
|---|---|
| Home LAN, Pi on Ethernet | dsc-brain-XXXX.local:8787 (the .local name on the kit card with :8787; cards made before 9.9.0 use dsc-brain.local), then the Pi's LAN IP with :8787 (find it on your router). Android phones often can't open .local names; use the IP address your router shows for the Pi instead |
| The Pi hotspot | The hotspot dashboard address printed on the kit card, or 10.42.0.1 |
Some phones refuse .local names or fall back to mobile data on a hotspot with no internet. Use the IP form and turn mobile data off. The services and ports a kit uses are listed in Addresses, ports and services.
Timing
- A fresh card needs 3–5 minutes on first boot.
- Every brain restart (an update, a deploy) drops the hotspot briefly; fleet devices rejoin within about two minutes. Wait, then reload.
Still nothing
- Ethernet link light on the Pi? Power light steady?
- Over SSH (user
dsc):curl -s http://127.0.0.1:8787/healthshould answer. If not:docker psshould listdsc-hub-brain;docker logs --tail 100 dsc-hub-brainshows why it is not up. - If the container is up but the page is blank, hard-reload the browser (Ctrl+Shift+R); a stale bundle after an update is the usual cause.
The ESPHome dashboard instead
Port 6052 on the same host is a separate service; it answering while 8787 does not means the brain container is the problem, not the Pi.
DSC-Brain user guide · Cannot reach the dashboard · this page is edited on the site; the Notion original was retired after the mirror
