Smart Home Device Inventory: The Spreadsheet That Saves Your Future Self

A smart-home inventory is disaster recovery for the physical house. Backups restore configuration, but they do not remember which sensor is taped inside a closet, which battery it uses, which Matter code was lost, which hub owns it, or which automations break when it dies.

Inventory rule: Record enough identity, ownership, and recovery detail to replace one device while the controller, cloud account, or primary maintainer is unavailable. Put pairing secrets in a vault, not in the sheet.

The Short Version

  • Track the physical device, protocol, controller, firmware, power source, room, setup code location, and automations affected.
  • Store Matter/HomeKit setup codes in a password manager; the spreadsheet should reference the vault item, not expose secrets.
  • Update the inventory after every add, remove, firmware migration, radio change, or battery replacement.

The Reader Question

What should I document before a smart home device, hub, phone, or account disappears?

This guide is for Home Assistant users, mixed-platform households, and the family member who inherits the system later. It assumes you can identify your hubs and open their device lists; it does not assume spreadsheet expertise. The goal is a readable recovery map, not a second source of truth that silently competes with Home Assistant.

Current Context and Prerequisites

Facts and links were checked on 15 July 2026 against Home Assistant 2026.7 documentation. Home Assistant distinguishes devices, entities, and areas, while a physical device can expose several entities or sit behind a hub. Before starting, locate the controller dashboards, household password vault, recent Home Assistant backup, and a place to keep an offline copy of the inventory. Matter fabrics, Thread border routers, vendor clouds, and firmware support change over time, so record the deployed state rather than assuming the brand name explains it.

Before You Start: Safe Defaults

  • Do not put setup codes and backup keys in a plain shared spreadsheet.
  • Record controller/hub ownership so replacements do not become guessing games.
  • Include reset/pairing notes and automation impact.
  • Keep one copy accessible when Home Assistant is offline.

Reference Model

The reference model below shows the practical order for smart home device inventory spreadsheet. Open each step for the operational detail behind the diagram.

Interactive reference model
Smart Home Device Inventory: The Spreadsheet That Saves Your Future Self reference model

Read the model left to right, then open each step below for the operational detail behind the diagram.

Plan Control Change Verify
01Record device

Room, name, protocol, model, serial/MAC/EUI, and firmware.

Output: document the evidence from this step before moving to the next one.

02Link controller

Home Assistant, hub, Thread border router, Zigbee/Z-Wave coordinator, cloud account.

Output: document the evidence from this step before moving to the next one.

03Protect codes

Setup codes live in vault; inventory links to the vault item.

Output: document the evidence from this step before moving to the next one.

04Use during failure

Replace device, re-pair, rename entities, and fix automations.

Output: document the evidence from this step before moving to the next one.

The SVG cards link to the matching expandable detail cards. The first card is open by default for context.

Decision Matrix

ChoiceBest FitWatch Point
SpreadsheetFastest useful startManual updates required.
Home Assistant exportDevice/entity registry contextDoes not capture physical notes by itself.
Password manager notesSetup codes and sensitive recovery dataNot ideal for bulk device filtering.
Labels/NFC tagsHidden devices and maintenanceNeeds a naming scheme.

Minimum Columns

Use columns for room, friendly name, protocol, integration, manufacturer, exact model and hardware revision, serial/MAC/EUI-64, firmware, controller or fabric, upstream hub, power or battery, install date, reset steps, setup-code vault reference, automations affected, cloud account owner, purchase date, warranty, support status, and last verified date. Add a photo reference for hidden devices and a stable label for multi-gang switches where the software view does not identify the physical endpoint.

Home Assistant Mapping

Home Assistant has device, entity, and area registries. Those records are useful, but they do not replace physical knowledge: where the device is mounted, which battery it uses, what QR code came in the box, or which family routine depends on it.

Replacement Workflow

When a device dies, the inventory should tell you the model to buy, how to reset or remove the old one, which automations reference it, and which entity names need to remain stable after replacement.

A Practical Pilot Scenario

Inventory one real room first: its hub, two battery sensors, one mains-powered device, and every automation that references them. Ask a second household member to identify each item, locate the vault reference, and explain the replacement order without opening Home Assistant. Missing model revisions, ambiguous names, and unknown account owners become concrete fixes before you spend a weekend cataloging the whole house.

The pilot passes when the second person can find the device, name its controller and battery, identify dependent automations, and reach recovery instructions without seeing a setup code in the sheet. Record what they could not answer. That handoff result is more useful evidence than a row count.

Implementation Details

Build the sheet from authoritative records, then resolve conflicts instead of copying them blindly. Home Assistant may know a firmware version while the vendor app knows the cloud owner and the device label shows the hardware revision. Mark unknown values explicitly. Do not rename entities or move devices merely to make the spreadsheet tidy; inventory work should be observational until a separately planned maintenance window.

  1. Create the minimum inventory columns.
  2. Export or review Home Assistant device/entity/area data.
  3. Add physical details for the top 20 most important devices first.
  4. Move setup codes and backup keys into a password manager.
  5. Label hidden devices where practical.
  6. Use the inventory during one battery replacement or device swap.

Evidence To Collect

  • A dated export or screenshot of the controller device list, retained according to household privacy needs.
  • One completed row that reconciles physical label, Home Assistant device, entity names, hub path, and cloud-account owner.
  • A dependency list showing which dashboards, scenes, scripts, and automations use the device.
  • A vault item reference that a designated backup maintainer can open without the secret appearing in the sheet.
  • A timed replacement walk-through: identify, remove or reset, pair, preserve names, validate automations, and revert if pairing fails.

Validation Checklist

  • A dead device can be identified by room, model, protocol, and controller.
  • Setup code location is known without exposing the code in the sheet.
  • Automations affected by replacement are listed.
  • Battery type and install date are visible.
  • The inventory can be opened when Home Assistant is down.

Maintenance Cadence

  • At installation or removal: add or retire the row, update the vault reference, and record the account or fabric owner.
  • After a battery or firmware change: update the date and version so repeated failures can be compared.
  • Quarterly: reconcile one room against the physical devices and Home Assistant registries, including unavailable or orphaned entities.
  • Yearly: ask the backup maintainer to recover one low-impact device from the sheet and the latest controller backup.

Troubleshooting

SymptomLikely CauseFirst Check
Automation fails after replacementEntity ID or device ID changedUse inventory to map old entity names and update automations.
Cannot re-pair Matter deviceSetup code lost or wrong controllerRetrieve vault item and verify fabric/controller ownership.
Sensor location unknownNo physical inventory or labelAdd room, mounting note, and photo/link for hidden devices.

Common Mistakes

  • Assuming Home Assistant backup remembers physical placement.
  • Storing Matter codes in a plain spreadsheet.
  • Letting entity names drift after replacement.
  • Forgetting cloud accounts and vendor hubs.
  • Inventorying only expensive devices while ignoring tiny sensors that drive automations.

Useful Gear And Buyer Notes

The inventory should reveal whether labels, NFC tags, battery storage, or a replacement controller solve a documented recovery gap. Verify label durability, tag compatibility, battery chemistry, controller radio support, warranty, and seller return terms before buying; none of these products substitutes for a current sheet and tested backup.

Affiliate disclosure: As an Amazon Associate, TechGeeks may earn from qualifying purchases. The product links below are buying references, not a requirement to buy a specific brand or seller. Verify compatibility, seller quality, warranty, and current specs before ordering.

Related TechGeeks Reading

What This Does Not Protect or Validate

A complete row does not prove that a device can be re-paired, that a Matter setup code remains valid for the intended fabric, or that a discontinued cloud service will still authorize the account. Home Assistant registry data documents its current view; it does not confirm physical placement, vendor support life, radio health, or the recoverability of a separate hub.

This article is documentation-backed and was not validated through an original whole-home replacement lab. A spreadsheet does not replace controller backups, vault recovery, firmware maintenance, network segmentation, smoke or life-safety procedures, or electrician/vendor instructions. Treat serial numbers, MAC addresses, purchase records, and account references as sensitive household data; restrict sharing and retain only what the recovery purpose requires.

Practical FAQ

Should I use Home Assistant export only?

No. It helps, but add physical location, setup-code reference, battery, reset steps, and automation impact.

Where do Matter codes belong?

In a password manager or secure vault. The sheet should reference the secure item.

How often should I update it?

Every device add/remove, firmware migration, coordinator change, battery replacement, or room move.

References

  • https://developers.home-assistant.io/docs/device_registry_index/
  • https://developers.home-assistant.io/docs/entity_registry_index/
  • https://developers.home-assistant.io/docs/area_registry_index/
  • https://www.home-assistant.io/integrations/backup/
  • https://csa-iot.org/all-solutions/matter/
  • https://www.nist.gov/publications/profile-iot-core-baseline-consumer-iot-products

Final Thought

The best smart-home inventory is the one you reach for when a tiny sensor silently becomes the reason the house stopped behaving.

Leave a Reply

Your email address will not be published. Required fields are marked *