Skip to content

Repository files navigation

HA Flow Map

Home Assistant SonarQube Quality Gate SonarQube Coverage

Read-only Home Assistant custom integration that indexes explicit relationships in automations, scripts and scenes, then exposes them through a Flow Map panel.

HACS availability

HA Flow Map is available as a HACS custom repository. In HACS, open Settings → Custom repositories, add https://github.com/alves-dev/ha-flow-map with category Integration, then search for HA Flow Map and install it. It is not declared as a default HACS catalog integration.

Installation

After installing with HACS, restart Home Assistant and add HA Flow Map from Settings → Devices & services → Add integration. The panel appears in the sidebar after configuration.

For manual installation, copy custom_components/ha_flow_map into the Home Assistant configuration directory's custom_components folder, restart Home Assistant, then add the integration through the same screen.

What the MVP indexes

  • State/entity triggers, conditions and explicit action targets.
  • Nested if, choose, repeat, parallel, sequences, waits and delays.
  • Script, automation, scene, service and event calls.
  • Scene entity states when their configuration is available.
  • Entity, device and area targets, with stable namespaced node IDs.

The panel searches the index, expands inbound/outbound neighborhoods (depth 1–3), distinguishes confirmed and dynamic references, and can hide/show service nodes without changing the stored graph. Rebuild is administrator-only.

Selecting a node also shows an impact summary: the automations, scripts and scenes connected to it, plus the maximum number of dependency levels. This walks references in both directions so it catches both callers and targets; results are bounded to keep the panel responsive.

Deliberate MVP limits

The integration does not render or execute Jinja templates. Literal entity IDs found inside templates are retained and marked dynamic; unresolved template results are therefore never shown as confirmed. It currently uses the runtime automation/script/scene configuration exposed by Home Assistant and reports a partial index if a source cannot be read.

Dashboard configurations, custom cards, execution traces/history and external callers (REST, Node-RED, voice assistants, etc.) are not statically indexed in this MVP. Their absence from the map means only that no supported source discovered a relation.

Technical documentation

Contributor setup, validation, testing and quality checks are in the development guide. Supported Home Assistant releases are listed in the compatibility matrix.

License

This project is licensed under the MIT License.

About

Home Assistant integration that maps relationships between automations, scripts, scenes, services, and entities

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Contributors

Languages