mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Introduction -> Architecture changes made. (#1092)
This commit is contained in:
parent
895e32d7fa
commit
7196cd2082
@ -11,7 +11,7 @@ footer: true
|
||||
|
||||
Before we dive into the Home Assistant architecture, it is important to get a clear overview of the home automation landscape as a whole. This will allow us to show how the different parts of Home Assistant fit in the picture. For a more lengthy discussion about what each part in this overview is responsible for, <a href='/blog/2014/12/26/home-control-home-automation-and-the-smart-home/'>check out our blog</a>. A tl;dr version of the blog:
|
||||
|
||||
* Home Control is responsible for collecting information on- and controlling devices.
|
||||
* Home Control is responsible for collecting information and controlling devices.
|
||||
* Home Automation triggers commands based on user configurations.
|
||||
* Smart Home triggers commands based on previous behavior.
|
||||
|
||||
@ -26,7 +26,7 @@ Before we dive into the Home Assistant architecture, it is important to get a cl
|
||||
The Home Assistant core is responsible for Home Control. It has four parts to make this possible:
|
||||
|
||||
* The **Event Bus** facilitates the firing and listening of events. This is the beating heart of Home Assistant.
|
||||
* The **State Machine** keeps track of the states of things. Fires a `state_changed` event when a state has been changed.
|
||||
* The **State Machine** keeps track of the states of things. It fires a `state_changed` event when a state has been changed.
|
||||
* The **Service Registry** listens on the event bus for `call_service` events and allows other code to register services.
|
||||
* The **Timer** will send a `time_changed` event every 1 second on the event bus.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user