Set fan speed tracked state
Use this action to tell Home Assistant what speed a Bond fan is actually running at, without sending any signal to the fan. Bond controls many devices over one-way radio, so it cannot always sense their real state. If the tracked speed drifts out of sync with the fan, this action corrects it.
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 tracked fan speed from an automation or a script:
- Go to Settings > Automations & scenes.
- Open an existing automation or script, or select Create automation > Create new automation.
- 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.
- In the Then do section, select Add action.
- From the search box, search for and select Bond: Set fan speed tracked state.
- In Entity, select the fan you want to control.
- Set the Fan speed to the percentage the fan is actually running at.
- Select Save.
Options in the UI
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. For how an automation or a script is built in YAML, refer to Automations in YAML and Scripts.
In YAML, refer to this action as bond.set_fan_speed_tracked_state. A basic example looks like this:
action: bond.set_fan_speed_tracked_state
target:
entity_id: fan.living_room_fan
data:
speed: 50
This tells Home Assistant that fan.living_room_fan is running at 50%.
Options in YAML
Targets of the action
This action requires a target. The target is the object of the action. You can point the action at a single 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], a device, an area, a floor, or a label, and Home Assistant will run the action on every matching Bond fan behind that target.
-
Entity: one specific Bond fan, such as
fan.living_room. - Device: every Bond fan that belongs to a device.
- Area: every Bond fan in a room or area.
- Floor: every Bond fan on a floor.
- Label: every Bond fan that shares a label.
You can also select different target types in one action. For example, you can add a specific entity and an area as targets in the same action to run the action on both of them at once.
In the UI, this action has an Entity field instead of targets. There, you can select one fan. To use a device, an area, a floor, or a label as the target, select the three dots menu
Good to know
- This action only updates the tracked state. It does not send a signal to the fan, so the fan keeps running exactly as it was.
- Use it to resync Home Assistant after the fan was changed with the original remote.
Try it yourself
Ready to test this? Open Settings > 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. In the visual editor, select the UI options listed in the example or paste the YAML code.
You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the visual 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: resync the fan speed after using the remote
Use this automation when a physical remote button tells Home Assistant the fan was set to high, so the tracked speed matches reality.
-
Trigger: State changed
- Entity: Fan remote button sensor
- To: High
-
Action: Bond: Set fan speed tracked state
- Entity: Living room fan
-
Fan speed:
100
Show example YAML
- alias: "Resync the living room fan speed"
triggers:
- trigger: state
entity_id: sensor.fan_remote_button
to: "high"
actions:
- action: bond.set_fan_speed_tracked_state
target:
entity_id: fan.living_room_fan
data:
speed: 100
Still stuck?
To test the action on its own, run it in the automation editor with Run action, and check the message that it shows. To see what the action did when the automation ran, open the trace of that run. 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 action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.
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
Explore related actions:
-
Set switch power tracked state: Updates the power state Home Assistant believes a Bond switch is in.
-
Set light power tracked state: Updates the power state Home Assistant believes a Bond light is in.
-
Set light brightness tracked state: Updates the brightness Home Assistant believes a Bond light is set to.