@emachestnut Same easy mesh problem with Archer AX55 and AX72, quest network is only at main router. And sometimes mesh don't work properly - camra is conected to weak signal from far away router, dispite near is other one and i must reset it manualy. 

  @tarekitsme agreed.

if tp-link is not going to take this fundamental functionality seriously, the conversation on this thread onwards should be talking about which other brands we should all look at that provides guest and IoT wifi via their mesh modes.

if tp-link realises that they are seriously bleeding customers over this issue, maybe they will look into it properly... maybe.

so, anyone has any recommendates what other mesh brands/models we should look at?

  @Kevin_Z 

It's great that you're finally extending the guest and IoT networks for one router. I need this for my BE800. Not having this is losing you a sale as I want to buy a range extender (RE653BE) because my IoT devices on the other side of my house are having connection issues. Please release updated FW for the BE800, or quit selling deceptive "range extenders".

  @osaya 

Based on my experience, I found what I was looking for with ASUS AiMesh.
I’m running ASUS in two different locations:
AX86U Pro + RP-AX58
AX53U + RP-AX58
In both setups the mesh broadcasts the main Wi-Fi and guest/IoT SSIDs on all nodes without issues. Segmentation stays consistent across the mesh and nothing gets disabled when you add nodes.
That was the main thing I needed and ASUS handles it correctly.
For TP-Link, I only use a single device now (a switch), not their mesh systems.

  @tarekitsme 

Thanks for your prompt response.

From your experience/research, is it better/cheaper/just as good between getting a setup like yours, i.e. ASUS router and then a mesh-extender, vs getting an ASUS mesh set like Zenwifi?

  @Kevin_Z 
I use Archer AX58 on 1.5.2 Build 20250812 rel.38324. It would be great to finally get the guest and iot mesh working!