Finding your Luma
Every Luma serves its full control page over your own network — the app is convenient, but a browser is always enough. These are the addresses a Luma actually answers to.
The addresses
| Address | When it works |
|---|---|
luma-<system>.local | The friendly address of your Main — e.g. luma-hilltop.localfor a system named “hilltop”. This is the one to bookmark. |
luma-<system>-<name>.local | A satellite’s friendly address — system name plus its display name, e.g. luma-hilltop-kitchen.local. |
Luma-XXXXXXXX.local | The permanent hardware address every device publishes, set up or not. The dashboard’s “Reach this Luma at” chip shows yours, with a copy button. |
luma-setup.local | Only while a device is mid-setup. |
| The raw IP address | Always. Shown on the app’s Devices screen and in your router’s client list — the fallback when name lookup fails. |
In the app
The app finds devices by Bonjour and remembers them afterwards. Two things gate that on iOS:
- Local Network permission. iOS asks once; if it was declined, the app can see nothing. The app detects this and offers to open Settings.
- Same network. Your phone must be on the same Wi-Fi as the Luma — not cellular, not a guest network that isolates devices from each other.
There’s also a manual-address field on the connect screen for networks where discovery is blocked — paste the IP or any address from the table above.
When discovery fails
- Wait a minute. After a Wi-Fi blip the device re-announces itself on reconnect and again every 60 seconds — a missing device often reappears on its own.
- Scans are slow by nature. Network discovery on small devices commonly misses the first ask; Luma deliberately asks twice. Expect a scan to take a few seconds, not an instant.
- Fall back to the IP.Your router’s device list always has it. Consider a DHCP reservation if your router reshuffles addresses often.
More symptom-by-symptom help lives in Troubleshooting.