Replies: 1 comment
-
Related links: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
NOTE: This feature request may span into the core project.
I've very thankful that currently we have entity history and it works for the most part.

But it really fails to provide value when you are trying to figure out why something actually happened as you have no context. And it makes it really hard to track it down to a specific automation or automation trigger. I'd really love if we could take this to the next level by being able to augment this information by providing additional data to service calls like a
source
andreason
. I think it would look like thisThis would make it so you could easily see what triggered the light to turn on and this could work across automations and node red automations or any service call. You could even have rich interaction to go right to the automation to edit it.
I think this would also solve some issues where users are using a custom entity sensor to provide this information.
Beta Was this translation helpful? Give feedback.
All reactions