Ability to show log book view next to an automation trigger or condition

[niemyjski]

I find myself using the logbook in a separate tab to find out why an automation didn't trigger or match a condition. It would be super nice if I could click a button or view inline what happened to that device or entity during a time frame.

[KTibow]

Maybe this could be added to the quick bar?

[niemyjski]

I'm not a designer by any means but I think there are many different ways to implement this in a useful way.

1. We could either put a narrow history in the footer of each trigger or condition. I think if you click on this it would bring up a modal with the log view.

2. We could add a dropdown option on the trigger to show the log book using the existing dropdown.

3. We could put a log view next to the entity on the left, this is less ideal as it makes the ui pretty busy
   

[niemyjski]

I just want to see a quick history so I can visually see if something changed and should have been triggered but wasn't. I'm a visual person. I think you may want to compose multiple histories in some circumstances like maybe for delayed or wait until actions (to see the current state).

[KTibow]

Okay. Now we just need to add this to the code. I would do this, but I'm not familiar with handling history. It could be you could just embed a Lovelace card that does that.
As for your second example: Think about mobile. Would the logbook be below or above or inside?

[niemyjski]

I think embedding a Lovelace card would work but some have different layouts for history card? Would it be better to see a log book of all trigger entities, a log book of all conditions etc...?

For mobile maybe they are hidden or it pops up a modal from the options menu on the trigger or condition?

[KTibow]

How about this icon in the device/entity text fields?