zlacker

[return to "Haier hits Home Assistant plugin dev with takedown notice"]
1. asylte+ma3[view] [source] 2024-01-19 16:13:08
>>linker+(OP)
I’m really worried this will become common practice. We MUST fight against this otherwise they will take away open source from us. Making an integration to work with devices you own is NOT ILLEGAL. I’m happy to contribute to a qualified and trustworthy gofundme to protect devs. I myself have a few integrations I made and would refuse to take them down. Granted, I intentionally don’t use any “cloud” api garbage.
◧◩
2. superg+Rr3[view] [source] 2024-01-19 17:28:49
>>asylte+ma3
Haier (at least this product in the EU) doesn't have a published/public API.

The code in question scraped the API off of app/device traffic.

Also, Home Assistant is a locally focused platform, and when it uses cloud APIs it creates HUGE amounts of traffic for the amount of users that use it.

Source: I run a developer program for a different IoT company

◧◩◪
3. asylte+6x3[view] [source] 2024-01-19 17:46:25
>>superg+Rr3
So? If you don’t want people using your APIs there are ways to block them. If it’s public, don’t complain.
◧◩◪◨
4. superg+zJ3[view] [source] 2024-01-19 18:39:25
>>asylte+6x3
That's exactly what Haier is doing, just via legal means than technical ones.

We actually have a public self-serve API. In some cases, if I've tried the diplomatic approach, I've had to actually shut off API access to get someone to even respond to me.

In this case, it appears they've taken the same access/creds as the mobile app maybe?

Another one of our platforms we cert-pinned the API to prevent this as well.

Yes there are ways, the other part we don't know is if they went straight to the legal route or not.

◧◩◪◨⬒
5. asylte+7h4[view] [source] 2024-01-19 21:22:05
>>superg+zJ3
Haier is abusing the threat of legal action that’s not the same thing
[go to top]