Try turning off Client Balancing in Radio Settings - RF Profiles  This will keep traffic from devices in the room on the same AP.  Client balancing can push devices in the room to a neighbouring AP with poorer signal and cause these types of issues. ... View more

I solved this by allowing the relevant port on an upstream firewall at our ISP.  Don't remember the exact port, but you can find the details of the ports that need to be allowed in Firewall Info on the dashboard.     ... View more

Answer: Open the relevant port outbound on the firewall   Source : LAN Destination : 3.210.175.34/32, 13.52.29.190/32, 13.54.51.60/32, 35.161.241.24/32, 35.162.58.56/32, 35.162.65.76/32, 50.18.100.0/32, 52.33.92.73/32, 52.57.34.238/32, 52.59.68.120/32, 52.208.175.132/32, 198.27.154.12/32, 209.206.48.0/20 Ports : tcp/udp- 6514 ... View more

None of the web app health metrics report any data.  Have tried Meraki support, and they came back with:   I spent some time on this case today and observed that your MX is currently in passthrough mode, which means the security appliance is acting as a Layer 2 bridge and does not route or translate client traffic Only traffic that passes through an MX can be tracked by Meraki Insight. For example, if the MX is handling all routing for a location then both WAN bound and Inter-VLAN bound application traffic will be tracked. However, if Inter-VLAN routing is happening on a downstream device and only WAN bound traffic passes through the MX then only WAN bound application traffic will be tracked.   I'm a bit confused because all traffic goes through the MX and Meraki don't state in the documentation that Insight web app health does not work in passthrough mode. ... View more

I have the same issue, but am not sure about the solution you have described.  Could you give more detail?   I have all traffic going through the MX. ... View more