When the product is really a subscription

The authentication layer no one disclosed

A smoke detector lasts until its sensor wears out. A drill lasts until the motor or the chuck fails. Both of these things can be measured: materials degrade on known timescales, and the failure mode is physical. A thermostat that phones home to a vendor server to confirm it is authorised to run is a different object entirely. Its lifespan is not set by its components. It is set by a boardroom decision.

This is the core mechanic behind what the industry calls a tethered device: hardware that will not operate fully — or at all — without a live connection to infrastructure the vendor controls. The tether is rarely disclosed plainly at point of sale. The box describes a thermostat, a hub, a camera, a lock. The word "subscription" does not appear. But the authentication call is in the firmware from day one, and when the server stops answering, the device stops working. The physical object is fine. The contract has expired.

The clearest documented case remains Revolv. Nest acquired the smart-home hub maker in 2014 and shut down its cloud service in May 2016. Revolv hubs — devices that had retailed for around $300 — became inoperable overnight. The hardware was undamaged. Owners had no recourse. The Federal Trade Commission received complaints, but no enforcement action followed. What the episode established, practically, is that a vendor who acquires a competitor acquires also the right to switch off that competitor's customers.

What the authentication call actually costs you

Zigbee and Z-Wave devices represent the practical proof that longevity is a design choice, not an inherent constraint of wireless home automation.

The purchase price of a tethered device includes, invisibly, a bet on the vendor's longevity. Nest could afford to absorb the Revolv episode because its parent, Google, had the scale to weather the reputational cost. A smaller company cannot make that guarantee, and a smaller company is far more likely to exit the market, be acquired, or simply stop paying its server bills. The residual value of a device that depends on a vendor's continued operation approaches zero the moment the service ends — and because the market knows this, secondhand prices for cloud-dependent hardware collapse well before shutdown, as rumours circulate and listings pile up.

The cost has a second dimension that is almost never discussed at retail: the opportunity cost of the data the device generates. A tethered device that processes voice, image or behavioural data on a vendor's server is not simply a device you bought. It is a node in the vendor's data-collection infrastructure. The value the vendor extracts from that data is not returned to you, and it is not disclosed in any figure on the box. When the service ends, that value extraction ends too — but so does the device's function, even though you still physically possess it.

Parts and repairability compound the problem. A tethered device that could theoretically be repaired at the component level is often sealed in ways that make repair impractical: adhesive construction, proprietary fasteners, no available schematics. iFixit's repairability scoring, which the organisation has applied to consumer electronics for well over a decade, consistently finds that cloud-dependent devices score among the lowest — not because the electronics are inherently fragile, but because the design anticipates replacement rather than repair. The European Commission's Ecodesign regulation ↗, which came into force for a range of product categories from 2021, requires spare parts and repair documentation for certain appliances, but its scope does not yet fully encompass smart-home devices, and authentication requirements are outside its remit entirely.

The open alternative, and why it hasn't won

The contrast with open-protocol hardware is instructive. Devices built on Zigbee — now governed by the Connectivity Standards Alliance, formerly the Zigbee Alliance — continue to function across hub generations because the radio layer was standardised and the authentication is local. A Zigbee sensor paired to a hub in 2016 can be re-paired to a different hub in 2025 without asking anyone's permission, and the sensor's value depreciates with its hardware, not with a vendor's balance sheet. Zigbee and Z-Wave devices represent the practical proof that longevity is a design choice, not an inherent constraint of wireless home automation.

Home Assistant, the open-source home automation platform, has grown substantially by absorbing devices that vendors have abandoned. When a manufacturer ends a cloud service, the Home Assistant community frequently reverse-engineers the local API — if one exists — and publishes an integration that restores function without the vendor's server. This works only where the device has any local control pathway at all; a device that requires the vendor's server for every command, with no local fallback, cannot be salvaged this way. The presence or absence of a local control mode is therefore a material fact about a device's long-term value, and it is almost never on the box.

The Matter standard, ratified in 2022 and overseen by the Connectivity Standards Alliance, attempts to address the application-layer problem that Zigbee addressed at the radio layer. Matter devices are required to support local control as a baseline. Whether the standard's adoption becomes broad enough to shift market norms is not yet settled — the installed base of cloud-dependent devices is enormous, and vendors have strong incentives to keep users on their own infrastructure.

What to check before you buy

The practical question, for anyone buying hardware today and wanting to know what it will be worth in five years, is whether the device has a meaningful support window and a local control fallback. A vendor who commits to a support window in writing, publishes the length of that window and provides a local API is making a verifiable promise. A vendor who says only that the app "will work with your device" is making no promise at all.

Right-to-repair legislation ↗ passed by the European Parliament in April 2024 moves the dial on physical repairability, but it does not touch the authentication layer. A device that you can open, and whose parts you can replace, still becomes a paperweight if the vendor's server goes dark. The hardware and the service are sold as one thing; they need to be evaluated as two. One of them is yours. The other is borrowed.