There has always been an adage in computing, "If it's not working right, turn it off and back on again." i.e power off the satellites, router, and modem. Power up the modem....wait....power up the router...wait....power up one satellite at a time.
There is one potential complication with doing this: stupid devices can connect stupidly. This often happens after a temporary power outage.
Mobile devices are programmed to continue scanning the available WiFi networks all the time. When they find a better connection, they drop the previous WiFi access point and reconnect to the better one. (There are official IEEE standard which describe how this is supposed to work.) Devices that are not designed to move (televisions, cameras, smart plugs, etc.) sometimes act like once they connect to a WiFi access point, they quit looking. This can be really annoying when the router WiFi signal appears first, before the satellites have begun broadcasting their WiFi signals. A device can connect to the router, which is farther away and has a weaker signal, and then "hang onto it" despite the poor performance.
One of the most frequently asked questions on the forum is, "How do I force a device to connect to a specific Orbi unit?" The answer is, "That is not possible." WiF devices follow IEEE protocols and connect however they connect.
(This is really a stretch, but....) If the device used to measure speed was originally connected to the router WiFi, then taken to a satellite location and remained connected to the router rather than switching to the satellite, then performance would be much less. Message 1 asked if reducing the Transmit Power level might help. If the Attached Devices page showed the test device clinging to the router connection rather than changing to the satellite, then reducing Transmit Power might force the device to switch. Attached Devices does not update instantly when a device switches. Can take several minutes.
