Interesting - we did a trial with Meraki and for us, the broadcast range was terrible in our building.
I found some tools <https://github.com/calmh/unifi-api> that work with the Unifi API to detect issues and can even trigger an access point reboot, I'm considering an experiment to cycle access points regularly to keep them "fresh" and see if that helps. -Alex ------------------ *The #1 mistake in community building is doing it by yourself.* Join the list: http://coworkingweekly.com Listen to the podcast: http://dangerouslyawesome.com/podcast On Mon, Apr 27, 2015 at 9:18 AM, Aaron Schaap <[email protected]> wrote: > We've been using Unifi for awhile now and started having the same issues > after a few months of usage. I did a lot of the load balancing stuff, along > with a lot of Channel/Band configuration to deal with problems. We had the > same issues of needing to reboot and it didn't matter if it was 60+ people > or only 10. I tried to see if it was a time of day and that didn't seem to > matter. I thought it was a POE issue for a bit but after playing with > different things, it didn't seem to be the case. > > We actually just switched everything to Meraki (https://meraki.cisco.com/). > I manage our infrastructure but also chat quite a bit with the building > owner that offers WIFI to the rest of the building (4 floors). They had > Unifi as well and were noticing the same things. The verdict is still out - > on day 2 right now but I like the additional reporting within Meraki. > > I also like how Meraki handles wireless band selection (2.4GHz vs 5GHz) > much better as well. Unifi is supposed to do this but doesn't do it well. > We noticed a lot of users (mostly Mac) could connect to 5GHz but got stuck > at 2.4GHz often. I ended up broadcasting only 5GHz and created another SSID > for 2.4GHz for the few users still needing that. Wasn't ideal but everyone > had a much better experience. Meraki does "Band Steering" much better by > detecting clients capable of 5GHz operation and steers them to that > frequency, while leaving 2.4GHz available for legacy clients. > > I'd be curious if you figure it out but we decided to switch to Meraki > ourselves. > > ------------------------------ > Aaron Schaap > The Factory - www.workthefactory.com > @schaapy and @coFactory > > -- > Visit this forum on the web at http://discuss.coworking.com > --- > You received this message because you are subscribed to the Google Groups > "Coworking" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Visit this forum on the web at http://discuss.coworking.com --- You received this message because you are subscribed to the Google Groups "Coworking" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
