Glossary


The glossary covers terms which are used around Home Assistant.

  • Action:

    Actions are events that fires once all triggers and conditions have been met.

  • Automation:

    Automations offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as a sunset to cause an event, such as a light turning on.

  • Binary sensor:

    A binary sensor returns information about things that only have two states - such as on or off.

  • Component:

    Integrations (see below) used to be known as components.

  • Condition:

    Conditions are an optional part of an automation that will prevent an action from firing if they are not met.

  • Cookbook:

    The Cookbook contains a set of configuration examples of Home Assistant from the community.

  • Cover:

    Covers are devices such as blinds, garage doors, etc than can be opened and closed and optionally set to a specific position.

  • Customize:

    Customization allows you to overwrite the default parameter of your devices in the configuration.

  • Device:

    A device is usually a physical unit which can do or observe something.

  • Device tracker:

    Device trackers are used to track the presence, or location, of a device.

  • Discovery:

    Discovery is the automatic setup of zeroconf/mDNS and uPnP devices after they are discovered.

  • Entity:

    An entity is the representation of function a single device, unit, or web service. There may be multiple entities for a single device, unit, or web service, or there may be only one.

  • Event:

    An event is when something happens.

  • Frontend:

    The frontend is a necessary component for the UI, it is also where you can define your themes.

  • Group:

    Groups are a way to organize your entities into a single unit.

  • Hass.io:

    Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration, and can easily be extended.

  • Integration:

    Integrations provide the core logic for the functionality in Home Assistant. Like notify provides sending notifications.

  • Light:

    A light has a brightness you can control, and optionally color temperature or RGB color control.

  • Lovelace:

    Lovelace is the name of the current frontend.

  • Notification:

    You can use notifications to send messages, pictures, and more, to devices.

  • Packages:

    Packages allow you to bundle different component configurations together.

  • Platform:

    Platforms make the connection to a specific software or hardware platform. For example, the pushbullet platform works with the service pushbullet.com to send notifications.

  • Scene:

    Scenes capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red.

  • Script:

    Scripts are components that allow users to specify a sequence of actions to be executed by Home Assistant when turned on.

  • Sensor:

    Sensors return information about a thing, for instance the level of water in a tank.

  • Service:

    Services are called to perform actions.

  • Switch:

    Switches are things that have two states you can select between, such as turning on or off a socket.

  • TTS:

    TTS (text to speech allows Home Assistant to talk to you.

  • Template:

    A template is an automation definition that can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions.

  • Trigger:

    A trigger is a set of values or conditions of a platform that are defined to cause an automation to run.

  • Zone:

    Zones are areas that can be used for presence detection.

  • hass:

    HASS or hass is often used as an abbreviation for Home Assistant. It is also the command-line tool.