Activity logs becoming more and more useless?

Configuration
1

Hi all,

I wanted to double check with the community… but I feel like the Activity log in home assistant is becoming more and more useless. Is it just me?
I believe to remember versions where each activity (if triggered via automation) had the name of the automation written in the activity.

Especially since version 2025.10+, I constantly see Activity logs like:

  • Entrance door light turned on triggered by action Light: Turn on
  • gallery 1 turned on triggered by action Script: Gallery_day-light
  • Bathroom sTRV changed to Heat

To mention this upfront, Entrance & gallery lights are never turned on manually, there isn’t even a button anywhere for this. TRVs are only controlled via automations or scripts.

I mean what’s this supposed to help me with?
I know the scripts are relevant, but all that matters is the automation, the automation triggers the script. So why is HA no longer providing the name of the automation?
Am I missing something? Did I overlook something?

Thanks all,

2

I have further pinpointed the issue:
By coincidence I was staying on the activity logs whilst an automation happened.
Whilst I was there and saw the Activity refreshed in real-time, I can see the messages
“Bathroom sTRV turned off triggered by automation JO_open window disable sTRV for 15 mins [tado] triggered by state of JO window”

but, the moment I leave the Activity log and come back, I only see:
“Bathroom sTRV turned off triggered by action Input boolean: Turn on”.

So it looks like a bug rather than a generic issue.
Does anyone else have a similar issue?
Or does someone know if this is maybe known?

I’m currently on 2025.12.4

3

You didn’t by “choice” click on the activity, to see possible details ?

4

Sorry, false alarm or my mistake.
In an attempt to reduce overall DB size a couple of months ago, I added the domain “automation” to the recorder exclusion yaml. From what I read, it said it would only exclude state changes about the automation, which I would’ve been fine with, when an automation changes, becomes unavailable during saving, becomes available again, etc. I wasn’t aware this would cause such an issue in the Activity log.
Especially since the logs in real-time did show as usual, but once I left and returned, the logs were useless.

To everybody who has this weird behaviour, don’t add this to your configuriation.yaml

recorder:
  exclude:
    domains:
      - automation