Software › Busy Display › Support
Busy Display Support
Busy Display turns your Mac into a status sign — an “in session”, “on air” or “do not disturb” display that anyone on your network can see and control from a browser. It runs entirely on your local network.
Getting started
- Open Busy Display on the Mac that will host the display
- Allow the Local Network permission prompt when macOS asks
- Scan the on-screen QR code, or enter the shown IP:port in any browser on the same network
- [Set your statuses and appearance in — name the screen]
- [Optional: connect a MIDI device or configure a webhook]
Frequently asked questions
How do I open the display on another device?
Busy Display runs a small web server on your Mac. Any phone, tablet or computer on the same local network can open it in a browser — no app to install on the second device. Scan the QR code shown in the app, or type the IP:port it displays straight into a browser address bar.
The browser can’t reach it — what should I check?
In rough order of likelihood:
- Same network? Phones often sit on a guest SSID while the Mac is on the main one. Guest networks almost always block device-to-device traffic.
- Client isolation. Many access points and hotel/office Wi-Fi enable AP isolation by default, which blocks clients from seeing each other even on the same SSID.
- Different VLAN or subnet. If wired and wireless are separated, traffic won’t route between them without a rule.
- Local Network permission. macOS may prompt the first time — check System Settings → Privacy & Security → Local Network and confirm Busy Display is allowed.
- macOS firewall. System Settings → Network → Firewall — allow incoming connections for Busy Display.
- Mac asleep. The server stops when the Mac sleeps. [Confirm your recommended setting — e.g. Prevent automatic sleeping when the display is off.]
- IP changed. DHCP may hand out a new address after a reboot. Re-check the QR code, or give the Mac a static/reserved IP.
Can I reach it from outside my network, or over the internet?
No — and that’s deliberate. Busy Display listens on your local network only and has no cloud component. Please don’t port-forward it to the internet: the app has no authentication, because it’s designed for a trusted network.
Why is there no password?
Busy Display is built for personal, home and studio use on a network you control. Anyone who can already reach your LAN can change the status. Keep it off guest and public Wi-Fi, and don’t expose it through a router. If you need it on a shared or untrusted network, put it on its own VLAN.
How do I trigger a status change from MIDI?
MIDI input is optional and processed entirely on your Mac. [Describe the setup: which screen to open, how to select the MIDI device, and how notes or CC messages map to statuses.] Useful for driving the sign straight from a console, control surface or DAW so the status follows the session rather than needing a separate action.
How do webhooks work?
Busy Display can accept plain HTTP requests from other devices on your local network, so you can drive it from automation you already run — Home Assistant, Shortcuts, a Stream Deck, or a script. [Give the endpoint format, e.g. http://IP:PORT/[path], which HTTP methods are accepted, and the available status values.] Nothing is logged or forwarded anywhere.
What is the QR code for?
Convenience only. It encodes the local address of the server (IP:port) so you can point a phone camera at the Mac’s screen instead of typing an address. It carries no tracking or analytics.
Does it need an internet connection?
No. Everything happens on your local network. [Confirm: App Store purchase validation happens locally through Apple’s APIs, so no connection is needed after installation.]
Where is my data stored?
On your Mac. Busy Display has no accounts, no cloud sync and no analytics, and it doesn’t transmit anything outside your local network. See the privacy policy for the full detail.
Reporting a problem
Network issues are much faster to solve with the details. Please include:
- Busy Display version and your macOS version
- Mac model, and whether it is on Wi-Fi or Ethernet
- What the controlling device is, and how it connects
- Whether the Mac and the device are on the same SSID / VLAN / subnet
- Whether it has ever worked, or never worked
- The exact IP:port shown in the app, and what the browser reports
Response time: normally within one working day (Mon–Fri, CET). Support languages: English, Polish, Spanish.