Home Assistant Core can be extended with integrations. Each integration is responsible for a specific domain within Home Assistant. Integrations can listen for or trigger events, offer services, and maintain states. Integrations are made up of a component (the base logic) and platforms (bits that integrate with other integrations). Integrations are written in Python and can do all the goodness that Python has to offer. Out of the box, Home Assistant offers a bunch of built-in integrations.
Home Assistant distinguishes the following integration types:
These integrations define a specific device category of Internet of Things devices in Home Assistant, like a light. It's up to the
light integration to define what data is available in Home Assistant and in what format. It also provides services to control lights.
For a list of defined domains, see entities.
To suggest a new domain, start a discussion in the architecture repository. Make sure to show what data your proposed entity would include and how it can be controlled. Include examples from multiple brands.
These integrations interact with external devices & services and make them available in Home Assistant via integrations that define IoT domains like
light. An example of such an integration is Philips Hue. Philips Hue lights are made available as light entities in Home Assistant.
For more information, see entity architecture.
These integrations represent entities either based on virtual data, like the
input_boolean integration, a virtual switch. Or they derive their data based on other data available in Home Assistant, like the
template integration or
These integrations provide small pieces of home automation logic that do common tasks within your house. The most popular one is the
automation integration, allowing users to create automations through a configuration format.
It can also be more specific, like the
flux integration, which controls lights based on the sun setting.