Fuel became low

The Fuel became low trigger fires when a Fumis pellet stove reports that its fuel is running low. The stove raises its low fuel level alert (A001), and this trigger passes that moment on to your automations.

Use Fuel became low to get a notification on your phone, add pellets to your shopping list, or remind everyone at home to refill the hopper before the fire goes out. It works on every stove that raises the low fuel alert, including stoves that don’t have a fuel level sensor.

Using this trigger from the user interface

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

To use Fuel became low in an automation:

1. Go to Settings > Automations & scenes.
2. Open an existing automation, or select Create automation > Create new automation.
3. In the When section, select Add trigger.
4. Search for Fuel became low and select it.
5. Under Stoves, select one or more of your stoves.
6. Select Save.

Options in the UI

Using this trigger 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. For how an automation is built in YAML, refer to Automations in YAML.

In YAML, put the settings that are specific to this trigger under options. Keep target, if the trigger uses one, and general settings such as id, alias, enabled, and variables at the top level, next to trigger.

When this trigger starts an automation, it passes data about what happened to the automation. You can use this trigger data in the templates of your conditions and actions. To see which data is available, refer to Trigger data in templates.

In YAML, refer to this trigger as fumis.fuel_became_low. A basic example looks like this:

trigger: fumis.fuel_became_low
options:
  device_id: 0123456789abcdef0123456789abcdef

This fires the moment the stove with that device ID reports that its fuel is running low. When you create the automation in the automation editor, it fills in the device ID of your stove for you.

Options in YAML

The options go under options.

Good to know

• This trigger uses the same low fuel level alert as the Alert sensor of your stove, so you don’t need a fuel level sensor for it.
• Your stove shows only one alert at a time, so another alert, like the door being open, can hide the low fuel alert. The trigger takes this into account. It fires once when the fuel becomes low, and doesn’t fire again when another alert comes and goes while the fuel is still low.
• After the integration reloads, an update fails, or the stove reports an unrecognized alert, the first valid update establishes a new baseline. If that update already reports low fuel, the trigger does not fire.
• Home Assistant checks your stove every 30 seconds, so it can take up to 30 seconds after the stove raises the alert before the trigger fires.
• If you want to pick your own moment and your stove has a fuel level sensor, use a Numeric state trigger on the Fuel level sensor instead.

Trigger variables

In addition to the data that all triggers include, this trigger includes the following data:

• trigger.device_id: The device ID of the stove that reported its fuel became low.

Try it yourself

Ready to test this? Go to Settings > Automations & scenes, create a new automation, and add this trigger. Save the automation, and then make the trigger react. For example, change the state of the targeted entityAn 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], turn on a light that the trigger monitors, or change its brightness. To check whether the automation ran, open its traces.

More examples

Real scenarios where this trigger fires in automations and scripts. Copy any example and adapt it to your setup. In the visual editor, select the UI options listed in the example when they are available, or paste the YAML code.

Automation: get a notification when the pellets run low

Never run out of pellets unexpectedly. This automation sends a notification to your phone when your stove reports that its fuel is running low, so you can refill the hopper before the fire goes out.

• Trigger: Fuel became low
  • Stoves: Living room stove
• Action: Send a notification message
  • Target: My Device (notify.my_device)

alias: "Notify when the pellet stove runs low on fuel"
triggers:
  - trigger: fumis.fuel_became_low
    options:
      device_id: 0123456789abcdef0123456789abcdef
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      title: "Pellet stove"
      message: >
        The stove reports its fuel is running low. Time to refill the
        hopper.

Automation: add pellets to the shopping list

When the stove reports its fuel is running low, it might also be time to buy a new batch of pellets. This automation adds them to your shopping list, so you don’t forget next time you’re at the store.

• Trigger: Fuel became low
  • Stoves: Living room stove
• Action: Add to-do list item
  • Target: Shopping list (todo.shopping_list)
  • Item: Pellets

alias: "Add pellets to the shopping list when the stove runs low"
triggers:
  - trigger: fumis.fuel_became_low
    options:
      device_id: 0123456789abcdef0123456789abcdef
actions:
  - action: todo.add_item
    target:
      entity_id: todo.shopping_list
    data:
      item: "Pellets"

Still stuck?

To find out why the trigger didn’t react, make the change that it should react to, and then open the traces of the automation. If the automation didn’t run, there’s usually no trace, but some triggers record a Did not trigger trace. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.

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

Related triggers

Explore related triggers:

• Numeric state crossed threshold: Triggers when a numeric value crosses a threshold.