cross-posted from: https://poptalk.scrubbles.tech/post/567593
Haier hits Home Assistant plugin dev with takedown notice
I’m not really big on “let’s make a movement”, but this independent dev has been hit with a cease-and-desist from making a FOSS Home Assistant addon for their Haier air conditioners.
Haier claims that they are losing out on millions of dollars due to this plugin which… lets you control their air conditions from home assistant. They haven’t bothered to explain how that’s possibly worth millions of dollars - they’re just claiming it.
So of course they hit the Streisand button and are demanding that he takes it down. He of course is complying… in a couple of days. Maybe you see where this is going.
It would be an absolute shame if any of you just happened to create a fork, or clone the code, or mirror it in your own instance. An absolute shame.
Just so everyone here knows which repositories NOT to clone or fork, here are the two links:
and please, don’t repost this anywhere, or share it in other communities, or anything like that. It’s a shame that so many people already know and are making clones. I’m just letting you know so you don’t do anything like telling others who may make their own copies.
(sidenote: Haier owns GE Appliance, so for our American folks it may affect you folks too)
I wonder if their notice is not absolute nonsense. They talk about breaches of their terms of service, which I think can be found here: https://go.he.services/tc/V1/en_GB/tc.html
The terms of service do purport to prohibit ‘reverse engineering’ of the app, which I think the developer receiving the notice may have done to understand the protocol between Haier’s service and the app. However, it looks like the developer is in Germany, and did the reverse engineering for the purpose of creating something that, in a way, competes with the app. According to https://www.twobirds.com/en/insights/2020/germany/vertraglicher-ausschluss-von-reverse-engineering, contractual provisions in Germany designed to prevent reverse engineering to create a competing independent program after the original is already available to the public are not valid.
Maybe they are saying that the developer is unlawfully interfering with their business by inducing others to breach the contract. However, the terms of service don’t appear to say prohibit connecting to Haier’s services from a competing act (at least nothing in them I can find).
They don’t really clearly define what their problem / claimed cause of action is. Maybe this is just an intimidation tactic against something they don’t like, but they have no real legal case - in which case perhaps the community around it could band together to create a legal defence fund, and have Haier laughed out of court.
Disclaimer: Not intended as legal advice.
Edit: And better yet would be if they could find a way to intercept the traffic between the devices and Haier and replace Haier in that protocol. Then there is no option for Haier to try to restrict who can use the servers on their side. I assume the devices have a set of Certificate Authorities they trust, and it is not possible to get a trusted certificate without modifying the device somehow though.