@David-TP No problem, log submitted.

About another subject, I have a Nuki smart lock, the 3.0 pro model and I notice a lot of disconnections.
Fortunately the smart lock reconnect quickly and I can use MQTT again.

Nuki have made some optimisation in firmware but I still observ the same disconnections.

Someone at Nuki told me the following: "You could try changing your WiFi DTIM interval to 3 if your router allows it. In combination with the “Medium” power saving setting this will lead to the Smart Lock not skipping anything on the network."

Unfortunately, it is not something we can change with Deco except if I miss-understood something.

Do you think a solution could be found? Because I am pretty sure I am not the only person who use a Nuki smart lock 3.0 pro on a Deco network.

When I connect my smart lock using other network, I don't observe any disconnection.

  @TP-Link 

i have 4 Deco M5 with firmware Deco M5_1.7.1_Build 20230608 but Connection Alert not working. This is a bug into app/firmware or M5 don't have this function anymore?

  @leogz 

If you are in accespoint mode:

"NOTE: The Connection Alerts feature is not available when Deco works in AP mode."

https://www.tp-link.com/en/support/faq/3022/

  @Er1 no, im in router Mode.

  @David-TP 

Ive reverted back to firmware 1.6.1 via the recovery tool.

I am still experiancing drops. Still mainly of the esp8266/esp32 devices.

I factory reset all Deco's one by one.

Network is on the same channel it was on a months ago (before issues).

Since ive also read that some devices battery drain faster since the update I suspect that perhaps the radio rom also had been updated. And that this update persists, even while downgrading. Regardless of the regular deco firmware.

I also notice on for example my phone, wich does not have connection issues that the signal strenght is reduced.

Coult it be that since firmware 1.7.1 the transmission power has been reduced?

  @TP-Link 

Hardware Model: Deco M5 3.20 (us)

Number of Units (decos): Only one (1) unity (as router on pppoe mode)

Current version: Deco M5(US)_V3.20_1.7.1 Build 20230608

I live in small apartment with only one deco as main router (with pppoe mode):

On versions 1.61 and 1.65 (us model 3.20) The Deco M5 in general is very stable: (lan is perfect, and wlan wifi2&5 is perfect).

Since,  1,7.X  versions, i have 3 disconnections per day wlan side (wireless 5ghz), lan is perfect!

Tp-Link engineers, please read my logs bellow and take note of my explanations: (I use voidlinux, and use wpa_supplicant in debugmode with a ax200 intel pci-e wireless adapter) POWER SAVE IS OFF and PCI is on MAX PERFOMANCE.

Disconnection Type 1: (3 beacon losts) without disconnect SSID session on wifi adapter:

2023-08-22T16:28:45.05991 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-22T16:28:45.16226 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.19308 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS

Disconnection Type 2: (5 beacon losts or more)  disconnecting SSID session on wifi adapter:

2023-08-22T16:28:45.05991 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-22T16:28:45.16226 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.19308 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.29555 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.39786 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS

wlp2s0: CTRL-EVENT-DISCONNECTED bssid=30:de:4b:48:XX:XX reason=4 locally_generated=1

When this beacon losts occur? (logs on debug mode on deco M5v3.20 US)

When MESH (daemon), scan all devices on wireless network to measure wifi signal of clients for realize the deco swap. (with 2 or 3 decos). On my case, with only 1 unity, (disable mesh mode on all clients in deco app), this problem occur with low frquency. And i discover after 1 or 2 days without found wifi mesh clients (with mesh mode disable set on deco app), this daemon enter in sleep mode and the deco operates perfect, like 1.6X firmware versions. 

I will generate the log on deco M5, when the problem occur and post bellow:

Please, Waiting for I catch the entries and post here... (to be continued)

SUGESTION FOR DECO ENGINEERS OF M5 FIRMWARE:  (PLEASE READ)!

Because Deco Mesh system uses ARP protocol to generate temporary client keys and and use a daemon to measure the signal, the beacon interval time value dont be set as Beacon Interval = 1, as default tplink routers (without mesh), like Archer c6v3, Archer C9v2 (my old tplink routers).

Increase the beacon interval time to Beacon Interval = 2 OR 3, will give to deco m5 more time to wifi clients respond and more time to mesh daemon do a network scan, renew arp generate wifi keys without disconnect wifi clients. (or other decos)

  @David-TP first of all, do you know if my log has been received?
I still had no reply, which looks strange, first time I have a so long delay without reply from the support.

At last, I have some precision about Espressive devices not shown as connected.
I tried to send a HTTP request at boot on one of my ESP devices, I use ESPHome.
As soon as I send this request so as soon as my device communicate externally to my local network, it is displayed as online in the Deco app.

But it is named "in-addrarpa" instead of expected name.
Then I re-uploaded the firmware which does not make this request and restarted the device, some minutes latter it is not displayed again as online.

So it looks like a device is not considered connected to the network while it has not sent any request to WAN.

More information:
If I keep the firmware which send a http request on boot, it is displayed as online.
A few tens of minutes latter, the device is displayed offline again.

So if a device does not communicate externally at all after its first request WAN, it is considered offline in the Deco app.

I'm also experiencing issues since updating the deco's to the latest firmware, unstable, dropouts, Slow web browsing, I have now stopped using them, how can I revert the firmware to the most stable one?