@Number2 & @Jerryb 

So I have been working with support and am now on a debug version of the current code. I am letting it run until I see the issue so I can send to them, I am wondering if iether of you have had the 2.4 or 5Ghz drop sence. I have gotten the steps to go back to the old beta code that didnt have issue and have done a quick writeup in GitHub. It is actually a very easy process and just requires to first load on the Debug version of the current software. Perhapse if you both have the issue you too can load debug and let it get logs so this can be resolved. I am curious however if I just need the factory reset then change settings manually if I will or will not see the issue.

Anyway currently running loggind on debug code and will try to let you all know. I do have the procedure to go back to old code but plan not to do this unless it fails while in Debug. If you guys still have the problem please post, and Ill plan to post the instructions to go back to 1.0.7 P1 Beta code.

Currently running for debug, logging in progress.

@samadril @Number2 @Jerryb 

When I upgraded to the current firmware (from the beta), I started having 2.4 devices drop again.  I then enabled smart connect and haven't had problems since. Honestly, not sure smart connect had anything to do with it, or if making a settings change and saving might have helped.   I was very happy with the beta, which was rock solid for months.

@samadril 

Not had any dropout or problems with either 2.4 or 5Ghz. Turned power off and on too and all came on with no problems. 

Support previously asked if I had any backups which unfortunately I didn't. At least you gave them chance to see what's happens after a firmware upgrade as shouldn't really have to do a hard reset to kick it into gear. 
 

Hope it answers something! 
 

@shaywood @Number2 @Jerryb

I wanted to gice you all an update. So issue happened again and I sent logs. It appears that they saw the 2.4G encryption used was TKIP which is old and may have been causing issue. The setting that is under 2.4G Wireless is the AES/TKIP setting. You would think it would default to AES but aparently is is not. I did go back to the old code and did not have the issue at all. I get logs running old code and sent to support where I did not have issue. I wonder on that old code if the setting did force AES, and then moving to the latest under that setting a regression allowed it to go back to using TKIP.

Long story short I have gone back to the latest code, BETA version supplied by support so I can monitor. I did see my restored setting did in fact set to "TKIP/AES" as the encryption option for 2.4G. I have now set to AES only and will monitor while logs collect. I am actually hopeful that this is the issue and that with so many devices, all possibly defaulting to TKIP encryption, there was an eventual failure that could only be cleared by a reboot.

@HERE - I wonder if you could look at your setting now that you have done hard resets. See if you are indeed set on a hard reset to AES only? Very curious. Also if you feel adventurious, backup your current setting and then load in those old setting that did not work and caused failure. I would love to know what that setting is? "TKIP/AES" or "AES" only. Please dont feel you have to by any means just very curious. I have included the reply from support and screen shots of the setting that may be causing the failure and what it should be.

#######################################################################################

#######################################################################################

@samadril   hello each of bands is set at AES. Had to turn off smart connect yesterday because the router wouldn't allow me to add a new device. 

Anyone have the instructions for completing a factory hard reset?  Is it the 30-30-30 method?

@shaywood Thanks for the update. Looks like AES only setting when you have alot of 2.4G Devices might be the way. Has only been over a day but still up without issue, Will continue to monitor.

@samadril Any chance you're able to share that beta firmware? I've been experiencing random disconnects from my 5G networks and am curious if it's known bug that's fixed in the version you're running. I'm on the latest stable firmware and have tried multitude of things to resolve but still happens. Thanks.

@tarund I have no problem at all sharing the information I learned in dealing with this issue. I like to take notes on items I may need to remember and put them in GitHub. Feel free to look over what I wrote based on what I was supplied by TP-Link. I hope it helps but remember you are on your own should you use the information, and if you are not technical or something doesnt make sence, reach out to TP-link directly. They will help and even do the steps remotely for you.

Link to personal notes in GitHub (GETTTING BACK TO OLDER FIRMWARE): https://github.com/samadril/tech-help/blob/main/tplink/README.md#tp-link-and-router-help

@HERE  - If this helps anyone else I feel blessed I was able to help but know this is just my notes on what to do based on an email from TP-Link support and not official.