Moving a Smart Home to Local Control: Inventory the Dependencies First

Determine the control path before changing it

A Reddit Home Assistant user asked how to determine whether an integration works offline before installing it. Previously the owner looked for a local IP address in setup instructions, but configuration through an app made that clue less visible. The underlying request is for an evidence-based inventory, not a promise based on a familiar brand.

List each device’s current integration, bridge or coordinator, required account, routine references and maintenance owner. A thermostat appearing on one dashboard may still receive commands through a remote service. Conversely, an account used for initial setup does not by itself prove every later command uses that service.

Source: Owner asks how to identify local integrations before installation

Use Home Assistant’s IoT class as a starting point

Home Assistant classifies integrations by how they communicate. Local Push and Local Polling indicate direct communication with the device; Cloud Push and Cloud Polling require the cloud and an active internet connection. Push means updates arrive from the source, while polling checks for them periodically. The classification describes the integration path, not every feature of the product.

Home Assistant also defines Assumed State and Calculated. Assumed State means the integration cannot read the device’s state and instead infers it from the last command. Calculated integrations produce a result without handling communication themselves. These labels alone do not establish where the command path or input data depends on a cloud service; record that dependency separately from whether the device confirms its state.

Review the integration documentation and its IoT class, then record feature-specific exceptions and setup requirements. For a custom integration, examine its declared manifest and documentation with the maintainer. Treat undocumented behavior as unresolved rather than assigning Local because the device has a local IP address.

Source: Home Assistant Developer Documentation: Integration IoT Class

Separate the radio from the command service

Wi-Fi is a network transport, so a Wi-Fi product can use either a local integration or a cloud API. Thread carries IP traffic and needs an application protocol such as Matter or HomeKit for control. Zigbee and Z-Wave need compatible coordinator and software support; the radio alone does not establish where a vendor hub runs its rules.

Keep separate inventory columns for transport, controller or bridge, command route, updates and recovery. Home Assistant’s Thread documentation explicitly distinguishes border routing from device control. That distinction helps identify which physical component can remain when the central automation software changes.

Source: Thread - Home Assistant

Plan around dependencies that other routines still use

For an illustrative inventory, one Wi-Fi outlet uses a supported local integration, while another device appears through a cloud-linked manufacturer account. Removing the account to simplify the first device’s dashboard could disable the second device. List the dependents before retiring any shared account or bridge.

Choose a limited change with a documented return path. Record what will be retained, what must be re-paired, which identifiers may change and which routine references need updating. The feature-compatibility guide handles missing functions; the internet-outage guide handles the actual disconnection test.

Finish with a maintainable ownership record

Assign the controller, account recovery, updates and backups to an authorized household maintainer. Store credentials and setup codes securely, separate from the ordinary user guide. A migration should reduce unexplained dependencies without placing recovery entirely with the person who happened to install it.

Expand only after the selected change preserves the agreed controls and its rollback is understood. Keep a dated inventory of versions and integration paths so a later update can be evaluated against what was actually installed.

Put it into practice

A decision table to keep handy