Pairing a light for the first time: why the device list stays empty
Pairing takes about twenty seconds when it works. When it does not, the app gives no error at all — the device list simply stays empty, which looks exactly like a dead light and almost never is.
Key takeaways
- An empty list means the wrong app or a denied Bluetooth permission far more often than a faulty light.
- Most of our controllers hold one phone at a time; close the app on any phone that paired before.
- Pair within a metre or two of the light. Move away only once it is listed.
- Wrong colours after pairing is channel order, fixed in the app under Modify Pin Sequence.
- A factory reset only helps for a lost phone or a swapped module. It does nothing for permissions.
Three checks before you start
Do these first and most "it will not connect" cases never turn into a support ticket.
- Confirm you have the right app. Each of our apps speaks one control protocol, and they are not interchangeable. An app that cannot speak your controller's protocol never lists the device, however long it scans — and that looks identical to a broken light. Check which app your light needs first; this is the single most common cause.
- Make sure no other phone is holding the connection. Most of our controllers accept one connection at a time. A phone that paired before reclaims the light silently whenever it is in range. If anyone else in the house has used the light, close the app on their phone.
- Check the app's Bluetooth permission. Recent Android and iOS versions need a nearby-devices or location permission before an app can scan at all. Denied, the app shows an empty list, not an error. Look in the phone's settings for the app, not inside the app — the table below says where.
Pair within a metre or two of the light. The first handshake is the least tolerant part of the process. Once the light is listed and answers a brightness change, you can move to wherever you normally sit.
What the flow looks like in each app
Each clip is the connection tutorial for that app, taken from its own documentation, and runs about eight seconds. Some apps scan as soon as they open; others have an explicit add-device step.
Which permission the phone is asking for
The empty-list symptom looks the same on every phone. The permission behind it does not.
| Phone | What the app needs | Where to turn it on |
|---|---|---|
| iPhone and iPad | Bluetooth permission for the app, asked once on first launch | Settings > Privacy & Security > Bluetooth > the app |
| Android 12 and later | "Nearby devices" permission | Settings > Apps > the app > Permissions |
| Android 6 to 11 | Location permission, and the phone's location toggle switched on | Settings > Apps > the app > Permissions, plus the Location quick toggle |
If you tapped "Don't Allow" on the first launch, iOS never asks again; you grant it by hand in Settings. On Android 6 to 11 the location requirement comes from the operating system, not from us: the app never reads your position, but the system returns no Bluetooth scan results without it. Android 12 replaced that rule with the separate nearby-devices permission. On every version the symptom from inside the app is the same — a scan that runs and finds nothing.
Reading the failure
| What happens | What it usually means |
|---|---|
| Device list stays completely empty | Wrong app, or Bluetooth permission denied. Check both before anything else. |
| Light appears, then vanishes from the list | Another phone claimed it mid-scan, or it is at the edge of range. |
| Connects, then drops after a few seconds | Competing connection, or distance. Test standing next to the light. |
| Connects but nothing responds | Connection is fine; the controller is not driving the strip. Check the connector between controller and light. |
| Responds to brightness but colours are wrong | Pairing is fine — this is channel order. Fix it in the app. |
| Several identical names in the list | Multiple controllers in range. Power down all but the one you want, or connect and rename each in turn. |
| Connects fine most days, occasionally fails near the kitchen | 2.4GHz interference, often a running microwave. Retry after it finishes, or move closer to the light while connecting. |
| App shows a device that no longer exists | Leftover entry from a swapped or removed controller. Remove it from the app's device list, or factory reset the module if the app cannot remove it. |
Why the first connection is more sensitive than a headphone's
Headphones pair once and reconnect for months, which sets the expectation. A lighting controller mostly behaves the same way after pairing. The first handshake is harder: the app has to discover which channels and effects the controller exposes before it can drive any of them, and that exchange has less margin than a plain audio link.
Bluetooth Low Energy also shares the 2.4GHz band with Wi-Fi and, in a kitchen, with a running microwave oven. Its advertising packets are short and easy to lose in that noise. The symptom is a light that pairs fine most days and needs a second attempt while the microwave runs, or in a room where a dozen other Bluetooth accessories are already connected. None of that is a fault in the light. Standing next to it while pairing gives the handshake far more margin, which is the whole reason for the note above.
Mesh apps add a step, on purpose
With the Bluetooth apps you connect to a light and control it. With iMeshting you also say what kind of device you are adding and which room it belongs to, and only then does it appear as something you can control.
For one light that is extra work. It pays off at the fourth or fifth fixture, when "all the lights in the living room" becomes one action instead of five connections to manage. If the installation will grow — a ceiling fan light plus the strips around it, say — assign rooms from the first fixture rather than re-adding everything later. Why fan lights run on mesh explains what the room group buys you.
Factory reset: when it is the right move
A factory reset clears the controller's stored pairing entirely. It helps in two situations:
- The phone that paired the light is lost, sold, or no longer around to unpair it. The light otherwise keeps holding a connection slot for a device that will never release it.
- A control module was moved between fixtures or swapped under warranty, and the app still shows the old entry pointing at hardware that no longer matches it.
It does not help with a permission problem, a wrong-app problem, or a light at the edge of range. Resetting a light that was never the cause adds a second problem on top of the first.
Most of our controllers reset on a power-cycle pattern — off, on, off, on, in quick succession — rather than a button, because the module has no exposed switch once it is installed. The exact pattern varies by fixture. In a multi-light installation the wrong pattern on the wrong circuit resets a light you did not mean to touch, so ask us for the one that matches yours.
Two settings to visit once it is paired
Both live in the settings pop-up rather than on the main control screen, which is why they get missed. Do them before you mount anything.
- Pixels, on addressable lighting — how many addressable points are on the strip. Set too low, an effect runs along the first section only instead of spreading across the whole run.
- Modify Pin Sequence, if the colours come out wrong — remaps the channel order in software instead of rewiring. Walkthrough here.
Why other systems pair differently
The empty-list problem above comes from a design choice: Bluetooth is the control channel itself, so there is no second step. The mainstream systems each add one.
| System | First connection | What happens next | Where people get stuck |
|---|---|---|---|
| Philips Hue | Bluetooth direct, up to 10 lights per phone at about 10 m; or Zigbee through the Hue Bridge, up to 50 lights | Bluetooth mode has no automation or remote access; the Bridge adds both | The eleventh light means buying the Bridge |
| Govee | Bluetooth first; the app then hands the device your 2.4 GHz Wi-Fi password | The device talks to Govee's cloud from then on, under a Govee account | Combined 2.4 and 5 GHz networks: Govee's own guidance is to split the bands and use WPA2; a device "stuck in Bluetooth mode" is deleted and added again |
| Matter | The device advertises over Bluetooth; you scan the QR code or type the 11-digit code | A Matter controller (HomePod, Nest, Echo, Home Assistant) and Wi-Fi or Thread are required | Rejected setup codes are common enough to have their own troubleshooting pages |
| Ours | Bluetooth direct, within 1–2 m, one phone at a time | Bluetooth stays the control channel: no router step, no account | The wrong app (empty list), a permission, or the previous phone still connected |
The practical consequence is that none of the 2.4 GHz, 5 GHz or WPA3 problems in the table can happen here, and there is nothing to add again after a router change. The trade is range: control is Bluetooth range, not the internet, and what offline gives up covers what that means for scenes across a house.
Sources: Philips Hue FAQ, connecting without a Bridge; Govee, connection FAQs; Connectivity Standards Alliance, Matter FAQ.
Still not connecting?
Tell us which app you are using, whether the light appears in the list at all, and what happens when you change brightness. Those three answers narrow it down immediately. Questions about a specific controller of ours? Contact us.