ActionHome AssistantUpdated September 2026
How do I read a Home Assistant entity state?
Short answer: You can get ha entity state in Home Assistant by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Home Assistant Get HA Entity State action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
ID id | string | Required | ID |
Sample request
{"id": "{{trigger.id}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get HA Entity State.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get HA Entity State.
What does the Get HA Entity State action do in Home Assistant?
Returns current state of a specific entity (e.g., light.living_room state=on, brightness=128). The base read for state-aware workflows ("if the door sensor shows open, alert me").
What inputs does Get HA Entity State require?
Required: ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Home Assistant returns an error?
The run history shows the failed step with its input and the error message Home Assistant returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get HA Entity State support batch operations?
Run Get HA Entity State inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Home Assistant's rate limits.
More actions
Other Home Assistant actions.
Action
Check HA Config
Validates the YAML config without reloading. Useful for "after editing config → confirm valid before reload" maintenance workflows.
ActionRender HA Template
Renders a Jinja2 template against current Home Assistant state. Useful for "compute this value based on multiple entity states" workflows or for testing template expressions before adding to automations.
ActionGet HA Config
Returns the running Home Assistant config including location, units, version. Useful for capability detection in cross-version workflows.
ActionList HA Event Types
Returns the event types Home Assistant's event bus is configured to emit. Useful for "what events can I subscribe to" introspection at workflow-build time.
ActionList HA Services
Returns all available services (light.turn_on, switch.toggle, automation.trigger, etc.) with their parameter schemas. The lookup for resolving service names at workflow setup.
ActionList All HA States
Returns current state of every entity in the connected Home Assistant instance. Useful for "weekly state snapshot" backup workflows or for bulk-state-analysis workflows.