It started with a phone call on a gloomy Thursday in March. An older homeowner in Minnesota said his Honeywell thermostat was flashing “Heat On” but the baseboard heaters stayed cold. He’d already paid two contractors. The second one told him to replace the thermostat entirely. That didn’t help either.
That call landed on my desk for one simple reason: I’m the person who signs off on every product before it hits the market. For four years, I’ve been reviewing roughly 200 HVAC controls annually. In 2024 alone, I rejected 14 different batches—about 5% of what came through—because of spec mismatches or documentation that didn’t align with real-world behavior. This one felt different, though. The thermostat had passed every test on our line.
The Initial Investigation
I started by pulling the production records for that exact unit. Firmware version? Checked. Calibration? Within tolerance. Thermal sensor? Accurate. Everything looked exactly as it should. That left two possibilities: either the product failed in the field due to something external, or the customer had received a damaged unit. The photos arrived later that afternoon.
Honestly, I expected to see a loose ground wire or a mislabeled terminal. Instead, I saw something I hadn’t anticipated. A Milwaukee blower—the kind of portable air mover you might use as an outdoor fan for venting a workshop—was wired into the same control box as the Honeywell hot water heater control. The contractor had used that blower to keep a small utility room ventilated. It was sharing the same transformer as the thermostat.
That’s when I felt the first real shift in my thinking. This wasn’t a case of a faulty product. It was a case of mixing systems that were never designed to work together.
How a Radiator Works—and Why This Matters
Let me explain what I mean. A radiator, whether it uses steam or hot water, doesn’t need electrical signals to generate heat. It just needs a valve to open and fluid to flow. The Honeywell thermostat on the wall is effectively a switch that tells the valve to open when the room temperature drops below the setpoint. It’s a simple, robust loop.
The Milwaukee blower, on the other hand, is an inductive load. It draws a surge of current every time it starts. That surge creates magnetic interference that can confuse the thermostat’s safety logic. The thermostat interprets the interference as a short circuit or fault condition. So what does it do? It blinks “Heat On” and refuses to energize the heating system. The heat never comes on.
This is a classic mismatch. The thermostat was designed to control a slow, non-electrical device like a radiator valve. It was never meant to handle an electric motor running in the same circuit. And here’s the kicker: the manual did include a warning about inductive loads. But it was buried at the bottom of page 17, in a paragraph that looked like legal boilerplate.
I looked at that manual myself that day. I would have missed the warning too. If the people who built the product can’t find the critical piece of information, how can we expect a busy contractor to find it? That was a humbling realization.
The Real Problem: Missing Transparency
So this wasn’t user error in the traditional sense. It was a failure of information. We had the knowledge, but we presented it in a way that was almost designed to be ignored. I’ve spent years reviewing quality documents, and I’d never once tested a manual from the perspective of a first-time installer.
Once we moved the blower to a separate circuit, the blinking stopped. The heat came on within minutes. The customer asked if he could keep the replacement thermostat we’d sent. I told him to keep it. It works fine. The original unit wasn’t defective.
That experience changed more than my perspective on manuals. It changed how I think about transparency in every area of our business. Price. Specs. Compatibility. All of it.
What Transparency in Pricing Actually Looks Like
I remember a supplier once gave me a quote that was $800 cheaper than a competitor’s. I asked, “What’s not included?” They said, “Nothing.” But the cable kit was $200. The mounting plate was $150. The programming setup fee was $400. That “cheap” quote ended up costing $300 more than the higher-priced, honest one.
That’s the same pattern I saw in the thermostat case: the cost of missing information is always higher than the cost of providing it upfront. According to the U.S. Department of Energy, a programmable thermostat can save you about $180 per year on heating and cooling bills. But that savings only happens if the thermostat is installed correctly. If the wiring is wrong, you’ll spend more on a service call than you’ll ever save in energy.
When I review a product now, I ask a new question: if a first-time installer followed this guide step by step, would they succeed? If the answer is no, we fix the guide. We redraw the diagrams. We put warnings where people will actually see them—not just in a legal appendix.
I’ve also changed how I talk to customers and vendors about cost. I no longer accept a simple “yes, it includes everything.” I ask for a line-by-line breakdown. If an item isn’t listed, I ask why. It feels awkward at first, but it saves so much pain later.
The Bottom Line
Call it a mid-career correction. I used to think quality was all about specifications and tolerance ranges. Now I think it’s about clarity. If a contractor has to guess how to connect a hot water heater control to a fan, that’s a quality failure. If a homeowner has to call a support line to decode a blinking light, that’s a trust failure.
The real cost of missing transparency isn’t just the hourly bill from a second contractor. It’s the confidence your customer loses in the product, the brand, and the entire industry. And once that trust is gone, no discount can bring it back.
I still think about that angry phone call from a rainy Thursday. It wasn’t about a faulty Honeywell thermostat. It was about all the information we didn’t share until it was too late. These days, I’d rather annoy someone with too much detail than leave them guessing in the dark.
