Set speed

The Set speed action sets the download speed limit for the NZBGet queue, in kilobytes per second. Set it to 0 to remove the limit and let downloads run at full speed.

This is handy for throttling downloads automatically, for example, capping the speed during the day and lifting the limit at night.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To set the download speed limit from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create automation > Create new automation.
  3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
  4. In the Then do section, select Add action.
  5. From the search box, search for and select NZBGet: Set speed.
  6. Enter the Speed limit you want to apply.
  7. Select Save.

This action does not support targets. In the UI, you are not prompted to choose an area, device, entity, or label.

Options in the UI

Speed (Optional)

The download speed limit, in kilobytes per second. Set to 0 for no limit.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as nzbget.set_speed. A basic example looks like this:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: nzbget.set_speed
data:
  speed: 500

This limits the download queue to 500 kilobytes per second.

Options in YAML

speed integer

The download speed limit, in kilobytes per second. Set to 0 for no limit.

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

More examples

Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup.

Tip

You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.

Automation: throttle downloads during the day

Cap the download speed during the day and lift the limit again overnight.

  • Trigger: Time, 08:00
  • Action: NZBGet: Set speed
YAML example for throttling downloads during the day
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Throttle downloads during the day"
triggers:
  - trigger: time
    at: "08:00:00"
actions:
  - action: nzbget.set_speed
    data:
      speed: 500

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Tip

AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.

Related actions

These actions work well alongside this one:

  • Pause: Pauses the NZBGet download queue.

  • Resume: Resumes the NZBGet download queue.