@Virgo

There are no entries in the reboot schedule (took me a few minutes to locate that).

In any case, the entries are not at a regular time. They happen more or less randomly, more often than not during day time.

They don't happen every day.

Also, if the router was rebooted, I'd expect its uptime to reflect that. I have 7 readoption entries over the uptime of the router.

Arguably, on average, that's an entry every other day. There's one day where it happened twice though. Pretty random...

In terms of patterns, these last 7 entries are not followed by a "was connected" entry.

Earlier on, while I was setting things up, there would be a connection entry within seconds of the readoption entry.

One of my PCs is connected directly into the router as a side effect of trying out the discovery tool (more on that in another thread).

I never bothered to change ports again.

I've only noticed the "dropouts" while browsing and didn't know about the re-adoption entries last time I had such "dropout".

They are very transient too (browser shows a ERR_INTERNET_DISCONNECTED (not sure, barely time to read) for couple seconds but then refreshes)...

Now that I know about the readoptions, I will remember to check if I notice them around the times of browsing dropouts.

I have not noticed glitches while streaming or playing online (on other devices) so it could be that machine or browser...

The router is plugged in directly in my ISP's fiber ONT (upgraded couple weeks before I got this tp-link gear).

I'm not aware that I can monitor anything on this device...

In any case, I'm not sure how an ONT issue would affect connectivity of devices within my LAN.

I'm seeing this as well, where all Omada devices would get readopted automatically every couple hours at random intervals. Any troubleshooting advice appreciated!

Device uptimes show no interrpution.

Log shows all connected clients would be disconnected and connected again each time this happens.
All devices and AP's have static ip's. 

Controller: OC200
Router: ER605 v1.0
Switch: TL-SG2210P v3.20
EAPs: EAP615-Wall(US) v1.0

This is happening to me as well.  I was having issues where it would get disconnected, but that is not happening anymore, or it has not happened for the last several days.  I see several of ER605 router was readopted automatically, then was connected only to repeat the process.

I wonder what is going on?

  @Virgo Thanks for taking the time to think about my issue!

The OC200 is 1.0 with 5.1.7, and all other devices have current firmware as well. 

This is a fairly new install and I've only recently discovered where to view the events log, so suspect that it has been happening since the beginning. I'm afraid I couldn't pin this down to a specific change. Topology is pretty standard (attached).

I had a couple hypotheses after my original post yesterday: 1) When I ordered the components from Amazon, only the switch had been previously used and returned (but sold as new). Maybe an intermittent issue with the POE delivery would cause an occasional disruption to the hardware controller and EAP's. 2) The OC200 also runs fairly hot, which I read that others have experienced as well, but maybe I could try reducing it's load.

So I tried reducing broadcast power on all EAP's to medium, turned off Fast Roaming, and restarted every network device. So far no more readoptions but I'll continue to monitor, and try bringing power then Fast Roaming back up individually. I'm not convinced it was just the restart that fixed it, since I've also done that a bunch when cable managing. 

@Virgo, I have the same controller versions as Hua (v1 & 5.1.7).

OTOH, only my router is being re-adopted periodically and I'm not seeing the connected events either (apart from one time when it is preceded by a disconnected event).

Interestingly, the problem seemed to have disappeared for a few days (6/2 to 6/8), only to reoccur since yesterday.

All devices have up times greater than 2 weeks and I have not made significant changes.

In fact, the only I recall having made within the last week is re-enabling syslog logging.

My topology is similar:

BTW, is there a network diagram tool that people recommend?

I've seen diagrams with additional info (e.g. VLAN) that I'd like to maintain...