Smart Home

Apple Home upgrade: devices offline

Recover after the Apple Home architecture upgrade — the iPad-is-no-longer-a-hub trap, guest-device lockouts, minimum OS versions, and the can't-view-home path.

Problem summary

Apple ended support for the previous Apple Home architecture on Feb 10 2026, and the forced migration knocks devices offline in predictable ways. The biggest trap is that an iPad is no longer a valid home hub — homes relying on an old iPad lose remote access and automations. Every device that touches the home must meet a minimum OS (iOS/tvOS/etc. 16.2+, including invited guests), and updating requires two-factor on the Apple Account. This is a recovery runbook, not a deadline reminder.

Operator snapshotEvidence first

First proof

Identify what was acting as your home hub before the update.

Screen to open

Home app > Home Settings > Home Hubs & Bridges

Expected signal

Your hub was an Apple TV or HomePod, not an iPad.

Stop boundary

Assuming Apple dropped specific accessory brands (it didn't publish such a list) or ignoring guest-device OS minimums.

Layer path

1Apple ended support for the previous Apple Home architecture on Feb 10 2026; the forced migration to the current architecture knocks devices offline in a few predictable ways.

2The biggest trap: an iPad is no longer a valid home hub, so homes that relied on an old iPad lose remote access, automations, and Thread until an Apple TV or HomePod takes over.

3Every device that accesses the home must meet a minimum OS (iOS/iPadOS/tvOS 16.2, macOS 13.1, watchOS 9.2 or later) — including invited guests, who get locked out on older versions.

4Updating the home requires two-factor authentication on the Apple Account with iCloud Keychain — a stuck update usually traces to 2FA being off, and homes you own update together.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Restore a valid home hub

Check: If you relied on an iPad, add/confirm an Apple TV or HomePod as the hub.

Expected result: Remote access, automations, and Thread come back.

If not: An iPad will not serve as a hub on the current architecture.

Bring every device to a supported OS

Check: Update controllers, hubs, and guests to the architecture minimums.

Expected result: No one is locked out by an old OS.

If not: A single old device can hold up access or the update.

Enable the update prerequisites

Check: Turn on two-factor and iCloud Keychain for the Apple Account.

Expected result: The home update can proceed.

If not: A stuck 'will update soon' usually clears once 2FA is on.

Separate accessory issues from the upgrade

Check: If only some accessories fail, switch to the No Response runbook.

Expected result: You fix accessory-level problems with the right tool.

If not: Don't chase a network/hub fix for a single dead accessory.

Confirm the home is healthy

Check: Verify remote control, automations, and each member's access.

Expected result: The home works end-to-end on the new architecture.

If not: If Thread devices misbehave, see no-Thread-border-router-found.

Decision tree

If: Remote access and automations stopped after the update.

Then: The hub was an iPad (no longer supported).

Action: Add/confirm an Apple TV or HomePod as the home hub.

If: A specific person can't see the home.

Then: Their device is below the minimum OS (guests included).

Action: Update that device to a supported OS, then re-verify access.

If: The home update is stuck / 'will update soon'.

Then: Two-factor is off or a controller is on an old OS.

Action: Enable 2FA + iCloud Keychain and update all owner/admin devices.

If: Only some accessories are unresponsive.

Then: This is accessory-level, not the architecture upgrade.

Action: See /smart-home/homekit-no-response for the one-vs-many fork.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Automations/remote control died post-update.	What the home hub was before (iPad vs Apple TV/HomePod).	Home hub (iPad deprecated)	Add an Apple TV/HomePod as the hub.
One member locked out of the home.	That device's OS version vs the minimums.	Minimum OS / guest lockout	Update the device; re-share access if needed.
Home won't finish updating.	Two-factor status; iCloud Keychain; controller OS versions.	2FA / OS prerequisites	Enable 2FA + Keychain; update all owner devices.
Scattered accessory No Response.	Whether it's home-wide or specific devices.	Accessory-level, not architecture	Use the HomeKit No Response runbook instead.

Reference

Commands and settings paths

Confirm the home hub

Home app > Home Settings > Home Hubs & Bridges

Where: On your iPhone/iPad.

Expected: A connected Apple TV or HomePod is listed as the hub.

Failure means: No hub (or only an iPad) means no remote control/automations.

Safe next step: Add or wake an Apple TV/HomePod hub.

Check device OS versions

Settings > General > About (each Apple device)

Where: On every controller, hub, and guest device.

Expected: All are at or above the architecture minimums.

Failure means: Any below the minimum is locked out of the home.

Safe next step: Update the device, then re-verify home access.

Verify two-factor / Keychain

Settings > [your name] > Sign-In & Security (2FA) and iCloud > Passwords/Keychain

Where: On the owner's iPhone.

Expected: Two-factor is on and iCloud Keychain is enabled.

Failure means: If off, the home can't complete the architecture update.

Safe next step: Enable both and retry the update.

Hardware boundary

Hardware and platform boundary

Change only when

Add a wired Apple TV 4K as the home hub if you were depending on an iPad, and standardize the household on supported OS versions before troubleshooting accessories.

Evidence that matters

A supported, always-on home hub (Apple TV 4K / HomePod), current OS on every controller and guest, and two-factor + iCloud Keychain enabled.

Evidence that does not matter

Trying to keep an iPad as a hub — it's no longer supported regardless of how new the iPad is.

Avoid

Assuming Apple dropped specific accessory brands (it didn't publish such a list) or ignoring guest-device OS minimums.

Related tool

Use the linked tool to turn this runbook into a guided check for your exact setup.

Device setup troubleshooter

Last reviewed

2026-06-03 · Reviewed by HomeTechOps. Built from 2026-06 research verified against Apple Support 102287 (Update Apple Home); written as a recovery runbook (the Feb 10 2026 cutover is past), centered on the iPad-no-longer-a-hub trap, guest OS minimums, and the 2FA-required-to-update prerequisite. Re-verify the hub-eligible device list before publishing.

Sources/assumptions

Reflects Apple's state as of mid-2026: support for the previous Apple Home architecture ended Feb 10 2026 — this is framed as a completed cutover, not an upcoming deadline.
Minimum OS versions and the iPad-no-longer-a-hub change are taken from Apple's 'Update Apple Home' support article; re-verify the hub-eligible device list before asserting it.
Third-party accessory compatibility is the device maker's responsibility — Apple does not publish a list of 'broken' accessories, so brand-specific breakage is not asserted.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Apple Support: Update Apple HomeUsed for the Apple Home architecture upgrade — support for the previous version ended Feb 10 2026, iPad is no longer a home hub, the minimum OS versions, and the 2FA-required-to-update fact.Apple Support: If a HomeKit accessory shows No ResponseUsed for the one-vs-several-manufacturers diagnostic fork, the Thread accessory power-cycle timings (5 min off, 10 min to stabilize), home-hub restart, and the router/VPN/security-software checks.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Confirm the layer (radio, IP, app) before deep config.
4. Stop when the evidence says the risk moved.

FAQ

My automations and remote access died after the Apple Home update — why?

The most common cause is that your home hub was an iPad. The current Apple Home architecture no longer supports iPad as a home hub, so remote control, automations, and Thread now need an Apple TV or HomePod present. Add one as the hub and the home's remote features come back. See Apple's Update Apple Home article.

A family member or guest can't see the home anymore — what happened?

Every device that accesses the home must meet the minimum OS for the new architecture (iOS/iPadOS/tvOS 16.2, macOS 13.1, watchOS 9.2 or later) — and that includes invited guests. A guest on an older OS is locked out until they update. Have them update, and confirm your own controller and hub are current too. If only some accessories are unresponsive instead, that's the HomeKit 'No Response' path.

It says it can't update the home / 'Home will update soon' is stuck — how do I fix it?

Updating the home requires two-factor authentication on your Apple Account and iCloud Keychain enabled — a stuck update usually traces to 2FA being off. Turn on two-factor, make sure every owner/admin device is on a supported OS, and retry. Homes you own update together, so one out-of-date controller can hold up the whole home.