You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/_components/history.markdown
+11-6Lines changed: 11 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ comments: false
8
8
sharing: true
9
9
footer: true
10
10
logo: home-assistant.png
11
-
ha_category: "History"
11
+
ha_category: History
12
12
ha_release: pre 0.7
13
13
---
14
14
@@ -44,7 +44,8 @@ Configuration variables:
44
44
45
45
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:
46
46
47
-
- 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`).
47
+
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`).
48
+
48
49
```yaml
49
50
# Example configuration.yaml entry with exclude
50
51
history:
@@ -57,7 +58,9 @@ history:
57
58
- sensor.last_boot
58
59
- sensor.date
59
60
```
60
-
- 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.
61
+
62
+
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.
63
+
61
64
```yaml
62
65
# Example configuration.yaml entry with include
63
66
history:
@@ -67,7 +70,9 @@ history:
67
70
- switch
68
71
- media_player
69
72
```
70
-
- Use the `include` list to define the domains/entities to display, and exclude some of them with in the `exclude` list. This makes sense if you for instance include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in.
73
+
74
+
Use the `include` list to define the domains/entities to display, and exclude some of them with in the `exclude` list. This makes sense if you for instance include the `sensor` domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the `include` `entities` list just include the `sensor` domain and exclude the sensor entities you are not interested in.
75
+
71
76
```yaml
72
77
# Example configuration.yaml entry with include and exclude
73
78
history:
@@ -84,7 +89,7 @@ history:
84
89
85
90
#### {% linkable_title Implementation details %}
86
91
87
-
The history is stored in a SQLite database `home-assistant.db` within your config directory.
92
+
The history is stored in a SQLite database `home-assistant_v2.db` within your configuration directory.
88
93
89
94
- events table is all events except `time_changed` that happened while recorder component was running.
90
95
- states table contains all the `new_state` values of `state_changed` events.
@@ -96,7 +101,7 @@ The history is stored in a SQLite database `home-assistant.db` within your confi
96
101
- `last_updated`: timestamp anything has changed (state, attributes)
97
102
- `created`: timestamp this entry was inserted into the database
98
103
99
-
When the history component queries the states table it only selects states where the state has changed: `WHERE last_changed=last_updated`
104
+
When the `history` component queries the states table it only selects states where the state has changed: `WHERE last_changed=last_updated`
0 commit comments