Loads of time changes in log => Error?

Configuration
1

Hi everyone,

this morning i noticed loads of time changes on the logbook. I think this also prevents automations from running?
Any ideas?

Thanks. Kay.

27. Dezember 2018

11:43

Internet Time changed to @488

11:43

Date & Time changed to 2018-12-27, 11:43

11:43

Time changed to 11:43

11:43

Time (UTC) changed to 10:43

11:43

Time & Date changed to 11:43, 2018-12-27

11:29

Internet Time changed to @478

11:29

Date & Time changed to 2018-12-27, 11:29

11:29

Time changed to 11:29

11:29

Time (UTC) changed to 10:29

11:29

Time & Date changed to 11:29, 2018-12-27

11:14

Internet Time changed to @468

11:14

Time (UTC) changed to 10:14

11:14

Time & Date changed to 11:14, 2018-12-27

11:14

Date & Time changed to 2018-12-27, 11:14

11:14

Time changed to 11:14

10:59

Internet Time changed to @457

10:59

Time (UTC) changed to 09:59

10:59

Time & Date changed to 10:59, 2018-12-27

10:59

Date & Time changed to 2018-12-27, 10:59

10:59

Time changed to 10:59

10:44

Internet Time changed to @447

10:44

Time (UTC) changed to 09:44

10:44

Time & Date changed to 10:44, 2018-12-27

10:44

Date & Time changed to 2018-12-27, 10:44

1 Like
2

Nevermind! I fixed it by removing the sensor:

# Example configuration.yaml entry
sensor:
  - platform: time_date
    display_options:
      - 'time'
      - 'date'
      - 'date_time'
      - 'time_date'
      - 'time_utc'
      - 'beat'

Lets see whether the automation now works again.

3

I have the same issue.

Are you saying that you removed the time_date sensor?

4

That’s like cracking a walnut with a sledgehammer.

You have removed a sensor that you will find you will need (eventually). Just to stop it spamming the logbook. When what you should have done is this:

logbook:
  exclude:
    entities:
      - sensor.date
      - sensor.date_time

And while you are at it:

recorder:
  exclude:
    entities:
      - sensor.date
      - sensor.date_time

Read more here:

I doubt that is true.

3 Likes
5

I had the same problem and what solve my issue was putting in the configuration.yaml file the following entries:

logbook:
  exclude:
    entities:
      - sensor.time
      - sensor.date
      - sensor.date_time
      - sensor.date_time_utc
      - sensor.date_time_iso
      - sensor.time_date
      - sensor.time_utc
      
recorder:
  exclude:
    entities:
      - sensor.time
      - sensor.date
      - sensor.date_time
      - sensor.date_time_utc
      - sensor.date_time_iso
      - sensor.time_date
      - sensor.time_utc
sensor:
  - platform: time_date
    display_options:
      - 'time'
      - 'date'
      - 'date_time'
      - 'date_time_utc'
      - 'date_time_iso'
      - 'time_date'
      - 'time_utc'

Is that ok?

6

This is a five year old topic. Things change. You would have been better off creating a new topic.

But in answer to your question yes and no.

Yes the excludes are fine. No the time_date sensor yaml is not. As of version 2024.2.0 this integration is set up using the UI, not yaml. See:

https://www.home-assistant.io/blog/2024/02/07/release-20242/#integrations-now-available-to-set-up-from-the-ui

and https://www.home-assistant.io/integrations/time_date/

7

Not sure why you’d want to remove the time and date sensors. I used the same logbook and recorder yaml but just excluded the two TP-Link sensors of mine that were logging entries every minute:

logbook:
  exclude:
    entities:
      - sensor.kitchen_light_strip_device_time
      - sensor.tp_link_power_strip_p300_device_time
recorder:
  exclude:
    entities:
      - sensor.kitchen_light_strip_device_time
      - sensor.tp_link_power_strip_p300_device_time

Logbook peace at last! :slight_smile: