Hello @timbo4
Access point selection is decided by the client device itself, not the network. Google/Nest WiFi does provide some devices with extra information they can use to make better decisions, but fixed devices (like cameras) don't typically implement the standards used to communicate that information (802.11k and 802.11v). Those devices are on their own to make the decisions.
What often happens, though, is that when the network restarts, the primary/router unit comes up first and starts beaconing the common network name, then the secondary/point units come up shortly after that. During that time in between, when only the primary/router unit is beaconing, WiFi clients that are already powered on may end up connecting to the primary/router unit, and then stick with it even after the secondary/point units come up. It sounds like that may be what's happening in your case.
You may be able to get a better result by just restarting those cameras after the network is up and running.
However, some devices were designed at a time when multiple access points in a single network was rare, and they may still stick with the same access point (BSSID) they connected to last time. If that happens, you may get better results by resetting those cameras and connecting them again while your network is running. Hopefully, they'll select a better access point (and then stick to it).
Unfortunately, some devices don't even do a proper scan during startup to select an optimal access point. These devices often just connect to the first access point they hear a beacon from, and as long as it works, stick with it. These tend to show up as connecting to random access points on startup, which it doesn't sound like is happening for you, but it's not impossible.
