Archer AX53 IoT config lost after reboot or power loss
Archer AX53 IoT config lost after reboot or power loss
Hi here, in the last firmware, has included a separated network for IoT devices. When power lost or reboot the router, this network turning off, and must enter in his config an enable again. Please, fix this with a firmware release and not abandone it.
Greets.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, for this issue, you could also refer to the solution in this thread: Archer AX53 V1 and Archer AX72 Pro V1 IoT Network Config Lost after Reboot
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for the feedback.
Do you mean only the IoT network settings lost after reboot or power loss, or all the configurations will be lost including the login password, customized main WiFi settings etc.?
Please share with us your configuration backup file and send me a private message to provide the login password, we will try to use the same router with the same configuration for testing to see if the issue can be reproduced on our end.
- Copy Link
- Report Inappropriate Content
@Sunshine i sent encripted config here and in private msg the password to decrypt it.
- Copy Link
- Report Inappropriate Content
In another tests, I turned into router mode and the IoT wifi not lost, only in bridge mode, may a bug with the bridge mode.
Greets.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Yes, in access point o AP mode, in router mode doesn't lost the IoT Wifi config.
Greets.
- Copy Link
- Report Inappropriate Content
To assist you efficiently, I've forwarded your case to the TP-Link support engineers who will contact you with your registered email address later. Please pay attention to your email box for follow-up.
- Copy Link
- Report Inappropriate Content
I received a beta firmware and update with it and seem to fix the bug, I ve reported via email to engineer. I hope release a stable firmware for AX53 v1.
Greets.
PD: I reverted to stable firmware for now.
- Copy Link
- Report Inappropriate Content
Thank you very much for the update, glad to hear that the beta firmware is able to solve the problem.
If the issue appears again after you revert the official firmware, you could try changing it back to Router mode first, then reset the device to factory defaults and then configure it to AP mode again manually to see if the issue can be resolved this way.
- Copy Link
- Report Inappropriate Content
@ChusD Hello, how can i get this beta firmware? I'm having issues with 160mhz band with ax53 router. I posted it yesterday here.
- Copy Link
- Report Inappropriate Content
@Dezinn you must report this to be fixed by tplink engineers fix it and well, you said here, I hope to read it and contact with you to test the issue.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 764
Replies: 12
Voters 0
No one has voted for it yet.