You did a factory reset on your hub because nothing else worked. The hub came back fresh, with no devices, no rooms, no automations. Now you have a closet full of paired devices that need to be re-introduced one by one. The slow part is not the pairing itself, it is rebuilding the metadata (names, rooms, automations) and ensuring your existing voice assistants and integrations continue to work.
Before you start re-pairing
If you have not yet done so, document what the hub previously knew:
- Take screenshots of the device list from any voice assistant or third-party app that synced with the old hub. Alexa, Google Home, HomeKit all retain the names and rooms as they remember them.
- If you have backups of the hub from before the reset, list every device, name, room, and automation.
- Write down which devices in your home are paired to the hub vs which are paired elsewhere (Wi-Fi smart plugs that go directly to their manufacturer cloud do not need re-pairing).
This documentation is your map for the next two hours.
Exclude devices first (Z-Wave) or factory reset (Zigbee)
Z-Wave devices need to be excluded from their previous network before they will pair to a new one. Even though the hub is reset, the devices themselves still think they belong to a network.
- Run general exclusion on the new hub setup (this is supported on every Z-Wave hub).
- For each Z-Wave device, trigger its inclusion button. The new hub will exclude it from its old (now nonexistent) network.
Zigbee devices typically need a factory reset to clear their previous network membership. Each manufacturer has its own reset procedure. Common patterns:
- Bulbs: power-cycle off-on 5 to 6 times in quick succession
- Sensors and battery devices: hold the reset button for 5 to 10 seconds
- Plugs: hold the physical button for 10 seconds
Reset before attempting to pair, or the pair will fail.
Pair in a methodical order
Pair one room at a time, completing each room fully before moving to the next. This is more efficient than pairing all devices first and then organizing, because:
- You can verify each device works as soon as it is paired
- You can assign it to its room immediately with full context
- You can rename it to match its original name while you remember it
- Voice assistants and integrations can be told about the new device incrementally rather than in a big batch
Plan: kitchen, living room, primary bedroom, secondary bedroom, hallway, exterior. Do one fully, take a brief break, do the next.
Per-device flow
- Reset or exclude the device.
- Put the hub in pairing mode.
- Trigger the device’s pairing.
- Wait for the device to appear in the hub app.
- Rename the device to match its original name from your documentation.
- Assign the device to its room.
- Test the device by toggling it from the app.
- Move to the next device in the same room.
Allow 3 to 5 minutes per device. Some devices, especially Z-Wave locks and S2 devices that need DSK entry, will take longer.
Keep your voice assistants in sync
If your voice assistants (Alexa, Google Home, Siri) were linked to the old hub, those connections survive the factory reset because they live in the voice assistant cloud, not on the hub. After the hub re-link, the voice assistants will see your re-paired devices appear with the same names you originally gave them.
However, if the integration was deeply broken (you re-installed the hub’s app, you switched hubs entirely), you may need to re-link the integration. Open the voice assistant’s app, find the hub integration, log out and log back in.
Existing voice routines that referenced devices by name will continue to work if the names match. If you renamed during re-pairing (using your documentation), names should match.
Rebuild automations after all devices are paired
Do not rebuild automations during re-pairing because partial automations break in confusing ways. Pair everything first, then rebuild automations using your documentation.
Most hubs do not import automation definitions from elsewhere. You have to manually rebuild each one. For a typical setup with 10 to 20 automations, this is another hour or so.
The HomeKit room synchronization quirk
If your hub was acting as a HomeKit bridge (Hue Bridge, Aqara hub, SmartThings via Matter), each device will reappear in HomeKit but will not automatically inherit its previous HomeKit room. You need to assign each device to its HomeKit room manually after re-pairing.
This is annoying but unavoidable. HomeKit’s room assignment is independent of the bridge’s room assignment.
Test before declaring done
After re-pairing and rebuilding, run through your typical day’s automations to verify everything works:
- Trigger your morning routine
- Walk through motion sensor zones
- Test voice commands for several rooms
- Open and close any tracked doors or windows
- Verify scheduled automations run at their scheduled times (or fast-forward via manual trigger)
Bugs you find at this stage are usually about specific automations that did not get rebuilt correctly. Fix them while everything is fresh in your mind.
When to stop re-pairing and accept a partial recovery
If you have a device that consistently refuses to re-pair after the reset (perhaps it has a wear issue, perhaps it was at the edge of its useful life), do not let it block the rest of the rebuild. Skip it and come back when the rest of the home is working. Sometimes a device that refused to pair the first time will pair on the second attempt after the hub has been running for a while.
If you eventually decide the device is unusable, replace it. Living with a half-working device is worse than spending forty dollars on a replacement.
The Sunday afternoon that saves the next Sunday
Block a Sunday afternoon for re-pairing rather than spreading the work across an evening every day for a week. Sustained focus is faster per device because you stay in the rhythm. Spread across days, each session re-loads the context overhead.
Put music on, lay out all the devices, and work room by room. Most users report that a forty-device re-pair takes about three hours if done in one sitting. Spread across days it can run a week. The room-first organization principle from our cross-hub migration guide applies here too.
