You open the Linksys app to set up your new Velop Pro 7 and it just sits there. "Couldn't find device." "Setup failed." "Network unavailable." The Velop Pro 7 uses the Linksys app as its primary setup tool, and when the app won't cooperate, you're locked out of the whole mesh.
The fastest single move: fully close the Linksys app and reopen it with Bluetooth on, Location permission granted, and your phone disconnected from any other Wi-Fi network. Setup uses Bluetooth Low Energy to discover the node, and the app needs Location access to scan networks (both iOS and Android require this). Missing either permission is the top reason the app can't find the Velop Pro 7.
If that doesn't get you in, here's the full order of things to try.
Enable Bluetooth, Location, and Local Network Permissions
On iOS, open Settings, scroll to Linksys, and make sure Bluetooth, Location, and Local Network are all set to Allow. The Local Network toggle is the one most people miss, without it, the app can discover the node via Bluetooth but can't actually configure it, and setup silently fails. On Android, long-press the Linksys app icon, tap App Info, then Permissions, and grant Location and Nearby Devices.
Turn Off VPN and Personal Hotspot
A phone-level VPN can block the app's connection to the Velop Pro 7 during setup. The same goes for Personal Hotspot on iOS, if hotspot is active, the phone won't handshake properly with the new node. Disable both, then retry setup. You can turn them back on once the mesh is configured.
Get Within a Few Feet of the Node
Bluetooth LE has a real-world range of about 5 to 10 feet through walls. For initial discovery, sit on the floor next to the Velop Pro 7 with your phone inches away. Once the app pairs and configures the node, you can move freely. Failed discoveries from across the house are usually just signal range, not a router problem.
Power-Cycle the Velop Pro 7
Unplug the node from power. Wait 30 seconds. Plug it back in and wait for the LED to return to a steady solid state, that takes about 90 seconds. Reopen the Linksys app and try setup again. This clears any half-finished pairing state from a previous attempt.
Update the Linksys App
Open the App Store (iOS) or Play Store (Android) and check for an update to the Linksys app. The app gets frequent updates to support new hardware and fix bugs. If you're on an older version, it may simply not recognize the Velop Pro 7's latest firmware. Also confirm your phone is running iOS 14+ or Android 8+, which the app requires.
Check for Linksys Cloud Outages
The Velop Pro 7 depends on the Linksys cloud service for app-based setup and management. Linksys has occasional cloud connectivity outages. If the app can't reach the cloud, setup gets stuck at "Connecting..." You can check the Linksys status page or social media for any reported outages. If a cloud outage is active, the only fix is to wait. In the meantime, you can try the web UI at 192.168.1.1 for basic configuration, more on that below.
Try the Web UI (Advanced Option)
Unlike some mesh systems, the Velop Pro 7 has a backup web interface. Connect a computer or phone to the node's default open Wi-Fi (SSID usually "Linksys Velop Pro 7 - Setup" or similar), then open a browser and go to 192.168.1.1. You can complete the basic setup there and then use the app later for features like Cognitive Mesh optimization and MLO band steering. This is a solid workaround when the app itself is buggy or the cloud is down.
Factory Reset the Velop Pro 7
If the node is stuck in a failed setup state, a factory reset clears everything. Locate the reset button on the bottom of the node. Use a paperclip to press and hold it for 10 seconds. The LED will flash, then turn solid. Release after 10 seconds. The node will reboot and take about 3 minutes to return to fresh-out-of-box mode. Open the Linksys app and start the new device flow. This wipes all settings, so make sure you're ready to set up from scratch.
Reinstall the Linksys App
If nothing above worked, delete the Linksys app completely and reinstall it from the store. This clears any local database corruption that can block node discovery. Sign back into your account, your existing mesh configurations (if any) should sync from the cloud. Then try setup again.
