Pairing a light for the first time
Pairing takes about twenty seconds when it works. When it does not, it almost never gives you a useful error — the device list simply stays empty. This page covers what to check first, and shows the actual flow for each of our five main apps.
Three checks before you start
Doing these first turns most "it will not connect" situations into a non-event.
- Confirm you have the right app. Our apps each speak a particular control protocol and they are not interchangeable. An app that cannot speak your controller's protocol will never list your device, no matter how long you scan — 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, and a phone that has paired before will reclaim 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 require nearby-devices or location permission to scan at all. Denied, the app shows an empty list rather than an error. Look in your phone's app settings, not in the app.
Pair with the phone close to the light — within a metre or two. You can move away once the connection is established, but the initial handshake is the least tolerant part of the process.
What the flow looks like
Each of these is the connection tutorial for that app, taken from its own documentation. They run about eight seconds. Different apps present the step differently: some scan automatically when you open them, others have an explicit add-device step.
Why the connection is more sensitive than other Bluetooth devices
Bluetooth headphones and speakers pair once and then reconnect automatically for months without drama, which sets an expectation that a light should behave the same way. It mostly does, once paired — but the initial handshake for a lighting controller is more exacting than a headphone's, because it has to establish not just a link but the specific service and characteristic structure the app uses to address individual channels and effects. That extra negotiation is what makes the first connection the fragile moment, rather than day-to-day use.
Bluetooth Low Energy shares the 2.4GHz band with Wi-Fi and, in a kitchen especially, a microwave oven — all three can occupy overlapping frequencies, and BLE's advertising packets are short and easy to lose in a noisy environment even though the standard is designed to tolerate some of this. In practice this shows up as a device that connects fine most of the time but occasionally needs a second attempt right next to a running microwave, or in a room with an unusually large number of other Bluetooth accessories already connected nearby. None of this is a fault in the light; it is the shared-spectrum reality every BLE device lives with, and it is why the advice above is to pair close to the light rather than across the room — a strong initial signal has far more margin against that background noise.
Factory reset: when it is actually the right move
A factory reset clears the controller's stored pairing information entirely, which is useful in two specific situations and unhelpful in most others. It helps when a light was previously paired to a phone that is lost, sold, or no longer available to unpair it properly — the light otherwise keeps holding a connection slot for a device that will never release it. It also helps when a control module has been moved between fixtures or swapped during a warranty replacement and the app still shows the old device entry pointing at hardware that no longer matches it.
It does not help with a permissions problem, a wrong-app problem, or ordinary out-of-range behaviour — resetting a light that was never the cause of the fault just adds a second problem on top of the first. The reset method varies by fixture; most of our controllers use a power-cycle pattern (off, on, off, on, in short succession) rather than a physical button, since the module itself has no exposed reset switch once installed. Ask us for the exact pattern for your fixture before attempting it, since doing it on the wrong device in a multi-light installation resets a light you did not mean to touch.
Mesh apps add a step, on purpose
With the Bluetooth apps you connect to a light and control it. With iMeshting you tell it what kind of device you are adding and which room it belongs to, and only then does it appear as something you can control.
That feels like extra work for one light, and it is. It pays off at the fourth or fifth fixture, when "all the lights in the living room" becomes a thing you can act on rather than five separate connections to manage. If you are only ever going to control one light, the extra step buys you nothing — but if the installation will grow, do it properly at the start rather than re-adding everything later.
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 physical module if the app cannot remove it. |
After it is paired
Two settings are worth visiting once, before you mount anything:
- Pixels, on addressable lighting — tells the controller how many addressable points are on your strip so effects spread across the whole run rather than compressing into the first section.
- Modify Pin Sequence, if colours are not coming out right — remaps the channel order in software instead of rewiring. Walkthrough here.
Both live in the settings pop-up rather than on the main control screen, which is why they are easy to miss.
iOS and Android ask for permission differently
The empty-list symptom in the checks above is worth one more layer of detail, because the two platforms fail silently for different reasons. iOS ties Bluetooth scanning to a system-level Bluetooth permission the app requests on first launch; if you tapped "Don't Allow" without reading it, the app has no way to prompt again, and you have to grant it manually in Settings > Privacy & Security > Bluetooth. Android, from version 12 onward, additionally requires a "Nearby devices" runtime permission separate from location, and on older Android versions it requires location permission specifically for Bluetooth scanning even though the app has no interest in your location — that requirement comes from the OS, not from us, and predates the newer nearby-devices model. Either way, the symptom looks identical from inside the app: a scan that runs and finds nothing.
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. Contact us.