Back to Blog
Smart Home

How I Made My QuietCool Whole House Fan Smart

11/13/2026
4 min read

My QuietCool fan only worked with its own remote. A Bond Bridge could not fix that, so I built a bridge to Home Assistant. Here is how, and why windows matter.

My QuietCool whole house fan came with one smart feature: a remote. No app, no Wi-Fi, no way for Home Assistant to know it existed. A fan that moves a whole house of air should not depend on me finding a remote.

I wanted it in Home Assistant, with timers, and with a safety rule that stops it from starting when the house is shut. Here is what failed, what worked, and the one rule I would not skip.

What Didn't Work: A Bond Bridge

I tried a Bond Bridge first. It is a popular little box that learns remotes and lets you control them from your phone. It did not work for this fan.

The reason, according to Bond's own forum, is that QuietCool remotes do not talk the way most remotes do. They need a two-way conversation with the fan, and Bond's team said QuietCool was not on their roadmap in the thread I read. If your fan is a QuietCool, do not spend money on a universal bridge and hope.

What Did Work: A Small Board With a Radio

The fix was a small circuit board, a LilyGO LoRa32, that has a radio built in. The "LoRa" part of the name does not matter here. What matters is that the board can speak the same radio language as the remote. I loaded it with ESPHome, free software that turns a board like this into a Home Assistant device.

People in the Home Assistant community have already worked out how the QuietCool remote communicates, and you should start with their work instead of reinventing it. The esphome-quietcool project targets this exact board, and a forum thread covers the remote itself. Remotes come in different generations, so check yours matches before you buy anything. Also add a proper antenna before you transmit.

It works well. I can start the fan from my phone, from a dashboard, or from an automation.

What It Does Now

Home Assistant sees the fan as a switch, plus a few helpers:

  • Preset buttons for Low and High, each for 1, 2 or 4 hours, plus Off.
  • A timer that shows how long the fan has left.
  • A check that the fan really did what I asked. The board listens for the fan's reply, so Home Assistant does not just assume the command worked.
  • A fault light, in case something goes wrong with the radio.

That confirmation matters more than it sounds. Most cheap remote bridges shout a command and hope. I want the dashboard to show what the fan is doing, not what I told it to do.

The Rule I Would Not Skip: Windows

A whole house fan pulls air out of the house, and that air has to come in through open windows. QuietCool's own manual warns that with too few windows open, the fan can pull exhaust back down gas appliance vents, which is called back drafting. That is a real safety problem, not a comfort problem.

So my rules are simple:

  1. The fan will not start unless at least two windows are open.
  2. If it is running and the open windows drop below two, it shuts itself off, even if someone started it with the physical remote.
  3. It never turns itself on after a power loss or a restart.

I built the window check into the little board itself, so it keeps working even if Home Assistant is down. When the board blocks a start or shuts the fan off, it sends a high-priority alert to my phone that says what happened.

A software rule is a guard, not a guarantee. It does not replace reading your fan's manual or having a qualified person check your venting.

The Dashboard Card

I wanted a card that shows the real state and is not a casual on/off button. Tapping the main card does nothing. The fan only starts from an explicit preset button, and if too few windows are open, the card says so. It uses the custom:button-card add-on from HACS. The entity names below are samples, so swap in your own.

type: custom:button-card
entity: switch.example_whole_house_fan
name: Whole House Fan
icon: mdi:fan
show_state: false
show_label: true
tap_action:
  action: none
label: |
  [[[
    const on = entity.state === 'on';
    const w = Math.round(parseFloat((states['sensor.example_fan_open_windows'] || {}).state) || 0);
    const ev = states['sensor.example_fan_timer_remaining'] || {};
    const rem = parseFloat(ev.state);
    if (on) return 'Running' + (isNaN(rem) ? '' : ', ' + Math.round(rem) + ' ' + (ev.attributes.unit_of_measurement || '') + ' left') + ' | ' + w + ' windows open';
    return w >= 2 ? 'Off | ' + w + ' windows open' : 'Locked out | ' + w + ' of 2 windows open';
  ]]]

Below it I have a row of buttons, one per preset. Each one looks like this:

type: custom:button-card
name: Low 2h
icon: mdi:fan-speed-1
tap_action:
  action: call-service
  service: esphome.example_fan_preset
  data:
    preset: Low 2h

Is This for You?

Only if you already run Home Assistant and are comfortable flashing a small board. It is a weekend project, not a plug-and-play product.

If the fan has wired controls you can safely reach, a smart relay is simpler. People on the Home Assistant forum have done this with a Zooz relay, though it involves fan wiring and is a job for someone qualified. And if you like the idea of keeping things working without the cloud, that is the same reason I moved off SmartThings, which I wrote about in Goodbye SmartThings.

Disclaimer: This post is for educational and informational purposes only. Whole house fans move large volumes of air, can back draft gas and other combustion appliances, and are connected to household electrical wiring. Transmitting on radio frequencies is regulated, and modifying or controlling motorized and electrical equipment carries real safety risk and may void warranties. I am not a licensed electrician or HVAC technician. Do your own research, follow your fan's manual and local codes, and hire a professional where needed. Grant Glazer assumes no liability for property damage, personal injury, code violations or hardware failure.