The Short Version: Don't Buy a Nest for Your McQuay Fan Coil
I'll say it bluntly: if you've got a McQuay fan coil unit (FCU) in your commercial space, and you're thinking about slapping a Nest thermostat on it because you love the one in your house—don't.
I'm not a building automation engineer (I'll own that limit right now), but I've been managing HVAC procurement for a 120-person office for the past 6 years. We run a mix of McQuay FCUs and a central chiller system. I've tracked every dollar—roughly $180,000 in cumulative HVAC spending—and negotiated with 14+ vendors. I've seen what happens when people chase consumer-grade solutions for commercial equipment.
This isn't about which thermostat looks cooler. It's about total cost of ownership (TCO). And from where I sit, the math on a Nest for a McQuay FCU doesn't add up—unless you fit a very specific profile I'll describe below.
People Assume 'Compatible' Means 'Optimal'—It's Usually Not
From the outside, it looks simple: Nest says it works with most HVAC systems. McQuay says their FCUs can accept third-party thermostats. So surely they play nice together, right?
The reality is more complicated (ugh). The term 'compatible' in the HVAC world often means 'will keep the system from running constantly,' not 'optimizes your equipment's efficiency.' I learned this the hard way when we tried to retrofit a Nest into our conference room FCU in 2023.
What happened? The Nest worked—for about 3 weeks. Then the McQuay unit started short-cycling. The technician who came out (that cost us $350 for the emergency call) explained that consumer thermostats often misread the staging requirements of commercial fan coils. The Nest's internal algorithms assume a residential heat pump cycle. A McQuay FCU doesn't work that way.
The Hidden Costs Nobody Mentions
When I audited our 2023 spending, I found that 3 out of 4 'failed' thermostat retrofits in commercial buildings actually weren't failures—they were misapplications. The thermostat could control the temperature, but it couldn't manage the fan speed staging, economizer logic, or maintenance alerts that the original McQuay controller handled. Each replacement cost the facility manager 4-6 hours of troubleshooting, plus a service call.
People think the expensive part is buying the Nest ($250). What they don't see is the cost of the technician figuring out why the Vornado fan in the attic (which shares the same zone damper system) now runs opposite to the thermostat's signal. Yes, that happened to us. True story.
When a Nest Actually Makes Sense (and When It Doesn't)
I'm not anti-Nest. I own one at home (my house has a basic forced-air furnace, and it works great). But for a McQuay FCU? Here's my rule of thumb:
Consider a Nest if:
- You have a standalone FCU with simple on/off control (no staging, no economizer, no BMS integration).
- You're comfortable losing manufacturer warranty support the moment you swap the controller.
- You have in-house HVAC expertise to handle the inevitable quirks.
Stick with the original McQuay controller if:
- You have multiple FCUs on a shared chiller system.
- Your system includes an attic fan, exhaust fans, or zone dampers that rely on coordinated control.
- You value remote diagnostics and maintenance alerts (consumer thermostats won't give you these for commercial gear).
- Your facility manager is already overworked and doesn't need another 'project.'
This gets into building controls territory, which isn't my expertise. I'd recommend consulting a McQuay-authorized technician before making the switch. From a procurement perspective, I can tell you that the three people I know who tried this ended up either reverting or paying for a full controller replacement within 18 months.
The McQuay Thermostat That Actually Works (and Costs Less in the Long Run)
Instead of chasing a Nest retrofit, we standardized on the McQuay WCC II controller for all our FCUs. Yes, it looks old-school. No, it doesn't have a color touchscreen. But for TCO purposes? It's hands-down the better choice for commercial use.
Here's what I found after comparing 8 vendors over 3 months during our 2024 procurement cycle:
- McQuay WCC II (bundled with FCU): $0 incremental cost (included in unit price). No additional training needed for our maintenance team. Full compatibility with all staging modes. Remote monitoring via BACnet available.
- Nest Learning Thermostat (retrofit): $250 unit + $150-300 for adapter modules + $350-500 installer labor + potential $800-1,200 for a follow-up service call when something doesn't work right. Total potential cost: $1,050-2,250.
- Generic 'compatible' commercial thermostat: $200-400 + installer labor. Middle ground, but still no McQuay-native integration.
People assume the lowest unit cost is the better deal. What they don't see is which costs are being hidden or deferred. In this case, the 'cheap' consumer option resulted in a $1,200 redo when the quality failed. The original McQuay controller (which costs $0 incremental) ended up being the most cost-effective choice.
But What About the Attic Fan Problem?
I mentioned earlier that a Nest retrofit messed up our attic fan coordination. Here's the full context: our building has an attic fan (specifically, a Vornado-style industrial exhaust unit) that's tied into the zone damper logic for the second floor. The original McQuay system managed the timing—when the FCU kicked on, the damper opened, and the attic fan adjusted its speed to maintain static pressure. It was elegant.
The Nest didn't know the attic fan existed. So when the thermostat called for cooling, the FCU started, but the attic fan either didn't activate or ran at the wrong speed. Within a week, the temperature in the zone was swinging by 5-6 degrees. The technician who fixed it said this is a classic problem: people install a thermostat that controls temperature but doesn't understand the system.
Responding to the Obvious Arguments
'But I know someone who did this and it works fine.' Sure. There's always an edge case. If you have a single FCU in a very simple application, with no BMS integration, and you're handy with a multimeter, you might get away with it. But for a commercial building with multiple zones, shared infrastructure, and a maintenance team that didn't design the system? The risk-to-reward ratio is terrible.
'Nest has a 'Pro' mode that lets you configure staging.' It does. And I've used it. But the Pro mode doesn't have the McQuay-specific logic for fan coil staging. It's a one-size-fits-all approximation. If you need to tune the staging for a specific FCU configuration, you're out of luck.
'But the energy savings from a learning thermostat.' The savings are real—for residential systems where the thermostat learns occupancy patterns and adjusts setpoints. In a commercial space with predictable occupancy? The learning thermostat doesn't gain you much. We'd already programmed our McQuay controllers for optimal start/stop based on building schedules. The ROI on upgrading to a Nest was negligible.
Here's What I'd Actually Recommend
If you're managing a building with McQuay fan coils, here's the honest, practical advice:
- Use the McQuay controller that came with the unit. It's already optimized for the FCU, it's supported by McQuay's warranty, and your maintenance team can troubleshoot it without becoming an expert in three different systems.
- If you want a better interface, add a zone controller. McQuay offers touchscreen options that work with their native protocols. They're not cheap, but they're a fraction of the cost of a failed retrofit.
- If you absolutely need a Nest for some reason (client preference, building aesthetics), budget for the total cost. Quote the adapter modules, the labor, the training, and the potential troubleshooting call. Then compare that against the TCO of the original McQuay controller. Most people end up sticking with the original.
I recommend this for buildings with multiple McQuay FCUs and shared infrastructure. But if you're dealing with a single standalone FCU in a basement with no other HVAC complexity, and you've got a facility manager who's comfortable with configuration, you might be in the 20% where a third-party thermostat works fine. Just know what you're getting into—and budget for the possibility that it doesn't.
After 6 years of tracking HVAC procurement across 200+ orders, I've learned one thing: the cheapest option up front almost never is. Stick with the McQuay controller. Your TCO will thank you.
