Yes, the #1 rule of IoT - if it doesn't have a solid LAN-only protocol, don't buy it. Anything relying on a single cloud service isn't worth your time or money. If you have LAN-only access it means not only that you'll have the ability to use it after the manufacturer goes away but also that you can always secure it by simply dropping it behind the appropriate NAT or firewall.

I was just reading a review of a sous vide stick the other day that mentioned that issue. Fortunately, it supported Bluetooth...

Even Bluetooth is a no-go. What happens if the control is app no longer available or drops support for your model? Something like a sous vide stick should have control buttons.

Ditto for stuff like Roombas. I've noticed all the new ones have their schedules set via an app. WTF? My current one has buttons and that works just fine. I'm seriously thinking of getting a spare now.

Smartphones are great solution for controlling a lot of things, but it seems like we're in a place where people stupidly think it's the solution to control all things.

I think Bluetooth could be doable; assuming their use of the protocol is well documented and open to 3rd party implementation. For a lot of these devices, the API could be described in AT commands (flung over any of several bluetooth profiles) pretty easily.

These devices use Bluetooth Smart/LE (as opposed to traditional). It provides functionality more akin to RPC and Pub/Sub. But yes, it's easily implemented if documented, I've done a device to replicate another vendor's protocol for some basic IO.

Yeah fortunately. I was just thinking the other day how terrible life was before Bluetooth enabled sous vide.

This has got to win HN today for the most HNist of comments. ;)