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:
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).
- # Example configuration.yaml entry with exclude
+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).
+
+# Example configuration.yaml entry with exclude
history:
-exclude:
- domains:
- - automation
- - weblink
- - updater
- entities:
- - sensor.last_boot
- - sensor.date
+ exclude:
+ domains:
+ - automation
+ - weblink
+ - updater
+ entities:
+ - sensor.last_boot
+ - 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.
- # Example configuration.yaml entry with include
+
+
+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.
+
+# Example configuration.yaml entry with include
history:
-include:
- domains:
- - sensor
- - switch
- - media_player
+ include:
+ domains:
+ - sensor
+ - switch
+ - media_player
-
-
- - 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.
-```yaml
- Example configuration.yaml entry with include and exclude
- history:
-include:
- domains:
- - sensor
- - switch
- - media_player
-exclude:
- entities:
-
- - sensor.last_boot
- - sensor.date
-```
-
-
-
+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.
# Example configuration.yaml entry with include and exclude
+history:
+ include:
+ domains:
+ - sensor
+ - switch
+ - media_player
+ exclude:
+ entities:
+ - sensor.last_boot
+ - sensor.date
+The history is stored in a SQLite database home-assistant.db within your config directory.
The history is stored in a SQLite database home-assistant_v2.db within your configuration directory.
time_changed that happened while recorder component was running.When the history component queries the states table it only selects states where the state has changed: WHERE last_changed=last_updated
When the history component queries the states table it only selects states where the state has changed: WHERE last_changed=last_updated