home-assistant.io/source/_integrations/transmission.markdown

title, description, ha_category, ha_release, ha_iot_class, ha_config_flow, ha_codeowners, ha_domain, ha_platforms, ha_integration_type, ha_quality_scale

title	description	ha_category	ha_release	ha_iot_class	ha_config_flow	ha_codeowners	ha_domain	ha_platforms	ha_integration_type	ha_quality_scale
Transmission	Instructions on how to integrate Transmission within Home Assistant.	Downloading Sensor Switch	0.87	Local Polling	true	@engrbm87 @JPHutchins	transmission	sensor switch	service	bronze

The Transmission integration allows you to monitor your Transmission BitTorrent downloads from within Home Assistant and set up automations based on that information.

Prerequisites

Before setting up the Transmission integration, ensure you have:

1. Transmission installed and running on your network.
2. The IP address or hostname and port of your Transmission instance.
3. The username and password of your Transmission instance, if set.
4. Your Transmission client must first be configured to allow remote access. In your Transmission client navigate to Preferences -> Remote tab and then click the Allow remote access checkbox.

{% include integrations/config_flow.md %}

{% configuration_basic %} Host: description: "The IP address or hostname of your Transmission instance. For example: 192.168.1.100 or transmission.local." Path: description: "The RPC request target path, for example, /transmission/rpc." Port: description: "The port Transmission is running on. Default is 9091." Username: description: "Your Transmission username, if set." Password: description: "Your Transmission password, if set." Verify SSL certificate: description: "Enable SSL certificate verification when connecting via HTTPS." {% endconfiguration_basic %}

Supported functionality

The Transmission integration will add the following sensors and switches.

Sensors

• The status of your Transmission daemon.
• The current download speed [MB/s].
• The current upload speed [MB/s].
• The current number of active torrents.
• The current number of paused torrents.
• The total number of torrents present in the client.
• The current number of started torrents (downloading).
• The current number of completed torrents (seeding).

Switches

• A switch to start/stop all torrents.
• A switch to enable turtle mode (a.k.a. alternative speed limits).

Event automation

The Transmission integration is continuously monitoring the status of torrents in the target client. Once a torrent is started or completed, an event is triggered on the Home Assistant Bus containing the torrent name and ID, which can be used with automations.

Possible events are:

• transmission_downloaded_torrent
• transmission_started_torrent
• transmission_removed_torrent

Inside the event, there is the name of the torrent that is started or completed and the path where the files are downloaded, as seen in the Transmission User Interface.

Example of an automation that notifies on successful download and removes the torrent from the client:

{% raw %}

- alias: "Notify and remove completed torrent"
  triggers:
    - trigger: event
      event_type: transmission_downloaded_torrent
  actions:
    - action: notify.telegram_notifier
      data:
        title: "Torrent completed!"
        message: "{{trigger.event.data.name}} downloaded to {{trigger.event.data.download_path}}"
    - action: transmission.remove_torrent
      data:
        entry_id: eeb52bc78e11d813a1e6bc68c8ff93c8
        id: "{{trigger.event.data.id}}"

{% endraw %}

Actions

All Transmission actions require integration entry_id. To find it, go to Developer tools > Actions. Choose the desired action and select your integration from dropdown. Then switch to YAML mode to see entry_id.

Action add_torrent

Adds a new torrent to download. It can either be a URL (HTTP, HTTPS or FTP), magnet link or a local file (make sure that the path is white listed).

Data attribute	Optional	Description
entry_id	no	The integration entry_id
torrent	no	Torrent to download
download_path	yes	Absolute path to the download directory. If not specified, the Transmission's default directory will be used.

Action remove_torrent

Removes a torrent from the client.

Data attribute	Optional	Description
entry_id	no	The integration entry_id
id	no	ID of the torrent, can be found in the torrent_info attribute of the *_torrents sensors
delete_data	yes	Delete torrent data (Default: false)

Action start_torrent

Starts a torrent.

Data attribute	Optional	Description
entry_id	no	The integration entry_id
id	no	ID of the torrent, can be found in the torrent_info attribute of the *_torrents sensors

Action stop_torrent

Stops a torrent.

Data attribute	Optional	Description
entry_id	no	The integration entry_id
id	no	ID of the torrent, can be found in the torrent_info attribute of the *_torrents sensors

Templating

Attribute torrent_info

All *_torrents sensors e.g. sensor.transmission_total_torrents or sensor.transmission_started_torrents have a state attribute torrent_info that contains information about the torrents that are currently in a corresponding state. You can see this information in Developer Tools -> States -> sensor.transmission_total_torrents -> Attributes, or by adding a Markdown card to a dashboard with the following code:

{% raw %}

content: >
  {% set payload = state_attr('sensor.transmission_total_torrents', 'torrent_info') %}

  {% for torrent in payload.items() %} {% set name = torrent[0] %} {% set data = torrent[1] %}

  {{ name|truncate(20) }} is {{ data.percent_done }}% complete, with {{ data.ratio }} ratio, {{ data.eta }} remaining {% endfor %}
type: markdown

{% endraw %}

Removing the integration

This integration follows standard integration removal. After removal, your Transmission instance continues running with its current configuration.

{% include integrations/remove_device_service.md %}