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
Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.
Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation
Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk
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
This only hides the entries from the logbook, but they're still being saved to database taking up disk space.
I would go further and exclude them from the recorder
.
Assuming you’ve configured recorder to include them (or all entities).
That's a safe assumption given the post is about entries in the logbook and that depends on the recorder.
Thanks!
Appreciate you taking the time to share this, have a great weekend.
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.
Brilliant solution
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?