Sure, the ESP32 will connect to whichever mesh node provides the best 2.4 GHz signal

- It monitors CSI from that specific node (the one it's associated with)

- If the ESP32 roams to a different mesh node, it will start monitoring CSI from the new node

The system doesn't care about the router's internal mesh topology, it just needs a stable connection to receive CSI data from the associated access point.

In terms of layout of rooms and useful monitoring, you have to be able to configure which node it attaches to, right? Because it's going to monitor the physical space between itself and that node.

So you might have an ESP32 placed across the room from one mesh node to monitor that particular room. But if that ESP32 roams to, say, the mesh node on the floor above it, it's going to monitoring a much less useful space - just the vertical space between itself and the mesh node on the floor above.

Am I envisioning this correctly? I'm thinking its a problem for systems like eero, where you can't lock a device to a particular mesh node.

On the critical topic of Mesh Routers and Roaming, a possible solution is to force the ESP32 to hook onto the MAC address of a single Access Point, as discussed here:

https://github.com/francescopace/espectre/discussions/6