ryannathans
Regular Contributor
Hi all
When running on 384.13 I had great success with my network, everything was nice and stable. Since then, I've had some horrific instability on portable devices and only in some locations - ironically locations with strong signal.
I think I've finally found the cause - the Smart Connect seems to work differently now.
All I've done to fix it is increase the "dwell time" (10 min) and "window time" (2 min) so that my device will get auto-balanced less often when I'm in areas with equal-ish coverage of multiple bands. So far the connection has been far more usable.
Oddly my chromecast doesn't work reliably since 384.13 either unless I disable MU-MIMO (or possibly Universal Beamforming, not certain) but that's a problem for another day
When running on 384.13 I had great success with my network, everything was nice and stable. Since then, I've had some horrific instability on portable devices and only in some locations - ironically locations with strong signal.
I think I've finally found the cause - the Smart Connect seems to work differently now.
All I've done to fix it is increase the "dwell time" (10 min) and "window time" (2 min) so that my device will get auto-balanced less often when I'm in areas with equal-ish coverage of multiple bands. So far the connection has been far more usable.
Oddly my chromecast doesn't work reliably since 384.13 either unless I disable MU-MIMO (or possibly Universal Beamforming, not certain) but that's a problem for another day