@Igor87 Yes, this behavior has been reported by some users and is likely a firmware-related issue rather than a configuration problem on your side. Since the extender settings (SSID, password, etc.) are retained but only the device name resets in the Tether app, it suggests the custom name isn’t being properly saved to the cloud profile after reboot.

 Hello @Joseph-TP, yes I have received the email related to the ticket escalation, thanks!

Joseph-TP wrote

What are the other TP-Link models you have? 

You mentioned that ' it always takes some time to find the correct one to connect to.' Do you mean it will revert to custom settings instead of the default settings?

With this I was referring to the fact I have 4 RE705X, and when they are rebooted they all appear with the same "RE705X" name in Tether, so I have to check connected devices to understand exactly which unit am I connecting to.

It worth to mention that this only happens with "Cloud Devices" and not "Local devices", since when I am connected to the same local network of the extenders, the "Local Device" name is preserved across reboots. When I connect with mobile connection instead (or via wifi from another network) i see the default "RE705X" name.

The main network router is a NX200, but i also have 2 BE3600, another NX200, a MR600, a RE305 and a RE500 that do not have this issue at all.

As @brevishead said, it just seems RE705X name is not properly saved to the Cloud (but it is correctly saved locally).