That is a new entity as of 2024.2. You should be able to exclude it from the logbook via configuration, and automate as usual using a state trigger, or template sensor, etc.
That’s what I’ll probably end up doing. Although it definitely could be useful for future automations, the sheer amount of updates is definitely clogging up my logbook
AFAIK, excluding from the logbook is only possible from the YAML config. Would be a nice UI feature though.
Also, entities with a “unit of measurement” are automatically excluded from logbook in order to avoid issues like this. Not sure of “date” is a valid unit of measurement, but maybe this entity could be excluded by the integration.
I have the same thing, but it started 2 days ago and slows down HA (rPi4).
I definitly pressed the vote button, but why would anyone like "last seen"to completely flood the log and slow down the system?
I’m disabling the entities because if it’s a new entity since 2024.2, I will not notice not having it, but it seems more like a bug than anything else to me, logging multiple non-events per second)
Edit: na I was correct after all… Sorry for all confusing stuff…
I have added a few lines in configure.yaml that seems to remove this from the log/recorder - this may och may not be the correct solution, so be aware:
What’s the benefit? Is there a reason to not turn them off? I can’t think of a way that I would use them, but I assume that code got written for purpose.