@LaMpiR 

Got a reply with many questions to be answered:)

1. Where did you see this information? Could you please take a screenshot of the error message and CPU, and send them to me?

2. When did this issue happen firstly? Did it work fine before?

3. Can you still get an internet connection with Deco?

4. How many Deco units do you have in total? Try to reboot the Main Deco. Will this issue still happen?

5. Usually how many devices are connected to the Deco?

What are they, like laptop or NAS? When the connection of 5GHz drops, what are their network behaviors? Like large flow downloading, playing games?

@Double_Jay 

Thank you :) So a first level support. I will add those info to my existing ticket (third day no reply). 

@FireDZ 

I disconnected my two AP deco's.

Now running with only the router.

CPU load spikes to 60% (was to 100%)

Minimum CPU much lower at 3% (was 9%).

I guess average CPU about 30% (was 70%). 

No disconnects so far. 

The problem can be pinpointed to the backhaul/AP's?

Will try later with router and one AP, 5 meters away.

@ReneP Interesting you tried this, I disconnected one of the APs and I am running just the Master and one remote AP and I have had better stability however still the same errors in the logs.

@ReneP 

I don't have any drops, sometimes it stops just, but happened in the last 5 days only few times. Mine are working in access point mode, so they shouldn't have high CPU usage at all. 

I only have 5Ghz setup, because 2,4Ghz remained on my main router and I have maximum of 4 devices connected: 2 phones, 1 laptop and FireTV stick. 

I am just testing the system because I want to install it at my parents house, but maybe I should go with the M4 and simply use an ethernet backhaul system. 

I have created a ticket with TP-Link Germany support on 25. June and still haven't received any reply back. 

Been contacted by tp-link support requesting further details:

- ISP / Modem model

- Details of Deco units

However, no update in regards to possible root cause/s or a resolution (e.g. Firmware update, etc).

Will update when I get more info.

tp-link support have been back in contact to advise the matter is being escalated to one of their senior engineers.

Will update when I have more info.

Wed Jul  1 08:16:41 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::fb is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1000 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1000 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1000 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1000 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1000 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1000 is link-local multicast address
Wed Jul  1 08:16:42 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:1003 is link-local multicast address

following this one, as I have also lots of these warnings and disconnects since the last FW upgrade...

FireDZ wrote

tp-link support have been back in contact to advise the matter is being escalated to one of their senior engineers.

 

Will update when I have more info.

Good to hear, looking forward to a solution because the stability of my connection hasn't been worse.

Do you guys also have this notification is your logs?

Wed Jul 1 09:00:12 2020 daemon.notice nrd[4279]: wlanifLinkEventsCmnGenerateDisassocEvent: Client DC:72:9B:87:75:F6 disassociated on APId 255 ChanId 9 ESSId 0

Wed Jul 1 09:00:12 2020 daemon.err client_mgmt: wireless client associate or disassociate.

Wed Jul 1 09:00:12 2020 daemon.err client_mgmt: client_mac:DC-72-9B-87-75-F6, client_ifname:ath0, client_action:disassociate

Wed Jul 1 09:00:12 2020 daemon.err client_mgmt: client(DC-72-9B-87-75-F6) disassocaite by if(ath0).

Disassociate seems like a broken connection for some reason?

(Here's another thread with this issue: https://community.tp-link.com/en/home/forum/topic/211810?page=1. @ReneP suggests "Seems to me that cpu load gets too high with 3 deco p9 installed." ).