|

Meross Smart Plug Not Responding to Alexa: Troubleshooting

ByAlex Turner

When your Meross smart plug stops responding to Alexa, the plug itself is rarely the problem. The failure usually lives in one of three layers: the Wi-Fi connection between the plug and your router, the cloud session between Meross’s servers and Amazon’s Alexa service, or the skill link that ties your Meross account to your Alexa account. This guide walks through the fixes in the order that actually resolves them.

First, Confirm What “Not Responding” Actually Means

Alexa says “device is not responding” for three different reasons. The fix differs depending on which one you’re seeing:

Symptom Likely Cause Fix Priority
Alexa says “not responding” but Meross app works Skill link broken or stale Re-link skill
Alexa says “not responding” and Meross app also fails Plug offline / Wi-Fi issue Power-cycle plug and router
Alexa finds the device but can’t control it Cloud session timeout Disable/re-enable skill

Branch point: If the Meross app also fails to control the plug, start with Step 1 (power-cycle). If the app works fine, skip straight to Step 3 (re-link the skill). The single most common time-waster is re-pairing a plug that’s already online.

Step 1: Power-Cycle the Plug

Unplug the Meross smart plug from the wall outlet for 30 seconds. Plug it back in. Wait 2 minutes for it to reconnect to Wi-Fi and re-register with the Meross cloud.

This clears the most common failure state: the plug’s Wi-Fi module drops its association with the router but stays powered, so it appears “on” without actually being reachable. The Meross app will show it as offline during this window.

Common mistake: Only restarting the Alexa app or the Echo device. That doesn’t help because the plug itself is the offline endpoint.

Verification: After 2 minutes, open the Meross app and confirm the plug shows as “Online.” If it does, test with a voice command. If the plug still shows offline, move to Step 2 before attempting anything else.

Step 2: Check the Wi-Fi Band

Meross smart plugs only support 2.4GHz Wi-Fi. They do not connect to 5GHz networks. If your router broadcasts both bands under one SSID (band steering), the plug may have connected to 2.4GHz initially but the router may have pushed it to 5GHz during a reconnect, which the plug can’t handle.

Fix: Open your router’s admin panel and check the connected devices list. If the plug shows up on 5GHz, either disable band steering or create a dedicated 2.4GHz SSID and re-pair the plug to it.

Common mistake: Assuming “the Wi-Fi works” because your phone connects. Your phone is dual-band; the plug is not.

Verification: After re-pairing to a dedicated 2.4GHz network, confirm the plug appears in the router’s connected list on the 2.4GHz band. Then test with Alexa before moving on.

Step 3: Re-Link the Meross Skill in Alexa

This is the fix that resolves most “not responding” cases where the Meross app still works.

1. Open the Alexa app on your phone.

2. Tap More (bottom right) → Skills & Games.

3. Search for “Meross” and select the official Meross skill.

4. Tap Disable Skill.

5. Wait 30 seconds.

6. Tap Enable Skill.

7. Sign in with your Meross account credentials.

8. Tap Discover Devices.

Wait 2–3 minutes after discovery completes. Alexa needs time to re-sync device states with the Meross cloud.

Common mistake: Re-enabling the skill but not signing in again. Disabling the skill does not always clear the stored OAuth token. If you don’t re-authenticate, you’re re-enabling a broken session.

Verification: Say “Alexa, turn on [plug name].” If it responds, you’re done. If not, check the Alexa app’s device list — the plug should show as “Online” next to its name. If it shows “Offline” despite the Meross app working, proceed to Step 4.

Step 4: Delete and Re-Discover the Device in Alexa

If re-linking the skill didn’t work, the device entry in Alexa’s registry is likely corrupted. You need to remove it and let Alexa re-discover it fresh.

1. In the Alexa app, tap Devices (bottom right).

2. Select the Meross plug from your device list.

3. Tap the gear icon (Settings).

4. Scroll to the bottom and tap Delete Device. For third-party devices like Meross, you’ll see a trash can icon in the top right corner of the settings menu — tap that to remove it.

5. Confirm deletion.

6. Say “Alexa, discover devices” or go to Devices → Add Device → Plug.

7. Wait for Alexa to find the plug again.

This forces Alexa to re-query the Meross cloud for the device’s current state, which clears stale cached status data.

Common mistake: Deleting the device in the Meross app instead of the Alexa app. That removes the plug from your account entirely and forces a full re-pair. Only do that as a last resort.

Branch point: After re-discovery, check whether the plug appears in Alexa’s device list. If it does but still won’t respond to commands, the issue is a cloud session timeout — move to Step 5. If Alexa can’t find the plug at all, the Meross skill’s OAuth token is stale; repeat Step 3 from scratch.

Step 5: Check the Meross App for Firmware Updates

Open the Meross app, select the plug, and look for a firmware update option (usually in the device settings gear icon). Meross pushes firmware updates that address cloud connectivity stability, and an outdated firmware can cause exactly this “works in app, not in Alexa” behavior.

If an update is available, install it, then repeat Step 3 (re-link the skill). Firmware updates can reset the device’s cloud session, which requires the skill to re-authenticate.

Common mistake: Updating firmware and not re-linking the skill afterward. The update invalidates the old session token.

Verification: After the firmware update and skill re-link, confirm the plug responds to a voice command within 5 minutes. If it does, the issue is resolved. If not, continue to Step 6.

Step 6: Verify the Echo Device’s Network

If the plug is on 2.4GHz and your Echo is on 5GHz, they can still communicate — but only if your router allows inter-band traffic (most do by default). The more common issue is an Echo device that’s on a guest network or a VLAN that blocks device-to-cloud traffic.

Check which network your Echo is connected to in the Alexa app: Devices → select your Echo → gear icon → About → Wi-Fi SSID. It should match the network the Meross plug is on (or at least be on the same LAN).

Common mistake: Assuming all your smart home devices are on the same network because “they all work.” The Meross plug may have joined a different SSID during setup if you have multiple networks.

Verification: If the Echo and plug are on different networks, move the Echo to the same SSID as the plug. Wait 2 minutes, then test the voice command again.

Step 7: The Router-Level Fix

If you’ve done all the above and the plug still won’t respond to Alexa, the issue is likely your router’s firewall or NAT table. Smart plugs maintain a persistent connection to the Meross cloud (MQTT over port 443). If your router drops idle connections aggressively, the plug’s cloud session dies silently.

Fix: Log into your router and look for:

  • NAT timeout settings — increase TCP timeout from the default (often 300 seconds) to 3600 seconds or higher.
  • Firewall settings — ensure outbound connections to Meross’s cloud servers aren’t being blocked or rate-limited.

This is less common but explains why the plug works for weeks, then stops responding, and a router reboot fixes it temporarily.

Common mistake: Replacing the plug or router without checking NAT timeouts first. The hardware is fine; the session is being killed.

Verification: After adjusting NAT timeout, wait 24 hours and test the plug again. If it responds consistently, the fix held. If it fails again within that window, the router’s firmware may be the limiting factor — consider a firmware update for the router itself.

Expert Tips Worth Knowing

Tip 1: Use the Meross app as your diagnostic tool, not Alexa.

If the Meross app shows the plug as online and responsive, the plug, Wi-Fi, and Meross cloud are all healthy. The problem is isolated to the Alexa skill layer. Don’t waste time re-pairing the plug — go straight to re-linking the skill. The common mistake is factory-resetting the plug when the app already proves it’s online.

Tip 2: Group devices in Alexa to reduce discovery failures.

If you have multiple Meross plugs, create an Alexa group (e.g., “Living Room”) and add the plugs to it. Groups force Alexa to maintain a separate device registry entry, which can bypass corrupted individual device states. The mistake to avoid is leaving devices ungrouped and expecting individual discovery to refresh reliably.

Tip 3: Schedule a weekly router reboot if you have an older router.

Many “not responding” issues trace back to router uptime. Older routers leak memory and drop connection tracking entries after days of uptime. A scheduled weekly reboot (most routers support this in settings) prevents the silent session drops that cause this exact symptom. The mistake is rebooting only when the problem appears — by then, the plug has already lost its session and needs a power-cycle anyway.

Quick Diagnostic Checklist

Run through these in order. Each item is a pass/fail check.

  • [ ] Meross app controls the plug? → Yes = skip to skill re-link; No = plug is offline, power-cycle it
  • [ ] Plug connected to 2.4GHz Wi-Fi? → Yes = continue; No = re-pair to 2.4GHz network
  • [ ] Meross skill shows “Enabled” in Alexa app? → Yes = continue; No = enable and sign in
  • [ ] Device deleted and re-discovered in Alexa within the last 10 minutes? → Yes = continue; No = delete and re-discover
  • [ ] Firmware up to date in Meross app? → Yes = continue; No = update and re-link skill
  • [ ] Echo and plug on same LAN/VLAN? → Yes = continue; No = move Echo to same network
  • [ ] Router NAT timeout set to 3600 seconds or higher? → Yes = done; No = adjust and monitor

If you pass all seven checks and the plug still won’t respond, the issue is likely a Meross cloud outage or a defective plug. Check Meross’s status page or contact their support with your device’s MAC address (found in the Meross app under device settings).

When to Consider a Different Plug

If you’ve gone through all the steps above and the plug fails again within a week, the hardware may have a failing Wi-Fi module. Meross plugs are generally reliable, but no consumer device is immune to component failure.

If you’re replacing it and want a plug that sidesteps the Wi-Fi dependency entirely, consider a Zigbee-based option like the THIRDREALITY Smart Plug Gen3 4 Pack. Zigbee plugs connect through a hub (like an Echo device with a built-in Zigbee radio) rather than directly to your Wi-Fi network, which eliminates the Wi-Fi band, NAT timeout, and router firewall issues that cause most “not responding” errors. The trade-off is that you need a Zigbee-compatible hub — the Echo (4th Gen), Echo Plus, and Echo Show 8 (3rd Gen) all have built-in Zigbee radios.

For a Wi-Fi plug that handles Matter natively, the Leviton Decora Smart Dimmer Plug supports Matter via firmware update, which gives it a more robust local control path with Alexa when paired with a Matter-enabled Echo device.

That said, most “not responding” issues are fixable with the steps above. The plug replacement rate for this specific problem is low — it’s almost always a session or network issue, not a hardware failure.

<!– cluster-navigation –>

Explore This Topic

Related guides in this cluster:

Similar Posts