The history component will track everything that is going on within Home Assistant and allows the user to browse through it. It depends on the recorder component for storing the data and uses the same database setting. If any entities are excluded from being recorded, no history will be available for these entities as well.
The history component will track everything that is going on within Home Assistant and allows the user to browse through it. It depends on the recorder component for storing the data and uses the same database setting. If any entities are excluded from being recorded, no history will be available for these entities.
To enable the history option in your installation, add the following to your configuration.yaml file:
# Basic configuration.yaml entry
history:
@@ -103,8 +103,8 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
-Without any include or exclude configuration the history displays graphs for every entity (well that’s not exactly true - for instance hidden entities or scenes are never shown) on a given date. If you are only interested in some of the entities you several options:
-Define domains and entities to exclude (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like weblink) or rarely change (updater or automation).
+Without any include or exclude configuration the history displays graphs for every entity (well that’s not exactly true - for instance hidden entities or scenes are never shown) on a given date. If you are only interested in some of the entities you have several options:
+Define domains and entities to exclude (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like weblink) or rarely change (like updater or automation).
# Example configuration.yaml entry with exclude
history:
exclude:
@@ -117,7 +117,7 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
- sensor.date
-Define domains and entities to display by using the include configuration (aka. whitelist). If you have a lot of entities in your system and your exclude lists possibly get very large, it might be better just to define the entities or domains to display.
+Define domains and entities to display by using the include configuration (aka. whitelist). If you have a lot of entities in your system and your exclude list is getting too large, it might be better just to define the entities or domains to include.
# Example configuration.yaml entry with include
history:
include:
@@ -154,7 +154,7 @@ they are listed in the included entity list, you can set the flag
Implementation details
-The history is stored in a SQLite database home-assistant_v2.db within your configuration directory if the recorder component is not set up differently.
+The history is stored in a SQLite database home-assistant_v2.db within your configuration directory unless the recorder component is set up differently.
- events table is all events except
time_changed that happened while recorder component was running.
- states table contains all the
new_state values of state_changed events.
@@ -177,7 +177,7 @@ they are listed in the included entity list, you can set the flag
The history information are also available through the RESTful API.
+The history information is also available through the RESTful API.