Boost the ventilation while the cooker hood runs
A smart plug measures the cooker hood's power, and a Home Assistant blueprint switches the ventilation to a supply-heavy boost while you cook.
- Published
- Level
- Beginner
- Hardware
- SONOFF S60ZBTPF Zigbee smart plug with power metering, ventilation unit with presets
A cooker hood that vents outside blows a lot of air out of a tight house. With the ventilation unit on its normal setting, the house goes into underpressure: the hood pulls less, doors whistle, and replacement air leaks in through every gap. This setup notices from the hood’s power draw that it’s running and switches the ventilation to a preset with more supply than extract air until the cooking is done.
There’s no wiring into the hood. It plugs into a Zigbee smart plug that measures power, and that reading is all the automation needs.
What it does
- Notices the hood from its power. When the plug’s reading stays above a threshold for 20 seconds, the ventilation switches to the boost preset.
- Runs on after cooking. Once the hood has been off for 2 minutes, the ventilation returns to its home preset, or to away if nobody is home. Changing the hood’s speed doesn’t end the boost.
- Undoes only its own change. If you or another automation change the preset while you cook, that change stays when the hood stops.
- Respects a stopped ventilation. If the ventilation is off, for example because a smoke guard stopped it, the hood never switches it on.
What you need
- A smart plug with power metering for the cooker hood. Mine is a SONOFF S60ZBTPF on Zigbee2MQTT. Any plug that gives Home Assistant a power sensor in watts works.
- A ventilation unit that shows up as a
fanentity with presets. Mine is a Vallox 110 MV.
Set the plug to stay on after a power cut (power_on_behavior: on in Zigbee2MQTT), and leave its switch on. The automation only reads the power; the hood’s own buttons still control it.
Vallox units. The preset names in Home Assistant don’t match the ones in the unit’s web control. The profile the web control calls Custom, with its own supply and extract fan speeds, is Fireplace in Home Assistant. Home Assistant’s Extra preset is the programmable input profile, which does nothing unless the unit has that input in use. I set Custom to 80 % supply and 50 % extract, so the unit replaces the air the hood blows out. The Custom profile’s own duration (6 hours here) works as a safety timer: if Home Assistant is down when you stop cooking, the unit still returns to Home on its own.
Step 1: find the threshold
Switch the hood on at each speed for half a minute and watch the plug’s power sensor. Mine reads 0 W when off and 76–127 W running; on many hoods the light can’t be switched on without the fan. Pick a threshold between the off reading and the lowest running reading, with some margin. I use 30 W. If your hood’s light can be used on its own, set the threshold above the light’s draw.
Step 2: a flag helper
The automation remembers that it started the boost with a toggle helper. Create one under Settings → Devices & services → Helpers → Create helper → Toggle, for example Cooker hood boost. It doubles as a dashboard indicator.
Step 3: the blueprint
Save it as config/blueprints/automation/automate_the_north/kitchen_hood_boost.yaml and reload automations.
Import blueprint to Home Assistant(opens in a new tab)View on GitHub(opens in a new tab)
Show the blueprint
blueprint: name: Ventilation boost from the cooker hood author: Automate the North description: > Switches the ventilation to a boost preset while the cooker hood runs, measured with a smart plug, and back once the hood has been off for a while.
**How it works**
- When the hood's power stays above the threshold, the ventilation switches to the boost preset and a flag remembers that this automation did it.
- When the hood has been off for the after-run time, the ventilation returns to the home preset, or to the away preset if nobody is home.
- It returns only if the boost preset is still on. If you or another automation changed the preset during cooking, that change stays.
- If the ventilation is off (for example a smoke guard stopped it), the hood never switches it on.
**Vallox units:** pick **Fireplace** as the boost preset. It is the profile the unit's own web control calls Custom, with adjustable supply and extract fans. Home Assistant's **Extra** preset is the programmable input profile instead. source_url: https://github.com/automate-the-north/home-assistant/blob/main/blueprints/automation/automate_the_north/kitchen_hood_boost.yaml domain: automation input: power: name: Hood power description: The power sensor of the smart plug the cooker hood is plugged into. selector: entity: filter: - domain: sensor device_class: power threshold: name: Threshold description: > The hood counts as running above this. Pick a value between the plug's reading with the hood off and its lowest fan speed. default: 30 selector: number: min: 1 max: 500 unit_of_measurement: W on_seconds: name: Delay before boosting description: How long the power must stay above the threshold. default: 20 selector: number: min: 0 max: 300 unit_of_measurement: s off_minutes: name: After-run time description: > How long the hood must stay off before the ventilation returns. Clears the last of the steam, and changing the hood's speed doesn't end the boost. default: 2 selector: number: min: 0 max: 60 unit_of_measurement: min ventilation: name: Ventilation description: A fan entity with presets, such as a Vallox unit. selector: entity: filter: - domain: fan active: name: Boost flag description: An input_boolean this automation turns on while the hood boost is running. selector: entity: filter: - domain: input_boolean preset_boost: name: Boost preset description: Ideally one with more supply than extract air, to replace what the hood blows out. default: Fireplace selector: text: {} preset_home: name: Home preset default: Home selector: text: {} preset_away: name: Away preset default: Away selector: text: {} home_zone: name: Home zone description: Its state is the number of people at home. default: zone.home selector: entity: filter: - domain: zone
mode: queuedmax: 10
# trigger_variables are available in triggers (the 'for' below) as well as in actionstrigger_variables: power_entity: !input power threshold: !input threshold on_seconds: !input on_seconds off_minutes: !input off_minutes
triggers: - trigger: template id: hood_on value_template: '{{ states(power_entity) | float(0) > threshold | float(30) }}' for: seconds: '{{ on_seconds | int(20) }}' - trigger: template id: hood_off value_template: '{{ states(power_entity) | float(0) <= threshold | float(30) }}' for: minutes: '{{ off_minutes | int(2) }}'
variables: fan_entity: !input ventilation zone_entity: !input home_zone p_boost: !input preset_boost p_home: !input preset_home p_away: !input preset_away current: "{{ state_attr(fan_entity, 'preset_mode') }}" normal: '{{ p_home if states(zone_entity) | int(0) > 0 else p_away }}'
actions: - choose: - conditions: - condition: trigger id: hood_on - condition: state entity_id: !input ventilation state: 'on' - '{{ current != p_boost }}' sequence: - action: fan.set_preset_mode target: entity_id: !input ventilation data: preset_mode: '{{ p_boost }}' - action: input_boolean.turn_on target: entity_id: !input active
- conditions: - condition: trigger id: hood_off - condition: state entity_id: !input active state: 'on' sequence: - action: input_boolean.turn_off target: entity_id: !input active # Only undo our own boost: leave the preset alone if someone changed it, or if # the ventilation is off - if: - condition: state entity_id: !input ventilation state: 'on' - '{{ current == p_boost }}' then: - action: fan.set_preset_mode target: entity_id: !input ventilation data: preset_mode: '{{ normal }}'Create an automation from Ventilation boost from the cooker hood and pick:
- Hood power: the plug’s power sensor
- Threshold: your value from step 1
- Ventilation: your ventilation fan entity
- Boost flag: the toggle from step 2
- Boost preset:
Fireplaceon a Vallox; otherwise the preset with the most supply air
Check that the preset names match your unit; open the ventilation entity and look at the preset list if unsure.
Good to know
- Why supply-heavy. A boost that raises supply and extract equally leaves the underpressure from the hood in place. More supply than extract replaces the air the hood takes out.
- Works next to other ventilation automations. The boost ends only if its own preset is still on, so it doesn’t fight a CO₂ boost or a manual change. After the hood stops it returns to home or away; a CO₂ automation boosts again the next time CO₂ crosses its limit.
- If the boost starts on its own, the plug’s reading is above the threshold without the hood running. Raise the threshold.