But forget the analogy.
Cloud services are services. If you buy a device that requires continued services to operate, and the service goes away, it doesn’t operate.
People might be mad about this, but I’m sure everyone on this forum is smart enough to realize that servers don’t run themselves
They destroyed the lawnmower and now want you to rent one.
The customer didn't buy access to a service with a physical product to serve as support for that service, they purchased functionality, and that functionality is (potentially illegally) being taken away from them.
Nor is there really anything unique about artificial proprietary lock-in when it comes to services. As a business practice it’s not uncommon.
Are they? To me it looks like legitimate complaints and only that.
> Nor is there really anything unique about artificial proprietary lock-in when it comes to services. As a business practice it’s not uncommon.
It's unique in its illegallity. They're lucky these aren't very expensive products, or people would actually go to court and maybe force the manufacturer's hand for once.
Like with Nest going EOL. There's no reason that it needed a wifi connection to operate. The server doesn't hold any useful information and just proxies instructions to your nest device when you use the app.
It would have been nice if rather than wifi being used to communicate with googles' servers, wifi was just used to communicate with your app on your device via the local network. Or bluetooth was available as a fallback.
I’m a nest early adopter affected by the nest EOL. I presume you mean: there’s no reason it needs a cloud service? Because it definitely needs network access for you to connect to it remotely.
But if you are familiar at all with the history of IOT devices, the reason why cloud connected devices took off in popularity, is because they do NAT traversal for you. Most people struggled to set these devices up before the advent of cloud IOT.