Load Home Assistant data to DuckDB

Home Assistant is a smart home automation platform that provides a REST API for interacting with system states, services, and configuration. Everything needed to build a working Home Assistant → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Home Assistant to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Home Assistant to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Home Assistant API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Home Assistant API at a glance

These values come from the Home Assistant API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Home Assistant API?

All API requests must include an Authorization header with the value 'Bearer ', where is a long-lived access token generated in the user profile.

1. Get your credentials

To obtain a long-lived access token, log in to your Home Assistant dashboard in a web browser. Navigate to your user profile page (typically located at /profile). Scroll to the bottom of the page to find the 'Long-Lived Access Tokens' section. Click 'Create Token', provide a descriptive name for the token, and copy the generated token immediately, as it will not be displayed again.

2. Add them to .dlt/secrets.toml

Copy
[sources.home_assistant_source]
home_assistant_url = "http://your_home_assistant_ip:8123"
home_assistant_token = "your_long_lived_access_token_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Home Assistant data can I load into DuckDB?

These are the Home Assistant endpoints dlt can load into DuckDB:

---

How do I load only new Home Assistant records?

The Home Assistant API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "states", "endpoint": {
    "path": "api/states",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Home Assistant pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /api/states and /api/services from the Home Assistant API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def home_assistant_source(api_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://<IP_ADDRESS>:<PORT>/api/",
            "auth": {"type": "bearer", "token": api_token},
        },
        "resources": [
            {"name": "states", "endpoint": {"path": "api/states"}},
            {"name": "services", "endpoint": {"path": "api/services"}}
        ],
    }
    yield from rest_api_resources(config)


def load_home_assistant_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="home_assistant_pipeline",
        destination="duckdb",
        dataset_name="home_assistant_data",
    )
    load_info = pipeline.run(home_assistant_source())
    print(load_info)


if __name__ == "__main__":
    load_home_assistant_to_duckdb()

Run it with python home_assistant_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Home Assistant data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("home_assistant_pipeline").dataset()
df = data.states.df()
print(df.head())

SQL:

Copy
SELECT * FROM home_assistant_data.states LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Home Assistant to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Home Assistant loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Home Assistant data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack