If this is the real reason, how long can you expect Haier to support the API free of charge for existing customers? Not very long I bet.
The only sane solution are applicances that can be controled locally without an internet connection.
Or just support a local API with a published spec. Matter is supposed to be that standard, but adoption is going slowly. Pretty sure zero people using the original reverse engineered cloud API for the Haier stuff in HA want to be using it in preference to a local API.
This seems naïve: "Yes, it's making money, but it isn't making enough money" is the phrase on the tombstone of a lot of goods, services, and come down to it, countries through history. Being a customer is no guarantee you get to keep being a customer.
> and drive manufacturers to make locally-controllable devices to appeal to price-sensitive consumers.
"Special Deal: Comes With Free Six-Month Subscription With Purchase!" because six months is how long they intend to support the device, after which they turn off the service and brick all of them, and of course you can't opt out of the special deal because they don't get any of your data from a device that isn't slaved to their servers.
I'm jaded enough to know it's not a panacea. It's further along the spectrum from "This is costing us money..." at least.
Collective action would end this problem overnight, just like it did here (although I think they are insane for buying cloud appliances in the first place).
What boggles my mind is how the average person seems so accepting of this. I get this pervasive sense that because "it's computers" or "computer adjacent" it's a given that you'll have to accept loss of functionality as devices age.
I guess it needs to get a lot worse before it gets better.
Needs to isn't the write term... Going to get a lot worse is going to happen. Getting better, well the issue is in doubt.
They don't know much about how those things work. They do know if they're losing functionality even if they don't know how they work.
My observation is that people seem endlessly patient about losing functionality in computer adjacent devices-- far beyond what they would tolerate with other devices. I simply don't understand why this is the case.
For virtually every consumer good there is some ability for independent repair. I think people would be up in arms if their car stopped working and the manufacturer said "Yeah, you just need to buy a new one". We have consumer protection laws in the US to prevent this very thing.
With software connected to "smart" devices there are no significant protections. I don't think people even know to be up in arms about a device that doesn't work because it's "old" and the native app stops working or the Internet hosted servers went away. Worse, they just landfill the device and go buy the newest one.
I assume it has something to do with the subsidized nature of smart phones and relatively short time people stick with a given phone. The "wow" factor of new technology probably dazzles people into forgetting about long-term usability too.
Hopefully when the "throwaway" mentality of smart phones really starts to cost people (as more durable good type "smart" devices embrace this model) we'll see some public backlash.
The relevance to this situation is that PetNet made a pretty good pet feeder about 5 years ago. It dispensed well, had a good app, and mostly just worked. Then, during 2020, the company just disappeared. The app stopped working, and eventually, the feeders stopped feeding. I tossed mine into the ever-growing box of "I'll get to it later", and forgot about it for a few years.
Getting it up and running wasn't tremendously difficult, and now it works almost as well as it did when its new, working significantly better in one critical area: Instead of having to sign into some other random app and fiddle with it there, I can just press a button in HomeAssistant and my cat gets a bunch of food. Maybe later I'll wire in things like the hopper sensors, scales, and other features that the device had, but for now a 1 second pulse of power works well enough
There's not really any valid reason PetNet couldn't have just released the firmware flashing keys on the way out. The device likely runs on a microcontroller very similar to ESP32/ESP8622, and so had those keys been available, I could have used the "native" hardware.
I suspect the overwhelming majority of these feeders wound up in landfills, as very few people, even the technically competent, are willing to take it apart, solder in a new control board, and get said board up and running. Which is an absolute shame.
[1]: https://pdx.su/blog/2024-01-19-fixing-a-broken-smart-cat-fee...
Agreed. I wish companies would take the work already done for them with Matter and just integrate, but if they can't, the least they could do is support the things customers to do the things they want to do.
- Management sees cost spike, asks Sysadmins
- Sysadmins investigate and say "not our fault, it's them pesky commie devs"
- Management rings up legal, shenanigans ensue
Now they've been publicly bitch-slapped, it's likely that management will do a bit of a sing and dance and then let engineers talk to engineers, while they piss off to some expensive restaurant at the company's expense.The only thing I can think of is someone outside of the "knowledge chain" caught wind of it and just fired of the legal threat.
For instance, if I told some people inside my company how much traffic HA uses in terms of how many users are on it they'd probably freak out like this too.
But their reason (cost and traffic) is the biggest reason we don't like it either.
So stop building cloud-only device interaction then... Home Assistant users will take a LAN API over a cloud API any day.
A LAN API should satisfy everyone really, no unnecessarily large bills for the manufacturer, and Home Assistant users can get better/faster integrations with shorter update intervals.
Local API for control, then submit telemetry via the cloud-version of the API they use for the app.
The obvious answer why not is: it enables people like me to just block the telemetry uploads.
But they can't have it both ways then, they can't make inefficient cloud-based control mechanisms, and then complain when people (ab)use them, because the truth is that that will not stop no matter how many cease and desists they send.
Security by obscurity is another phrase for it.
- Reading information from utility providers which few people are able to measure locally
- You want to integrate with some system which is physically outside your home, like I don't know a smart mailbox if those exist (and god damnit now I want that...)
- You are forced to because the product you have can't be controlled any other way and it's not feasible to replace it
- A locally controllable version of X exists, but it's three times the price of one from vendor Y which requires a cloud integrationI've seen a few people DIY them. You can put a reed switch or similar on the door, and watch for state changes, to trigger a "PostBox opened last at" style sensor, or use a light sensor in the box to do the same.
If you want to seriously over-engineer, you could put the box on a load cell, and measure the weight of the post.
Use an ESP32 for your control board, and its pretty much just basic ESPHome plumbing
But I appreciate the suggestions!
Get everything into HomeAssistant, build dashboards, have cool stats and automations tying stuff together. Increases the family-acceptance-factor as well, as its a hell of a lot easier to say "Everything is in this app on your phone" rather than "ok well the washer is in the Miele app and the lights are in the Lutron app and the sprinklers are the…" If something is cloud based, so what, you can still get it into HomeAssistant. Sure, local is better, but thats a secondary concern over just having it there to begin with.
Additionally, one might observe that you can make a "cloud-only" smart device local control with varying levels of intrusiveness from custom hardware devices. You can stick an ESP32 with a current loop around the power leads on a washing machine, for example, to track when the machine stops running. You could use a light sensor taped over the "DONE" light to do the same. But these are passive, observation only controls. What if you wanted to start the machine too? Or observe where in its cycle it is. An ESP based controller gets a hell of a lot more invasive, and your wife/partner might not be too happy that you just took apart the $2000 washing machine to stick a $2.50 "computer chip board" inside it.
Ideally, we'd all have everything 100% local. I'll even go out of my way to buy things that not only have local control over things that have cloud control, but within limits. Its a checkbox on a comparison sheet, not a be-all-end-all. I'll even favor things that use HTTP based configuration/APIs over apps and stuff (see the UnfoldedCircle remote, which is 100% browser configured) becuase its one less thing to have to worry about
Normal users don't want a LAN API though. They want an app that works. They want an app that works, and keeps working, even if their WiFi access point has client isolation, or their phone decides that it doesn't like the WiFi and switches to a cellular connection. They might even expect the app to work while they're not at home, and they certainly won't set up working NAT for it.
That means that the vendor has to implement a cloud API for the majority of users. At that point, it's probably cheaper to only have their app use that cloud API, even if the devices are on the same network and could see each other, simply due to the complexity of switching and maintaining the extra logic.
So the LAN API would be a completely separate feature that would have to be developed separately, and without extra effort, it would likely quickly go stale or break because there are no official use cases exercising it. That means a lot of spending for a small subset of users.
As much as I'd want a local API and would likely avoid most cloud-only devices that I can't somehow convert, I understand why vendors do it.
This aligns with the companies interests too because after they've built that they'll have somewhere to upload telemetry to.
The presence of a cloud API doesn't rule out a LAN API. The control functions exist regardless, just expose them to both the cloud and on the LAN. You could even use the cloud integration to provision authentication for the LAN API (although I'd much prefer a fully local version personally, but I'll take that compromise).
> That means that the vendor has to implement a cloud API for the majority of users. At that point, it's probably cheaper to only have their app use that cloud API, even if the devices are on the same network and could see each other, simply due to the complexity of switching and maintaining the extra logic.
Yep, that makes sense, still doesn't make having a LAN API for users to play with themselves in any way a problem, the device functions still need code somewhere to run, and exposing that code in two APIs is only marginally more work than once, the bulk of the work is in the endpoints/functions themselves.
You could even simplify the process by only building a local HTTP API, and then contain the functionality that communicates with the cloud in a single binary that just makes local HTTP requests and relays the response to the cloud.
> As much as I'd want a local API and would likely avoid most cloud-only devices that I can't somehow convert, I understand why vendors do it.
I'm not gonna lie or pretend to be naive, I understand as well, it's just that as a developer myself I know how I'd do it to provide both with minimal effort, and when I read articles like these it makes me mad because the engineering effort to get them out of this situation is tiny in comparison to the shitstorm they create by making it a legal issue.
I honestly think there needs to be some piece of regulation written about selling devices that require an online backend, because we've seen time and again how devices become non-functional because the company goes bust. That regulation should stipulate that any cloud-based functionality must be replicatable by a device-owner via local control.
Or, god forbid, contributed to the open source code repository in a way beneficial to all.
Had Haier reached out and asked the dev to optimise their HTTP calls, or perhaps adviced him on what kind of call pattern their cloud servers were optimised for so that costs could be kept low, Haier wouldn't have received all this bad press. Like many reverse engineered APIs, the HACS plugin probably does a whole bunch of inefficient API calls because there's no way of knowing what API calls are cheap and what calls are expensive.
Haier could've gone further, and set up a dialogue to include a Haier component into Home Assistant directly, and slap a "works with home assistant" logo on their products' website. I'm no market analyst, but I'd be surprised if Haier wouldn't turn a profit on implementing official Home Assistant support.