After looking in r/eero; There is a very active developer that kindly communicated the complexities of their system.

This request appears to be past the "taken to the team phase".

redwindmill She's the lead radio dev and will explain why so many "easy" requests are anything but.  Great in-depth information over at /r/eero. 

redwindmill If eero wants to communicate to its customers, shouldn't they be using their own forums rather than Reddit?

txgunlover Nope, what's been posted rarely goes further than saying, oh it's really hard.

jimdenver there is no excuse Jim. Either implement a huge customer request OR tell your customers it's not possible with the current hardware. They've done neither. The real sign will be what happens with the pending eero pro 6. Will their new high end product have it? If it doesn't, then they aren't listening and don't care. 

jimdenver oh, and stop asking is the WORSE thing to do. There are only 2 ways to pressure a company. Feedback and/or stop using/don't buy their product. If you stop using/don't buy their product they don't know why. Feedback is critical let a company know why they lost you. If enough do it then they face dire consequences if they don't act. 

Mgreer316 They don't need to implement it for the people who have already bought the system, they've got our money.  And if they keep quiet, rather than say bandwidth monitoring is never going to happen, they'll continue to get people buying it.

YetAnotherUserName That's a horrible business strategy IMO. This is not some obscure request. This is critical and will grow in criticality over time. So critical, it will be worth switching systems just to obtain it. New purchasers will assume its there and be dismayed when they discover its not. If not addressed, it will become a marketing advantage to eero's competitors. Lastly, the oodles of otherwise satisfied eero customers who left or will leave the platform because of this won't be silent. In YouTube reviews and other avenues they'll repeatedly point out this lack. IMO, it'll be much better for eero to be open and honest and get out in front of this. 

jimdenver Disagree 100%, the hardware is already counting everything, it must to even function as a router, there's more than enough cpu / memory to increment counters this is definitely not a hardware issue or a political data ownership issues, it's purely a poor-engineering issue. I've worked on hardware so much less powerful than this before, and in software, kernel extensions, networking, etc and believe me its easy and its mostly already done in the kernel anyways it's just not exposed or perhaps aggregated in the windows a human might like. They just need to send the data in their regular data pushes to api.eero.com, and then build the widgets in the UI to display them. Stupid simple. In fact, things like DDWRT are proof of how simple it is, you can actually write an entirely open source full router in open source and have it work with someone else's hardware! Imagine how easy it is when you're already a software developer at eero with full src control? No, this is just really bad mgmt and engineering debt on their part. All the engineers were let go or everyone is too junior or the mgmt is too concerned over google integrations to pay attention to customers, or the product is being deprecated or they have no testing platform or Barbara, the only one who deals with metrics in the kernel is on holiday to Brazil for 9 mos... it'll be something like one of those.

atrieger That is incorrect and I recommend you talk to the lead developer over at /r/eero.

txgunlover this is what I don't get. Why isn't the lead developer in eero's own customer forum? Why at reddit but not here? That makes no sense.