Before firmware 1.7.3, my best Speedtest result I ever got for smartphone connected to M5 was 475Mbps, on gigabit Internet. After 1.7.3 upgrade, tested with the same smartphone, I've got 530Mbps. Which is quite an improvement.

Alexandre. wrote

Before firmware 1.7.3, my best Speedtest result I ever got for smartphone connected to M5 was 475Mbps, on gigabit Internet. After 1.7.3 upgrade, tested with the same smartphone, I've got 530Mbps. Which is quite an improvement.

On wireless? or Speedtest from deco app (lan speed)?

RobertFernandes wrote

Alexandre. wrote

Before firmware 1.7.3, my best Speedtest result I ever got for smartphone connected to M5 was 475Mbps, on gigabit Internet. After 1.7.3 upgrade, tested with the same smartphone, I've got 530Mbps. Which is quite an improvement.

 

On wireless? or Speedtest from deco app (lan speed)?

  @RobertFernandes 

On wireless. Not LAN speed. 

1.7.3 is the perfect firmware. 3 weeks in this version and 0 disconnects, no beacon losts on my linux server and the max stability and speed for a IPQ4019 Qualcomm processor.

Thanks, for the Tp-Link Engineers team!

  @TP-Link I kept having DHCP problems on my network, which became so bad that yesterday half of my Homekit accessories (including my doorbell) went offline. I spent all night troubleshooting (after factory resetting my cable modem I could narrow the issue down to the master-Deco M5) and realized there is a bug in the new firmware. My Deco units have always been set up in access point mode; however, the 1.7.3 firmware doesn't seem to honor this setting fully, and even in access point mode the master unit tries to hand out IP addresses. This results in behavior where devices get an IP address for 2-3 seconds, then lose it again, and then they might regain it after several minutes (depending on whether the device wants to wait that long).

The solution turned out to be extremely simple, so for anyone who might experience these problems: set the Deco network to 'router mode' (which takes a reboot and about 3 minutes), wait until the network is fully back online, then set the Deco network to 'access point' again. Once the Deco network is fully back online, it should no longer try to act as DHCP server.

  @TP-Link I've had to hard reset my devices and set them up again following the update to 1.7.3. The devices appeared to have been either restarting themselves in a recursive loop or knocking off the connectivity to devices.

I did attempt to downgrade back to the firmware I was on previous to the upgrade but this only applied to the main Deco and the behavior described above persisted.

  @TP-Link 

i have Deco x60 and currently running version 1.5.1. I'm having hugh issues where different devices don't select correct mesh. Leaving hugh frustration. If I could manually select the correct mesh to use this would not be an issue. Is there any fixes coming soon?

  @Sourkush I had the same issue with my main unit. After it applied it connected to the internet for a very brief time then dropped. Tried resetting it but same issue. I had a spare m5 which i used instead

My main unit is currently running 1.7.1 and a AP which did successfully do the upgrade is 1.7.3. I now want to upgrade my main unit to 1.7.3 but obviously very nervous to do so. Thoughts anyone?