BE800 - Wifi issues on 2.4Ghz
I bought this in September. Worked great, no issues until this week. Now, 2.4 Ghz Wifi devices connect at first but eventually disconnect.
I have 2 gig fiber internet. The BE800 Archer functions as the main router and also the Wifi. No issues with LAN. 6Ghz seems to work fine. I believe 5Ghz is working ok too, but not 100% sure.
I have tried:
-Turning off Smart Connect.
-Changing the 2.4Ghz security.
-Rebooting the router (multiple times).
-Factory reset the router (3 times).
-I even bought a second router. Same exact issue.
Hardware Version:
V1.60
Firmware Version:
1.0.12 Build 20231117 rel.33787(5553)
This is unusable.
Please advise.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @eousphoros,
I understand we can do some workaround, even reboot the router every day on schedule. I think that's why the "Reboot Schedule" function exists.
This is a very irresponsible approach, pushing features to consumers that cannot solve the underlying problem instead of providing tools to solve it. After all, it is a high-end price-positioned product.
- Copy Link
- Report Inappropriate Content
Hi @Kevin_Z,
Thank you for your reply.
I'm not looking for a workaround solution, but I hope it's a functional router that functions like a regular product.
As a senior software engineer, I'm sure it's a software problem.
It just happened right now. I can search the BSSID on all my available devices for the 2.4G signal, but it is not connectable. All connected to 2.4G devices are just disconnected.
If I can grab these logs, I'm very willing to provide useful information to improve the product. Otherwise, it's just a useless screenshot.
Cheers.
- Copy Link
- Report Inappropriate Content
i don't know if i would call my changes a workaround. As a software engineer im sure you understand that edge cases exist and im positive networks like ours are not the primary target.
I'm thankful that TP-Link gave us the nobs and functionality tho to enable our use case.
Not so different then tuning a Java jvm or Linux sysctl's.
s80275 wrote
Hi @eousphoros,
I understand we can do some workaround, even reboot the router every day on schedule. I think that's why the "Reboot Schedule" function exists.
This is a very irresponsible approach, pushing features to consumers that cannot solve the underlying problem instead of providing tools to solve it. After all, it is a high-end price-positioned product.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 2440
Replies: 23