Thankfully I don’t use any of their products, but this really pisses me off. They claim that this open source project “causes significant economic harm to their company”

This is ridiculous. It is truly ridiculous. How can something that enables the user to efficiently control their AC cause “significant economic harm”???

Consider forking the repository or mirroring it to another platform like GitLab, Codeberg or your self-hosted Git server, so the project can continue to exist and someone can maybe fork it and maintain it.

The effected repos are: https://github.com/Andre0512/hOn and https://github.com/Andre0512/pyhOn

If you don’t know about Home Assistant, check it out. It’s an amazing piece of open-source software, that you can run at home on your own server and use it to control your smart home devices. That way, you don’t need to connect them to the manufacturer’s (probably insecure) cloud. It gives you sovereignty over your smart home instead of some proprietary vendor-locked garbage. Check out their website and the Lemmy community: !homeassistant@lemmy.world

I also highly recommend Louis Rossmann’s video about this: https://youtu.be/RcSnd3cyti0

He makes awesome videos in general, consider subscribing.

As Rossmann said, don’t ever buy anything from such a shitty company that doesn’t respect their customers. This move by Haier is nothing other than a slap in the face for everyone, who just wants to comfortably control the product they paid for. This company is actively hostile towards their paying customers. Fuck these bastards!

  • DeltaTangoLima@reddrefuge.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    I think it’s because the dev might’ve reverse-engineered the calls to the cloud service, and that may be where the legal sticking point is. Not a lawyer, so not 100% sure - will be interesting to see where this goes.

    I saw elsewhere the dev has insurance, and they’re going to cover a lawyer, so they may very well fight it.

    • intensely_human@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      10 months ago

      As a writer of software code and also of contacts (freelancer), I’m intrigued by the challenge of writing a TOS to prevent reverse-engineering an API.

      In some way you’d have to represent the interface itself as the intellectual property, or something. Normal copyright covers copies, but this would be sort of like covering complementary parts. Like you invented a lock, and you’re trying to copyright or protect the set of keys that could open that lock.