May I know how do you locate the three Deco units? Are they wired together or set up via wireless?

All the client devices will experience the interrupted issue or only some specific devices? When internet gets interrupted, will the client devices disconnect totally from the Wi-Fi network or keep connected but without internet?

Open Deco App, tap "More" at bottom right corner, then tap on "Wi-Fi" and switch off the 5GHz network (or 2.4GHz network), then check if the issue is still there.

I have this same issue, I have two Deco M9 units and both 2.4 and 5ghz frequencies enabled.  When in the same room as my Main Deco unit and not moving (connected to a strong 5ghz channel), I have several wifi connection drop-outs from the network whilst on a video call.  The next morning, this time in the same room as my secondary unit and again not moving, I was on another video call and the same connection disruption issue.  I have had no issues with my wifi connection up until I swapped out my standard modem/router for the M9 this week.  Please advise.

Same here. Devices connected wireless (8m distance, almost direct visibility), 2.4GHz and 5GHz (also tested only 2.4HGz). Also "Fast Roaming" doesn't looks working as when I go to other room, phone reconnects.

Have a 3 deco m5 set up.

Deco 1 (Wired - Main)

- Has most wireless devices connected to it including two working laptops often on video calls

Deco 2 (Not Wired) = middle of home, apprx 5 metres from Deco 1

- approx 4-5 wireless devices connected

Deco 3 (Not Wired) = end of home, approx 12 meters from Deco 1, and 7 metres from Deco 2

- approx 1 wireless device connected

I completely lose connection at least 3x a day, and they often happen approx 12pm, 3pm and 8pm everyday. It varies. I have not been able to find an activity on any of the devices that trigger the wifi interruption

• The Deco 1 wired is connected to an ASUS RTAC88U directed via ethernet. Wifi on the ASUS RTAC88U has been completely turned off and I've checked. 
• Deco is setup as Access Point, not router.
• I have dedicated IP addressed for each of my 3 Deco M5s on my ASUS router.
• I have the latest firmmare update for the Deco M5 as of Apr 1, 2020.

Please help. This only started 3 weeks ago, and has been happening every day. 

I have the same issues as FPope. I have three M9 with a very good WiFi coverage now, but poor experience. When I switch to cable or 4G all works as expecyed, no connection timeout/interruptions. Please could you provide some help how to diag the Deco Wifi essues?

I can see alot of "MSGQ :: CsrMeshGetMsgFromTxQueue" in the DECO log.

-----------

Sat Apr 4 11:25:04 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:25:04 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:25:04 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:25:14 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:25:14 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:25:14 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:25:14 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:25:14 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:25:24 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:25:24 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:25:24 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:25:24 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:25:24 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:25:34 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:25:34 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:25:34 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:25:34 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:25:34 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:25:44 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:25:44 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:25:44 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:25:44 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:25:44 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:25:54 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:25:54 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:25:54 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:25:54 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:25:54 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:26:04 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:26:04 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:26:04 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:26:04 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:26:04 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:26:14 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:26:14 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:26:14 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:26:14 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:26:14 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sat Apr 4 11:26:24 2020 user.err csrMeshGw[5306]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Apr 4 11:26:24 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Apr 4 11:26:24 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Apr 4 11:26:24 2020 user.err csrMeshGw[5306]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Apr 4 11:26:24 2020 user.err csrMeshGw[5306]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Seem problem, any update?

@ jun.y  That problem I had with firmware 1.4.4 which is the latest for M5. I had to downgrade to Beta 1.4.2 and everything works fine.
I have the configuration as a router not as in your case that you have it as an access point.

@Rioja I'm having the same issue. How do you do the downgrade?

Thanks in advance.

BR.

Jose.

@drv_au  Good morning. Confinement gives for many things.
I want to apologize for this and some more hasty post, regarding the firmware update 1.4.4 for Decos M5.
I commented that I had to downgrade to beta firmware 1.4.2 and I did so. I decided to give the 1.4.4 firmware another chance, I reinstalled it and I can say that it works perfectly for me, even better than 1.4.2, I think the first day I installed this firmware, a five-minute storm was the culprit for the failures that I perceived. and rush to degrade.
I apologize to TP-Link to Kevin and all the foreros who have been able to read my unfortunate post, judging firmware 1.4.4 as faulty. It works great for me!
Health for all