Home Assistant
Read and drive a Home Assistant instance: states, services, events, configuration, templates, history and calendars.
OCNORA ships 18 typed Home Assistant operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Home Assistant
- Authentication
- Bearer token
- Credential
- the long-lived access token, or {"access_token": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Home Assistant
Operations, grouped by what they do to your data.
Read and search 13
Update 1
Delete and cancel 1
Other operations 3
A sample Home Assistant workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Home Assistant trigger is needed.
- 2Check Confighome_assistant.check_configAsk Home Assistant to validate configuration.yaml and report errors.
- 3Call Servicehome_assistant.call_serviceRun a Home Assistant service, optionally against named entities.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 18
- Call ServiceRun a Home Assistant service, optionally against named entities.home_assistant.call_service
- Check ConfigAsk Home Assistant to validate configuration.yaml and report errors.home_assistant.check_config
- Delete StateRemove an entity from the state machine.home_assistant.delete_state
- Fire EventFire an event on the Home Assistant event bus.home_assistant.fire_event
- Get Calendar EventsRead the events of one calendar entity between two timestamps.home_assistant.get_calendar_events
- Get ConfigRead the instance's configuration: version, location, units and more.home_assistant.get_config
- Get HistoryRead the state changes of named entities over a period.home_assistant.get_history
- Get LogbookRead logbook entries over a period, optionally for one entity.home_assistant.get_logbook
- Get StateRead one entity's current state and attributes.home_assistant.get_state
- Handle IntentSend a named intent with its slots to Home Assistant's intent handler.home_assistant.handle_intent
- List CalendarsList the calendar entities the instance exposes.home_assistant.list_calendars
- List ComponentsList the integrations currently loaded by the instance.home_assistant.list_components
- List EventsList the event types that currently have a listener.home_assistant.list_events
- List ServicesList the services each domain offers, with their fields.home_assistant.list_services
- List StatesList every entity currently in the state machine with its state.home_assistant.list_states
- Render TemplateRender a Home Assistant Jinja2 template against the live state machine.home_assistant.render_template
- Search StatesFind entities by domain, name fragment or exact state, from one snapshot of the state machine.home_assistant.search_states
- Set StateWrite a state and attributes into the state machine for an entity.home_assistant.set_state
Home Assistant questions
- How does OCNORA authenticate with Home Assistant?
- With a stored Bearer token credential, shaped the long-lived access token, or {"access_token": "…"}. A connection test can check it when you add it.
- What can I automate with Home Assistant?
- 18 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Home Assistant operation I need is not listed?
- Where Home Assistant has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Home Assistant?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Home Assistant calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Home Assistant workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.