You're trying to pair your new smart plug or printer with the ASUS ZenWiFi BT10 and it just won't connect. The phone says "Can't connect to network". The printer setup page never finds the WiFi. The smart home app hangs at "Configuring." The BT10 is a potent Wi-Fi 7 mesh system, but its advanced security defaults and tri-band steering can lock out perfectly normal devices.
Sort the device first: if it's a printer, smart plug, or anything pre-2022, the issue is almost always that the security mode got changed to WPA3-Personal only; if it's a modern phone or laptop that used to connect and just stopped, look at Fast Roaming and AiProtection. The fastest single move for an older device is dropping the security mode to WPA2/WPA3-Personal (transition mode) in the ASUS Router app under Settings > Wireless > Security. Save and retry pairing. If that doesn't do it, work through the rest of these fixes.
Check These Settings First
Several common settings on the ZenWiFi BT10 can quietly block new devices. Here's what to look for:
- WPA2/WPA3-Personal transition mode: The BT10 ships with WPA2/WPA3 transitional by default, but many users accidentally toggle it to WPA3-Personal only. That locks out any device that doesn't support WPA3. Keep it in transition mode unless you have a specific compliance reason not to.
- Single SSID across all bands: Devices that need the 2.4 GHz band (most IoT) get steered to 5 or 6 GHz and fail. Create a separate 2.4 GHz network for those devices.
- AiProtection blocking: The free-for-life security engine can auto-block unrecognized MAC addresses. It's aggressive by default.
- MAC filtering enabled: If you set up an allow list, new devices won't connect until added.
- Special characters in the WiFi password: Smart plugs and older printers often choke on apostrophes, ampersands, or non-ASCII characters.
- Captive portal confusion: A guest network or portal may be intercepting the handshake.
- DFS channels on 5 GHz: Some older clients can't see the network when the 5 GHz band is on a DFS channel.
Create a Separate 2.4 GHz Network for IoT
Many smart home devices only support 2.4 GHz Wi-Fi, but the BT10 broadcasts a single SSID and tries to steer everything to the best band. The phone you're using to set up the IoT device may be on 5 GHz while the plug is searching for 2.4 GHz, and the pairing fails.
Open the ASUS Router app, go to Settings > Wireless > IoT Network, and enable a separate 2.4 GHz network. Give it a different SSID (like "Home-IoT"). Connect your phone to that network temporarily, pair the device, then switch back. This solves the vast majority of smart home connection problems.
Check AiProtection for Blocked Devices
AiProtection Pro by Trend Micro is free for life on the BT10, but it can auto-block devices it considers suspicious. In the ASUS Router app, tap AiProtection > Network Protection. Look at the list of blocked devices. If your new device is there, tap to unblock it.
If you've enabled any parental control or QoS profiles, those can also reject unknown clients. Review those settings under AiProtection > Parental Controls to make sure no filters are blocking the device's MAC.
Confirm MAC Filtering Isn't On
Log into your router's web interface at router.asus.com, go to Wireless > Wireless MAC Filter. If MAC Filtering is enabled and set to Accept mode, your new device's MAC isn't on the list. Either add it or switch the mode to Disabled.
You probably set this up months ago for security and forgot about it. It's a frequent hidden cause of connection failures.
Use a Simple Password Temporarily
Some older smart home devices and printers don't handle special characters well. If your WiFi password contains an apostrophe, ampersand, semicolon, or backslash, change it temporarily to something simple like 12 letters and numbers with no symbols.
Pair the device, then change the password back. Most devices remember the password for the network name, so you won't have to re-pair them after you revert.
Disable DFS Channels on the 5 GHz Band
DFS channels (52 to 144 on 5 GHz) require the router to vacate the channel if it detects radar, but many older devices can't tune to them at all. Go to router.asus.com, navigate to Wireless > Professional, and for the 5 GHz band, set the channel to 36, 40, 44, or 48 (the non-DFS lower band). Save the settings.
This solves a class of "network not found" issues for smart TVs and older gaming consoles.
Clear Stored Network Credentials
If a device previously connected and now refuses, it may have a stale credential cached. On the device, go to its WiFi settings, find your network, and tap Forget or Remove. Then try connecting fresh. This clears whatever state was wrong and forces a full handshake.
Disable Fast Roaming
Fast Roaming (802.11k/v/r) on the ZenWiFi BT10 is one of ASUS's most-cited causes of devices failing to associate or repeatedly dropping during the join. Open the ASUS Router app, go to Settings > Wireless > Professional, look for Fast Roaming, and turn it off. Try the pairing again. If the device connects, leave Fast Roaming off, the BT10 still hands clients between nodes without it, just less aggressively.
If you're using a device that supports Multi-Link Operation (MLO), make sure you're running firmware 3.0.0.4.388 or later, as MLO requires that update to function properly. You can check the firmware version in the ASUS Router app under Settings > System.
Move the Device Within a Few Feet of the Main Node for Pairing
Especially for smart plugs and other IoT gadgets, the initial pairing process is more sensitive to signal strength than normal operation. Bring the device into the same room as the main ZenWiFi BT10 node during setup. Once it connects, you can move it back to its final location.
Update the Firmware via the ASUS Router App
Open the ASUS Router app, tap Settings > System > Firmware Update. Install whatever's available. New firmware often includes compatibility fixes for specific devices. The router reboots automatically after the update.
If you have an existing ASUS router, the ZenWiFi BT10 supports AiMesh, so you can add it as a node to extend mesh coverage. But AiMesh setup can be tricky when mixing models, make sure both routers are on the latest firmware before pairing.
