@Satheskumar 

Hi, thank you very much for the feedback.

Did it make any difference if we disable "EasyMesh" on the Archer NX200 and set RE450 as a standard wireless range extender?

By the way, I didn't find the current firmware version "1.5.0 3.0.0 v60a2.0 Build 250818 Rel.41696n". Did you use any beta firmware version for Archer NX200_V1?

Wait for your reply.

Best regards.

  @David-TP 

Thank you for your response.

NX200 beta - I have received beta from your technical team for resolving below two issues reported by me. 

https://community.tp-link.com/en/home/forum/topic/835710

https://community.tp-link.com/en/home/forum/topic/830486

Using the RE450 as a standard wireless range extender is not my requirement. I specifically need seamless roaming, either through EasyMesh or OneMesh.

With my earlier setup (MR600 + RE450), OneMesh worked perfectly, and I could move around without switching between router and extender SSIDs. However, with the NX200 + RE450 combination, the 5GHz backhaul disconnects intermittently, and this affects seamless roaming.

My expectation is to have the same seamless experience with NX200 + RE450, without being forced to use different SSIDs or standard extender mode.

Can you please confirm,

1. Whether RE450 is officially supported for EasyMesh/OneMesh with NX200?

2. If yes, is there a beta / firmware fix planned to resolve the 5GHz disconnection?

Thank you for your support.

  @Satheskumar 

Hi, thank you very much for the update.

Both RE450 and Archer NX200 officially support EasyMesh.

Disabling "EasyMesh" is a temporary suggestion to narrow down the possible causes.

I'll follow up on your case via email and consult the senior engineer to see whether they have any other suggestions.

Please check whether you can receive my email later.

Thanks a lot.

Best regards.

  @David-TP 

Great to hear that RE450 and Archer NX200 officially support EasyMesh.

Yes i received email and replied too, will follow up there further. 

  @David-TP 

I am not getting any update on email on the emails, even after several week, just to higliht there

Also, facing other issues, I have reserved the example Tapo camera’s IP address in the NX200 router under address reserved some particular IP. However, when the camera connects through the RE450 extender, it sometimes uses the reserved IP and other times (for example, after a restart) switches to a dynamic IP. Note that the camera itself does not have a static IP configured.

Additionally, when the device is blocked in the RE450, it still manages to connect through the main router (NX200), even though both devices are in EasyMesh mode and follow the same settings. These inconsistent behaviors are causing multiple issues over time.

I need urgent support 

  @Satheskumar 

Hi, thanks for the update.

I'll leave a note for the senior engineer to speed up the process.

For the "Address Reservation", have you tried to set "IP&MAC binding" on the Archer NX200>Advanced>Security?

For the device blocking issue, did you block certain devices via Access Control>Blacklist on the RE450? 

In the EasyMesh network, NX200 is the EasyMesh Controller, and RE450 is the Agent. I don't think the Controller might follow the settings on the Agent. It would be better to block these devices directly on the NX200>>Advanced>Access Control>Blacklist.

Thank you very much.

Best regards.

  @David-TP 

I have been using Address Reservation under Network > LAN in all my TP-Link routers (including older models, last year’s MR600, and my current NX200).

However, you suggested using IP & MAC Binding (under Security) for reserving device IPs like cameras and printers. Could you please clarify the exact difference between these two options?

Do we need to configure both, or is one sufficient? It’s becoming difficult to maintain both configurations. If possible, please share any official guidelines or documentation explaining which method should be used and when.

Blocking these devices is not critical at the moment — I just noticed this different behavior while testing.

Also, I have another question: since my RE450 and NX200 are connected through EasyMesh, could this setup be causing the issue? I didn’t face such behavior earlier with the MR600 and RE450 OneMesh combination. If OneMesh can resolve this, can we enable OneMesh for the NX200 and RE450 setup?

  @David-TP  Kindly provide some solution on this URGENTLY , as its impacting lot, even IP&MAC binding not effective or not convenient as like LAN address reservation.. 

Also can we quickly confirm oneMesh can be supported for NX200 its another major issue with easyMesh as its not following base router setting.