home-assistant.io/source/_integrations/logbook.markdown

title, description, ha_category, ha_release, ha_domain, ha_quality_scale, ha_codeowners, ha_integration_type, related

title	description	ha_category	ha_release	ha_domain	ha_quality_scale	ha_codeowners	ha_integration_type	related
Activity	Instructions on how to enable the activity integration for Home Assistant.	History	0.7	logbook	internal	@home-assistant/core	system	docs title /docs/configuration/ Configuration file

The Activity {% term integration %} provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. It depends on the recorder integration for storing the data. This means that if the recorder integration is set up to use e.g., MySQL or PostgreSQL as data store, the activity integration does not use the default SQLite database to store data.

This integration is by default enabled, unless you've disabled or removed the default_config: line from your {% term "configuration.yaml" %} file. If that is the case, the following example shows you how to enable this integration manually, by adding it to your {% term "configuration.yaml" %} file:

# Example configuration.yaml entry
logbook:

{% configuration %} exclude: description: "Configure which integrations should not should not track activity. (Configure Filter)" required: false type: map keys: entities: description: The list of entity ids to be excluded from tracking activity. required: false type: list entity_globs: description: Exclude all entities matching a listed pattern from tracking activity (e.g., sensor.weather_*). required: false type: list domains: description: The list of domains to be excluded from tracking activity. required: false type: list include: description: Configure which integrations should tracking activity. (Configure Filter) required: false type: map keys: entities: description: The list of entity ids to be included when tracking activity. required: false type: list entity_globs: description: Include all entities matching a listed pattern when tracking activity (e.g., sensor.weather_*). required: false type: list domains: description: The list of domains to be included when tracking activity. required: false type: list {% endconfiguration %}

Configure filter

By default, the activity will use the same filter as the recorder. To limit which entities are being exposed to Logbook, you can use the include and exclude parameters.

# Example filter to include specified domains and exclude specified entities
logbook:
  include:
    domains:
      - alarm_control_panel
      - light
    entity_globs:
      - binary_sensor.*_occupancy
  exclude:
    entities:
      - light.kitchen_light

{% include common-tasks/filters.md %}

Common filtering examples

If you want to exclude messages of some entities or domains from activity tracking, just add the exclude parameter like:

# Example of excluding domains and entities from activity tracking (formerly called logbook)
logbook:
  exclude:
    entities:
      - sensor.last_boot
      - sensor.date
    entity_globs:
      - sensor.weather_*
    domains:
      - sun

In case you just want to see messages from some specific entities or domains, use the include configuration:

# Example to show how to only track the activity of the listed domains and entities
logbook:
  include:
    domains:
      - sensor
      - switch
      - media_player

You can also use the include list and filter out some entities or domains with an exclude list. Usually, this makes sense if you define domains on the include side and filter out some specific entities.

# Example of combining include and exclude configurations for activity tracking
logbook:
  include:
    domains:
      - sensor
      - switch
      - media_player
  exclude:
    entities:
      - sensor.last_boot
      - sensor.date
    entity_globs:
      - sensor.weather_*

Exclude events

If you have sensor.date to show the current date in the UI, but you do not want activity tracking for that sensor every day, it can be excluded. To exclude these entities, just add them to the exclude > entities list in the configuration of the activity tracking.

To exclude all events from a whole domain, add it to the exclude > domain list. For instance, if you use the sun domain only to trigger automations on the azimuth attribute, then you are possibly not interested in activity tracking for sun rise and sun set.

Excluded entities still take up space in the database. It may be advisable to exclude them in recorder instead.

Custom entries

It is possible to add custom entries to activity tracking by using the script integration to fire an event.

# Example configuration.yaml entry
script:
  add_logbook_entry:
    alias: "Add activity"
    sequence:
      - action: logbook.log
        data:
          name: Kitchen
          message: is being used
          # Optional
          entity_id: light.kitchen
          domain: light

{% important %} When calling the logbook.log action without a domain or entity_id, entries will be added with the logbook domain. Ensure that the logbook domain is not filtered away if you want these entries to appear in your Activity panel. {% endimportant %}

{% note %} Sensor entities that have been assigned units (for example, have a unit_of_measurement attribute) are assumed to change frequently and those sensors are automatically excluded from activity tracking. {% endnote %}