> They do require a one-time connection to perform key exchange of a long-live authorization key

What does my offline dishwasher need a long-lived authorization key for?

Maybe it has some embargoed technology and needs to make sure it's not in China or something.

IANAL but I'm pretty sure the issue is distribution, so as long as they don't sell their dishwasher in China it isn't their problem. If someone buys and resells it in China then the reseller is in trouble. (Obviously it is a bit more complicated if they should know about this reselling but it shouldn't require online activation.)

It's a joke. It's probably made there anyway.

I assume only if you're setting it up to work "offline" with the app. Issuing a key pair to the hardware and the app from their ecosystem's trusted authority does seem like a secure way to do it.

Why can't the dishwasher or phone generate that key though?

Because they want people to connect online.

I’ll assume they use this to “register” your product so they know when the warranty actually started.

Cool. I’d still prefer a “no wifi” or even “no app” mode, and control everything via hardware buttons.

Hardware offline UX gives me hope that my data would not be sold or that I wouldn’t have to pay for an extra subscription or watch ads. Perhaps it’s correlation.

Still, “no cloud” is a step in the right direction; I’ll take it.

“ In no-cloud mode the only way to interact with the devices is through their app, and an app isn’t always the most convenient way to interact with devices in the home.”

Note that it is "the only way to interact remotely". That is, no cloud mode disables interaction with e.g. Home Assistant but not interaction with the buttons.

Jeff mentions it in the post:

> Another third option is somebody has reverse engineered this protocol and built HCPY, a Home Connect Python library.

> But here's the problem: I already spent like four hours getting this dishwasher installed in my kitchen. I don't want to spend another four hours configuring my own web UI for it—which still requires at least a one-time connection through Home Connect!—and maintaining that as a service on my local network, relying on an unauthorized third party library using reverse-engineering to get at the private dishwasher API!

...how long is "long-live" ?

We've all been there. It works, until the shareholders decide differently, and you can no longer use your dishwasher without connecting / agreeing to the terms.

The shareholder of Bosch is, with 94% of the shares, the Robert Bosch Foundation. Look it up to see what they do.

https://en.wikipedia.org/wiki/Robert_Bosch_Stiftung

That's an improvement, but the requirement to use an app is still a serious problem, even if it never phones home. Everything should be able to be done on the appliance itself. Installing an app should never be a requirement.

I disagree. Moving stuff to an API with full local control is a UI decision. Moving it to the cloud is a privacy and obsolescence decision. Huge difference.

Using an app has inherent security implications (it's very, very hard to trust apps). However, I agree that in terms of security, using an app with local control is better than something cloud-connected.

My primary issue with requiring the use of an app is that apps are a pain in the ass. Allow the use of an app as an option, sure, but the appliances should be able to be fully used with the controls on the appliance itself as well. Requiring the use of an app is a dealbreaker for me, but for usability reasons more than security reasons.

Hence the UX decision