How to Fix WiFi Not Working on an Amazon Echo or Echo Dot: Alexa App Re-Pairing, 2.4 GHz Band Selection, and Factory Reset Fixes for Smart Speaker WiFi Issues

Amazon Echo and Echo Dot smart speakers stop connecting to WiFi for three consistent reasons: they were placed too far from the router, they are trying to join a 5 GHz-only network that older models can’t see, or the Alexa app pairing data has gone stale and needs to be refreshed. Run a speed test first to confirm your internet connection is working, then work through the steps below in order from quickest to most invasive.

Step 1: Confirm Your Echo Supports Your Network Band

This is the most common source of confusion. Echo device WiFi compatibility has changed across generations:

• Echo Dot (1st, 2nd, 3rd gen) and Echo (1st, 2nd gen): 2.4 GHz only. These models cannot see or join a 5 GHz SSID under any circumstances.
• Echo Dot (4th gen, 5th gen), Echo (3rd gen and later), Echo Show, Echo Plus: Dual-band, supporting both 2.4 GHz and 5 GHz (802.11a/b/g/n).
• Echo Studio, Echo Hub: Dual-band 802.11a/b/g/n/ac.

If your router broadcasts separate SSIDs for 2.4 GHz and 5 GHz (for example, “HomeNetwork” and “HomeNetwork_5G”), point your Echo at the 2.4 GHz SSID during setup. Even dual-band Echo models benefit from 2.4 GHz’s better wall penetration for a fixed smart speaker that doesn’t need peak throughput. If you run a single merged SSID with band steering, your router handles band assignment automatically — confirm band steering is enabled and not forcing 5 GHz-only in your router’s admin panel.

Check that the 2.4 GHz network is visible and not hidden. Our guide on common WiFi interference sources explains why the 2.4 GHz band can appear to drop when congested by neighboring networks or nearby appliances.

Step 2: Power Cycle Your Echo and Router

A full power cycle resolves most temporary authentication failures and DHCP stale-lease issues before you touch the Alexa app:

1. Unplug your Echo from power.
2. Unplug your router and modem from power.
3. Wait a full 60 seconds for all devices to lose power completely.
4. Plug in the modem first and wait 30 seconds for it to reconnect to your ISP.
5. Plug in the router and wait 30 seconds.
6. Plug in the Echo and wait for the startup sequence to complete.

The Echo’s light ring will cycle through startup colors. When it connects to WiFi, most models announce “I’m ready” or flash teal. A spinning orange ring means the device is in setup mode and is waiting for WiFi credentials.

Step 3: Re-Pair Using the Alexa App

If the Echo shows a spinning orange ring or a solid red ring, it needs fresh WiFi credentials entered through the Alexa app on iOS or Android. The web interface and PC app do not support full device setup:

1. Open the Alexa app and tap Devices in the bottom navigation bar.
2. Select your Echo device from the list, then tap Change next to Wi-Fi Network.
3. The app will prompt you to put the Echo in pairing mode. On most models, press and hold the Action button (the circle/dot button) for 5 seconds until the ring turns orange.
4. Follow the in-app prompts to select your network and enter your password.

If the App Can’t Find the Echo

If the Alexa app cannot detect your Echo during setup, confirm Bluetooth is enabled on your phone and the Echo is in pairing mode (orange ring). The app uses Bluetooth Low Energy for initial device discovery before switching to WiFi for configuration. Disabling any VPN on your phone during setup removes another common source of pairing failures. Keep your phone within 10 feet of the Echo throughout the process.

Step 4: Check Distance and Interference

Amazon recommends keeping Echo devices within 30 feet (approximately 9 meters) of your router for reliable operation. Concrete walls, metal appliances, and dense building materials reduce effective 2.4 GHz range significantly. Common interference sources include microwave ovens (which operate at 2.45 GHz), DECT cordless phones, and baby monitors. Move the Echo close to your router temporarily as a test: if it connects immediately when placed nearby but drops when moved to its usual spot, range or interference is the root cause.

If the Echo’s intended location is too far from your router, the cleanest fix is adding a mesh node or access point to cover that area. See our guide to extending WiFi coverage and our WiFi dead zones guide for the most effective options.

Step 5: Assign a Static IP to Prevent Recurring Drop-Offs

If your Echo connects initially but drops offline every day or two, a DHCP IP address conflict is a likely culprit. When your router’s DHCP server issues the same IP to multiple devices, or when a lease renewal assigns a new address that the Echo cached as stale, one device loses connectivity. Fix this by assigning a DHCP reservation (also called “static IP” or “address reservation”) to your Echo’s MAC address in your router’s admin panel.

Your Echo’s MAC address is visible in the Alexa app under Device Settings → About. Assign the Echo an IP address outside your router’s normal DHCP range so no other device can receive it automatically. On a typical 192.168.1.x subnet with a DHCP pool starting at 192.168.1.100, a reservation in the 192.168.1.2–50 range works well.

Step 6: Factory Reset Your Echo

A factory reset clears all stored WiFi credentials, account associations, and firmware-level settings causing connection failures. The procedure varies by generation:

• Echo Dot (3rd gen and later) / Echo (3rd gen and later): Press and hold the Action button for 25 seconds until the light ring turns orange.
• Echo (2nd gen): Press and hold Volume Down and Microphone Off simultaneously for 20 seconds until the ring turns orange.
• Echo (1st gen): Use a paperclip to press the recessed reset button on the bottom of the device until the ring turns orange.

After the reset, the light ring spins orange — the device is ready for fresh setup. Open the Alexa app and re-pair as described in Step 3. A factory reset resolves corrupted credential storage and firmware WiFi driver issues that resist all other fixes.

After Reset: Still Not Connecting?

If the Echo fails to complete setup even after a factory reset, confirm your router is not blocking new devices via MAC address filtering. Also check that your SSID does not contain special characters — some older Echo firmware versions mishandle network names with apostrophes, emoji, or Unicode characters. Rename the SSID to a plain alphanumeric string as a final test.

When It’s Not the Echo

If your Echo connects and responds but Alexa is slow to answer or smart home commands time out, the problem is likely upstream: ISP congestion or Amazon service latency rather than a local WiFi issue. Run a speed test to confirm your connection speed and latency are within a normal range. A ping above 100ms or packet loss above 1% on the speed test points to an ISP or routing issue, not a problem with your Echo or home network. If speeds look healthy, check Amazon’s Alexa Service Status page for regional outages before spending more time troubleshooting local hardware.