I spent 4 months on this back it 2016, initially i was sorry I purchased ruckus, but then it sort of came together.
I got really angry with apple, becasue if you go to "sys-info" ->wifi
and make a note of the : (they stripped a lot of the info out....),
Card Type: AirPort Extreme (0x14E4, 0x134)
Firmware Version: Broadcom BCM43xx 1.0 (184.108.40.206.1a2)
you will find macs from EXACTLY the same family with specific revisions of the BC chipset
BUT with different FW versions!!!!!, ESP. if they are from different years of production.
when you update a mac it DOES NOT update everything at a system level, apple DOES NOT keep the internal FW's updated and in sync. (no FW is NOT available)
So you might have two 'identical' "MacBook Pro (Retina, 15-inch, Late 2013)"
but the damned BC FW is NOT the same!!!, how the hell can any system be reliable & stable , using such poor attitudes.
We.... me .. apple.. ruckus, identified a specific issue with sleep, where RCs was "closed out" due to time out, but since the mac was woken from sleep, it still considered the "link" to be alive..
we clearly saw packets going out from apple kit and disappearing into the "ether"
Much of this should have been fixed in later os updates of both sides.
Now my kit in factory location is fine over 3 floors of production area (110M long)& passes off nicely as long as it cannot see distant WIFI points it tied to previously & moved whilst sleeping.
but now users just toggle the wifi if it gets "stuck" (we have seen AP hand off stuck with other brands of kit as well)
as long as my mac does not sleep... i can freely wander about our sites and no handover issues.
and currently i have about 160 devices on WIFI... in this 1 location.
I think it is tolerated because:
1. the mix of devices is less legacy
2. Due to pixel masterbation... kit does not sleep so much.