@JanRekenaar hi. I'd say it's worse. Updated, opened app, looked at network then went to check for updates. Deco rebooting. 

  @Orm53 iOS or Android?

  @David-TP 

Same exact thing is happening to me.  If I open the Deco app to view the client list, notice it has gone stale, attempt to refresh the list multiple times, this will eventually cause the main deco to reboot thereby disconnecting all devices.  Eventually once it is back up and running, the client list will reflect properly.  However, this issue returns after an hour or 2 of not being in the deco app.  And as others have mentioned, my mesh network works fine if I don't try to do anything in the Deco app, but that means I can't administer the network.  

Samsung Galaxy S24+ 

Deco App version 3.9.23 (last updated on March 26, 2025)

I routinely have 60+ devices connected at any given time, nearly 40 of which are IOT devices.  I have the IOT devices on their own 2.4 Ghz only IOT network and everything else on the 5Ghz only main network.  I have tried beta firmwares and beta app versions in the past for various issues experienced and at this point I am not willing to do that anymore because both my wife and I work at home and cannot tolerate the reboots.  I have been a TP-Link Deco Mesh network user since 2020 but I am about ready to jumpship because despite liking the TP-Link Deco Mesh platform and the simplicity of setup as well as the introduction of new features fairly regularly, there are simply too many problems being introduced that aren't being fixed quick enough despite numerous complaints from the community.  

I've also noticed that if you log into the web UI to grab system logs after the reboot, there are no logs available prior to the reboot, so it is impossible to even see what is occurring right before the reboot.  The logging capabilities need to be better in order to help troubleshoot these issues, starting with the ability to capture logs continuously.

  @RobertAN 

For everyone else running the X50 V1 (EU) and having the open client list -> reboot bug. I've installed the beta firmware 1.6.4 around 2 weeks ago after experiencing this issue for months, it finallly seems to te solved. I didn't had a single reboot since the update.

To test i used the IOS app quite heavily the last week also over several days, no reboot issues so far.
 

Only real issue found so far is that it looks like the client list is mixed-up sometimes and wrong client name / ip is shown, which also reflects in the reserve IP config (DHCP) and so results in wrong and even double reservations (so 2 different MAC addresses with the same IP reservation).

Link to beta 1.6.4 firmware
https://community.tp-link.com/en/home/forum/topic/736386

  @JurgenM thank you for your comment. I am running 4 deco X50 v1 EU 1.6.1 and I have iOS App Version 3.9.12 since last week. The first couple of days I had no disconnects and reboots: everything seemed fine. 
 

But now the issue is back. Could you please report back to us when you still encounter issues with 1.6.4? 
 

@David-TP  I have a strong feeling that "client identification option" has also impact on the clientlist not available -> reboot issue. I turned the option on, but it turns itself off after a day or so. And when I turn it back on : BAM decos go reboot. 

How I typically work is : I open the deco app. Cliënt list is messed up. I refresh the list. More than once : BAM. Reboot of deco. 

Regards 

Jan 

  @JanRekenaar 

Hi Jan, 

I've the feeling the issue isn't related to the IOS version but to the router firmware version. But this is nothing more than gut feeling.

Will let you know if i experience any issues with the new firmware, but until now still fine.

 

  @JurgenM thnx. I agree, I think firmware should fix this issue. I am on 1.6.1 and based on your experience with 1.6.4 I have good hope there will be a solution nearby when 1.6.4 is available. 
 

Problem I see is that when I will update through the app when 1.6.4 is available, the app and/or deco will crash during the update; as the app / deco reboot when using the app. @David-TP : what is your suggestion how to handle this issue?

  @JanRekenaar 

you can run the update from the router web interface so for the update you don't need the app. And yes keep it closed while updating, i can imagine you will brick the device if it crashes during the update.
 

That said I assume/hope/pray that they where smart enough at tp-link to disable all client access during the update. wishful thinking...