Home Assistant keeps track of the states of entities in a state machine. The state machine has very few requirements:
- Each state is related to an entity identified by an entity id. This id is made up of a domain and an object id. For example
light.kitchen_ceiling. You can make up any combination of domain and object id, even overwriting existing states.
- Each state has a primary attribute that describes the state of the entity. In the case of a light this could be for example "on" and "off". You can store anything you want in the state, as long as it's a string (will be converted if it's not).
- You can store more information about an entity by setting attributes. Attributes is a dictionary that can contain any data that you want. The only requirement is that it's JSON serializable, so you're limited to numbers, strings, dictionaries and lists.
Using states in your component
This is a simple tutorial/example on how to create and set states. We will do our work in a component called "hello_state". The purpose of this component is to display a given text in the frontend.
To get started, create the file
<config dir>/custom_components/hello_state.py and copy the below example code.
In the file header we decided to add some details: A short description and the link to the documentation.
We want to do some logging. This means that we import the Python logging module and create an alias.
The component name is equal to the domain name.
setupfunction will take care of the initialization of our component. The component will only write a log message. Keep in mind for later that you have several options for the severity:
Trueif everything is ok.
Add the component to your
After a start or a restart of Home Assistant the component will create an entry in the log.
The next step is the introduction of configuration options. A user can pass configuration options to our component via
configuration.yaml. To use them we'll use the passed in
config variable to our
To use the latest feature of our component, update the entry in your
DEFAULT_TEXT variable the component will launch even if no
text: field is used in the
configuration.yaml file. Quite often there are variables which are required. It's important to check if all mandatory configuration variables are provided. If not, the setup should fail. We will use
voluptuous as a helper to achieve this. The next listing shows the essential parts.
text: is missing from the config, Home Assistant will alert the user and not setup your component.
After a start or a restart of Home Assistant the component will be visible in the frontend if the
configuration.yaml file is up-to-date.
In order to expose attributes for a platform, you will need to define a property called
device_state_attributes on the entity class, which will return a dictionary of attributes:
Entities also have a similar property
state_attributes, which normally doesn't need to be defined by new platforms. This property is used by base components to add standard sets of attributes to a state. Example: The light component uses
state_attributes to add brightness to the state dictionary. If you are designing a new component, you should define
To get your component included in the Home Assistant releases, follow the steps described in the Submit your work section. Basically you only need to move your component into the
homeassistant/component/ directory of your fork and create a Pull Request.