Wifi / mesh issue with video calling

[FuzzyLogic]

Ive got two Asus routers, one in the lounge and one upstairs in the office. The lounge router (AiMesh node) is connected via cable to the upstairs . Wifi strength is great throughout the house and the phones etc switch automatically between the routers. Problem occurs if you are on facetime or other video chat and move between the routers.. it drops the connection for several seconds until it re-establishes... Any ideas how I can improve / fix this?

[xeny]

Check the firmware is utterly up to date and the mesh is configured correctly.

See if you can get adequate wifi with one unit (guess you can't which is why you have both?)

Spending money on a better mesh system may help.

[FunkyGibbon]

Which models of Asus routers do you have and do you have the latest firmware? AiMesh 2.0 is a vast improvement.

[FuzzyLogic]

both AC68U and both with latest firmware. One on its own does not provide house wide coverage

[xeny]

Which leaves

Spending money on a better mesh system may help.

Handover between wireless access points is notoriously tricky to make glitch free.

May be worth posting in the Weapons Grade WiFi thread to see if anyone can say how their product behaves in this scenario?

[FunkyGibbon]

FuzzyLogic said:

both AC68U and both with latest firmware. One on its own does not provide house wide coverage

I have an AI-Mesh and have no issue moving devices about including when using Teams etc.

I'd suggest re-setting the mesh and let it handle the 2.4 and 5 MHz network as one - if it is not already.

[FuzzyLogic]

FunkyGibbon said:

I have an AI-Mesh and have no issue moving devices about including when using Teams etc.

I'd suggest re-setting the mesh and let it handle the 2.4 and 5 MHz network as one - if it is not already.

Thanks - I believe it is already. I have the node connected via ethernet backhaul & both points are correctly showing in the mesh topology. Both 2.4 & 5M networks showing with the same SSIDs under the topology also.

Changing the hardware is not an option, however I might consider moving the node if I cannot fix the issue to see if that helps