The Fridge That Needs a Firmware Update

Connected appliances are sold like property but run on a hidden lease. When the software support ends, your device doesn't just age—it gets evicted.

It was a good fridge. Kept the milk cold, the ice dispenser hummed along. But for years, the little screen on the front displayed nothing but an error message where a Google Calendar used to be. Samsung had pushed the smart fridge as a command center for the kitchen back in 2014; by the time iFixit wrote about it in December 2015, owners had been staring at that broken calendar app for over a year, waiting for a fix that never quite stuck. The hardware was fine. The ghost in the machine had simply moved out.

This is the quiet catastrophe of the connected object. When you buy a refrigerator, a security camera, or a washing machine today, you are purchasing two things: a physical good designed to last a decade or two, and a software service guaranteed to last—well, nobody actually tells you. The object is sold as a one-time purchase, a fixture of the home. But functionally, it operates as a subscription without a bill. You pay once, take it home, and hold a ticket to a show that can close at any time, leaving you with a very expensive box that has forgotten how to do the tricks it performed on the showroom floor.

The failure mode here is not mechanical breakdown. It is abandonment. We tend to think of planned obsolescence as things wearing out—batteries swelling, hinges snapping. But the connected object introduces a stranger phenomenon: the perfectly functional device that becomes useless because a server in a data center somewhere gets switched off, or a company decides that supporting a four-year-old product line is no longer worth the engineering hours. The hardware doesn't fail. The relationship does.

This creates a peculiar form of consumer limbo. You own the plastic and silicon, but you license the functionality. And unlike a gym membership or a streaming service, there is no recurring charge to remind you that the arrangement is temporary. The dependency is hidden until the moment it is severed. When Hive announced it would end support for its View indoor and outdoor security cameras on 1 August 2025, rendering them devices that would “no longer function or be secure,” the cameras didn't stop working because they were broken. They stopped working because the company declared them dead.

For a long time, this was simply the Wild West. You bought the thing and hoped. But in November 2024, the Federal Trade Commission published a staff paper examining 184 smart products—hearing aids, door locks, cameras—and found that 161 of them, nearly 89%, failed to disclose on their product webpages how long they would receive software updates or when that support would end. Basic internet searches couldn't turn up support-duration information for two-thirds of the devices. The paper noted that one product advertised “lifetime” support, yet the manufacturer had already stopped providing security updates for it in 2021. Another device’s support timeline was misreported by Google's AI Overviews, because even the machines couldn't find the truth.

The FTC suggested this silence might run afoul of the Magnuson Moss Warranty Act, which requires pre-sale availability of written warranties for products costing more than $15. But the deeper issue was cultural, not just legal: the transaction had been structured to obscure the temporal nature of the goods. When you buy a toaster, you assume it will toast until the heating element gives out. When you buy a smart toaster, you are entering a relationship with a server you cannot see, governed by terms that were never stated.

Regulators have started forcing the conversation. In the UK, the Product Security and Telecommunications Infrastructure Act came into force on 29 April 2024, requiring manufacturers to publish, for each connectable product, a defined minimum security-update support period with a clear end date. It was an admission that this information had been previously unstated, a legal acknowledgment that the “forever” implied by the purchase price was a fiction. Yet compliance remains patchy. A survey by Which? after the law took effect found that of 128 brands, 29 had no published policy or didn't respond, and 23 had unclear policies. Only 76 had compliant policies.

In the United States, the push is happening state by state. In January 2026, WIRED reported on twin bills introduced in Massachusetts by senator William Brownsberger and representative David Rogers—”An Act Relative to Consumer Connected Devices”—that would require manufacturers to disclose on packaging and online how long software and security updates will last, and to notify customers when a device nears end of service, what features will be lost, and what security risks arise. New York has a similar bill in committee. These are disclosure regimes, not mandates for longevity. They force the vendor to say the quiet part loud: This device will die on a date we choose.

But disclosure only solves half the problem. The other half is what happens after the end date arrives. Because these objects rarely get thrown away immediately. They linger. A refrigerator with a dead screen still cools. A camera that no longer receives security updates still records video. It sits on your home network, a dormant vulnerability, an open window that no one is patching. The FTC study found that many unsupported devices remain connected for years, creating a security tail that extends long after the manufacturer has moved on. The risk shifts from the company to the consumer, silently.

We have built a domestic infrastructure out of temporary commitments. The average appliance is expected to last a decade; the average software support window is often a fraction of that. This mismatch means that the most durable goods in our homes are becoming vessels for the most ephemeral services. We are filling our houses with objects that are built to outlive their own intelligence.

There is a different way to structure this. We could demand that connected devices degrade gracefully—that when the cloud connection dies, the object retains its core functionality. A smart lock should still lock. A smart bulb should still turn on. The failure of a server should not render a door handle useless. But this requires engineering restraint, a willingness to design for a future where the company may not exist or may not care. It requires treating the software as a utility that can be severed without killing the hardware, rather than as a leash.

Until then, we are left with the strange spectacle of the modern home: a collection of objects that are physically present but digitally precarious. The refrigerator in the kitchen, the camera above the door, the speaker on the counter—they are all waiting for a message from a server that may never come, holding their breath for a firmware update that will determine whether they remain tools or become trash. We bought them thinking they were ours. They are, until someone else decides they aren't.