zlacker

>>linker+(OP)
I wish there would be an appliance manufacturer that would actually hire developers to create and maintain Home Assistant.

>>elkos+ya
Home Assistant users are small minority of many of these companies user bases (including ours), and these integrations being locally focused often poll HEAVILY causing an upside down ratio in API traffic compared to all other users.

The solution is to allow local interfaces (matter, HTTP, etc) but most company cybersecurity teams just freak out at this.

Oh, and the reason we don't have a full time team managing HA is like I said.. addressable market versus FAANG/Samsung.

It takes a full time person (persons) to manage Alexa, Google, Samsung, etc.

>>superg+bf
Yet most 3rd party home assistant integrations are maintained by a single person in their free time. The devs targeted by Haier even maintains TWO integrations in his own free time.

It doesn't have to cost the manufacturer one full-time employee to maintain a relation with the home assistant community. Just let the community do the work to develop integration for your products for free! Just look at how companies like Asus maintain a relationship with open source router firmware maintainers for example. Asus spent a minimal effort in that front, yet the community is very happy and keep recommending Asus routers to their friends and family. It's basically a win-win relationship.

All Haier need to do is sending an email to the maintainer of the open source integration asking them to not polling so heavily and they'll usually comply! It shouldn't take a dedicated employee 40 hours per week to send that email. Taking down an integration should be the last resort because it burns the goodwill of your community. The first step should be reaching out to the dev and work something out.