By chance, do you have a Layer 7 Application deny rule in place (the Peer 2 Peer applications in particular) for that SSID under Wireless - Firewall & Traffic Shaping -Block applications and content categories?   If so, you might want to temporarily remove it if able to per your configuration requirements and monitor connectivity.   For reference, I experience seemly random loss of browsing (random devices on random APs) when on any network when the above is active.  This issue returns and stops when activating or deactivating this Deny rule.  I have a support case open as this Deny rule was in place for several years and appears to have only started since upgrading APs to 30.x Firmware. ... View more

What you are really dealing with is that each client, the client alone,  decides to which AP that it joins. There is no central coordination for Wi-Fi, it doesn't exist today.  Each client is different. Each OEM has their own algorithm/ special sauce that is used to connect Wi-Fi. The AP has no say. It may make suggestions but the client makes the decision.     What you can do is define what you want the network to do and then pick your most important least capable client and build your AP design around that devices abilities or lack of abilities.   Trust the RRM unless you want to be endless tweaking each and every AP constantly. ... View more

Their is an option called something like "NAT persistence" that support can enable that helps this issue.  Check out this post.  Also search on things like "Nitendo NNAT type D". https://community.meraki.com/t5/Security-SD-WAN/Nintendo-Switch-NAT-Type-D/m-p/248820   ... View more

For that you need to talk to a account manager or someone within Cisco Meraki. For the group policies you could also ask if you want to be included in that private beta if you have a testing network of course or an adventurous client 😉 ... View more