+
+
+
+
+ Creating Components
+
+
+
+
+
+ Home Assistant offers built-in components but it
+is easy to built your own.
+
+Each component is responsible for a specific domain within Home Assistant.
+Components can listen for- or trigger events, offer services and maintain
+states. Components are written in Python and can do all the goodness that
+Python has to offer.
+
+We can differentiate between two different types of
+components within Home Assistant.
+
+Components that interact with devices
+
+These components are keeping track of devices within a specific domain. It will also provide services to control those devices.
+
+For example, one of the built-in components is the switch component. This component is responsible for interaction with different types of switches.
+
+If you are planning on adding support for a new platform, do not forget to check out the add new platform section.
+
+Components that respond to events that happen within Home Assistant
+
+These components can provide automation logic or services that do common tasks within your house.
+
+For example the device_sun_light_trigger component tracks the state of
+devices and the sun to make sure that the lights are turned on when it gets
+dark and there are people home.
+
+An example of such a component can be found in /config/custom_components/example.py.
+
+Loading components
+
+A component will be loaded on start if a section (ie. [light]) for it exists in the config file. A component can also be loaded if another component is loaded that depends on it. When loading a component Home Assistant will check the following paths:
+
+
+<config directory>/custom_components/<component name>homeassistant/components/<component name> (built-in components)
+
+
+Once loaded, a component will only be setup if all dependencies can be loaded and are able to setup. Keep an eye on the logs to see if your component could be loaded and initialized.
+
+Warning
+You can override a built-in component by having a component with the same name in your config/custom_components folder. This is not recommended and will probably break things!
+
Note
+Home Assistant will use the directory that contains your config file as the directory that holds your customizations. By default this is the config folder in your current work directory. You can use a different folder by running Home Assistant with the –config argument: python3 homeassistant --config /YOUR/CONFIG/PATH/.
+
Initializing components
+
+After loading, the bootstrapper will call setup(hass, config) method on the component to initialize it. The following parameters are passed in:
+
+
+
+
+| Parameter |
+ Description |
+
+
+
+
+ hass |
+ The Home Assistant object. Call its methods to track time, register services, listen for events or track states: Overview of available methods. |
+
+
+ config |
+ A dict containing the configuration. The keys of the config-dict are component names and the value is another dict with the component configuration. |
+
+
+
+
+
+Guidance on using the Home Assistant object
+
+The Home Assistant object contains three objects to help you interact with the system.
+
+
+
+
+| Object |
+ Description |
+
+
+
+
+ hass.states |
+ This is the StateMachine. It allows you to set states and trach when they are changed. See available methods. |
+
+
+ hass.events |
+ This is the EventBus. It allows you to trigger and listen for events.
See available methods. |
+
+
+ hass.services |
+ This is the ServiceRegistry. It allows you to register services.
See available methods. |
+
+
+
+
+
+Example on using the configuration parameter
+
+If your configuration file containes the following lines:
+
+1
+2
+ | [example]
+host=paulusschoutsen.nl
|
Then in the setup-method of your component you will be able to refer to config['example']['host'] to get the value paulusschoutsen.nl.
+
+
+
Home Assistant