So I can now see that the mesh option is specific to a connecting client and not the system as a whole.

I think I may have also of found a work around to force the furthest Deco to connect to the middle and not the main Deco. By sending ping requests to the main deco from 2 different devices when I restarted the furthest Deco it automatically selected the other one.

Would still appreciate TP-Link confirming if a feature to manage this is in development or not and what the roadmap is please?

I just don't understand why you use ping to establish which device to connect to rather than signal as this negates the purpose of a mesh system!

Hi @o0nAw0o 

I posted a similar question, but no answers.

My farthest Deco is connected to the main with poor connectivity, while my other Deco, in the midldle between the other two, has got a very good signal.

I am not sure I got you workaround: did you ping from a device connected to the farthest? Can you please be so kind and give me some more details?

Many thanks

Massimo

@o0nAw0o 

I have the same problem with a brand new 3-set of x-20´s.

Main in the basement, and one on each other floor.

This is total crap and has nothing to do with a mesh system.

I really hope there is a solution

/Flexter

@o0nAw0o, @Flexter 

something happened, unexpected.

My son switched off my 3rd device by accident and since restarted, it is magically connected to the closest one, the 2nd (and not the main, the farthest)

So it seems the some "mesh" rule applied, finally.

@Massimo_Italy 

I set a ping to the main Deco from a laptop on the same wireless network (not on the same Deco that you want to restart). Whilst the ping -t is running reboot the Deco and it should go to the other Deco as the 1st is responding to a ping request. Apparently ping is how each Devo decides which to connect to. This seems to work everytime in AP mode.

Hope that helps. 
 

I am going to try fixing my mobile to the main deco and downloading an app to do this from there.
 

Thank you @o0nAw0o