@TP-Link 

Any word on what 1.7.4 brings? One of my Deco M5s were offered the update this morning. 

  @TP-Link it would really be very useful to have the ability to modify DTIM interval.
It could help for some connectivity issues with some ESPs and the Nuki smart lock 3pro, very recently I read again on the Nuki developers forum some people who have improved the situation with their smart lock when they set the dtim interval to 3. Even a Nuki founder confirmed this can really help to improve connectivity issue but nothing from TP-Link when asking. It is not a big feature which will increase memory consumption, it is something to write in config files when set by the Deco app...

  @TP-Link 

Please Support, enable the possibility to set the WI-FI channel.

I live in a residential complex and the decos are using the worst channels and conflicting with the different routers around me.

I noticed that when accessing the web version of the router, for a few seconds, options are available to define the channel, bandwidth and other options, which makes me believe that it can be done and/or enabled.

Thank you for your attention and I would be very grateful if this resource was released.

BeerBee wrote

Hi All,

 

After upgrade my Deco M5 to 1.7.3 Build 20230906, I found that both download and upload throughput are becoming obviously lower.

Before upgrade, tested with SpeedTest or Fast.com it was 300Mbps, but after upgrade to 1.7.3 it becomes around 100Mbps.... 

 

I verified the CPE throughput with Ethernet connection, it's still 300Mbps, so I'm sure that it's Deco M5's problem.

 

I'm just wondering if anyone encounter the same issue with me?

Thanks.

 

  @BeerBee 

Update, I found the lower throughput issue is caused by the total bandwidth of QoS default setting in 1.7.3 Build 20230906,

After tweaking it to 300Mbps, the download/upload throughput performance is back to normal.

  @budgie29 see my post from earlier this week; you can probably solve it by switching you Deco network to Router mode, reboot, then back to Access Point mode.

  @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? 

  @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?

  @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 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.