@Ethan-TP Here's a video of the login prompt. As you can see when the blue select line freezes for a split second every 2 seconds, that's when character input also freezes and won't accept any key input while it's frozen. It results in bad username and password input requiring many attempts to log in.

*stream*able.*com*/rrl2vp

remove the * from above link

  @Ethan-TP Ok, email sent. Thanks.

  @MrTom 

Was there ever any word or resolution on this issue??? 

I am experiencing the exact same issue on my ER605(2.3.3 Build 20251029 Rel.18054) I was able to notice in browser dev tools under network.... There is a POST for locale?form=lang occurring at the same frequency as the stutter. It makes it hard to log in. I've attached an image to show the HTML running.

I also noticed this behavior does not occur in the tplink emulator for this version.

See attached screenshot.

 

  @becantew No resolution yet for me. They apparently don't see it as a bug. I posted a video of it happening. I've sent an email to support 5 months ago. They don't seem to care. I'm surprised they can't reproduce it themselves. I've seen it on 3 different ER605 routers with firmware 2.3.3. It does make it difficult to log in when key input keeps freezing every 2 seconds.

Luckily for me the main ER605 I deal with on an almost daily basis is controlled by an OC200. But when I have to log into the other ones it gets annoying.

  @becantew Ok, I ran the JS through chatgpt, and it basically says "The exact line causing the repeated POSTs is effectively: $ . su . locale . get() inside the recursive timer loop."

It also says "Possible synchronous AJAX. If $ . su . locale . get() internally uses synchronous XHR (async: false), the browser UI will freeze during every request."

"setTimeout(function()  [t()], 2e3)" basically sets the timeout for 2 seconds (2e3=2000 milliseconds). It also found the login.html polling loop every 20 seconds too. It could also show how to rewrite it safely.

This is probably checking whether the router language/session changed.

The freezing happens because:

1. The request runs continuously forever.
2. The device at 192.168.1.1 is probably slow (embedded router CPU).
3. If the AJAX call blocks UI updates, the browser main thread stutters every poll.
4. Multiple overlapping requests may accumulate if responses are slow.

But nothing we can do, though.

  @MrTom 

TP link replied to the other thead on this https://community.tp-link.com/en/business/forum/topic/860954?replyId=1692476 to try the latest beta firmware and see if this helps. I planned on trying this soon.

  @becantew Cool, thanks. I'll try this later on my home router. I'm not trying any betas in my production environment. :)