There is a growing catalogue of smart home products that stopped functioning because a company discontinued a service, was acquired, or simply switched off servers.
In several documented cases, devices that worked perfectly well as hardware became unusable because the software they depended on was withdrawn.
The determining factor is an architectural choice, and it's visible before purchase if you know what to look for.
Two architectures
Cloud-dependent. The device communicates with a manufacturer's servers. Your app talks to the servers, which talk to the device. Even when you're standing next to it.
If the servers go away, the device stops responding to control, regardless of whether the hardware works.
Local control. The device can be controlled directly over your local network, without reference to any external service. Cloud connectivity may exist for remote access and isn't required for basic function.
If the company vanishes, the device continues working on the local network.
Most consumer smart home products are cloud-dependent, for reasons that are commercially rational.
Why manufacturers choose cloud
It's easier. Remote access works without users configuring anything. Updates can be pushed. Devices can be simpler and cheaper because processing happens elsewhere.
It provides data. Usage information has value.
It enables recurring revenue. A device requiring a service is a device that can require a subscription.
And it provides control. The manufacturer determines what the device can do, indefinitely.
None of that is unreasonable from the manufacturer's perspective, and it creates a dependency the buyer generally doesn't evaluate.
The failure modes
Discontinuation. Company withdraws the product line and shuts down servers. Devices become inert.
Acquisition. Acquirer discontinues the acquired platform, migrates users to their own, or simply stops maintaining it.
Business failure. Company ceases trading and servers stop.
Feature removal. Functionality that worked is moved behind a subscription, or removed.
Outage. Temporary but disruptive. A cloud outage means lights that don't respond and locks that don't unlock, which for some device categories is more than an inconvenience.
Connectivity loss. Your internet connection fails and devices in your house stop responding to controls in the same house.
What to check before buying
Does it work without internet? The single most useful question. Some manufacturers state this clearly; for others, reviews and community forums will establish it.
Does it support a local protocol? Devices supporting local control over standard protocols can generally be integrated with local automation systems that don't depend on any manufacturer.
Is there a physical control? A smart switch that also works as a switch is a substantially better product than one that only works through an app. This is easy to check and frequently overlooked.
Is there an open API or local access? Enables third-party integration and provides an escape route if official support ends.
What's the company's track record? Manufacturers that have previously discontinued products and left customers stranded are likely to do so again.
The interoperability standards
Industry efforts to address fragmentation exist, aiming to provide common standards so devices from different manufacturers work together and support local control.
Adoption has been slower than announced and implementations vary in completeness. Some devices support a standard nominally while requiring the manufacturer's app for setup or for anything beyond basic functions.
The direction is positive and the promise of universal interoperability remains partly unfulfilled. Checking what a specific device actually supports, rather than which logos appear on the box, is necessary.
Local automation platforms
The approach that most directly addresses the dependency problem.
Open-source home automation platforms run on hardware you control, integrate with devices over local protocols, and continue functioning regardless of any manufacturer's decisions.
The trade-off is real: setup requires more effort, some technical comfort is needed, and you become responsible for maintenance.
For anyone with more than a handful of devices, or with anything important depending on them, it's worth considering. The effort is front-loaded and the resulting system doesn't stop working because a company changed strategy.
The categories where it matters most
Not all devices carry equal risk.
Low stakes: a smart bulb that reverts to a normal bulb. Annoying, not serious.
Higher stakes: heating controls, where failure has consequences in cold weather. Door locks, where failure has obvious implications. Security cameras and alarms, where the entire function depends on the service. Anything relied upon for accessibility.
For those categories, the local control question isn't a preference. It's the difference between a device that degrades gracefully and one that fails completely at the moment a company you've never dealt with makes a decision.
The end-of-life question
A specific thing worth asking before purchase and almost never asked: what has this manufacturer committed to, in writing, about how long the service will run?
Most provide nothing. Terms typically reserve the right to discontinue at any time with limited notice.
A small number of manufacturers have made explicit commitments to minimum support periods, or have committed to releasing local control capability if they discontinue a product. Those commitments are a genuine differentiator and worth seeking out.
Regulatory attention to this is emerging in some jurisdictions, including proposals requiring disclosure of support periods at point of sale, which would make the comparison possible.