For better or worse, most devices don't have local interfaces. Some matter devices exist in the past year or two, but not all data/functions are available via matter. Older devices likely won't ever be updated to support matter.
Also lump in the fact that HA is a locally run/focused application, it isn't super compatible with a cloud based API/data delivery system without some additional development from the OEM end.
Last I did the math for an internal system.. in 24 hours HA traffic was ~20% of total, for less than 1% of users. That's wild. Mostly because each instance is pinging the API directly every X or less minutes.
If an executive here heard that math, they'd likely ask to block it as well. Right or wrong that's how people react.
So many people are overengineering this... I have a wireless Jabra headset. Works great. At home I use one of those usb speakerphone pucks, works great. Not these super special desktop mics that streamers or radio broadcasters use.
The people who try to use their webcam mic or the built in mic are the ones causing most of the problem (yes I'm also looking at you Macbook users).
I always thought it'd be a great idea if in your internal Teams or Zoom instance you had a "send this person a new headset" button to fix the problem.
Whenever you see one of these "it's product" or "it's engineers" all I can think of is "someone has more business context or knowledge than the others"
The best teams I've ever worked on as a product manager/owner is where we have shared context. These problems described here are minimal. In those teams I could provide technical input to engineers, and engineers gave me "consumer facing" suggestions on features.
I've believed for a long time that lack of business/use context drives a lot of these issues.
Take for instance I currently work at an IoT company, and if I'm working with engineers who have no idea what a thermostat does/how it works other than "makes it hotter or colder" then we have much more difficulty building shared understanding of a feature request.
I also know this because 10 years ago that was my simple understanding of a thermostat... so it was much harder for me to understand why we were doing certain things.
The State of MN stopped accepting certain credit cards for many DMV type activities, and now only accept ones that allow an explicit surcharge (Visa, Mastercard, Discover, Amex).
Are your various friends/family all tech-y people?
My "normal" friends and family are majority iPhone users. I'm Android.
I "literally ruin" their group texts. I've seen people actually reject relationships because they don't date people with "green bubbles".
Don't even get me started about work group texts.
I know restaurants where some of the servers have group iMessage chats with customers for early notification about nightly specials, Android users literally can't be added.
Likely not maliciously, but this has created almost a "second/lower class" of phone users that encompasses ~50% of the country.
And yet here I am with my 10+ years of experience, without a degree. I've met people better than me with less experience and no degree, and people who aren't very good that have MANY degrees.
Yet we've gone through many iterations of the interview process (and testing, things like leetcode) to avoid having to basically accept a gut check of "do I think this person will perform well".
It's more of an art versus science than I think people give it credit for.
Or the fact that many of the major "security bad press" or "S in IoT stands for security" stories are because such interfaces were made but not properly secured. (see bosch story)
That's what I don't get, why they didn't just start with pure math/data when reaching out to the developer.
The only thing I can think of is someone outside of the "knowledge chain" caught wind of it and just fired of the legal threat.
For instance, if I told some people inside my company how much traffic HA uses in terms of how many users are on it they'd probably freak out like this too.
But their reason (cost and traffic) is the biggest reason we don't like it either.
> Yes, they are your users. They are likely the people who will gush about your product to their friends and result in more sales. If the plugin could be behaved better: Make a PR and improve it. People will love you if you do it under your company name, but if you don't want the potential internal drama just do it anonymously. Wins all around.
Which is why to this point, I let it go and don't actually tell anyone how much traffic it takes up. It isn't worth fighting over. Haha.
> Power users are some of the best cheap marketing available to device manufacturers. They will post about your product online. They will tell their friends. They will make your product better for no charge to you.
If I had some way to quantify that, I'd accept it. But as it sits now the vast majority of our users don't interact with any integration models short of "share data with my installer". Alexa being the most popular aside from that.
> I'd love to hear about how this could be considered a cybersecurity issue. It's typically far more secure than a cloud connected solution, but most companies don't like that line of reasoning because it doesn't allow them to track their users.
Go look at major IoT "security problem" news. It is either "cloud leaked data" or "OEM didn't lock down local interface correctly". See the recent Bosch Thermostat story.
Or the "horror years" of Chinese ODM cameras showing up on shodan with live feed video access.
Infrastructure (servers, bandwidth, etc) costs money.
For better or worse, most devices don't have local interfaces. Some matter devices exist in the past year or two, but not all data/functions are available via matter. Older devices likely won't ever be updated to support matter.
Also lump in the fact that HA is a locally run/focused application, it isn't super compatible with a cloud based API/data delivery system without some additional development from the OEM end.
Last I did the math for an internal system.. in 24 hours HA traffic was ~20% of total, for less than 1% of users. That's wild. Mostly because each instance is pinging the API directly every X or less minutes.
If an executive here heard that math, they'd likely ask to block it as well. Right or wrong that's how people react.