Actionist·App Store

Home Assistant

· #98 most-used

Your smart home, fully under your agent's control

AutomationDeveloperSecurityProductivityAnalytics

Home Assistant is the open-source home automation platform that runs locally on your own hardware — no cloud dependency, no data leaving the building. Connect it to Actionist and your agents gain direct access to every device in the building: they can read sensor states, call any service across lights, climate, locks, and media, fire events into the automation engine, and retrieve full entity histories. Whether you're automating an office, a showroom, or a distributed facility, the agent acts on real device data the moment it matters.

Try Home Assistant with ActionistVisit Home Assistant
Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents handle the recurring checks, scene-setting, and log-pulling that facilities and building teams repeat dozens of times a week across every device-connected space.

Schedule

What your Home Assistant agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Mon
Tue
Wed
Thu
Fri
7am
8am
9am
10am
11am
12pm
1pm
2pm
3pm
4pm
5pm
6pm
Agents
Multi-app workflows

Home Assistant × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~27 hrsSaved / week
6Personas served
customer-success★ FeaturedSaves 45m saved · runs ~8× /week

Smart office welcome for every new client visit

When a client-visit confirmation lands in Gmail, your agent reads the Home Assistant configuration to identify available meeting room scenes, fires the 'client-ready' service call to set lighting and temperature, then posts the room status and parking instructions to Slack — and drops the appointment details on Google Calendar so nothing falls through. The client walks into a room that's already at the right temperature, with the right light, before you've had to touch a single switch.

Trigger: When a Gmail message with subject 'Client visit confirmed' arrives
Step 1 trigger
Gmail
Detect client visit confirmation email
Step 2 read
Home Assistant
Get all states to check room availability
Step 3 write
Home Assistant
Call a service within a specific domain to activate client-ready scene
Step 4 write
Slack
Post room-ready notification with parking instructions to #client-visits
Step 5 write
Google Calendar
Create visit appointment block on room calendar
→ Zero manual room-prep steps
Savings

What this looks like for your team

The comparison strip shows real manual tasks your agent replaces. The calculator translates that into your team's numbers.

Without Actionist
With Home Assistant agent
  • Sales
    Manual showroom setup
    Sales reps arrive 20 minutes early to manually set lights, AV, and temperature before every demo or open house.
    18 min/week
    Sales Agent
    Agent activates the scene on cue
    When the Slack signal fires, the agent reads current device states and calls the demo scene service in under five seconds.
  • Marketing
    Manual event space prep
    Marketing coordinators configure room environments by hand before every event, ticking through device checklists.
    13 min/week
    Marketing Agent
    Agent sets the environment on registration
    When a HubSpot registrant is created, the agent activates the venue scene automatically — no one has to arrive early.
  • Customer Support
    Device-state triage calls
    Support agents spend time on the phone walking clients through reading device states and diagnosing smart home issues.
    18 min/week
    Customer Support Agent
    Agent reads and reports states instantly
    The agent fetches live entity states and logs, giving support a full picture before the client finishes describing the problem.
  • Human Resources
    Office access coordination
    HR manually coordinates building access for new starters — emailing facilities, chasing door code updates, confirming badge access.
    7 min/week
    Human Resources Agent
    Agent provisions access on join date
    When an onboarding calendar event fires, the agent calls the lock and access panel services to provision the new starter's access automatically.
  • Finance
    Manual energy meter reads
    Finance staff manually export sensor data from the HA dashboard each month to compile energy cost reports for the accountant.
    13 min/week
    Finance Agent
    Agent pulls and calculates costs automatically
    On the 1st of each month, the agent reads entity history, applies the tariff rate via template, and delivers a formatted cost breakdown.
  • Operations
    Daily facilities walkthrough
    Ops teams physically or manually check doors, windows, and equipment states across the building each morning to catch overnight issues.
    25 min/week
    Operations Agent
    Agent sends overnight anomaly digest
    At 07:00 the agent reads all states, filters for anomalies, and posts a ranked issue list to #facilities before anyone sets foot in the building.
  • Legal
    Access log export for audit
    Legal manually pulls door-lock and camera event logs from Home Assistant when responding to access or compliance queries.
    6 min/week
    Legal Agent
    Agent retrieves and formats audit logs on demand
    When a compliance request arrives, the agent reads the relevant entity history and exports a timestamped log in under 30 seconds.

+ 100s of other automations your agent handles

Average monthly savings
10 hours / person
ROI calculator

See what your team gets back

Team size
10 people
Fully-loaded rate
$20 / hour
Hours / week
25
Hours / year
1,250
Annual ROI
$25,000

Baseline: 2.5 hrs saved per person per week, across the full Home Assistant automation set.

Connect

How to plug Home Assistant into Actionist

Pick the connection method that suits your environment.

The fastest path to full Home Assistant control. Connect via the Home Assistant MCP server and the agent can read states, call services, fire events, and retrieve logs through a single permissioned channel — no token management, no manual API wiring.

1
Open the Apps tab

Find Home Assistant in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Home Assistant

The agent opens your Home Assistant instance's OAuth flow. Select the user account to connect and approve the requested scopes — state read, service call, and event access are pre-selected.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Read the Home Assistant docs →
Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

6 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Home Assistant

Reusable agent skills that work well alongside this app.

Home Assistant

Control any Home Assistant entity via REST API — call services, read states, fire events, and receive webhook triggers from HA automations bidirectionally.

Home Assistant CLI

Run hass-cli commands from the agent for advanced tasks: event monitoring, history queries, and rich formatted entity discovery with auto-completion.

Homeassistant Skill

Access 25 entity domains — lights, climate, locks, presence, weather, calendars, and more — via a purpose-built REST API skill optimised for smart-home agent workflows.

MCP servers

MCP servers that work with Home Assistant

Connect Actionist to MCP servers built for or around this app.

allenporter/mcp-server-home-assistant

Expose all Home Assistant voice intents as MCP tools, enabling the agent to control devices and run automations through natural-language service calls.

home-assistant-mcp
Official

Full Home Assistant control from your IDE via MCP — author automations, edit dashboards, apply themes, and push configuration changes without leaving Actionist.

mcp-homeassistant
Official

Expose the Home Assistant REST API as MCP tools — states, services, events, and history — giving the agent structured access to every entity on your instance.

FAQs

Questions about Home Assistant + Actionist

How do I connect Home Assistant to Actionist?
Open the Apps tab, find Home Assistant, and click Connect. The recommended path is MCP — the agent handles the OAuth handshake with your Home Assistant instance and confirms the connection with a read-only state check. Alternatively, use the API Token method: generate a Long-Lived Access Token in your HA profile settings (Security → Long-Lived Access Tokens) and paste it alongside your instance URL. The token method works well for self-hosted instances on a local network where OAuth redirects aren't available.
What permissions does the agent need in Home Assistant?
For read operations (Get all states, Get entity history, Get all services) the agent only needs read access to your Home Assistant instance. For write operations — calling services, creating events, firing webhooks, upsert state — the connected user account must have the ability to call services in the relevant domain. A dedicated Home Assistant user created for Actionist with appropriate role permissions is the safest approach; avoid using an admin account for automated access.
Can the agent combine Home Assistant with other apps in one workflow?
Yes, and that's where the most useful automations live. The agent can read a state from Home Assistant, use the result to make a decision, call a HA service, and then post a Slack notification or log a row to Google Sheets — all in one uninterrupted sequence. Common patterns include: Gmail triggers that activate HA scenes, Google Calendar events that set HVAC pre-conditions, and HA state changes that create ClickUp maintenance tasks.
What are the most useful automations for a business using Home Assistant?
The highest-leverage automations centre on facilities operations and cost reporting: daily anomaly sweeps (agent reads all states at 07:00 and flags open doors, offline sensors, or out-of-range temperatures), monthly energy cost reports (agent reads entity history, applies tariff rate via template, outputs to a spreadsheet), and event-triggered scene management (agent calls the right service the moment a meeting or visit fires in the calendar). Security log retrieval — pulling entity history on demand for compliance queries — is another high-value use case that previously required manual dashboard navigation.
Does Actionist work with self-hosted Home Assistant instances?
Yes. The API Token connection method is specifically designed for self-hosted instances. Provide your instance URL (e.g. http://homeassistant.local:8123 or your external domain if port-forwarded) and a Long-Lived Access Token. For instances only accessible on a local network, run Actionist on the same network or expose HA via a secure reverse proxy. The MCP path also works with self-hosted instances as long as the instance is reachable from the Actionist runtime.
How do I avoid trigger loops when the agent writes states that could re-fire a trigger?
Two safeguards work well in practice. First, include a state-check step before writing: the agent reads the current entity state and only calls the service if the state isn't already what you want — breaking the retrigger cycle before it starts. Second, scope your triggers narrowly by entity ID and new-state value rather than listening to all state changes; a trigger on sensor.office_temp crossing 28°C only fires when the threshold is crossed, not on every update. For automations that write virtual sensor states, use a cooldown attribute or a dedicated input_boolean as a lock to prevent re-entry.
What rate limits should I be aware of when the agent calls Home Assistant services frequently?
Home Assistant's REST API is self-hosted, so rate limits depend on your hardware rather than a vendor-imposed cap. On a Raspberry Pi 4, expect comfortable handling of up to 10–20 service calls per second; on a more powerful host, the limit is effectively your network throughput. The main constraint to watch is the recorder database write rate — high-frequency state upserts can saturate SQLite on low-spec hardware. For polling patterns that run more than once per minute, prefer the WebSocket API via MCP over repeated REST calls; it holds a persistent connection and imposes far less overhead.
Can the agent react to Home Assistant events in real time, or does it poll?
Via the MCP connection the agent uses a persistent WebSocket channel to Home Assistant, so it reacts to state changes and events in real time — typically within 100–500 ms of the event firing. The trigger types (Entity state changed, Motion detected, Door or window opened, Low battery alert) are all event-driven; the agent doesn't poll. If you're using the API Token method without a persistent connection, you can still use scheduled runs to approximate real-time behaviour, but true event-driven reaction requires the MCP path.