AC Diagnostic Monitoring & Predictive Maintenance

Over the past decade, I’ve had my air conditioners fail multiple times due to refrigerant leaks, bad thermostatic expansion valves (TXVs), failed condenser units, bad start capacitors, and other issues. These repairs are often expensive, and the failures always seem to happen during the hottest days of summer. Therefore, I’d like to catch problems as early as possible.

This past June, I had my third case of a refrigerant leak from an AC coil inside an air handler. While troubleshooting the issue, I noticed that the outdoor unit was drawing about half its normal current: approximately 4 A instead of 8 A on each leg of the 240 V circuit for my upstairs unit. The HVAC company confirmed that the compressor was under very little load because virtually all the refrigerant had leaked out, which explained the significantly lower power draw.

I’m working on an ESPHome setup to monitor temperatures and pressures before and after the air handler, cycle length and frequency, and other parameters to help determine the overall health of each system. However, I wanted to implement something immediately using data I already collect, so I put together the cards below. Both units are currently working correctly:


(Note: The representation of amperage shown above is incorrect. See below.)

For the 240 V outdoor unit, summing the amperage measured on both legs is incorrect because the same current flows through both legs. For example, 10 A on L1 and 10 A on L2 is still a 10 A, 240 V load, not a 20 A load.

Summing the power , however, is correct. The complication is that I’m trying to represent the combined load of a 240 V outdoor unit and a separate 120 V indoor air handler.

Using the numbers above:

Outdoor unit:
10 A × 240 V = 2,400 W

Air handler:
5.4 A × 120 V = 648 W

Total:
2,400 W + 648 W = 3,048 W

Looking at the outdoor unit as the sum of the power measured on its two legs gives essentially the same result:

(10 A + 9.9 A) × 120 V + (5.4 A × 120 V) = 3,036 W

The small difference is due to L1 and L2 not measuring exactly the same current, along with timing differences between sensor samples and screen updates.

However, for amperage I obviously can’t just add the 240 V outdoor unit’s current to the 120 V air handler’s current and call that the total, since the loads operate at different voltages.

As a side note, the Emporia Vue 3 energy meter in my outdoor electrical panel provides V, W, A, and other data for the outdoor units. The Jasco switches powering the indoor air handlers only provide W, so I use a template to estimate A using the corresponding L1 or L2 V reported by the Vue 3. The numbers may not always line up perfectly due to timing differences between sensor samples and screen updates, but they are typically close.

Q1: Is there a better and electrically correct way to represent the total power draw of a combined HVAC system consisting of both a 240 V outdoor unit and a 120 V air handler? Is the best solution simply to show the A of each load separately and use summed W as the overall system load?

Q2: What is the best way to characterize normal power draw and flag abnormal deviations in HA?

Q3 especially for the HVAC experts: How much should I expect power draw to vary during normal operation? These are basic fixed-speed, on/off compressors with no inverter or variable-speed control. I realize operating conditions affect compressor load, but should I expect power consumption to remain within a relatively narrow range under similar conditions, or can it vary substantially even when the system is working correctly?

Looking for examples of what others have done and/or suggestions! Thanks!

It’s fine to sum power, as long as it’s of the same kind, meaning it’s RMS power (as opposed to instantaneous AC power or DC power, and I wouldn’t trust summing instantaneous AC power in HA since the 1 sec clock of the HA state engine is nowhere fast enough for that at 50/60Hz). I’d keep A of each apart.

What I would personally do is to put an EMA filter on each to remove some noise and timing effects, and sum those.

Why do you want to track the combined power?

@parautenbach - Apart from the recent equipment failure, I also recently changed electric service contract in order to reduce my abnormally high electric bills. Usage has been around 25MW/yr the past few years.

I am reworking many of my dashboards to give a better representation of the power usage, and for the larger equipment - where it makes sense - I also want to catch technical issues ideally before they reach a critical state.

For usage, I have added the power used next to most switches that support it (except lighting). For example:

HVAC systems, oven and dryer are the largest loads in the house. I am revising my electrical dashboard to eliminate the errors (I was summing A for L1 and L2 on 240V appliances), and to make it more useful in detecting potential issues (such as the one I described in my previous post).


Work in progress…

To answer your question, to track HVAC power usage, I need to sum the power used by the exterior condenser unit, to the power used by the interior air handler.

Other things I am considering are looking at combined power usage by device type (ie Lighting).

You’ve discovered Ohms law. Good! Watts is a measurement of power, of workload, which is probably what you need to monitor.

Your power consumption and temperature figures vary, by the minute, hour, day and season.

Instantaneous readings for your compressor temperature, current draw, and refrigerant temperature are collected, but the trends can be analysed over a longer period to allow for days of the week and seasons, and compare them to what happened over the same period last time to spot out of band errors. This is called hysteresis and your friendly experienced HVAC technician should be able to advise on expected values and ‘normal’ ranges to test for. You may wish to derive virtual values sensors based on a rolling averaged value to compare instantaneous values against. You can have ones for days, months, seasons, etc, and test for each and squawk if anything is drastically wrong.

Plotting your measurements over a day, a week, a month, a year should visually show you what I mean. Automating that averaging to spot deviations should be a multi stage operation, to allow for short term as well as long-term changes to be identified. You may want to have a separate dashboard for these, as data graphing with long term bar or line charts can be resource intensive, and may not be necessary to display in real time.

Bonus: slowly trending upticks indicates need for maintenance, often as simple as stopping the fans, both inside and outside long enough to brush the dust build-up off the fans and fins (carefully), and when the readings go crazy like for refrigerant leaks, a proactive service with regas, oil and filter change. You also have real figures for any climate change discussions…

GUI Comments: Choosing a gauge graph for your switches is useful for discouraging unwise usage, but you could consider a dashboard which has an overall glance at yout entire ecosystem, showing red only for abnormal situations, so an ‘all green’ display only merits a simple glance, but if there are any other colors, you can drill down and investigate. You know what is normal for your house, you have the figures to analyse them. Now you can embolden yourself to interpret them with automation to help.

@IOT7712 - I am indeed going to look at past data but due to changes in sensors and db mishaps, I may not have reliable past data to work with. Anyhow, the running amps of the condenser unit (compressor) seem to be fairly stable around 8 (3.5T unit) to 10A (4T unit) @ 240V so I can flag on that. Maybe, as you suggested, I can show compressor amps in the green zone when in the correct range and notify when not.

When I look at amps, I am generally thinking in terms of branch capacity. All my normal 120V branches have 20A breakers but the 240V condenser units are on 25 and 40A breakers.

I believe the CTs are just reading RMS Amps, but I can spot check when needed with an in-rush clamp amp meter to detect start-up issues… but that is outside my automation scope unless thete is a practical way to do that as well.

One of my bar charts shows amps by breaker limit but thinking about it more, I don’t think that’s very helpful as the HVAC loads on those breaker don’t change (better use those bar charts for branches with outlets) and I can’t measure in-rush current with a VUE3.

Some of the tests you mentioned appear to be ones done by techs on the unit outdoors so not too practical for me. But one indicator of a properly working unit is the temperature delta before and after the coil. The air temperature delta in the air handler, before and after, should be between 9 and 12C when cooling is on and stabilized.