All nineteen pieces, by section

Nest shut down the Revolv hub's service in 2016 after acquiring the company, which turned working hardware into a case study cited ever since.

A device that authenticates against a vendor server has a lifespan set by the vendor's business, not by its components.

Firmware updates have disabled features, third-party accessories and in some cases whole units, with no route back to the previous version.

Authentication chips in cartridges, batteries and accessories exist to make a third-party part fail rather than to make the product work better.

Adhesive assembly and proprietary fasteners raise the cost of opening a device far above the cost of the part inside it.

Serialised parts mean a replacement can be identical and still be rejected, which is the practice several repair statutes now name directly.

Zigbee and Z-Wave devices keep working across hub generations because the radio layer was specified independently of any one vendor.

Matter is an industry attempt to standardise the application layer, and its value will be judged on whether devices survive their vendors.

MQTT was designed for constrained links and remains the practical spine of self-hosted device control two decades on.

Home Assistant exists to keep control on the local network, and the size of its integration list is a measure of how much has needed rescuing.

Global e-waste is reported in the tens of millions of tonnes a year, with a documented collection rate far below what is generated.

Repair laws in the EU and several US states now compel parts, tools and documentation, which is a legislative answer to a design decision.

Resale value collapses when the service ends, which is why lifespan and price should be read together at purchase.

Reported service lifespans for consumer electronics have fallen, and the fall is steeper for connected devices than for unconnected ones.

Repair rates are low and the reasons recorded are cost, parts availability and time rather than a lack of interest.

Stated support windows for connected devices are short relative to the hardware's physical life, and several markets now require the period to be published.

Networked consumer appliances appear at the end of the 1990s, and the dependency was in place before anyone asked what happened when the server left.

By the early 2010s the vendor cloud was the assumed control path, and local-only operation had to be argued for.

Recent statutes require parts and documentation but mostly stop short of requiring that a device keep working when the service ends.