Excluded time and date entities still shows up in logbook

Configuration
1

I hope configuration.yaml is the place to exclude entities from the time and date integration from showing up in the logbook.

I’ve read around and think this is right, but probably not, since even after a hard reboot, they still (over)populate the logbook.

Anyone have any idea of what I’m doing wrong?

logbook:
  exclude:
    entities:
      - sensor.time
      - sensor.date
      - sensor.date_time
      - sensor.date_time_utc
      - sensor.date_time_iso
      - sensor.time_date
      - sensor.time_utc
2

That should definitely exclude them.

Do you have any other conflicting logbook include: config?

Were did you put that config?

Can you also take a screenshot of what you mean by the “logbook”, just to make sure we are talking about the right thing.

3

Sorry, I don’t understand what you mean. What config?

1000082637
10000826371440×2852 152 KB

4

This config:

5

If you don’t want the history of the values as opposed to them only not appearing in the logbook, then under the recorder: setting in your configutation.yaml:

purge_keep_days: 10
auto_purge: true
exclude:
  entities:
    - sensor.date
    - sensor.date_time
    - sensor.time_date
    - sensor.time
    - sensor.time_utc
6

That is placed, as I wrote, in my configuration.yaml. At the bottom.

7

I really don’t see the need for these values appearing anywhere, so I’ll read about the recorder and paste in as you suggested.