>>linker+(OP)
The two subject repos are:

  https://github.com/Andre0512/hon
  https://github.com/Andre0512/pyhOn

Make whatever use of that information you will before the takedown occurs.

>>linker+(OP)
This is stupid and just like Chamberlain with their MyQ snafu [1]. Assuming the developer did not steal the code, then this sort of work should be protected. If you have a public API, people should be legally allowed to use it and work against it. If you as a company don't like that, then make it harder for 3rd parties. If the open source code is abusive, then use a freaking WAF to protect yourself. But unless they are hacking yours system, stealing code, or being intentionally abusive there should be no legal recourse here.

Or... better yet, engage with these clearly VERY passionate customers. This is someone who not only bought your product but has donated hundreds or thousands of hours of their free time to making your product better. Better how? Because its works in a way your customers want that you don't otherwise offer. Instead of demanding take down, file a bug report with them to explain how the code is misbehaving. Bugs happen, maybe the developer didn't include an exponential fall off for outages. Whatever. Let them know and they'll probably fix it. Heck, you could use one of the in house developers to file a pull request to fix it yourself.

That's how you be the good guys. Instead of stomping on small projects of passionate customers, you engage with them. Make them even more a fan of your product, rather than a lifetime hater.

[1] https://www.home-assistant.io/blog/2023/11/06/removal-of-myq...

>>linker+(OP)
Unfortunate. I'm not directly affected by this takedown, but I just started using Home Assistant with my GE (owned by Haier) washer and dryer via this repo: https://github.com/simbaja/ha_gehome

I often forget to take clothes out of the dryer in the garage, so I'm working on an automation to flash the lights by my desk with increasing urgency the longer clothes are left in.

I'm very surprised how well Home Assistant works for its kind of hobby project, it's matured quite a bit from when I looked into it a few years back. It's not a huge win if all your devices are already HomeKit and programmable via Shortcuts, but it's that it can bridge my non-Homekit Nest, ECOVACS, and GE devices into HomeKit land, and offer unified WebSocket & REST APIs to program against.

I can see why companies would send the takedown notices if their API service implementation is low quality. The HomeAssistant user has to be a super-expert, the sort of person to set up a Google Cloud project to create OAuth credentials so you can connect your calendar. There can't be a lot of those people, and the integrations are probably quite spammy with API polling.

>>elkos+ya
Ubiquiti did that[1], didn't work out so well[2].

1. https://www.home-assistant.io/blog/2018/04/12/ubiquiti-and-h...

2. https://www.home-assistant.io/blog/2019/05/03/update-from-th...

>>H8cril+Fu
Probably this: https://github.com/Andre0512/pyhOn/blob/main/pyhon/const.py

>>linker+(OP)
[dupe]

Discussion: >>39044932

>>kstrau+ug3
Scratch off everything that requires internet access (in this case the Home Assistant integration talked to the vendor's API servers).

See also previous discussion on >>39044932

>>Dyslex+0k3
Pretty much any vendor selling commercial appliances. SpeedQueen even gives you the choice of the old school mechanical controls. I don't know if they even have any smart consumer devices. They can be a bit more expensive but rarely break from household use.

For smaller non-appliance stuff there's CloudFree [1] which sells products from other vendors that can be reflashed with ESPHome (no affiliation, just a happy customer).

[1] https://cloudfree.shop/

>>malerm+Lm3
ZWave is another option here too. I wouldn't recommend devices that don't have at least a "500 series"[0] chipset, but pretty much any device you'd buy today or moving forward will contain this or a newer chipset.

[0] https://www.silabs.com/wireless/z-wave/500-series-modules

>>beeboo+MD3
legislation?

Radio Equipment Directive which now has a huge cybersec impact. So if you want to sell hardware in EU it must be certified

here is a lot of what will be in there. https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02...

the final standard is not the above but based on the ideas in ETSI.

While the above applies mostly to the "thing" the cloud and edge that enable services for IoT will be covered by the hotly debated CRA:

>>38818734

>>38787005

>>linker+(OP)
I was researching whether there's legal precedent making such uses legal, and ChatGPT pointed out that "Sony Corporation of America v. Universal City Studios, Inc.," where it was decided that developing a VCR where users can record Universal's content is legal.

https://en.wikipedia.org/wiki/Sony_Corp._of_America_v._Unive....

I think this applies here as well. Curious how this will play out.

>>lxe+tJ3
Here's the chat log if you're curious:

https://chat.openai.com/share/6386ad1f-a44d-4cc1-a5d1-0e3c3c...

Sega Enterprises Ltd. v. Accolade, Inc.: In this 1992 case, the court held that Accolade's reverse engineering of Sega's game console for the purpose of developing compatible games without licensing was a fair use.

Sony Computer Entertainment, Inc. v. Connectix Corporation: In 2000, the court ruled that Connectix's reverse engineering of the Sony PlayStation to create a compatible emulator (Virtual Game Station) was fair use.

>>Dyslex+0k3
Esphome supports several AC units using a simple dongle: https://static.xtremeownage.com/blog/2023/pioneer-mini-split...

>>hangon+Xp3
You can see "Adversarial Interoperability" on Youtube to see talks on this.

This is a good one:

https://www.youtube.com/watch?v=rimtaSgGz_4

>>linker+(OP)
FWIW This is Haier Europe, Haier US supports Home Automation and DIY IOT:

https://www.reddit.com/r/homeassistant/comments/19a615l/haie...

>>linker+(OP)
Just like the recent case of Mazda sending a Cease and Desist to someone writing an integration:

>>37990990

I would suggest complying. Then, probably, a clone of the repo could maybe show up in some other git host, like Gitee, without authorship information that can reveal who to send further legal threats.

I would of course never do such thing. Just talking about an idea a friend had.

>>hedora+ot4
> At what point will the courts decide that post purchase contracts are unenforceable?

I believe EU has already done that. That'd be a hidden term, I believe.

https://europa.eu/youreurope/citizens/consumers/unfair-treat...

>>hoover+lL
Not sure if you mean bulbs or strips. For bulbs, most of IKEA's smart home stuff is Zigbee, supported by HE community drivers, and is priced well.

For strips, if you're ok with wifi, HE supports local control of Kasa devices, which is made by TP-Link. Otherwise your best bet is something Zigbee-controlled but I don't have a particular recommendation.

Check the HE forums[1], too, they're very active and full of recommendations, driver links, and experience reports.

[1] https://community.hubitat.com/

>>beeboo+yz3
I think the issue, particularly in the case of some of the companies that have been hostile to Home Assistant integrations, is that, according to them, the small number of users with reverse engineered access to their cloud, tend to abuse the API by creating a significant percentage of the traffic, presumably by accessing it "incorrectly".

I agree with you wholeheartedly that it should be fair game, but ultimately, if reverse engineered users are creating, say, 50% of traffic[0], because they're polling instead of using the proper push mechanism, these sorts of companies can and will get upset.

Frankly, as a backend software engineer myself, if any system I built with the purpose of being constantly accessed by a fleet of devices sold on the open market couldn't handle the relatively tiny numbers MyQ created a fuss[1] over, I'd be embarrassed.

[0] https://chamberlaingroup.com/press/a-message-about-our-decis... [1] https://www.home-assistant.io/blog/2023/11/06/removal-of-myq...