Insteon shut down its servers overnight in 2022 and bricked tens of thousands of homes. Lowe’s Iris hubs went dark in 2019. Wink stopped processing commands without a subscription that customers were never told to expect. Logitech killed Harmony Hub in 2021 (then partially walked it back, but the trust was gone). Best Buy ended its Insignia Connect hub. Charter killed its “Spectrum Home Security” product line and gave customers 30 days. Wyze had three separate cloud incidents in a single year. The pattern is consistent enough that planning for it isn’t paranoid — it’s just realistic.
If you live in a Utah home that has anything more than a few smart bulbs, this post is the survival guide. What actually happens when a manufacturer sunsets a product, what to do in the moment, and (most importantly) how to buy in a way that minimizes the damage when it happens again.
What “loses cloud support” actually means
Cloud sunsets come in flavors, and they don’t all hit equally hard. From least to most catastrophic:
- App removed from the store, but devices still work. Annoying. New family members can’t install the app. Existing installs continue to function. You have time to plan.
- Cloud features go away, local control survives. Voice assistant integration breaks. Push notifications stop. Remote access from outside the home stops. But the device still talks to local controllers (Home Assistant, HomeKit hub, Z-Wave/Zigbee coordinator).
- Cert chain expires or is revoked. The device fails to connect to its cloud relay because the server’s TLS certificate stopped being valid for it. Symptoms look random: devices that were fine last week start showing as offline. No replacement firmware is coming.
- Cloud goes fully dark. The relay shuts down. The device can’t phone home, and because it was designed to require a successful cloud handshake at boot, it doesn’t function locally either. This is the Insteon scenario. It is a brick.
The first two are inconveniences. The fourth is what people mean when they talk about stranded smart-home devices. We covered the broader business pattern in our piece on smart-home vendor failure and what to do about it. This post is the practical companion: when it happens to you, here is what to do.
Step 1: figure out what you actually have
The first move on any sunset announcement is an inventory. We use the same checklist we run on takeover audits: walk every floor, photograph every smart device, and note the protocol it uses. The protocol matters more than the brand.
- Wi-Fi only, cloud-required. The most vulnerable category. If the product is sunsetting, these are paperweights. Wyze cameras (older models), most cheap Tuya-relabeled bulbs and plugs, original Insteon hub.
- Wi-Fi with local API. LIFX bulbs, Shelly relays, Tasmota-flashed devices, ecobee thermostats with the local API enabled. Cloud loss is annoying but survivable — Home Assistant or HomeKit can keep them working.
- Zigbee / Z-Wave / Thread. These are local protocols by definition. Even if the manufacturer’s app and cloud go away, a third-party hub (Hubitat, SmartThings, Home Assistant with a USB Zigbee/Z-Wave stick) can re-pair the devices and bring them back. Hue bulbs, most Lutron Caseta gear, Aqara, and Ikea Trådfri all live here.
- Matter. Newer category, but the protocol is local-first by design. A Matter-over-Thread bulb will keep working even if the original brand disappears, as long as you have any Matter controller (Apple Home, Google Home, SmartThings, Home Assistant).
Step 2: triage by criticality
Not every device is worth saving. The order of operations on a sunset, in our experience:
- Door locks, garage doors, alarm system. If anything in this list relies on a cloud relay that’s going away, replace immediately. We don’t accept risk on access. Period.
- Cameras. Cloud cameras losing cloud means losing footage retention. For a house we already migrated to a local NVR — per our local NVR vs. cloud cameras post — this isn’t a crisis. For a household running purely on cloud, it is.
- Thermostats. A non-functional smart thermostat is still a thermostat — you can usually fall back to manual control. But the automations and the cost-saving features go away. Plan a replacement on a non-emergency timeline.
- Lighting. If your bulbs are Hue, Caseta, or Z-Wave, you’re fine; the protocol survives the brand. If they’re cloud-Wi-Fi bulbs, the cheapest move is to replace gradually rather than panic-rip.
- Convenience devices. Smart plugs, button remotes, robot vacuums — these are inconveniences if they go dark, not emergencies.
Step 3: set up Home Assistant before you need it
Home Assistant is the single best insurance policy a smart-home household can buy. It’s open-source, runs on cheap hardware (Raspberry Pi or a $300 mini-PC), supports effectively every protocol, and most importantly it doesn’t depend on any vendor cloud. When a manufacturer sunsets, Home Assistant’s community usually has a local integration online within days.
We compared the platforms in detail in our post on Home Assistant vs. HomeKit vs. Alexa. The short version for this post: even if you run HomeKit or Google Home as your primary user-facing automation platform, you should have Home Assistant in the basement as a fallback bridge. It costs almost nothing and it has saved more than one of our customers from a Wink-shaped paperweight collection.
Step 4: stop the bleeding on subscriptions
A sunset announcement often comes with a companion email: “upgrade to our new product line for $X/month.” This is the vendor monetizing your installed base. Read carefully. Sometimes the new offer is honest value; often it’s just a way to fund the next sunset. We have a long post on evaluating these offers in smart-home subscription creep — the rule of thumb is that any feature that worked locally before and now requires a subscription is a red flag.
How to buy so this hurts less next time
The buying rules we recommend to homeowners in Holladay, Lehi, Draper, and Park City who have been burned once and don’t want to be burned again:
- Prefer protocols, not brands. Zigbee, Z-Wave, Thread, and Matter outlive individual manufacturers. A Zigbee bulb works on any Zigbee hub. A Wi-Fi bulb that only talks to one app doesn’t.
- Prefer local-first ecosystems. Lutron Caseta, Hue, and the Apple Home Key family all work without internet access. UniFi Protect cameras record to your local NVR with no cloud dependency. These are the ecosystems with the cleanest sunset path because there’s nothing to sunset.
- Avoid cloud-required big-ticket items. A $1,200 Wi-Fi-only cloud-required pool controller is a $1,200 brick when its servers go away. A protocol-based equivalent is sometimes a few hundred dollars more upfront and survives forever.
- Look at vendor age and finances. Lutron has been making lighting controls since 1961. Signify (Philips Hue) is publicly traded and has been at it for a decade. Random Kickstarter darling that launched 18 months ago is a different risk class even if the product looks great in the review videos.
- Choose UniFi or equivalent for the network layer. Network hardware that runs locally (UniFi controllers can run on your own NUC, no cloud account required) is the substrate that everything else depends on.
This isn’t about being anti-cloud. Cloud offers real value for some categories — voice assistants, off-site footage backup, remote access. It’s about not letting the cloud become a single point of failure for things that should be local. We dive into the broader philosophy on the smart switches vs. smart bulbs post, which is structurally the same argument.
The 30/60/90 sunset playbook
When a sunset notice arrives, here’s the timeline we work to:
- Day 0–7: Inventory. Identify which devices are critical (locks, alarms, cameras), which are convenient (lights, plugs), and which are cosmetic. Confirm protocols.
- Day 7–30: Replace or migrate the critical tier first. If your front door lock is going dark, don’t wait. Schedule the swap.
- Day 30–60: Stand up Home Assistant if you don’t already have it. Migrate any local-API devices to local control through Home Assistant before the manufacturer’s cloud goes dark, because you’ll need the cloud account to do the initial onboarding for some of them.
- Day 60–90: Retire devices that have no local-control path and aren’t worth replacing. Donate or recycle. Document the new state of the house in your network handoff packet.
The hardest part: telling the family
The actual hardest part of a sunset isn’t technical — it’s telling your spouse that the “Hey Google, turn on the porch light” that worked last week doesn’t work this week, and won’t until you finish the migration. We schedule this work in a single weekend whenever we can, with a clear plan up front, so the household isn’t living through a multi-week degradation. Surprises during a sunset are much worse than scheduled replacements.
Bottom line
Smart-home sunsets are a structural feature of the industry, not an exception. Plan for them up front by buying around protocols, keeping Home Assistant warm in the basement, and avoiding cloud-required gear in the categories where it matters most (locks, garage, alarms, cameras). When a sunset hits, triage by criticality, replace fast where you have to, and migrate slowly where you can. The households that suffer least are the ones that already had the answer in place before the question was asked.
Keystone Integration designs sunset-resistant smart-home systems for Holladay, Lehi, Draper, Park City, and the rest of the Wasatch Front — with local control, protocol-based device choices, and a Home Assistant fallback layer baked in from day one. See the full service list or get in touch if you’re staring down a vendor shutdown notice and need a plan by next weekend.