TP-Link network specs:

EAP670 x 4 (v1.0) all on firmware 1.0.6

EAP610 Outdoor x 1 (v1.0) on firmware 1.2.0

4 TP-Link Jetstream switches

Omada Controller v5.12.2 running on Windows 11 x64 PC w/32GB of RAM, N5105 CPU

I have a scheduled reboot that occurs ONCE a month on the 10th of the month in the middle of the night. So this is not causing this issue. I have a settings/client history backup scheduled to run at 5AM every day. There have been no problems with the site settings/client history backups, and the backup files are about 3MB in size. 

My network (with all the devices listed above) has been running rock solid for many MONTHS with no issues. This "failure to readopt" literally started happening on Aug 27th, out of the blue. Nothing has been added to or changed on this network for at least a month.

I've woken up twice over the past week, once on Aug 27th, then again this AM (Aug 29th) where I noticed a couple of my EAP's were in "adoption" mode randomly, with "failure to readopt" messages. I went ahead and rebooted all of the switches and EAP's from the Devices area within my Site, and the EAP's all provisioned and connected normally. In BOTH cases where "failure to readopt" first occurred, on August 27th and August 29th, the issue seems to have cropped up beginning at 3:30AM EST, then other EAP's dominoed with the same issue a few hours later. I have nothing scheduled to run at that time - no backups, no automated reboots, etc. 

The only useful response I've read on this issue is to uncheck "AI Roaming," which I have had enabled for over 6 months without problems. I've unchecked it to find out if that resolves anything. I have my doubts. 

I've pasted my network topology for reference.

Any suggestions or ideas on what might cause this "failure to readopt" EAP problem? Is this problem with the Omada Controller or the EAPs? I suspect it's a controller problem, perhaps a bug or some issue with 5.12.2. I've been running 5.12.2 since it was released (over a month ago).