Integration · Automation
AI agents for Home Assistant
Read the devices and sensors in a Home Assistant home (states, history, logbook, calendars, templates) and control lights, switches, climate, media players and other everyday devices through Home Assistant actions.
- Actions
- 9
- Read
- 7
- Write
- 2
Actions
What your agents can do in Home Assistant
Read the devices and sensors in a Home Assistant home (states, history, logbook, calendars, templates) and control lights, switches, climate, media players and other everyday devices through Home Assistant actions. Scenes, scripts, automations and covers (garage doors, gates) go through a separate action that needs approval; locks and alarm panels are not controlled. Works with a Home Assistant reachable over public HTTPS on port 443, such as a Home Assistant Cloud (Nabu Casa) remote address or your own reverse proxy.
Read 7
Look things up. Nothing changes.
Get the home's configuration
Reads the Home Assistant configuration: location_name, time_zone, unit_system, version, state (RUNNING when ready), latitude and longitude, and the loaded components (integrations).
List devices and sensors
Lists entities (lights, switches, sensors, climate, media players and so on) as a compact list: each with entity_id, name, state and area.
Get an entity's state
Reads one entity by its entity_id: state (like on, off, 21.5, home or unavailable), attributes.
Get state history
Reads how entities changed over a period (one day from the start by default): one list per entity of state and last_changed values.
Read the logbook
Reads logbook entries (what happened, in words: "Front door opened", "Hallway light turned on by automation") from a start time, for some entities or all.
Get calendar events
Lists the events of one Home Assistant calendar entity (a family Google calendar, a local calendar, trash collection and so on) between two times.
Render a template
Renders a Home Assistant (Jinja) template and returns the text, for questions a single read cannot answer, like how many lights are on, the average of several sensors, or every entity in an area.
Write 2
Create, change or send.
Control a device
Runs a Home Assistant action (service) on everyday devices.
Run a guarded actionDeletes data
Runs a Home Assistant action that can affect a home's security or set off routines.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Home Assistant account.
What you enter
- Long-lived access token
Settings
- Home Assistant address
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Home Assistant data
Ask a question in plain words. The agent can get the home's configuration, list devices and sensors or get an entity's state in Home Assistant, then answers with what it found.
- 02
Let an agent update Home Assistant
Have the agent run a guarded action in Home Assistant as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Home Assistant and Slack: it can get the home's configuration in Home Assistant and post a summary to a Slack channel in the same run.
Works well with
More Automation tools
- Zapier1 actionStart a Zap by sending it data, through the webhook URL of a Zap that begins with the Webhooks by Zapier "Catch Hook" trigger.
- Make1 actionStart a Make scenario by sending it data, through the address of a scenario that begins with a Webhooks "Custom webhook" trigger.
- n8n1 actionStart an n8n Cloud workflow by sending it data, through the production URL of its Webhook trigger.
- Pipedream1 actionStart a Pipedream workflow by sending it data, through the endpoint URL of a workflow that begins with an HTTP / Webhook trigger.
- UiPath9 actionsRun and watch UiPath robots in Automation Cloud Orchestrator.
- Power Automate7 actionsSee and manage Microsoft Power Automate flows stored in a Dataverse environment.
FAQ
Home Assistant and MyDeepAgents
Can MyDeepAgents connect to Home Assistant?
Yes. The Home Assistant connector has 9 actions: 7 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Home Assistant?
Paste an API key from your Home Assistant account. You'll need: Long-lived access token. The connection also asks for: Home Assistant address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Home Assistant without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Home Assistant in workflows as well as agents?
Yes. Every Home Assistant action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Home Assistant to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.