New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More

New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More

189 Reply
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Friday

  @Joseph-TP 

 

it's been a couple weeks since the last beta version, do you have any updates or news regarding a new (beta) firmware? Are there any ongoing issues that still need to be resolved? Is a public release (date) in sight yet? Please let us know....yes

  0  
  0  
#191
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Saturday - last edited Saturday

  @Joseph-TP 

 

I’m testing the current pre-release EasyMesh firmware  and I think I may be hitting a UI/feature exposure bug or partial rollout. 

 

My setup:

- Main router: Archer BE800 V1

- Satellite: Archer BE550 V2

- EasyMesh mode enabled

- BE550 connected as EasyMesh satellite

 

Firmware versions currently installed:

- BE800 V1: 1.4.1 Build 20260313 rel.47813(5553)

- BE550 V2: 1.3.1 Build 20260303 rel.49110

 

These appear to be the current pre-release builds from these forum threads:

- BE800 pre-release thread

- BE550 V2 pre-release thread

 

What is working:

I do have VPN Merge now on the BE800, so I know the BE800 pre-release is active.

My IoT Network now extends to the satellite, which did not happen on my previous firmware.

In Advanced > EasyMesh, I can click the Modify/Edit icon for the main router and go to the Clients tab.

In that pop-up, I do see “Bind to Current AP” for clients.

 

What is not showing:

The EasyMesh menu in the sidebar is not expandable on my BE800 UI.

I am not seeing the additional EasyMesh pages/options shown in the pre-release screenshots in the forum posts.

I am also not seeing a clear way to move/pin a client to the other node. The only option I currently see is “Bind to Current AP”, which only helps if the client is already connected to the node I want.

Any help on this matter is greatly appreciated

EDIT: I just realized I was getting two posts confused. It is the post for the BE550 V2 ( here: https://community.tp-link.com/en/home/forum/topic/853652 ) that shows the advanced EasyMesh options. Are these not coming to the BE800?

  0  
  0  
#192
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Monday

Hi @Lyfesaver ,

Yes, as you can see, this is a feature introduced in the BE550-v2. Generally speaking, the main router primarily displays the functions it supports.

  0  
  0  
#193
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Monday

  @Joseph-TP 

 

That means I need to make the 550 my main and the 800 my satellite?

  0  
  0  
#194
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Tuesday - last edited 8 hours ago

Hello @Lyfesaver ,

EDIT:

If you want to use the unique features of the BE550 V2, you might consider setting up the BE550 as your main router.

Some features, such as EasyMesh client binding and EasyMesh satellite node binding, require both the main router and satellite routers to support them for them to display and apply correctly.

On the BE550, it has Roaming Bindings for Client Affinity. This is basically similar to the EasyMesh Client Binding of BE800.

The final performance of the Tapo Cameras also needs to be configured and tested. I understand your return period is tight, which means you need to make a decision quickly. If you ultimately choose to return the item, we understand and respect your decision.

We also hope you can eventually find a suitable product to meet your needs. Please feel free to contact us if you have any questions about our products in the future.

  0  
  0  
#195
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Yesterday

  @Joseph-TP 

 

I am sorry for being difficult but I am genuinely struggling to understand. From what I am reading, you are saying that the BE800 wont get EasyMesh Client Binding and EasyMesh Satellite Node Binding so, in reality, setting the BE550 as my main wont give me EasyMesh Client Binding and EasyMesh Satellite Node Binding?

 

I am still within my return window for the BE550 and I can give my sister my BE800 if that's the case. I can then get Ubiquiti or Eero as I absolutely have to have this sorted pronto. We have been using the BE800 for a while and we had some Nest cams for security. Wanting to move away from cloud based cameras I bought 6 Tapo cams to replace the Nests and leveraged them using Frigate.

 

At that point the Tapo cams completely destroyed my WiFi, (computers, phones and smart devices just randomly fail) likely due to congestion. I added the BE550 as a satellite and I can see that the congestion is lowering (using my tinySA Ultra+ ZS407) allowing me to get 4 of the 6 cams working without WiFi devices throughout the house failing randomly. The reason I cant get the other 2 to connect is no matter what I do the cams in the front of the house want to jump right past the BE550 and connect to the BE800 in the back of the house where the 2 cams in back yard and 2 cams in driveway also connect, destroying my WiFi again. I cannot get them to stay on the BE550.

 

I have lowered the TX of the BE800 to LOW and forced the front cams to connect to the BE550, toggled "Bind to this AP" only to have the dang cams jump right back to the BE800 soon as I give it full TX again.

 

I am not telling you all this so you can help me with my issues, thats not what this thread is about. I am giving context so that you can see why I might just have to give up the ghost and move to other hardware solutions. I have until Thursday to return the Tapo cams and until the 29th to return the BE550 and I dont wanna have to go thru all of that if there is a way to make things work with the hardware I have and the only solution I see is the EasyMesh Client Binding and EasyMesh Satellite Node Binding.

Again, I apologize for being thick headed but I am still confused as to what I need to do to get EasyMesh Client Binding and EasyMesh Satellite Node Binding working in my house (which we run a daycare out of which is why the cams are essential).

Thank you again, Joseph

  0  
  0  
#196
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
17 hours ago

  @Joseph-TP Do you know if the BE800 is using HTTP/1.1 for DoH inquieries? I've noticed that DoH queries to any of the Quad9 addresses do not work. I did find this article about this not being supported with Quad9. This maybe something that I need to submit via normal support channels. 

  0  
  0  
#197
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
7 hours ago

 

Hello @Lyfesaver ,

Hopefully this won't bother you.

If possible, you can also try setting BE550 to v2 as the main router. This way, you can select network nodes for clients via Add Roaming Bindings.

 

Joseph-TP wrote

Hello @Lyfesaver ,

EDIT:

If you want to use the unique features of the BE550 V2, you might consider setting up the BE550 as your main router.

Some features, such as EasyMesh client binding and EasyMesh satellite node binding, require both the main router and satellite routers to support them for them to display and apply correctly.

On the BE550, it has Roaming Bindings for Client Affinity. This is basically similar to the EasyMesh Client Binding of BE800.

The final performance of the Tapo Cameras also needs to be configured and tested. I understand your return period is tight, which means you need to make a decision quickly. If you ultimately choose to return the item, we understand and respect your decision.

We also hope you can eventually find a suitable product to meet your needs. Please feel free to contact us if you have any questions about our products in the future.

 

  0  
  0  
#198
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
6 hours ago

Hello @TheSassyBear 

 

No similar feedback has been received regarding the BE800. Could you please provide a screenshot of the error message? If it contains personal information, please cover it up.

 

Also, have you tried these suggestions: 

1. Try Default Mode instead of Ultra Secure Mode: In Advanced > Network > Internet > DoH/DoT section, if you're using "Ultra Secure Mode", try switching to "Default Mode". In Default Mode, the router will use your specified secure DNS servers first, but if these are unavailable, it will fall back to the default DNS server. 

2. Temporarily disable DoH/DoT: To verify this is causing the TP-Link ID connection issue, temporarily set the DoH/DoT option to "None" and check if the router can connect to TP-Link ID and shows online in Network Map.

3. Verify DNS server addresses:
   • For DoT, make sure you're using the correct server name format (e.g., "dns.quad9.net" or "dns.nextdns.io" with your configuration ID)
   • For DoH, verify the complete URL format (e.g., "https://dns.quad9.net/dns-query")

  0  
  0  
#199
Options