I guess I'm not buying that GE washer/dryer combo now...
Haier hits Home Assistant plugin dev with takedown notice
61–70 of 172 posts
Re: Haier hits Home Assistant plugin dev with takedown notice
#62Earlier quoted context omitted.
Philips Hue did run locally, and now they are rolling out updates where a cloud account is required.
And I don't know if it's just me, but responsiveness seems worse in recent months (using iOS app, don't know if it's the app or the bulbs or the hub). And sometimes the app is out of sync with the actual light states. I haven't seen this in years of using Hue bulbs and app. Plus finding I'm logged out and having to log back in when I just want to turn a light on/off in the middle of the night (because baby) is a PITA…
I haven't had Hue login troubles, but the quality of the light control has gone down a bit. If I tell it to turn the lights to the fireplace mode, that gets turned into multiple instructions to the light bulbs, but sometimes it drops some of them for no reason. So I get half-brightness daylight-white instead.
Re: Haier hits Home Assistant plugin dev with takedown notice
#63Earlier quoted context omitted.
It's not marked as a fork in their systems. Instead, it's as if you'd written a bunch of code in a local repository and then pushed it to GitHub. It could still be identified as the same codebase by eg. comparing commit hashes or content hashes, but that's harder. If you really want to be sure, clone the repository, make a few local edits to files (eg. adding a comment to each file), copy the full source repository t…
Find the first commit and overwrite it :P
That could still be fairly easily detected by looking at the tree and blob ids.
Re: Haier hits Home Assistant plugin dev with takedown notice
#64I hate home automation! I hate home automation!
I have a Hubitat Elevation for Aqara temperature/humidity/pressure sensors mostly. They all run locally. I'd like to throw some smart LEDs in the mix for ambient lighting. What's a good, non enshittified vendor?
Re: Haier hits Home Assistant plugin dev with takedown notice
#65Earlier quoted context omitted.
>local HTTP interface A lot of the worst IoT vulnerabilities in the past have been due to exactly that. 'Local' unfortunately isn't something decided at design time, it's decided when someone connects it to a network. Most people plugging these devices in don't have any clue how to simultaneously secure them and connect them to the internet, so they often end up directly on the internet with default credentials or wi…
Even though I advocate for a local interface, I also completely agree with your statement. But, the alternative is we either accept this completely upside down API traffic ratio with locally focused integrations (bad, costs lots of money) or allow a local interface. Another potential workaround I advocated for was a "cloud down" message that could enable the local interface for those that ONLY go looking for how to d…
With my developer hat on, I agree.
With my business hat on, I'm not so sure. "Why are we spending development resources on a feature that isn't valuable for our target users?"
I could definitely see doing this if it were a product with a prosumer-type angle to the value prop. But for the devices we see on the shelf at a big-box store, I don't think those companies' management considers that valuable.
Re: Haier hits Home Assistant plugin dev with takedown notice
#66Earlier quoted context omitted.
At the risk of asking a dumb question, what does a git push do for you there? (Fully agree on the clone locally point.)
Not the GP but at that point it's available and more discoverable for at least a little while longer for others (and no guarantee you'd get hit with a takedown as well).
Don't rely on GH alone. Save a local copy. Host it somewhere that isn't so centralized and discoverable. One upside of increasing centralization is that people who you don't want finding things are awful at finding said things that exist outside it.
Re: Haier hits Home Assistant plugin dev with takedown notice
#67It's annoying how, in the world where a few boys could code Second Reality in 1993 in barely a megabyte or two, on computers that were a tiny fraction of what we're using today, we (collectively) have somehow obfuscated the matter of simple remote sensing and switching across a network into this ongoing kerfuffle of competing interests and complex, shaky solutions.
Re: Haier hits Home Assistant plugin dev with takedown notice
#68Earlier quoted context omitted.
Even though I advocate for a local interface, I also completely agree with your statement. But, the alternative is we either accept this completely upside down API traffic ratio with locally focused integrations (bad, costs lots of money) or allow a local interface. Another potential workaround I advocated for was a "cloud down" message that could enable the local interface for those that ONLY go looking for how to d…
With my developer hat on, I agree. With my business hat on, I'm not so sure. "Why are we spending development resources on a feature that isn't valuable for our target users?" I could definitely see doing this if it were a product with a prosumer-type angle to the value prop. But for the devices we see on the shelf at a big-box store, I don't think those companies' management considers that valuable.
At this point? I'd push harder to avoid all this negative press that is pervasive in IoT journo when it REALLY impacts a percent of a percent.
When the Chamberlain story happened, I received questions from executives on why it was such a big story.
From a business perspective, it just isn't.
I agree with you.
Same reason we don't dedicate people to write HA integrations.