@jonod 

Cant say I have ever come accross this issue, but it does sound like your browser or network stack, and not the OC200 if honest.    Are you going via a router or are the devices connected via a switch?

I have seen home routers do strange things like this, ultimately they are routers and not switches so LAN traffic is not their best hand and packets do get lost.    What browser are you using?   Firefox is good, find it works best personally for the controller.

  @jonod 

Try disable some advanced settings like auto backup, reboot schedule etc. When the controller is operating something, it may not have enough RAM to provide the web interface

  @jonod A couple of tips, that I've seen another user found.  Try doing a hard refresh of the webpage (often Ctrl + F5, depending on browser).  And clear the cookies and site data for the controller from your browser, you should be able to find it for the IP address in the list of site data.

Also if you are signed into Omada Cloud on the controller, try using the TPLink Cloud site to get to the controller, and see if it is slow there too.  omada.tplinkcloud.com  The Cloud site is free, and can be used for a controller on your local net.

 Thanks everyone for the suggestions, much apprecaited!

Philbert wrote

  @jonod 

 

Cant say I have ever come accross this issue, but it does sound like your browser or network stack, and not the OC200 if honest.    Are you going via a router or are the devices connected via a switch?

 

I have seen home routers do strange things like this, ultimately they are routers and not switches so LAN traffic is not their best hand and packets do get lost.    What browser are you using?   Firefox is good, find it works best personally for the controller.

 

My current router is an ER605. Both the computer and the controller are connected to a SG2008P switch. If it was an issue with the network stack I would have thought I wouldn't be able to ping the controller successfully or view the http://{controller IP} page? And yes, using Firefox, but the issue persists with Edge (chromium) as well.

Somnus wrote

  @jonod 

 

Try disable some advanced settings like auto backup, reboot schedule etc. When the controller is operating something, it may not have enough RAM to provide the web interface

Whilst I do have those settings enabled, they are all set to run in the middle of the night whilst nothing is in use. Regardless, if this is the cause that's very disappointing, TP link shouldn't be selling a controller not capable of running its own software fully.

JoeSea wrote

  @jonod A couple of tips, that I've seen another user found.  Try doing a hard refresh of the webpage (often Ctrl + F5, depending on browser).  And clear the cookies and site data for the controller from your browser, you should be able to find it for the IP address in the list of site data.

 

Also if you are signed into Omada Cloud on the controller, try using the TPLink Cloud site to get to the controller, and see if it is slow there too.  omada.tplinkcloud.com  The Cloud site is free, and can be used for a controller on your local net.

I just had it fail to load the controller before posting this message, and would you believe the control F5 worked and the page loaded! Ill try clearing data next time if it persists and the F5 doesn't work, but it will be interesting to see if this is the fix! I'm not signed in to Omada cloud because I'm a firm believer in keeping everything local that I can (and I can just VPN in to the network regardless if requried), but given that the mobile app works fine maybe the cloud would work ok too regardless?