@TP-Link 

Dear forum members, it was nice being with you... 

It was sad to see that TP-Link:

 - abandon its customers

 - don't care about correcting unacceptable errors for a mesh system, 

After years of problems & swearings, I found the definitive solution. 

I finally threw the deco S7 in the bin and bought a new mesh system.  

Ps I switched to Fritz!Mesh 

 Wow!!!!!

 More expensive but an epochal turning point.

 I recommend it to everyone. top software and applications, maximum configuration, works great with HomeAssistant and even the Mesh is definitely better, another planet.

 Goodbye TP-Link

  @TP-Link Still checking this page since 3 years ago. Still not fixed

  @TP-Link I installed a new set of Deco M4s for a relative and found that the option to set the WAN port now exists in the settings 

I checked my own M4s and they have the same settings available for picking the WAN port but I don't see the M4 on the list of Decos which have been 'fixed'

  @TP-Link 

Adding to this thread. It has been YEARS and you still haven't fixed this simple thing?! 

I finally found this thread after multiple times where my internet was down and my Hue hub wouldn't work. Now I know it's know Hue is YOU. 

This is a completely stupid design. FIX IT

  @TP-Link Wow, this thread is still alive. I will say it again: deco wont be fixed, because managed deco would be omada - and that will never happen because of pricing and market positioning. Im glad i returned mine in time (thanks to this thread).

  @nlow2323 

I just thought to check this thread to see how long it had taken for TP-Link to fix this issue.

My last post was in July 2022. I can't believe they are still so incompetent (or just don't care in the least about their customers) to have continued to ignore this.

I gave up on TP-Link totally at that point and replaced my Deco M5s with an ASUS router (that has the ability to add to it as a mesh but that has not been needed yet) and have had not one single problem from that day.

I binned the Decos as I was not going to inflict these on anyone else.

I would advise anyone that's having this problem with TP-Link to just jump ship now as I did.

  @TP-Link 

FIX YOUR ROUTERS!

• Given that the issue arises only when the ISP modem fails to assign an IP address for the main Deco, once the cable modem recovers,  the problem should be resolved. It is suggested to contact the ISP to restore the modem connection as a priority.

 

• The current workaround would be connecting the wired servers to the satellite Deco units instead of the main one.

  
Given that the BE65 model released last year, I expected it to have an option to disable auto wan sensing. But instead, I'm greeted with a mess. All 4 Deco models (M9+, X50 X68, BE65) I've owned have different settings and features, some have a Speedtest option while some do not.

Seriously, your workarounds are complete nonsense. No way I'm having a nas in my hallway or bedroom. ADDITIONALLY, THE WHOLE POINT OF A NAS IS SO YOU CAN ACCESS FILES EVEN IF THE INTERNET GOES OUT - WHAT'S THE POINT OF HAVING QUAD 2.5GBE IF I CAN'T ACCESS HOME ASSISTANT OR MY NAS WHEN THE INTERNET GOES OUT? I SERIOUSLY WOULD HAVE GOTTEN UBIQUITI IF THEY WERE SOLD IN MY COUNTRY.

The whole Deco “easy and simple plug-and-play” nonsense completely ruins the experience. Anything logical to have is stripped away in the name of “simplicity.” I would’ve recommended TP-Link routers to my family and friends, but Deco’s obsession with dumbing everything down just makes the whole thing a frustrating mess.

  @BadRouters which doesn't work !

the 'workaround' doesn't work, my deco's are setup as AP's and I have a router from another supplier running open wrt and my decos all go offline if there is no broadband/internet access