@Kevin_Z 

I just tested the scheduled restart, I set the main Be550 to restart, now my Daikin air conditioner was not able to reconnect, even though I have a Be550 in my room practically next to it. A newer Amazon Echo Spot device connected normally, but the 5th generation Echo dot did not.

I believe it is not a signal or range problem because there is a mesh be550 device in the same room and now the air conditioner has the same problem.

The signal in the room is strong, I can connect and get the maximum speed of my fiber optic internet provider Vivo on the S25 Ultra, 700Mbps. I did not notice any signal degradation when restarting.

Speaking of the S25 Ultra, when connected to the MLO network, in the Wifiman app I can see that it is connected to both 5Ghz and 6Ghz networks, but only the 5Ghz shows bandwidth, while the 6Ghz network shows 0 and the signal is very weak, even though it is next to the main modem that has the MLO network. I don't know if it is the app or the connection.

This problem of disconnecting and reconnecting or simply being unable to reconnect when restarting the modem was already occurring with the latest official firmware 1.1.1 build20241230.

Disabling Easymesh, the problem persists.

The Amazon devices and air conditioners reconnect normally to the Mitrastar Vivo Fiber modem, but they have problems when connected to the BE550 when restarting. I am talking about the Amazon devices because they are the ones that are presenting the most problems.

I would like to request, if possible, to implement the MLO network in the mesh system, either by cable or easymesh, as it seems to have been implemented in the Be800.

Edit - Ps5 Pro now is connecting and disconnecting.

Please, I need a solution.

  @Kevin_Z 

I would like to raise the issue of programming and code changes here. I understand that when someone changes something in the software, it is probably obvious that if something happens, it can be reverted. So could you explain me please - if this distinguished team of programmers makes some changes to the code, why the hell can't they revert what was working fine until now, but was broken? Especially in the case of releasing firmware that after updating does not allow users to revert to the older, working version. This is extremely annoying and frustrating for users who pay a lot of money for the hardware and receive a product in the phase of continuous beta testing. What kind of company policy is this? Don't get me wrong please - I don't want to be rude, but hey...do you guys are really serious ? Instead of simply reverting the changes - they make us wait for another solution to the problem that they themselves caused ! In my opinion, this only causes a growing aversion to the products of this company, It's nice that someone wants to fix a problem, but I mean problem created in the initial phase and not caused by changing the code to a non-working one. I had a well-functioning BE550 router, but because of its relatively good performance breaking down, I replaced it with the BE800, with which I see this great team of programmers is doing the same and with each update it works worse and worse. Just revert the changes please quick and don't make us wait for a miracle. It cost us a lot of money so playing like this is highly incomprehensible.

 Thank you for attention and sorry for bad words - I'm just tired of waiting for new problems to be solved all the time.

Rob

  @Kevin_Z 

I testing a while the new firmware. I use 2x BE550v1 as satellites only. One via Ethernet backhaul, the second via wireless backhaul, both connected with BE800v1 (main).

The connection for my network looks stable for now; I don't notice network/internet drops or something yet.

But I don't use the MLO function, which can create problems. :P

I notice EasyMesh has many limits.

1. Wireless backhaul on BE550v1 is limited to 1 Gb/s.

2. Ethernet backhaul on BE550v1 goes to 2 Gb/s in my case. But I use a TP-Link 2.5 Gb/s switcher between them; maybe that's why I lost speed, or maybe it's limited by software or hardware; who knows?

3. MLO is useless if it doesn't work in EasyMesh, so I don't use that option in my case. Solo MLO from the main router is too weak; the 6 GHz band has physical limits. Go through one wall, and speed drops 4 times. :D

USB share problems. In my observations:

1. There's a 50/50 chance after the update I need to format my USB disk connected to USB share to avoid bugs and permission problems. 

2. USBShare is so bugged with Windows 11 24H2 with the SMB/FTP function. Which can create 0 KB files or a popup alert window while you copy files to an empty disk; it says, "There are already files with this name," and you need to rewrite it.

Or you cannot delete/rename the created folder because the pop-out window says, "Something uses this folder."

3. Windows 11 24H2 makes USB share speed abnormal while moving files. Speed can drop 2/4x times without reason. Manually reconnecting the USB disk solves the problems most of the time, or restarting Windows LOL.

Solution:

When you connect via an outside program, for example, WinSCP, most of the time all works fine. Only kick out the session when you don't move files and need to reconnect often.

  @Kevin_Z  I will keep testing, and if I notice something important to share, I will let you know on this topic. :)

And those TP-Link guys are lucky that some have enough time and patience to constantly testing. Unfortunately, not everyone has that much time, when buying such an expensive router, it is probably obvious that they would like it to work as intended. For now I can say only that most of problems fortunately was resolved, however for example OpenVPN client can't connect to OpenVPN server on my BE550. I know that they released a beta fix, but because for a while I am far from my home and unfortunately can't do update remotely. To be honest can't do most of the changes remotely even when you login via TP-Link ID, which is also a bit annoying, especially if you can't get into your network via a running VPN server on that router.

  @Tester007 

I understand you so much. Unfortunately now we users become free beta testers.

And that looks won't change in the future.

I remember when the BE550v1 came to Europe half a year after release in the USA, and the firmware was a total disaster.

And I start asking myself, do USA people not test it?

So after opening the topic and cases by me and other users, TP-Link engineers start fixing it.

And believe me, now BE550v1 is working amazingly compared to what it was a year ago, LOL.

  @ChrisBS 

No, I don't agree with that, but you're right, because most people have this passive attitude - we have what we have. This is a main problem our times. Indeed, it looks like nothing will change, because to the delight of the manufacturers, users agree that this is how it has to be. Well - don't take it personally, I am also somewhat guilty of myself, I do not have time to write everywhere that I don't like such of behavior, especially when the rest does not object. Nothing can be never done alone. OK, sorry for off-topic. It remains to be hoped that all reported bugs will be removed quickly, however, there is still no answer to a simple question - why a well - functioning option cannot be restored after it was broken...wrrrrr...

  @ChrisBS 

1) I have a BE230 connected to a BE550 v1 via Ethernet (wired) backhaul, and the speed is the maximum possible, i.e., 2.5 Gb/s; there is no limitation to 2 Gb/s.

2) I also have a BE550 v1 connected to a BE550 v1 via wireless backhaul, and I cannot confirm that the speed is limited to 1 Gb/s.

3) Problems with SMB on Windows 11 24H2 are very well known, but are entirely the fault of Windows 11; routers, irrespective of brand, have nothing to do with them.

Regarding 1) and 2) above, I can only recommend always setting up your mesh network from scratch - this takes more time, but ensures the smallest risk of error.

While as regards 3), there are workarounds described on the internet.

  @Maciej 

I already talked with TPlink engineers via email, and they confirmed the wireless backhaul is limited between BE800v1 and BE550v1 to 1Gb/s.

"..after testing and verifying by our side, it's the same with yours, and our RD confirmed that's the case of wireless single pair performance."

BTW. When I detect bugs, I always set up everything from the start to verify problems to be sure I've tested everything. Because many times after firmware updates, backup files can be corrupted.