If you own or manage a 1920s two-flat with single-pipe steam, you have probably heard that a smart thermostat will “optimize” your heating. It will not. On a steam system, the thermostat is one of only two things that can start and stop the boiler—the other is the pressuretrol—but it is not the device that decides whether steam reaches the radiators. That decision belongs to the air vents, the piping, and the pressure settings. Dan Holohan’s explanation of steam short-cycling makes the mechanism plain: a thermostat or a pressuretrol can stop the burner, but if air cannot leave the system, steam cannot enter the radiators, and the boiler cycles without heating the building.
The useful role for a smart thermostat on single-pipe steam is as a sensor and a timestamp recorder. It can tell you when the boiler was called, how long the call lasted, and what the room temperature did. That log, kept over a heating season, is worth more than any “smart” schedule you can program into it. This article lays out a logging protocol you can run in a two-flat before you change a single setting, and explains how to read the results without fooling yourself.
Why single-pipe steam is a venting system, not a thermostat system
In a single-pipe steam system, the boiler makes steam, the steam pushes air out of the pipes and radiators through vents, and the steam condenses and returns through the same pipe. The Pacific Northwest National Laboratory Building America Solution Center describes venting as critical: “only with properly sized and operating air vents on headers, risers and radiators will steam reach all radiators at approximately the same time, which is a hallmark of a well-tuned system.”
When vents are clogged, painted over, or replaced with pipe plugs, the air has nowhere to go. The steam compresses it, pressure rises, the pressuretrol cuts the burner, the steam condenses, pressure drops, and the burner restarts—still pushing against trapped air. That is short-cycling. Holohan notes that raising the pressuretrol setting to force steam into air-filled pipes “makes the burner run longer, which wastes fuel” and can mask the symptom without fixing the cause.
A smart thermostat cannot see any of this. It sees room temperature and it sees its own call for heat. If you install one and immediately start adjusting schedules and setpoints, you will change the system’s behavior before you have measured it. The result is a log with no baseline and a building with no diagnosis.
What to log before you touch any setting
Pick a fixed sensor location—not a spot above a radiator, not a spot in direct sun, not a spot near a drafty window. The thermostat’s own temperature sensor is fine if the thermostat is mounted in a representative interior location. If it is mounted on an exterior wall or near a radiator, note that and consider a separate room sensor if your model supports one. The point is consistency: the same location, the same mounting height, the same nearby obstructions, for the entire logging period.
Log these fields at a consistent cadence. Daily is enough for most of them; the thermostat’s own data export may give you finer resolution.
- Call-for-heat timestamps. When did the thermostat call for heat, and when did the call end? If your thermostat exports runtime data, use it. If not, a daily note of “heat on at 6:10 a.m., off at 6:48 a.m.” is still useful.
- Burner on/off cycles where observable. If you can hear the boiler or see a flame, note the approximate cycle count per day. Do not guess; if you cannot observe it, leave the field blank rather than inventing a number.
- Room temperature at the fixed sensor location. Record the morning low and the evening reading, or export the full trend if your thermostat provides it.
- Outdoor temperature. A nearby weather station’s daily high and low is enough. You need this to compare weeks without confusing weather with control changes.
- Radiator warm-up order. Once a week, on a cold morning, walk the flat and note which radiators get hot first, which get hot last, and which stay cold. This is the field observation that tells you whether the problem is venting, piping, or control.
- Any changes you make. If you adjust a setpoint, replace a vent, or call a contractor, write it down with the date. A log without a change record is just a diary.
Run this baseline for at least two weeks of normal weather before you change anything. If the weather is mild, wait. A baseline taken during a warm spell tells you little about how the system behaves when it is working hard.
Reading short cycles correctly
A short cycle is not one thing. At least three different signatures can look similar in a thermostat log, and they call for different responses.
Thermostat satisfaction. The room reaches the setpoint, the thermostat ends the call, and the boiler stops. This is normal behavior, though on steam it can be a sign that the thermostat is set too low for the system’s ability to deliver heat evenly. If the room temperature overshoots the setpoint and then the boiler restarts quickly, the thermostat may be cycling on its own differential rather than on the building’s actual heat loss.
Pressuretrol cut-out. The thermostat is still calling for heat, but the pressuretrol stops the burner because system pressure has risen. This is the signature Holohan describes: trapped air, rising pressure, burner cut, pressure drop, burner restart. In a thermostat log, you see a call for heat that ends before the room reaches setpoint, followed by a restart while the room is still below setpoint. If you can observe the boiler, you may hear it cycle while the thermostat still shows a call.
Air-bound radiators. The boiler runs, the thermostat calls, but some radiators never get hot. The room temperature may rise slowly or not at all in the affected rooms. The thermostat log alone will not distinguish this from a pressuretrol cut-out; you need the radiator warm-up notes to tell them apart.
This is why the log should be read alongside the radiator walk, not instead of it. A cycle count by itself is ambiguous. A cycle count plus “the front radiator never got hot” points directly at venting or piping.
A pre-change checklist for the two-flat
Before you change any thermostat setting, have a steam-qualified contractor inspect the system and document what they find. The Partnership for Advanced Residential Retrofit study of Chicago steam-heated multifamily buildings lists the components that matter: main line air vents, near-boiler piping, boiler controls, and radiator vents. The study also notes that steam-heated buildings often suffer uneven heating because of poor control of steam entering each radiator, leading some tenants to open windows in winter while others use supplemental heat.
Ask the contractor to record, in writing:
- The condition and size of main vents and radiator vents, including any that are painted over, plugged, or missing.
- The pressuretrol cut-in and differential settings, and the observed cut-out pressure.
- The near-boiler piping configuration and whether it matches the boiler manufacturer’s specifications.
- Any signs of water hammer, surging, or low water level.
- The boiler’s rated capacity and the building’s approximate connected load, if they can determine it.
This inspection is the baseline for the maintenance log you will keep after any change. Without it, you will not know whether a later improvement came from the thermostat, a vent replacement, or a pressuretrol adjustment.
A hypothetical logging worksheet
The numbers below are illustrative only. They are not readings from a real building, and they are not targets. They show the shape of a useful log, not the values you should expect.
| Date |
Outdoor high/low (°F) |
Morning room temp (°F) |
Evening room temp (°F) |
Call-for-heat start/end |
Observed burner cycles |
Radiator notes |
Changes made |
| Jan 6 |
28 / 14 |
66 |
69 |
5:50 a.m. – 6:40 a.m. |
4 |
Front room hot first; rear bedroom cold |
None |
| Jan 7 |
30 / 18 |
65 |
70 |
5:45 a.m. – 6:35 a.m. |
5 |
Rear bedroom still cold |
None |
| Jan 8 |
25 / 10 |
64 |
68 |
5:40 a.m. – 6:50 a.m. |
6 |
Rear bedroom cold; front room overheated |
None |
After two weeks of this, you have a baseline. You can see whether the rear bedroom is consistently cold, whether the front room overshoots, and whether the cycle count rises on colder days. You still do not know why. That is what the contractor inspection and the radiator walk are for.
Making one change at a time
Once you have a baseline and an inspection, make one change at a time and log for at least a week after each change. The most common first change on a steam system is not a thermostat setting; it is a vent replacement or a pressuretrol adjustment. If you replace a clogged radiator vent, log the radiator warm-up order before and after. If the contractor adjusts the pressuretrol, record the old and new settings and watch whether the short-cycle signature changes.
The PNNL guide makes a related point about thermostatic radiator valves: after installation, boiler controls should be commissioned so the boiler is not short-cycling because of newly reduced demand. The same logic applies to any change that alters how much steam reaches the radiators. If you reduce demand in one part of the building, the boiler’s cycling behavior changes, and you need to re-check the pressuretrol and venting rather than assume the system is now “tuned.”
Do not change the thermostat schedule and the pressuretrol in the same week. If you do, you will not know which change produced which effect. The Chicago study reported that ten test buildings receiving venting upgrades and new control systems showed 10.2% savings on natural gas heating loads with a simple payback of 5.1 years, but that result came from a package of measures in multifamily buildings, not from a thermostat alone, and it does not transfer directly to a two-flat in a different climate.
Keeping a long-horizon maintenance log
The log you start before the first change is the log the next owner and the next contractor will inherit. Keep it in the mechanical room or with the boiler paperwork, and record:
- Every vent replacement, with the date, the radiator or main location, and the vent model or size.
- Every pressuretrol adjustment, with the old and new cut-in and differential settings.
- Every thermostat change, including schedule changes and setpoint changes.
- Every contractor visit, with the findings and the work performed.
- Any observed change in cycle behavior after each entry.
This is the part that green-tech marketing usually skips. A smart thermostat that logs data for one season and then gets replaced or reset leaves no history. A written maintenance log survives equipment changes, tenant turnover, and contractor turnover. It is also the only way to see whether a pressuretrol adjustment that “reduced short-cycling” actually masked a venting problem, as Holohan warns.
What this method cannot establish
A thermostat log and a maintenance log are useful, but they are not a savings measurement. They cannot tell you whether the building used less fuel, because they do not measure fuel. They cannot tell you whether the building meets a comfort standard, because ASHRAE Standard 55 addresses thermal environmental conditions for human occupancy and notes that personal comfort levels vary from one occupant to another; a single sensor in one flat is not a comfort survey. They cannot tell you whether the system is code-compliant, because that requires a professional assessment against the applicable code.
If you want to claim savings, you need utility data or submeter data for the building, weather-normalized, with a clear before-and-after period and a record of every change made in between. If you want to claim comfort improvement, you need occupant observations or a survey, not a thermostat trend line. If you want to claim code compliance, you need a licensed professional’s evaluation.
The U.S. Energy Information Administration’s Residential Energy Consumption Survey provides national and regional context for how homes use energy, but it does not substitute for building-level measurement. Use it to understand the scale of residential heating use, not to estimate your own savings.
FAQ
Will a smart thermostat fix short-cycling on my steam boiler?
No. A thermostat can start and stop the boiler, but short-cycling on single-pipe steam is usually caused by air that cannot leave the system, which raises pressure and trips the pressuretrol. The fix is venting and pressuretrol tuning, not a new thermostat. A smart thermostat is useful as a logger, not as a cure.
Can I use my smart thermostat’s runtime data as a cycle count?
Only if your model exports call-for-heat runtime and you understand what it records. Many thermostats record when they call for heat, not when the burner actually fires. On a steam system, the pressuretrol can stop the burner while the thermostat is still calling, so thermostat runtime is not the same as burner runtime. Check your model’s documentation before treating its data as a cycle count.
Should I raise the pressuretrol setting to stop short-cycling?
No. Raising the pressuretrol setting can make the burner run longer and mask the short-cycling, but it wastes fuel and does not fix the trapped air. The better response is to find and repair the venting problem, then verify the pressuretrol settings with a steam-qualified contractor.
How long should I log before making a change?
At least two weeks of normal weather, and ideally a full month that includes both mild and cold days. If you change settings before you have a baseline, you will not be able to tell whether a later improvement came from the change or from the weather.
Can I do this in a rental without the owner’s permission?
Logging room temperature and noting radiator behavior is generally low-impact, but installing a thermostat or adjusting boiler controls is not. If you are a renter, talk to the owner or manager before changing any setting or replacing any component. The maintenance log is most useful when the owner and the tenant both have access to it.