Add labels to Transmission add_torrent service and events#42742
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
This PR documents the new optional labels field for the Transmission integration's add_torrent action and updates event documentation to reflect that labels are included in events. The automation example has been modernized to demonstrate the labels functionality while making it more beginner-friendly by using persistent notifications.
Key changes:
- Added
labelsparameter documentation to theadd_torrentaction - Updated event automation description to mention labels are included in event data
- Replaced the previous automation example with an updated version that demonstrates label filtering and uses built-in persistent notifications
| message: >- | ||
| {{trigger.event.data.name}} downloaded to | ||
| {{trigger.event.data.download_path}} with labels | ||
| {{trigger.event.data.labels}} |
There was a problem hiding this comment.
The multi-line string in the template exceeds 80 characters per line. According to the documentation guidelines, contents of code fenced blocks must not exceed 80 characters per line. The message template should be reformatted to keep lines within this limit while maintaining readability.
There was a problem hiding this comment.
Not sure if this is correct
| - condition: template | ||
| value_template: "{{ 'remove' in trigger.event.data.labels }}" |
There was a problem hiding this comment.
According to the YAML style guide, when a property accepts a single mapping or a list of mappings, a list of mappings must be used. The condition should be formatted as a list with a dash prefix for consistency with Home Assistant automation standards.
There was a problem hiding this comment.
Not sure if this is correct
Proposed change
Adds documentation of new optional labels field on add_torrent action.
Amend the event documentation to include the labels field.
Update example automation using the new labels field, also changed to use built in persistent notification to make it beginner friendly.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.