alander
(Alex)
December 1, 2024, 9:02am
1
Step Details of a trace with multiple conditions can be very difficult to find the condition results you wish to check e.g.
Executed: 1 December 2024 at 07:51:52
Result:
result: true
conditions/0
Executed: 1 December 2024 at 07:51:52
Result:
result: true
conditions/0/conditions/0
Executed: 1 December 2024 at 07:51:52
Result:
result: true
conditions/0/conditions/1
Executed: 1 December 2024 at 07:51:52
Result:
result: true
conditions/0/conditions/1/conditions/0
Executed: 1 December 2024 at 07:51:52
Result:
result: false
conditions/0/conditions/1/conditions/0/entity_id/0
Executed: 1 December 2024 at 07:51:52
Result:
result: false state: ‘on’ wanted_state: ‘off’
conditions/0/conditions/2
Executed: 1 December 2024 at 07:51:52
Result:
result: true
conditions/0/conditions/2/entity_id/0
Executed: 1 December 2024 at 07:51:52
Result:
result: true state: ‘on’ wanted_state: ‘on’
Why can’t the elements such as conditions/0/conditions/2/entity_id/0 be changed to what it is in the GUI e.g.
Condition: Confirm light behind sofa is off
or just show the condition line shown with the result after;
- condition: state
entity_id: light.light_behind_sofa
state: 'off'
Recte
December 7, 2024, 3:59pm
2
Mentioned something like this at the feature request section too: Step names and aliasses in trace view of automations and scripts
1 Like
alander
(Alex)
February 14, 2025, 6:52am
3
Not sure if it was the 2025.2 release as I can’t immediately find it in all changes, but now it shows the comment or default title! Easier to read now! (I’d personally prefer the text to be the largest and the if/condition/0 in the square brackets to be honest but still much better!
Fanful
February 14, 2025, 7:59am
4
Looks like it was added here:
home-assistant:dev
← boern99:Add-additional-information-to-automation-step-details
opened 05:32PM - 12 Sep 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO NOT… DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
Adds some extra information to Automation Traces, such as describeCondition and entity_id
see https://github.com/home-assistant/frontend/discussions/20660
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
## Summary by CodeRabbit
- **New Features**
- Enhanced trace path details display with improved context on conditions and entities.
- Conditional rendering of `alias` and formatted display of `entity_id` for better clarity.
- **Bug Fixes**
- Improved navigation through nested properties for accurate detail retrieval.
alander
(Alex)
February 14, 2025, 6:40pm
5
Looks like it took a while to hit after the December release at least when I originally posted the WTH