@Glen.Appleton 

Thank you very much for your kind feedback.

We have reported it to the senior engineers already.

At the same time, could you please help me check the following information:

1. After changing the device name, normally how long would it last?
2. During this period, have you cleared the DNS caches or done some changes on the smartphone?

Thanks a lot.

@Myapps 

1. Sometimes it would hold for about a day, other times it would already be changed back the next time I open the app (within hours).

2. No, there were no changes to the phone between the time it was set, and the time it reverted back.

Thanks for creating the bug report and submitting to the devs.

@Glen.Appleton 

Thank you for your detailed info, we would like to escalate this case to the engineers and ask them to investigate further. Please check your email box and respond, thanks.

Kevin_Z wrote

@Glen.Appleton 

 

Thank you for your detailed info, we would like to escalate this case to the engineers and ask them to investigate further. Please check your email box and respond, thanks.

I was informed that the issue is with the latest firmware version.  Any updates on if a fix will be implemented in the next firmware release, and when that might be?

Thanks!

@Glen.Appleton 

Hi Glen, thanks for asking, while we have no ETA for the new firmware yet, it is suggested to keep an eye on the official wesbite or on your router web GUI in case there is a new firmware available.

@Kevin_Z,

I installed the latest firmware version published 2021-01-29, which states that it fixes this issue (item #5 in the fixes list), but it does not.  While the new name does take initially on the details page for the router in the app, the device list is not updated.  After closing the app and re-opening it once, the new name is in the device list.  After repeating the close / re-open step one more time, the device name is reverted to "Archer_A7".

Firmware page: Download for Archer A7 | TP-Link (tp-link.com)

This issue still is not fixed.  Please let the developers and testing people know that it's still on ongoing issue that should be addressed.  Thanks!

@Glen.Appleton 

Thank you very much for checking. We have reported this to the developers to confirm.