|

Old Smart Hub Will Stop Working What to Do: Buyer’s Guide

ByAlex Turner

When a smart hub manufacturer announces end-of-life for a product, you typically get 6–18 months of warning before the cloud servers go dark. That timeline sounds generous until you realize how many devices in your home depend on that hub for local automation, voice control, and remote access. The good news: you don’t have to wait for the shutdown date to make a smart decision.

This guide covers what to do when your old smart hub stops working, how to evaluate replacement options, and where most people waste money during the transition.

Confirm What Actually Stops Working

Not all hub failures are equal. Before you buy anything, determine which functions die when the hub’s cloud service shuts down:

Function Cloud-Dependent? Local Fallback?
Voice control (Alexa, Google, Siri) Yes No
Remote app access Yes No
Scheduled automations Depends on hub Yes, if hub runs locally
Sensor-triggered scenes Depends on hub Yes, if hub runs locally
Physical button/switch control No Yes
Z-Wave/Zigbee mesh routing No Yes, while hub is powered

Key distinction: A hub that loses cloud support but still runs local automations is different from one that becomes a brick. Check your specific model’s documentation. For example, older Samsung SmartThings hubs (V1/V2) lost custom device handlers but continued local operation for basic scenes. Other hubs, like the original Insteon Hub, became completely unusable when the company shut down in 2022.

Action step: Log into your hub’s companion app and look for a “Local” or “LAN” mode setting. If it exists, enable it now. Test whether your automations still fire when you disconnect the hub from the internet for 30 minutes.

What this means for your next move: If your hub still runs local automations after the cloud dies, you can delay the upgrade and replace only the voice/remote functions with a cheaper bridge or a single voice assistant device. If the hub becomes a brick — like the Insteon Hub did — you need a full replacement before the shutdown date, not after. Check your model’s known behavior on community forums like the SmartThings or Hubitat communities before assuming either outcome.

Inventory Your Devices by Protocol

Your replacement hub must speak the same wireless language as your existing sensors, locks, and switches. This is the step most people skip, and it’s why they end up buying a hub that can’t see half their devices.

Protocol Common Devices Hub Compatibility Notes
Zigbee Smart bulbs, contact sensors, motion sensors Most hubs support Zigbee 3.0; older hubs may use Zigbee 1.2
Z-Wave Locks, switches, thermostats Check Z-Wave frequency (US = 908.42 MHz); some hubs are Z-Wave only
Thread Matter-enabled devices, some sensors Requires a Thread Border Router (built into many newer hubs)
Wi-Fi Cameras, plugs, some bulbs Works with any hub that supports the device’s cloud API
RF (433MHz/IR) Ceiling fans, blinds, TVs Rare; requires a hub with IR blaster or RF transceiver

Common mistake: Assuming all Zigbee devices work with all Zigbee hubs. They don’t. Some manufacturers (IKEA, Aqara) lock their devices to their own hubs or require a “permit join” workaround. Check compatibility lists before purchasing.

Decision rule: If you own more than 10 devices on a single protocol, prioritize a hub with native support for that protocol rather than one that requires a USB dongle or bridge.

Verification step: Before buying, open your old hub’s app and export the device list. For each device, note the exact model number and protocol. Then cross-check that model against the new hub’s official compatibility list — not the marketing page, but the actual PDF or support page. For Zigbee devices, look for the specific “device type” (e.g., “IAS Zone” for sensors) because some hubs only support certain device types even when they support the protocol generally.

Decide Between a New Hub and a Software Migration

You have three paths forward. Each has different costs, effort levels, and long-term implications.

Replace with a Same-Brand Hub

  • Best for: Users with heavy investment in one ecosystem (e.g., Aqara, Hubitat, SmartThings)
  • Pros: Device pairing is usually seamless; automations may migrate automatically
  • Cons: You’re betting the new hub won’t face the same end-of-life fate
  • Cost: $50–$150

Move to a Protocol-Agnostic Hub

  • Best for: Users with mixed-brand devices or who want local control
  • Pros: No vendor lock-in; local automation support; often supports multiple protocols
  • Cons: Steeper learning curve; some devices require manual re-pairing
  • Cost: $80–$200 plus possible USB dongles

Switch to Home Assistant (Software-Only)

  • Best for: Users comfortable with tinkering and willing to run software on a Raspberry Pi, mini PC, or NAS
  • Pros: No hardware hub needed; supports nearly every protocol via USB dongles; full local control
  • Cons: Setup time is significant; ongoing maintenance required
  • Cost: $50–$150 (hardware) or free if you already own a compatible device

Trade-off to consider: Path A is fastest but repeats the same risk. Paths B and C take longer but give you local control that survives cloud outages. If your old hub died because the manufacturer went bankrupt, Path A should feel risky.

Where this goes wrong: Same-brand replacements don’t always migrate devices cleanly. Aqara’s newer hubs, for example, use a different Zigbee implementation than their older models — some older Aqara sensors need a firmware update before they’ll pair with the M3. SmartThings’ migration from the V2 to V3 hub required users to re-pair most devices manually despite promises of a smoother transition. Budget a full weekend for re-pairing, not an afternoon, and have your Wi-Fi password and device model numbers written down before you start.

What to Check Before Buying a Replacement Hub

Use this checklist before you commit to any new hub. Each item is a pass/fail test.

  • Protocol coverage: Does the hub natively support every protocol your devices use? (Check Zigbee version, Z-Wave frequency, Thread support)
  • Local automation: Can automations run without an internet connection? (Look for “local processing” or “edge” in the specs)
  • Platform compatibility: Does it work with your voice assistant and app ecosystem? (Alexa, Google Home, Apple HomeKit, Home Assistant)
  • Device limit: How many devices does it support? (Entry hubs cap at 30–50; advanced hubs handle 100+)
  • Cloud dependency: Does the hub require a manufacturer account to function? (If yes, check the company’s track record for end-of-life support)
  • Matter support: Is the hub Matter-certified? (This future-proofs for newer devices but doesn’t guarantee backward compatibility)

If a hub fails more than two items on this list, keep looking.

Fit verification on the actual device: Don’t rely on the spec sheet alone. After you receive the hub, check the “About” or “System” page in the companion app to confirm the firmware version and which protocols are actually enabled. Some hubs ship with Zigbee disabled by default or with Z-Wave region settings that don’t match your devices. If your Z-Wave locks came from a European seller, they may be on a different frequency than the US 908.42 MHz standard — a mismatch that won’t show up in any compatibility list and will only surface when the device fails to pair.

Replacement Hub Comparison

The three hubs below represent different approaches to the same problem: replacing a dead hub without losing device compatibility.

Hub Price Brand Best For Key Feature 1 Key Feature 2 Key Feature 3
Broadlink RM MAX Smart Home Hub Varies Broadlink Replacing IR/RF-controlled devices (TVs, ACs, blinds) Wi-Fi & BLE connectivity IR/RF universal remote Alexa & Google Home compatible
Matter Smart Wired Hub Gateway Varies Jinvocloud Matter/Thread ecosystems Matter controller support Thread & Tuya Zigbee 3.0 Works with Google, Alexa, HomeKit
Aqara Smart Home Hub M3 Varies Aqara Advanced automation with multiple protocols Matter controller & Thread border router Zigbee, Bluetooth, Wi-Fi, PoE, IR Supports HomeKit, Alexa, SmartThings, Home Assistant, IFTTT

Top Pick: The Broadlink RM MAX Smart Home Hub is the strongest choice if your old hub controlled IR/RF devices like TVs, air conditioners, or motorized blinds. It’s the only hub in this comparison that handles those older remote-controlled devices directly, and it works with both Alexa and Google Home. If your device inventory is primarily Zigbee or Thread-based, the Aqara Smart Home Hub M3 offers broader protocol coverage, including Power over Ethernet for stable wired connections — a feature that matters if your old hub died due to Wi-Fi instability.

Limitation to know before buying: The Broadlink RM MAX is not a Zigbee or Z-Wave hub. If your old hub managed battery-powered sensors or locks, this device won’t replace those functions — it only handles IR/RF remote-controlled gear. The Matter Smart Wired Hub Gateway from Jinvocloud covers Zigbee and Thread but lacks Z-Wave support entirely, so any Z-Wave locks or switches in your inventory will need a separate USB dongle or a different hub.

The Aqara M3 is the most flexible of the three but still doesn’t natively support Z-Wave — you’d need to pair it with a Z-Wave USB stick and a platform like Home Assistant or Hubitat to bridge that gap.

Migrate Devices Without Losing Automations

Once you’ve chosen a replacement, the migration process follows a predictable order. Do it in this sequence to minimize downtime:

1. Export your automation list from the old hub’s app (screenshot or note format). You’ll rebuild these manually.

2. Set up the new hub with a temporary name and network. Don’t connect devices yet.

3. Pair devices in batches of 5–10. Start with sensors and switches that control critical functions (doors, lights, thermostats).

4. Recreate automations one at a time, testing each before moving to the next.

5. Only after all devices are paired, remove the old hub from your network.

Common mistake: Trying to pair devices to the new hub while the old hub is still broadcasting. This causes join conflicts, especially with Zigbee networks. Power down the old hub before pairing.

If you’re moving to Home Assistant: Use the ZHA integration for Zigbee devices or Zigbee2MQTT if you need broader device support. For Z-Wave, use the built-in Z-Wave JS integration. Don’t mix both Zigbee integrations — pick one and stick with it.

Failure mode to watch for: Some Zigbee devices won’t leave the old hub’s network cleanly. If a sensor refuses to pair with the new hub, you may need to perform a factory reset on the device itself — usually a 5–10 second button hold or a specific power-cycle sequence. Look up the exact reset procedure for each device model before you start, because the wrong sequence can brick the device or put it into an endless pairing loop. For Z-Wave devices, you’ll need to exclude them from the old network first using the old hub’s “remove device” function; skipping this step leaves the device locked to the old controller.

Pro Tips Worth Knowing

Tip 1: Check the manufacturer’s end-of-life policy before buying.

Many hub makers publish a support lifecycle document. Look for how long they guarantee cloud services after a product is discontinued. Some brands (like Hubitat) emphasize local operation precisely because they know cloud-dependent hubs fail. Others (like some budget brands) offer no such guarantee. The common mistake is assuming a popular brand won’t shut down — Insteon’s 2022 shutdown proved otherwise.

Tip 2: Pair critical devices to a secondary controller if possible.

If your old hub supported Z-Wave, you can often pair a second controller (like a USB stick) to the same network as a backup. This doesn’t give you full redundancy, but it means you can control locks and lights even if the primary hub fails. The mistake is keeping all devices on a single hub with no fallback, which is exactly the situation you’re in now.

Tip 3: Rebuild automations from scratch instead of trying to replicate them.

Your old automations were built around the old hub’s quirks and limitations. When you rebuild, you’ll likely find opportunities to simplify — combine multiple triggers into one scene, or replace a time-based schedule with a sensor-based trigger. The mistake is copying your old automation list verbatim, which carries forward design flaws you didn’t notice before.

Tip 4: Test each device’s range after pairing.

A hub’s antenna placement matters more than most people think. If your old hub was centrally located, your new hub might need a different spot to reach the same devices. Walk around your home with the companion app open and check signal strength for each device after pairing. The mistake is assuming the new hub will perform identically to the old one — different antenna designs and radio power levels mean you may need to reposition the hub or add a range extender.

FAQ

Can I keep using my old hub after the cloud service shuts down?

It depends on whether the hub supports local operation. Some hubs continue to run automations without internet access, but voice control and remote app access will stop working. Test by disconnecting the hub from the internet for 30 minutes and checking which functions still respond.

Will my Zigbee sensors work with a new hub?

Usually yes, but not always. Zigbee devices from the same manufacturer as the hub are safest. Cross-brand compatibility varies — some devices (like certain IKEA sensors) require special pairing procedures or may not join at all. Check the new hub’s compatibility list before purchasing.

What’s the difference between Matter and Thread?

Matter is a communication standard that lets devices from different brands work together. Thread is a wireless protocol that Matter can run over. A hub with Thread support can act as a border router, allowing Thread devices to communicate with your network. Matter itself doesn’t guarantee compatibility with older Zigbee or Z-Wave devices.

Is Home Assistant worth the setup effort?

If you value local control and don’t want to depend on a manufacturer’s cloud service, yes. Home Assistant runs entirely on your hardware and supports nearly every protocol. The trade-off is setup time — expect several hours to configure it properly, plus ongoing maintenance for updates and integrations.

How long should a replacement hub last?

A good hub should last 5–7 years. The hardware itself rarely fails; the risk is the manufacturer discontinuing cloud support. Hubs with strong local automation support (like Aqara M3 or Hubitat) are safer bets because they continue functioning even if cloud services end.

What if my new hub doesn’t support one of my old devices?

You have three options: leave that device on the old hub until the shutdown date, replace it with a compatible model, or use a separate bridge or dongle to connect it to the new system. The worst choice is buying a hub that supports most of your devices and assuming the rest will somehow work — they won’t, and you’ll end up with a hybrid setup that’s harder to manage than either system alone.

<!– cluster-navigation –>

Explore This Topic

Related guides in this cluster:

Similar Posts