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.

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.

  @s80275 

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.

Hi @eousphoros,

I adjusted the settings a few days ago based on your suggestion. However, this does not solve the problem of 2.4G frequency band failure.

The intermittence can be blamed on signal interference, but it is completely unacceptable that the main 2.4G and IoT 2.4G are not working.

Before the new firmware is released, I will use my old Synology RT2600 in AP mode to handle the 2.4G band. (Replacing old equipment is the main reason why I bought BE800)

In the same price range; at least Synology's device allows me to SSH into it to see what's going on.

BTW, I don't think it's possible to tune the JVM or Linux sysctl without profiling and logs.

Cheers.

I'm also having the same issue with my BE800 (BE19000) router. Every few days, every single one of my devices on 2.4GHz network disconnects, and do not reconnect automatically until I reboot the router. 

It happened at 10PM last night, and I gave the situation 8 hours to "fix itself". It will not. 

Until this issue is addressed, I am scheduling a reboot at 3AM every day. I did modify my "additional settings" to reflect the recommendation on the previous post. We will see how this does.
If I need to provide any additional information to help solve this issue, please tag me.

Thanks,

PS1018

EDIT: Apologies for gravedigging this post. It seems that this is the most accurate thread to my problem.
If anyone has since solved this problem, please let me know. I really don't like the idea of daily reboots.

Hi @PS1018,

Try upgrading the firmware version to 1.2.1. It seems to resolve this issue.

I'm slowly moving a few IoT devices back to the BE800(BE19000) 2.4GHz IoT channel, adding one per day.

Now, it has 21 devices connected without causing the whole channel crash problem.

I hope this works for you also.

  @s80275 That's good news! I am already running 1.2.1 Build 20250108 rel.48985
In my case, all of my regular networks and bands have "AbrahamLinksys" SSID (same password as well)

The IoT networks are AbrahamLinksys#IoT

I think this is most likely my issue, but I have never had any issues with my ATT modem using the same setup.

  @PS1018 

I though it was just me. My 2.4 IOT has been dropping stuff lately also. I'm on the newest FW. My garage doors will just drop off the network but I can still see them in the DHCP list. I have to delete the MAC from my Access Control allow list and add it back in and I get 4-5 days of it being good then I have to go through it all over again.

  @jp23 

I still haven't been able to solve this one.

ive since created different SSIDs for each network.

It crashed this morning and like always I gave it ~30min to connect at least one device, it didn't.

Rebooting seems to be the only way to get the 2.4ghz network back up.

I'm convinced that it's some sort of bug that crashes the 2.4ghz networks at this point. Hopefully there will be a firmware update that addresses this!!

Hello everyone,

I have been reading the whole conversation thread because I have the same issue with the 2.4 GHz network on the BE19000. However, I have some particularities that haven't been mentioned.

I have a Sagecom router that only managed the 2.4 GHz network and IoT devices, along with a TP-Link Archer A55 Pro, where only the 5 GHz network was enabled. In other words, one router for IoT and another for more intense traffic. I never had any issues.

I decided to upgrade and buy the BE19000 to replace the TP-Link Archer 55 Pro. The BE19000 now handles all the devices (50 devices). The Sagecom router, which manages the 2.4 GHz network, is connected via an Ethernet cable to the TP-Link.

When I bought the BE19000, I wanted to follow the same connectivity scheme—I continued managing the 2.4 GHz network with the Sagecom router and connected it via an Ethernet cable to the BE19000. Essentially, the only change I made was replacing the TP-Link Archer with the BE19000.

However, I am experiencing disconnection issues with the IoT devices.

Can anyone explain why they are disconnecting if I am not using the BE19000 network?

Thanks,
Christian