Updated via Tether but Can't Find the Change Log

Updated via Tether but Can't Find the Change Log

Updated via Tether but Can't Find the Change Log
Updated via Tether but Can't Find the Change Log
2 weeks ago - last edited 2 weeks ago
Model: Archer C80  
Hardware Version: V1
Firmware Version: 1.13.15 Build 240812 Rel.53634n(4555)

I recently performed an update on my device via Tether, but I can’t seem to find any details about what changes were included in the update. I also checked the official website but couldn’t locate this specific update or its release notes. Is there another way to access the change log or learn more about what this update included?

For reference, the device is an Archer C80 V1, and the update version is 1.13.15.

  1      
  1      
#1
Options
1 Accepted Solution
Re:Updated via Tether but Can't Find the Change Log-Solution
2 weeks ago - last edited 2 weeks ago

  @gilnet 

 

Hi,

 

TP-Link's regional product websites are sometimes not being updated on time.

 

You can check out their "Global" / "Worldwide" webpage and see if firmware version 1.13.15 shows up for you. For some reason I need to click my browser's Refresh button several times before the information for 1.13.15 shows up.

 

https://www.tp-link.com/en/support/download/archer-c80/v1/#Firmware

Recommended Solution
  1  
  1  
#3
Options
2 Reply
Re:Updated via Tether but Can't Find the Change Log-Solution
2 weeks ago - last edited 2 weeks ago

  @gilnet 

 

Hi,

 

TP-Link's regional product websites are sometimes not being updated on time.

 

You can check out their "Global" / "Worldwide" webpage and see if firmware version 1.13.15 shows up for you. For some reason I need to click my browser's Refresh button several times before the information for 1.13.15 shows up.

 

https://www.tp-link.com/en/support/download/archer-c80/v1/#Firmware

Recommended Solution
  1  
  1  
#3
Options
Re:Updated via Tether but Can't Find the Change Log
2 weeks ago - last edited 2 weeks ago

  @woozle thanks refresh seems to work! 

But it's a weird bug anyway.

  1  
  1  
#4
Options