@madmanjustice,

I would assume from the behavior that you are describing that the final problematic node is the furtherst away from the main node. Oftentimes, if a satellite node can see the network from the main, it will try to connect directly, as each hop between a node will severely impact the quality and bandwidth of the connection. While it may sound odd, you may be able to force the connection through the other satellite by moving it further away. Otherwise, try moving the satellite closer so that the 2.4ghz backhaul to the main is more stable.

If possible, we always recommend using a wired backhaul as there will not be a decrease in the quality and speed of the connections to satellite nodes.

You may also try exchanging two of your satellite nodes to see if the behavior was specific to that specific node, or is a result of the location of the node.

Lastly, In the most recent firmware updates that are being pushed to Decos, there are two added features for your exact situation. 

Signal Selection - Allows selecting what node a specific client will connect to 

Node Source Selection - Allows you to select how a node is connecting to your network, whether through a satellite or directly to the main.

The teams are working to bring this firmware to as many Deco models as possible so make sure to check for updates to your network so that you can make use of the feature when it first releases.