Causes
- The setup flow hands off from Bluetooth to 2.4 GHz Wi-Fi, and your phone is on 5 GHz — the v5 joins your network during onboarding while the Pura app talks to it over Bluetooth 6.0. If your router broadcasts one merged SSID with band steering, the phone happily parks on 5 GHz while the diffuser needs the 2.4 GHz band, and the app times out waiting for the device to appear. Pura's own compatibility list confirms its diffusers are incompatible with 5 GHz Wi-Fi, which is why the pairing stage demands a network the device can actually join.
- The network is hidden, requires a login, or has extra security layers — hidden (non-broadcast) SSIDs, MAC-address authentication, Wi-Fi that asks for a username or portal login, and routers with additional security features are all listed by Pura as incompatible with its diffusers. The device can't answer an authentication prompt it was never designed to see, so onboarding simply never completes.
- MAC filtering meets Apple's private Wi-Fi address — iPhones and iPads randomize their MAC address per SSID by default. If your router runs a MAC allow-list, the randomized address is rejected mid-pairing, and the app stalls at the last step even though the diffuser itself did nothing wrong.
- Missing phone permissions on Android — the app needs Bluetooth enabled plus location permission granted while in use, because Android requires location access for Bluetooth Low Energy scans. If either is denied, the app can't discover the diffuser during the first steps and reports the device as unfindable.
- An outdated app or stale pairing data from a previous setup — Pura's support notes that old app versions are a frequent source of errors and connectivity issues, and a device previously paired to another network or account can hold onto stale credentials that block a fresh join.
How to Fix
- Prepare a broadcast 2.4 GHz network — confirm you have a visible 2.4 GHz SSID. If your router merges bands, split them or create a guest/IoT SSID that runs 2.4 GHz only, since the diffuser needs to land on that band to finish onboarding. Unhide the network name if it's hidden.
- Stand close to the router — place the phone and the diffuser within a room of the router during setup. Weak signal during the Bluetooth-to-Wi-Fi handoff is the most common cause of pairing timeouts — 5 GHz walls and distance make it worse.
- Check phone-side blockers — enable Bluetooth, and on Android grant the Pura app location permission (Allow while using the app) for BLE scanning. On iPhone, disable the Private Wi-Fi Address for that SSID in Wi-Fi settings during setup if your router filters MACs, then re-enable it when pairing finishes.
- Update the Pura app — install the latest version from the App Store or Google Play before retrying. Outdated builds are one of Pura's named causes of connection failures, and the current app also contains the newest onboarding fixes.
- Reboot everything, then re-add the device — unplug the diffuser for 30 seconds, restart the router if it has been up for weeks, and remove any old copy of the diffuser from the Pura app. Then start the add-device flow again, keeping the phone on the same 2.4 GHz SSID you want the diffuser to join.
- Do a hardware reset if the app can't reach the device — if the app won't let you remove or reconnect the diffuser, power it off, unplug it, and hold the on-device reset button while plugging it back in per the Pura Home 5 manual, then run the add-device flow fresh.
- Give onboarding its full window and then test cloud control — let the flow run for a full five minutes without interrupting; ending it early can leave stale data on the device. Once paired, trigger a scent schedule from the app over mobile data (Wi-Fi off) to confirm cloud control really works.