Device not connecting to the nearest/fastest Deco M5

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Device not connecting to the nearest/fastest Deco M5

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Device not connecting to the nearest/fastest Deco M5
Device not connecting to the nearest/fastest Deco M5
2020-09-18 11:53:57 - last edited 2021-09-08 03:00:12
Model: Deco M5  
Hardware Version:
Firmware Version: 1.47 Build 20200725 Rel. 63377

Hi,

  I recently purchased 2 units of Deco M5. I live in a 1860 sq.ft apartment. Both the Decos are present in the same floor.  I see that my devices are NOT connected to the closest Deco and connected to the farthest Deco most of the times. This causes a considerable reduction in speed and it defeats the very purpose of installing a mesh. 

 

To TP-Link R& D Team - Either improvise your algorithm to find the nearest Deco and connect seemlessly or let the user select the Deco M5 unit to which the device has to get connected to. 

 

Please provide me with any known solution/workaround to overcome this issue temporarily.

 

Rgds,

Priya

  15      
  15      
#1
Options
1 Accepted Solution
Re:Device not connecting to the nearest/fastest Deco M5-Solution
2021-09-08 02:59:39 - last edited 2021-09-08 02:59:45

@MarkSanchez123 

Hi, All, I will lock this thread, and please refer to this link to get the firmware 1.6.0 for Deco M5(V1, V2, V3, V3.2) only to manually select the signal source:

[New Firmware] Deco M5 1.6.0

 

Recommended Solution
  0  
  0  
#45
Options
42 Reply
Re:Device not connecting to the nearest/fastest Deco M5
2020-10-19 07:43:38 - last edited 2021-05-12 01:36:29

@PriyaVenkat 

 

Hello, we will add the option to allow the Deco administrator to choose to connect to which Deco node in the future firmware.

 

Generally, the Deco system will recommend the client device to roam to the closest Deco unit when the device is moving around. However, whether to roam or not depends on the device itself.

Some devices may stay connected to the original Deco unit rather than connecting to the closest Deco, possible reasons include the following:

1) The device doesn't support the roaming protocol. Then it won't roam until it disconnects from the Deco unit.

2) The device may regard the signal strength of the current connection is still strong enough and don't want to roam to another Deco unit. It's decided by the roaming threshold which is set by the vendor of the device.

 

Hopefully, that answers your question but let us know if you need more details.

  1  
  1  
#2
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-01-18 02:45:10

@TP-Link_Deco 

 

When will this be available, when you say in a future version?

  6  
  6  
#3
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-01-19 20:00:50

@TP-Link_Deco 

 

Sam issue here, device will not select nearest Deco unit.

 

I have one less than 10 feet away and it select one 28 feet away

 

When will this feature be available?

 

THanks

  13  
  13  
#4
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-01-26 07:08:12 - last edited 2021-01-26 07:08:31

@TP-Link_Deco 

 

Hi there,

 

same issue here with my Deco M4 (system of 3). Even if I turn OFF/ON device wifi it will connect to the Deco that was last used (not to the closest one). Maybe it was only me but I missed this part in the marketing material and listened only to the sentence 'Deco uses a system of units to achieve seamless whole-home Wi-Fi coverage — eliminate weak signal areas once and for all!' - this is exactly the very first sentence for this product on your website...

 

Replying to your points:

1) It would be nice if you could provide some more details about how to check if my device is supporting the roaming protocol. I have a Dell business laptop and 2 Android smartphones that don't seem to do so.

2) Unfortunately not. My devices reconnect to the last used Deco even after manually triggering a wifi OFF/ON cycle or after they lose connection completely for a couple of seconds (due to weak signal from distant Deco). It seems that for any reason the devices prefer one physical unit of my mesh system.

 

Issues to be added from my side:

  • it is extremely hard to identify which Deco my device is momentarily connected to. Sometimes the Deco app displays it, sometimes it displays no connected devices while I am using the internet.

 

System setup:

- Archer MR600 main router, wifi turned off

- 3 pieces of Deco M4 units in AP mode, signal source: Ethernet. All Decos are connected with cable to the main router, via switches.

- on the Decos 2.4 and 5Ghz are turned on both for main and guest networks

 

In case you would need any further information just let me know.

  6  
  6  
#5
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-01-26 12:09:42 - last edited 2021-09-08 02:57:28

 

Hi, All,

The official firmware 1.6.0 for Deco M5 would be released very soon which allows us to manually select the signal source; You would also wait for a while for the new firmware release;

and there is also another firmware that would improve the signal source selection mechanism: https://static.tplink.com/beta/2021/202102/20210207/Deco_M5_1.5.1_Network_Map_Optimization_Log.zip

How to update the firmware: https://static.tp-link.com/2020/202012/20201207/Documentation for upgrading Deco system.pdf

Thank you very much!

  2  
  2  
#6
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-01-26 14:53:44 - last edited 2021-01-26 15:21:47

@Pispidoor 

 

If you would like suggestions on improving device roaming performance, meaning helping devices (laptops, mobiles) select closest Deco node with strongest WiFi signal, here they are.

 

But, first, my experience: I do run Deco mesh with 3 nodes, they are located reasonably well from WiFi coverage point of view. I have two Android 9 smartphones that always connect to the node with the strongest signal and roam seamlessly as their owners walk through the house.

I also have Surface Pro that is a bit slow switching between nodes, but when it goes to sleep it turns off WiFi, and when user wakes it up - tablet connects to the Deco node with the strongest signal.

 

So, here are things to look at. Not that you have to, but doing it should improve device roaming in Deco mesh.

 

To better understand your network, I would suggest installing WiFi Analyzer on your smartphone. I am using WiFiMan from Ubiquiti and will be referring to it.

 

1. Disable 2.4GHz on Main Network.

 

Your smartphone will roam to closest Deco node faster, when it only runs on 5GHz. You will also see better download speeds.

Keep 2.4GHz for Guest Network, if you have devices that can't connect on 5GHz.

 

2. Node deployment, WiFi coverage.

 

Ideally, your Deco mesh nodes should be deployed in a way that in places which do matter you have only one node with strong signal, another node with weaker signal, and a third node with very weak or no signal. That will help your devices to choose the best node every time. Like that:

 

 

3. Keep relevant roaming settings enabled in Deco app.

 

That would be Fast Roaming, Beanforming and also Mesh per each device (enabled by default, but just check if it is).

 

 

4. For laptop specifically, see what Network device driver options it offers to improve WiFi roaming between mesh nodes

 

You can find these under Device Manager in Windows. In example below, you should choose 5GHz as Preferred Band and also should set Roaming Aggressiveness to High (or Highest).

 

 

Instead of "Roaming Aggressiveness" you may see "Roaming Sensitivity" or similar, depending on WiFi Network card brand. For laptop, make it High (Highest).

 

5. Enable "allow the computer to turn off this device to save power" for Network adapter

 

I have Surface Pro 4 which does not offer roaming tuning options. When it is in use and moved in the house, it sometimes stubborny cling to the node it is connected to, till signal gets really weak.

As a workaround, I found the setting in Power Management for network adapter, to save power when idle/sleep, and turned it on. Surface Pro now powers off network adapter when it goes to sleep, turns it on and reconnects to the closest Deco node when user wakes tablet up.

If your laptop does not have band selection and roaming tuning options, consider using this as a substitution.

 

 

 

Note that these recommendations are valid for any mesh deployment, with only Item 3 specific for Deco - but other mesh systems may have similar configuration parameters that should be set same way.

 

Also, when troubleshooting your mesh (any mesh, not just Deco) you can use WiFi analyzer running on Android smartphone to get real time info about mesh node your smarpthone is connected to.

  5  
  5  
#7
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-02-10 11:50:21

@TP-Link how do I get access to this beta? My issues is that I have 3 decos set up in my single floor condo that is only 1600 sq ft, however my deco in my bedroom is connecting to the main deco in my living room, instead of the hallway deco that was placed there for the very purpose of bridging the two. Why can I not change its signal source so it connects to the hallway deco instead of the much farther living room deco???? I bought this for the sole purpose of being able to work from my bedroom and instead of getting 200mbps like I do in my living room, I get the equivalent of dial up speeds 😑 this is a horrible user experience. 
 

  8  
  8  
#8
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-02-11 13:39:52

@PriyaVenkat I have the exactly same problem, did you fixed it somehow?

  0  
  0  
#10
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-02-20 07:49:20

@TP-Link Hello, how do I get my hands on the beta version so I can test it? Who do we contact with our findings, bugs and issues with the beta version?

  0  
  0  
#11
Options
Re:Device not connecting to the nearest/fastest Deco M5
2021-02-22 05:47:58

@bgoncal Not yet. Planning to try the beta FW version to see if it fixes the issue.

  1  
  1  
#12
Options