Tried to post in the main thread for 0.115, but it got buried.
Shouldn’t this be showing the automation that called light.turn_off?
1 Like
I get script names in there sometimes, but I’ve never seen an actual automation name. The services don’t really serve a purpose. Wait…my light was turned off by light.turn_off? You don’t say…
3 Likes
Seems like this feature is a bit wonky tbh, my kitchen light is showing correctly in the logbook this morning…
But in the history view of the entity itself it’s not even showing that the service turned it off, but curiously is showing that the service turned it on…
Nobody is sharing my pain here? Just brought up 0.115.4 and this is still an issue for me.
I’m running 115.3 and honestly not seeing anything in the log book of what’s updating entities unless I do it in the UI myself…
I just had the need to go look in the logbook for when one of my lights was turned on/off and all it said was “deck light turned on by service light.turn_on”. 
Really useful info there… 
Something tells me this feature needs a going over.
1 Like
All just in yaml, although at least 90% of mine are correctly showing what has changed and the cause of it in the logbook currently, but that percentage drops massively for the history tab on individual entity pages.
I have exactly the same problem in my setup. I have never seen an actual user name in the logbook. I use Postgres as logbook storage backend, which may be related. Is there anyone with a working fix for this or is this a real bug in HA?
Hmmmm…I’m using mariaDB as my backend storage. I wonder if there’s a connection to the database layer and this issue?
1 Like
I’m on mariadb too if that helps anyone works this out.
FYI, 0.118.0 changed nothing for me.
This still the case for you? I recently switched over to mariaDB and also noticed that my logbook shows service calls instead of automation names as well. I assume that’s the reason for the change?
Yes, this is still the case for me. Although I’m not willing to go back to a file database…mariaDB is so much faster for the amount of data I keep.
Yeah it doesn’t bug me so much, was just curious what the change might be. I guess I found my answer. Thanks!
I have never seen an automation name in my logbook or history view, it’s always just the service name. I use the default database, nothing special. I am running 2021.3.2, it’s been the same for every update. I was really hoping it would start working some point…
I actually saw some different behaviour in the latest release of HA. I have an automation that looks something like this:
automation:
- alias: the_automation
trigger: whatever
action:
- service: script.do_some_stuff
- service: light.turn_on
data:
entity_id: light.my_light
Then, in the log book, it says that light.my_light was turned on by script.do_some_stuff. That’s not right.
I posted in the community earlier about this same problem, after I couldn’t find anything related. Automation Triggered not shown in logbook
It always seems to happen that I find a related post (that wasn’t in the suggested topics pop-up) hours after I make one! 
It’s always reassuring to know others share your pain and then disappointing when the final post isn’t the solution.
I’m running the latest HA OS and basic db. It seems it should be expected behaviour to have the name of the automation that was triggered, appear in the logbook. I’ve even added a service call to the end of an automation for logbook.log and included the automation name, but I still don’t get anything showing in the logbook.
Have any of you managed to resolve the issue?
I still have this issue. I’ve just updated to the latest stable version as of yesterday.