@Fae Thanks, it successfully upgraded in stand alone mode, which is where I plan to leave until the adopt issues with the Omada controller are resolved.  With V5 I guess.

Fae wrote

Dear @runawayjimothy,

 

Here are the screen caps.  I'm not doing anything fancy here.  Clicking the "Upgrade" produces the error message I reported.

 

 

Thank you for your valued reply. I've forwarded this issue to the developer team to double-check the online upgrade process.

 

At present, if you still fail to upgrade the router by clicking the "Upgrade" icon, it's suggested to download the firmware and upload the bin file manually to upgrade it.

Thanks @Fae .  I have also tried downloading the firmware and manually upgrading.  The result is the same error message. 

Filename - ER605v1_un_1.0.1_20210113-rel35074_up.bin

Downloaded from this page - https://www.tp-link.com/us/support/download/er605/#Firmware

@Fae 

Update on my issue.....

My router reported a disconnected status overnight in my Omada controller.  To resolve that issue I rebooted the router.  Afterwards, I attempted the upgrade again from the controller to see if there was some transient issue contributing to my initial problem.  After clicking "Upgrade" in the controller, the device went through the expected upgrade process and is now running the latest version. 

@Fae Bought this, updated it.  And this thing is an unusable mess.  So many issues in this device.

The product description says multi-net NAT routing, but that tab doesn't even exist on this device. (With either original or update firmware.)

It seems like quality just took a giant step backwards.

Well, I take it all back.  I was misunderstanding some differences between the TL-R600 and this unit.  I got things sorted out and am a LOT happier with the TL-R605.  I think i was tired and annoyed last night and lashed out.  lol

I am old enough to know better and am gonna keep working on patience. 

@Fae I got two (2) symmetrical links running on the R605 (1.0.1 Build 20210113 Rel.35074) but I noticed that when the upstream of one port/link is not routing packets the device still keeps on sending traffic to that port.

Under the "Transmission" menu, I have the load balancing basic settings all checked/enabled.  Link backup is empty and online detection for both WAN and WAN/LAN1 is set to 'manual' with a ping and dns target of 8.8.8.8 (google's DNS).

When the upstream WAN is down, the Transmission->Load balancing->Online Detection->WAN shows port status as 'offline' (which is to be expected). However, the Network->WAN->WAN Connection Status shows 'Connected'.  I understand the rationale why this is so, it seems to be bound to the physical connection of the port and not routability.

I might have just missed a combination of settings (if so, appreciate if you can point this out) but just in case theres none, may I request that future patches allow the 'Connection' status of the WAN and WAN/LAN ports to also be affected by the 'Online Detection'?  Interface-wise maybe add an optional checkbox on the specific Network->WAN port screen. This way users dont have to physically unplug the dead link just to make the 605 route to the remaining one.

Thanks and I look forward to your reply.

json

 

@Fae 

The 1.0.1 Build 20210113 Rel.35074 has introduced a new issue. It resolved a number of things highlighted in this and other threads, however, every 2-3 days it will halt and fail. The only thing to do is a physical power cycle to get it to come back online. The App will report that the OC200 has disconnected and then reconnected on the Omada phone app several times, hence I know it is about to fail.

Looking from a web browser on the Devices screen it will state heartbeat missed, then adopting, It will do this a couple of times, before it eventually fails and the goes offline. Things will seem to be working from a client access point of view for a round 10 minutes, but then all internet access will fail.

The other thing that I have noticed is that the CPU will steadily ramp up in activity over the 2-3 days before the ER605 fails.

Yesterday, I removed the ER605 from Omada, did a full system reset by pressing the button on the front of the device and then adopted it back in to Omada. I am waiting to see if the 2–3-day failure cycle continues after this full reset.

I’ve attached a screen grab of the stats page for the ER605 from January until March 18 2021. The period from Jan 17 to Feb 22 it was running the previous firmware release. There seems to have been a memory leak issue as you can see the memory being consumed until it failed on February 22.

From Feb 22-March 18 it has been running 1.0.1 Build 20210113 Rel.35074 and you can see the restarts every 2-3 days.

Do you have any suggestions for a fix?

Thanks