Document Your Smart Home

Prices in this article are typical U.S. retail, checked October 2026.

Section 1: Why does your smart home need a file? (Introduction)

A smart home file records every device, account, password, network name and automation, so you or someone else can run the house after a move, a failure or a death. Keep it offline, update it quarterly and store a copy off-site.

A smart home is not only a collection of devices. It is a set of accounts, a network, a pile of receipts, and a list of people who can open the door. The devices are visible; the rest lives in apps, email inboxes, and someone’s memory.

The knowledge is fragile in a specific way. It lives in one person’s head and one phone, and it is rarely written down because the system works. The failure is not dramatic; it is a Tuesday when the app asks for a verification code sent to an email address nobody remembers creating.

That works while the installer is available. It fails at the worst moments: the phone is lost, the account owner moves out, the hub dies, or the house is sold. The new owner inherits a wall of switches nobody can name, and the old owner cannot remember which email address created the account.

The fix is a document — a plain file, kept somewhere the household can find it, with five lists. The Insurance Information Institute’s consumer survey found that only 47 percent of homeowners had prepared an inventory of their possessions; the smart home version is even less common, and it is the one that makes the system transferable.

This guide covers what goes in the file, how to secure it, and how to keep it current. The file is boring, which is the point. A boring file is a working file, and it should be used. For the wider foundations, start with the Foundations hub.

Section 2: What five lists belong in the file?

1. Accounts

Every service that owns a device or a subscription:

• The ecosystem apps (Apple Home, Google Home, Alexa, SmartThings).
• The manufacturer apps (the bulb, the lock, the camera, the vacuum).
• The hub (Home Assistant, Hubitat, a vendor bridge).
• The monitoring service and the internet provider.
• The energy, water, and insurance accounts that connect to the devices.

For each: the login email, the recovery email, whether MFA is on, and the subscription renewal date. Do not write passwords in the document; use a password manager and record only the entry name.

The owner email deserves its own line. It is the account that can reset every other account, and households often create it years before the smart home and forget which address it is. If it is an old ISP address that will disappear when the service changes, move the smart home accounts to a mailbox the household controls before the move.

Subscriptions are part of the account list

A camera plan, a monitoring contract, a cloud backup, a music service used for announcements: each is a recurring charge attached to an account. Record the renewal date and the cancellation terms. The subscription audit is easier when the list exists, and the household avoids paying for a camera plan after the camera is gone.

2. Devices

A table with one row per device:

The protocol and hub columns are the ones people skip, and the ones that matter when a hub dies. A device that speaks Zigbee does not connect to a Wi-Fi-only replacement hub.

The naming convention

Pick one pattern and use it everywhere: room + device type, for example “Kitchen — leak sensor” or “Hall — camera.” The pattern matters less than the consistency. When every app, automation, and voice command uses the same name, the documentation writes itself and the household can talk about the house without pointing.

3. Network

• Router make and model, and the admin login location.
• The Wi-Fi network names, including the IoT network if there is one.
• The DHCP reservations or static addresses for hubs and cameras.
• The ISP account and the modem/ONT location.
• Any VLAN or guest-network configuration, if the household uses one.

This is the list that makes a router replacement a project instead of a catastrophe.

4. Warranties and receipts

A folder — digital is fine — with the receipt, the model number, and the warranty terms for anything expensive: locks, cameras, hubs, appliances, the HVAC controller. Most manufacturers want the original receipt, and most households cannot find it two years later.

5. People and access

Who can enter, who can control, and who can administer:

• Household members and their role.
• Lock codes, with the name and expiration date of each.
• Camera sharing, per person.
• The person who inherits the owner account if something happens to the owner.

The access list is the one that needs a review after every move, breakup, or new roommate.

Section 3: How do you keep the file secure?

The document is a map of the house’s digital locks. Treat it accordingly.

Use a password manager

CISA’s guidance is direct: use long, random, unique passwords stored in a password manager. The file should reference the password manager entry, not the password itself. If the file is lost, the passwords are not in it.

Prefer an authenticator or a passkey

SMS codes are better than nothing, but they are vulnerable to SIM swaps and lost phones. An authenticator app or a passkey is stronger, and both can be backed up. The account that controls the house should use the strongest option the platform supports, and the recovery method should not depend on the same phone.

Turn on MFA

Multi-factor authentication is the single best protection for the accounts that control the house. CISA’s MFA guidance explains the point: a stolen password is not enough if the second factor is required. Turn it on for the ecosystem account, the email that recovers it, the hub, and the camera service.

Keep recovery codes offline

MFA recovery codes and account recovery keys should be printed or stored offline, not only in the same password manager that might be locked out. A fireproof box or a sealed envelope with a trusted person is a reasonable trade.

Do not use a shared login

A shared smart home account destroys the audit trail and makes offboarding impossible. Each adult should have their own login and the appropriate role; the file records who has which.

Where to keep it

A shared password-manager vault, a family wiki, or an encrypted document. The test is simple: can the other adult in the house find it without asking the owner, and can a trusted person find it if both adults are unavailable?

Section 4: How do you build the device map?

The five lists are the structure. The device map is the part that takes an afternoon, and the part that pays back the most.

Walk the house

Start at the front door and go room by room. For each device, note the name, the app, the protocol, and the power source. Photograph the label on the back of the device; the model number is often there and nowhere else.

Name things consistently

The app’s default name — “Smart Plug 4” — is not a name. Use “Living room lamp,” “Garage camera,” “Kitchen leak sensor.” The automation, the voice assistant, and the documentation should all use the same label.

Record the dependencies

A camera that records to a hub, a lock that needs a bridge, a sensor that needs a repeater: the dependency is the thing that breaks first. Draw it as a simple list or a diagram; a photo of a hand-drawn diagram is enough.

Back up the configuration

A hub is a small server, and its configuration is the most valuable file in the house. Home Assistant, for example, supports backups; vendor hubs may export a configuration or store it in the cloud. Put the backup location in the file, test a restore once, and note the date of the last successful backup.

Firmware updates belong on the same page. A device that has not been updated in two years may be missing a security fix, and a device that updates automatically may change behavior. Record the update policy and the last check.

Record the batteries

Battery type and last replacement date, per device. The smoke alarm has its own ten-year clock; the lock, the sensors, and the camera have shorter ones. A single “batteries” page saves a dozen small emergencies.

Section 5: What happens to the file when you sell or move?

A smart home is easiest to transfer when the file exists.

Handing over the documentation

When the house changes hands, the file goes with it in a redacted form: device list, network map, warranty folder, and the names of the accounts, without the credentials. The new owner re-pairs the devices to their own accounts. A buyer who receives a labeled, documented smart home is a buyer who is less likely to rip it out.

Selling the house

Decide what stays and what goes. Devices that stay should be factory-reset and re-paired to the new owner’s account, not handed over with the old one attached. Devices that go should be removed from the old account before they leave the house. The file’s device list is the checklist.

Moving out of a rental

Remove the devices you installed, restore the landlord’s fixtures, and revoke the codes and accounts you created. The renting guide covers the permission side; the file covers the inventory.

Death or incapacity

The digital legacy tools offered by Apple, Google, and password managers exist for this reason. They let a named person request access after a waiting period, without the owner handing over a password in advance. Set one up, and put the name of the person and the location of the instructions in the file.

Death or incapacity

Someone needs to be able to find the accounts, the recovery codes, and the access list. A password manager with an emergency-access feature, or a sealed document with the estate paperwork, is the practical answer. The goal is not surveillance; it is that the house does not become unmanageable at the worst possible time.

Section 6: What should you review once a year? (Conclusion)

1. Create the five lists. Accounts, devices, network, warranties, people.
2. Secure the accounts. Password manager, MFA, offline recovery codes, no shared logins.
3. Name and map the devices. Room, model, protocol, hub, battery.
4. Store the receipts. One folder, searchable.
5. Review access after every change. Move, breakup, new roommate, new caregiver.
6. Update once a year. Add new devices, remove old ones, check the renewals.

The review should be triggered by events, not only by the calendar: a new device, a new roommate, a router replacement, a move, a subscription cancellation. Each is a five-minute update that prevents an hour of reconstruction later.

Some households can keep this to a single page. A small apartment with a hub, a few bulbs, and a lock does not need a network diagram; it needs the account list and the lock codes. The file should be as big as the house.

A smart home is a small piece of infrastructure. Infrastructure has documentation, and the households that write it down are the ones that can fix, move, and hand it on. A document that is 90 percent complete is still useful; a perfect one that is never started is not.

Where to buy

Related reading

• Who Controls the House? — roles and permissions.
• The Smart Home Maintenance Guide — the seasonal checks.
• Renting a Smart Home — what to remove and restore.
• Smart Locks for Guest Access — codes and revocation.

Sources

• CISA: Use Strong Passwords — long, random, unique passwords and password managers, checked October 2026
• CISA: Turn On MFA — multifactor authentication for account protection, checked October 2026
• III: Homeowners and Renters Insurance Facts and Statistics — 47 percent of homeowners with a possessions inventory, checked October 2026
• Apple: Share control of your home — household roles and removing people, checked October 2026