Diagnosis
The issue occurs because your Motorola MH7023 system is currently operating in "Access Point" or "Extended" mode rather than a unified Mesh configuration. When the system is not correctly synchronized, the satellite node broadcasts a secondary SSID (the _EXT suffix) to indicate it is a separate extension of the main network. This creates a "sticky client" problem where your smartphone clings to the main router's signal until it becomes critically weak, then jumps to the _EXT signal, or vice versa, causing momentary drops in connectivity. This typically happens if the satellite was added manually via a secondary setup method or if the "Smart Connect" feature—which manages a single SSID across both 2.4GHz and 5GHz bands—has been disabled. To confirm this, check your phone's Wi-Fi list; if you see two distinct network names (e.g., "MyHomeWiFi" and "MyHomeWiFi_EXT"), the mesh system is treating the nodes as separate entities rather than a single fabric. The device is forced to make the decision of which network to join, rather than the MH7023 system intelligently steering the device to the strongest node.
How to Fix It
To resolve this and create a single, seamless network, you must unify the SSIDs and enable the system's intelligent steering. Follow these exact steps:
- Launch the Motorola Mesh app on your mobile device and log in to your administrative account.
- From the main dashboard, select the "Network Settings" or "Wi-Fi Settings" menu.
- Locate the toggle for "Smart Connect." Switch this to the ON position. This merges the 2.4GHz and 5GHz bands into one single network name.
- Navigate to the "Satellite" or "Nodes" management section. Check the status of your satellite node. If it is listed as a separate extension, select "Reconfigure" or "Sync Node."
- Ensure that the "SSID" field for the satellite is set to "Match Main Router" or "Inherit Settings." Delete any manual naming that includes the "_EXT" suffix.
- Save the changes and restart the entire system by unplugging the power cables from both the main router and the satellite for 30 seconds, then plugging in the main router first, followed by the satellite after two minutes.
If That Didn't Work
- Perform a Hard Factory Reset on the satellite node. Use a paperclip to hold the Reset button on the back of the MH7023 satellite for a full 15 seconds while it is powered on. Once the LED flashes amber, use the app to "Add New Node" and follow the pairing process from scratch. This forces the satellite to adopt the main router's SSID and security credentials exactly, eliminating the _EXT suffix.
- Adjust the Satellite Placement. If the satellite is placed too close to the main router (less than 20 feet), your phone may constantly flip-flop between the two because the signal strengths are nearly identical. Move the satellite to a position roughly 30-40 feet away, ensuring there are no more than two walls between the nodes.
- Disable "Private Wi-Fi Address" on your smartphone. In your phone's Wi-Fi settings for the Motorola network, toggle off "Randomized MAC" or "Private Address." Some mesh systems struggle to steer devices that rotate their hardware IDs, causing the device to treat the mesh nodes as separate networks.
- Check for Firmware Mismatches. In the app, go to System Settings > Update. Ensure both the main router and the satellite are on the same firmware version. A version mismatch can disable the 802.11k/v/r roaming protocols required for seamless transitions.
Heads Up
- Avoid placing the satellite node inside a closed cabinet or behind a television; the MH7023 relies on clear line-of-sight for the backhaul connection to maintain a single SSID.
- If you use legacy IoT devices (like old smart plugs) that only support 2.4GHz, enabling "Smart Connect" may occasionally cause them to disconnect. If this happens, you may need to briefly disable Smart Connect to pair the device, then re-enable it.
- Always update the main router's firmware before adding new satellite nodes to prevent synchronization errors.
- The LED indicator on the satellite should be solid white; if it is pulsing or amber, the mesh link is too weak to support seamless roaming, and the system may revert to the _EXT fallback mode.