3 ms·
Because someone will invariably buy this thing and then hang 15 access points off of it, and it won't be able to manage given build of materials this device has
by blantonl 3y ago
Because someone will invariably buy this thing and then hang 15 access points off of it, and it won't be able to manage given build of materials this device has.
And then they'll be pissed off because it doesn't "do" what they want it to.
This thing is designed for what 95% of household's need. A router and one or two WAPs. That's really it.
- tjoff 3y agoOf course it will manage 15 access points, there is nothing to it.
- wkat4242 3y agoYeah it's not like it needs to talk to them constantly. Just push settings and updates periodically and retrieve some statistics.
- simfree 3y agoUbiquiti isn't convinced the hacky mess of MongoDB they run won't corrupt itself when it hits a resource constraint on this device, and they also want to avoid RMAs when the controller either wears out the small amount of our device storage from too many writes, or when the whole unit bogs down from too many paired devices. The controller should really be off board, or the on-board controller should be tuned to communicate less with the devices it s and write significantly less often to storage.