@budgie29 thnx for the update. 

Same problem with 2 camera's now. I never get this error before the update.

Now my 2 camera's go offline and don't come back online.
I need to reset the power adapter on both.

This is what I get back in the log:

Tue Jun 28 02:50:14 2022 daemon-info hostapd: ath0: STA XX:XX:XX:XX:XX:XX IEEE 802.11: disassociated due to inactivity
Tue Jun 28 02:50:15 2022 daemon-info hostapd: ath0: STA XX:XX:XX:XX:XX:XX IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

Wed Jun 29 02:08:49 2022 daemon-info hostapd: ath0: STA XX:XX:XX:XX:XX:XX IEEE 802.11: disassociated due to inactivity
Wed Jun 29 02:08:50 2022 daemon-info hostapd: ath0: STA XX:XX:XX:XX:XX:XX IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

(address changed to XX).
(i have a - instead of a . done between daemon and info because the forum tells me not to post a link)

Do you have any idea how that is possible and how I can solve it?

  @TP-Link When is it going to be available in Brazil?

 Thank you!

  @TP-Link 

Well I also updated to 1.6 which was offered by the app on my phone last week.

Last couple of days I have been battling with my smart switches at home. On/off dropping off the network constantly. 

Pretty dangerous since some of them are switches that turn on lights on the stairs.

Deco's are in AP-mode. Raspberry pi does DHCP etc .

Edit seems not only the smart-life things are dropping off the network but while checking the Sonoff switch dropped off the network.

Edit 2 : checking and it's full of IEEE 802.11: disassociated on these devices which was never ever a problem before.

Edit 3 : checking the logs on home assistant my Xiaomi smart stuff is also battling ... like all other stuff on the wifi. The logs are being filled up with them dropping on / off the network.

Edit 4 : The one that is connected wirelessly doesn't have a hostname. Like why?

Turning on guest mode to check cannot be done since the switch is run on home assistant. I can see the log of that one. Seems to be on/off all of the time since I probably switched to 1.6..

And yes : 'MESH' setting is set to off.

Full reboot done

Wifi smart switch reboot done

I have 3 x M5. 2 of them, main and other are connected via cable and have most smart stuff on it.

I should have checked this forum before I did this.

How can I go back to the latest version?  If I can not I would like to get new M5's on version 1.5.

I will be travelling soon and I cannot afford to not being able to control or monitor my devices when not being home! 

  @JanRekenaar 

Jan, I think it is the handover protocol that manages the device to switch to an AP that has a stronger signal.

Check these protocols  IEEE 802.11k/r/v  TP-link to correct me.

In my case. 40 minutes ago I reconnected and switched on my R7800 router and enabled 2.4GHz and the same SSID and pwd as a matter of test.  Disabled the 2.4GHz on the M5.  Guess what. All devices, even 2 floors up with very weak wifi, have been up and running since I have switched the R7800 on. 

Something seriously wrong with this firmware I guess. 

  @Lukesan 

Lukesan wrote 

I reconnected and switched on my R7800 router and enabled 2.4GHz and the same SSID and pwd as a matter of test.  Disabled the 2.4GHz on the M5.  Guess what. All devices, even 2 floors up with very weak wifi, have been up and running since I have switched the R7800 on. 

Can you explain again, why you can't do that same thing with Deco Guest Network? I have smart switches connected to Guest Network that runs on 2.4GHz only, they do just fine with M5 running on firmware 1.6. My Deco mesh runs in AP mode and here is its WiFi configuration:

  @Alexandre. 

Well first of all why would I have to run stuff in Guest mode when it worked perfectly before?

I would like to use the stuff I buy and pay for the way it is supposed to be used for. Also my Guest network uses a different SSID and I still plan to use it as a guest network. 

As I see it now with your configuration there is no automatic switching between 5GHz and 2.4GHz when walking around in area's where 5GHz is not that strong which is also a no go.