@RedRoger 

Hello, do you mean that the wireless device will connect to the slave Deco which connects to the main Deco by wireless, but won't connect to the slave Deco which has ethenret backhaul enabled?

Usually, if the signal strength does not reach the threshold value, it won't trigger AP/Band steering, you can try to move them further away from each other.

Meanwhile, what is the current network diagram?

And if you want to connect the client to the specific Deco, you can connect it to the specific Deco first and then disable mesh technology if your Deco supports this feature. Then the Deco won't suggest the client to roam between different bands/APs.

Besides, forcing client connect to the specific Deco feature has been noted and we will keep an eye on the similar feedback and forward it to the product department.

Good day.  

@Kevin_Z No, This is not about "device - Deco" link, but "Deco-Deco" link. The slave Deco has an ethernet connection to the network and can access to the main Deco by ethernet. But instead it uses Wifi link, at least I can see it in app...

@Kevin_Z I can add that problem as I can see in the fact that if eth connection between Decos is off for a while (for example switch is being rebooted), slave Deco moves to WiFi connection with the master one. When eth connection is restored it's obvious that slave Deco should chose eth link for connection with the master Deco. Should be priority to eth port... But instead of this, slave Deco continues to use WiFi link...

@RedRoger 

Thanks for your updates. 

Theoretically, the ethernet backhaul has higher priority than wifi backhaul. 

Please show us a screenshot of the signal source page of the Deco unit which connects to the main Deco by wired cable. 

And you can reboot the whole system and change another ethernet cable/port to give it a go. 

Good day.