The Home Assistant (HA) app has a lot of custom terms that can sound like a new language for beginners. The following diagram and definitions should help beginners navigate HA’s powerful feature sets.
┌────────────────────────────────────────────────────────┐
│ INTEGRATION │
│ (The software bridge connecting HA to a Device) │
└───────────────────────────┬────────────────────────────┘
▼
┌────────────────────────────────────────────────────────┐
│ DEVICE │
│ (The physical hardware product in your home) │
└───────────────────────────┬────────────────────────────┘
▼
┌────────────────────────────────────────────────────────┐
│ ENTITY │
│ (The individual tracking points or controls) │
├───────────────────────────┼────────────────────────────┤
│ STATE │ ATTRIBUTES │
│ (The main value: ON/OFF) │ (Extra details: BRIGHTNESS)│
└───────────────────────────┴────────────────────────────┘
Core Feature Glossary
| Term | Simple Definition | Example |
| Integration | The software bridge or plugin that allows Home Assistant to talk to a specific brand, service, or hardware protocol. | AlphaMon MQTT, Philips Hue lighting system, Spotify cloud-based audio, Amazon Ring home automation, or Z-Wave wireless IoT devices. |
| Device | A physical object or logical grouping of sensors that represents a real-world piece of hardware. | An AlphaMon Device, a smart bulb, a robot vacuum, a phone, or a thermostat. |
| Entity | A single sensor, switch, or data tracking point inside a Device. Devices usually contain multiple entities. | A multi-sensor device will have separate entities for temperature, motion, and battery level. |
| State | The current, primary piece of information or condition of an Entity at this exact second. | A switch is on, a door is open, a thermometer reads 22°C, or a tracker is home. |
| Attribute | Extra pieces of background data attached to an Entity that provide more context beyond its main State. | A light entity with a state of on will have attributes like brightness: 80%, color_temp: 3500k, or friendly_name: Kitchen Light. |
| Area | A digital “room” or “zone” you create to group your Devices and Entities logically based on their physical location. | Assigning your smart speaker, main lights, and motion sensor to the Living Room Area. |
Action & Automation Terms
| Term | Simple Definition | Example |
| Service | A specific command or action you tell Home Assistant to perform on an Entity, Device, or the system itself. | Calling light.turn_on to illuminate a room, or tts.speak to make a speaker announce something. |
| Automation | A set rule that triggers an action automatically without human intervention, based on the Trigger, Condition, Action (TCA) logic. | When the front door opens (Trigger), And it is after dark (Condition), Then turn on the hallway light (Action). |
| Scene | A saved snapshot of specific states for a group of entities, allowing you to instantly set a mood. | A “Movie Night” Scene that dims the TV lights to 10%, closes the smart blinds, and switches off the kitchen lights. |
| Script | A sequence of predefined actions or steps that you can trigger manually (like a macro button) or use inside an automation. | A “Leave Home” Script that checks if the garage is shut, locks the front door, turns off all media players, and arms the alarm. |
| Blueprint | A pre-made, reusable automation template typically created by the HA community. It allows you to build complex logic by just selecting your devices from a drop-down menu. | Downloading a community blueprint for a “Motion-activated light with a smooth fade-out timer” so you don’t have to build it from scratch. |
System & Interface Terms
| Term | Simple Definition | Example |
| Dashboard (Lovelace) | The customizable visual interface where you view, control, and interact with your smart home on your phone, tablet, or PC using digital “cards”. | A tablet mounted on the wall showing a grid of buttons for your lights, a weather forecast, and live security camera feeds. |
| YAML | A human-readable, programmer-oriented, text format used for storing settings and configurations. Can be somewhat complex for beginners. Pronounced “yam-uhl”, it stands for Yet Another Markup Language | Note: HA automatically writes your settings into YAML files in the background when you click buttons in the visual menus. However, experienced HA users often edit the HA YAML configuration file directly |
| Visual User Interface | The standard point-and-click interface of Home Assistant where you configure devices and automations using toggles, menus, and dropdowns. | Building an entire automation using dropdown menus in the browser without ever needing to look at code. |
| Add-on | A separate, third-party software application run inside an isolated container to give your Home Assistant server completely new capabilities. | Running Node-RED for advanced logic, Plex for your home media server, or Mosquitto MQTT for advanced smart device tracking. |
| HACS | Stands for Home Assistant Community Store. It is a popular, unofficial plugin store used to download custom themes, dashboard cards, and integrations made by independent developers. | Downloading a custom, highly-styled weather card for your dashboard that isn’t included in Home Assistant by default. |
What is YAML’s Role? (The Visual UI vs. Code)
When you first start with Home Assistant, you will hear the word YAML thrown around a lot. Beginners often worry they need to learn programming to use HA, but that is no longer true.
- The Visual UI does the heavy lifting: Today, 95% of Home Assistant can be managed purely through the regular browser menus. You click buttons, choose items from drop-down lists, and slide toggles to set up your home.
- YAML is the blueprint behind the curtain: Every time you create an automation or dashboard using the Visual UI, Home Assistant translates your clicks into lines of text called YAML. It acts as the “save file” for your configurations.
- Why do people talk about it? Advanced users like editing YAML directly because they can copy and paste massive automation setups from the internet in seconds. As a beginner, you can completely ignore writing YAML and rely strictly on the Visual UI!