Most smart home devices do not run on Bluetooth. They run on Wi-Fi, Thread or Zigbee. Bluetooth Low Energy is only used for the setup handshake, the short conversation where your phone tells the device which network to join and hands over the credentials.
That handshake is the fragile part, and when it fails almost everyone concludes the device is faulty. Often the device is fine and never even got asked. The phone either could not scan, could not connect, or connected and then had nothing useful to hand over.
The Test That Settles It in Two Minutes
Before troubleshooting anything: try the setup from a different phone.
If a second phone completes setup, the device was never the problem and you can stop reading the device’s manual. If both phones fail in the same place, the problem is the device or the network it is being asked to join, and is it the device, the radio, the router or the cloud is the better starting point.
This one test skips most of what follows, and it is worth doing first because it costs nothing.
The Permission Problem, Which Is the Most Common Cause
Bluetooth being switched on is not the same as the app being allowed to use it.
On iPhone, each app needs its own Bluetooth permission, granted the first time it asks. If that prompt was dismissed once, months ago, the app cannot see any device and usually reports it as “no devices found” rather than as a permission problem. It is in Settings under the app’s own entry.
On Android the situation depends on the version. Android 12 introduced separate runtime permissions for scanning and connecting to nearby devices. On versions before that, scanning for Bluetooth devices required Location permission, which is why so many smart home apps ask for your location for no apparent reason. On those phones the app needs Location permission granted and Location services switched on system-wide. Either one off and the scan returns nothing.
This is the single biggest source of “the device will not appear in the app.” The app is not lying. It genuinely cannot see anything.
The Device Is Already Talking to Something Else
A Bluetooth Low Energy device accepts one connection at a time. While it is connected, it is invisible to everything else.
Three ways that bites during setup:
It is still bonded to another phone. Your partner tried first, their phone is in the room, and it grabbed the device the moment it powered on. Move the other phone out of range or turn its Bluetooth off, then power-cycle the device.
A hub already claimed it. If the device was previously added to any ecosystem, that hub may reconnect automatically. This is the usual reason a second-hand or returned device refuses to set up, and it needs a factory reset on the device rather than anything on your phone.
Your own phone has a stale connection. The phone thinks it is connected from a previous attempt and the app is waiting on a session that is already dead. Toggling Bluetooth off and on clears this; forgetting the device in the phone’s Bluetooth settings clears it more thoroughly.
If the device never entered setup mode at all, that is a different problem and it is covered in how to put a smart device into pairing mode.
The Phone Is on the Wrong Network to Hand Over
This one produces the most confusing failure, because Bluetooth connects successfully and setup fails afterwards.
The app reads the Wi-Fi network your phone is currently on and passes those credentials to the device. So the phone’s network at that moment matters.
If your phone is on the 5 GHz band and the device is 2.4 GHz only, the app may pass a network the device cannot join, or refuse to proceed. Many phones and routers make this invisible because both bands share one name. Whether to split them is its own decision, argued in separate 2.4 GHz and 5 GHz network names, and the related failure mode is in band steering and smart home problems.
If your phone is on a guest network or a different VLAN from the one the device should join, the credentials handed over are for a network you did not intend, and the device disappears from the app the moment it connects. The general shape of that mistake is in IoT VLAN versus guest network.
If your phone is on cellular data with Wi-Fi off, there is no network to hand over at all.
The Things That Quietly Interfere
A VPN on the phone. Many setup flows need the phone to reach the device directly on the local network after the Bluetooth stage. A VPN routes that traffic away and the setup stalls at the last step, after Bluetooth appeared to work. Turn it off for setup.
Battery saver and background restrictions. Setup often takes a minute or more with the screen dimming. Aggressive power management can suspend the app mid-handshake, and the device is left half-configured. Keep the screen on and the app in the foreground.
Distance. Bluetooth Low Energy at setup power has a short usable range and people stand further away than they think, particularly when the device is a ceiling fixture or is inside an appliance. Get within a couple of feet of the device for setup, then move it afterwards.
A crowded 2.4 GHz band. Bluetooth and 2.4 GHz Wi-Fi share spectrum, and a badly congested band makes the handshake unreliable rather than impossible, which shows up as setup that fails at a different point each time. What else is competing for that space is in 2.4 GHz interference sources at home and what blocks a 2.4 GHz signal in a house.
The Order Worth Working Through
- Try a second phone. Settles device-versus-phone immediately.
- Check the app’s Bluetooth permission, and on older Android its Location permission and that Location services are on.
- Turn off any VPN.
- Make sure your phone is on the 2.4 GHz network the device will actually join, not guest, not 5 GHz only, not cellular.
- Get within arm’s reach of the device.
- Clear stale connections: Bluetooth off and on, forget the device in phone settings, power-cycle the device.
- Check nothing else owns it: other phones out of range, and a factory reset if it has ever been added anywhere before.
If it still fails after all seven, the device or its radio is a genuine suspect, and smart device will not pair troubleshooting picks up from there.
After Setup Succeeds
Bluetooth has done its job at that point and the device is on Wi-Fi, Thread or Zigbee. A device that sets up fine and then drops out later is a completely different problem, and it is not a Bluetooth one. That belongs to smart home device keeps going offline, and the first thing to check there is signal rather than pairing, using a smart device Wi-Fi signal strength check.
The Short Version
- Bluetooth is only the setup channel. A failure here rarely means a faulty device.
- Try a second phone first. It separates phone from device in two minutes.
- App-level Bluetooth permission is the most common cause, and on older Android, Location permission and Location services too.
- BLE takes one connection at a time. Another phone or an old hub holding the device makes it invisible.
- The phone’s current network is what gets handed over. Guest network, 5 GHz only, or cellular all break the handover after Bluetooth succeeded.
- Turn off the VPN, stand close, keep the screen on.