I had this when I added time and date sensors. In your configuration.yaml, exclude those entities from the log book.
logbook:
exclude:
entities:
- sensor.time
- sensor.date
- sensor.date_time
I had this when I added time and date sensors. In your configuration.yaml, exclude those entities from the log book.
logbook:
exclude:
entities:
- sensor.time
- sensor.date
- sensor.date_time
I have the same since I have the time integration set up as you do. But I have so many activities happening that a time change every minute is drowned and disappears in the list quickly.
So my solution is to add more add-ons and integrations to drown out the time.
I don't know how to solve it, but I can tell you that this isn't normal behaviour, I have no such thing in my activity log.
Do you have a helper entity for time or something?
all 10 comments