When a light turns on at 3 a.m., the logbook tells you that its state changed. It does not easily tell you which action was called, with what data and from where. Home Assistant now has a page for exactly that. Joost Lekkerkerker's "Action history" tab in the Tools panel was merged on 26 October 2026, followed the same day by two additions to its detail view. A matching backend command in the logbook was merged on 23 October. All of it is in the development branch and set for Home Assistant 2026.11.

What the page shows

Every recorded action call appears as a row in a table with five columns: Action, Action ID, Targets, Cause and Time. Targets are shown by name, so instead of raw IDs you see the entity, device, area or floor the action was aimed at. The cause column uses the same wording as the logbook and names the user, automation or script behind the call. When the trace integration is loaded, an automation or script cause links to its trace, which is where you go next to see why it fired.

There is a search box and a date range picker with a refresh button. By default the page covers the start of the previous hour up to two hours ahead. If nothing happened in that window, it says "No actions were performed in this time range."

The data comes from the logbook, so the page shows what the logbook has recorded and keeps it as long as your recorder keeps history.

Copy it or run it again

Clicking a row opens a detail dialog with the user, the context ID and the full data sent with the call. Two buttons were added on the same day. "Copy as YAML" copies the call in the format you would paste into a script or automation, for example:

action: timer.start
target:
  entity_id:
    - timer.test_timer
data:
  duration: '00:00:20'

"Perform again" runs the same call once more and takes the place of the close button. This helps when a voice command or a dashboard button did the right thing and you want to turn it into an automation, or when you need to repeat a call while testing a device without rebuilding it by hand in the action editor.

Where it fits

Until now, finding out which action reached a device meant digging through traces one automation at a time or turning on debug logging. The new page collects every call in one list, whatever started it. It does not replace traces, which still explain the steps and conditions inside an automation, but it gives a quick answer to the first question: what was called, by whom and when.