@David-TP Is there an updated Beta with Onemesh control for VR2100 v1? Only I note my router updated to 1.6.0 0.9.1 v009e.0 Build 220518 Rel.41627n (official) This newer firmware still has no on/off for Onemesh. Still struggling with erratic/slow 2.4Ghz (5Ghz fine) and wondered if this might be linked.

  @mehdi_08 

Hi there, the latest firmware update 1.5.0 does not work for me either. Like @KentAu i still get EMF redings from the device, even when WiFi and One Mesh are disabled. Please advise on how to completely disable any WiFi/ OneMesh transmissions on the VR400 V3. Thanks.

Is this issue currently looked at by anyone at the TP-Link customer support? The modem should not radiate RF waves when WiFi and OneMesh is disabled. The radiation can be tested for example with the TriField EMF Meter. I get readings as high as 1.2 mW/m2 at a distance of half a meter.

I would really appreciate a solution for this issue.

Hello.

I also had similar problem in my Archer VR400 V3 Build 220321.

I have disabled OneMesh and fully disabled 5GHz wifi, but device constantly broadcasts hidden networks. Are you planing to update devices and fixed this problem?

I finally received a beta version of the firmware from the support team that works for me: https://static.tp-link.com/upload/beta/2022/202209/20220926/Archer_VR400V3_1.5.0_0.9.1_up_boot(220921).zip

At first it didn't work after the installation. But then i turned OneMesh on and off again and the RF radiation stopped.

When re-booting the modem afterwards, i only noticed two short spikes in my EMF meter, but for me personally this is ok now.

Thanks to the support team.

  @yeahna 

TPLink support also emailed me this same firmware link yesterday for testing:

 https://static.tp-link.com/upload/beta/2022/202209/20220926/Archer_VR400V3_1.5.0_0.9.1_up_boot(220921).zip

This seems to be working with no further RF emitted once I turn OneMesh on and off again. It also survives a reboot unlike the previous beta firmware provided.

I do see ~ 10,000uW/m2 for about 1 second upon a reboot and then it drops to zero.

Well done TPLink team for persevering with this.  It is important that OFF is OFF and vendors can be trusted to implement features like this correctly.

Next for the TPLink team to roll this fix into a general release and to update us all here please once done for testing.