Learn/Demand Response Programs: What Utilities Ask For

Demand Response Programs: What Utilities Ask For

Β·2 Views

This article may contain affiliate links. If you make a purchase through these links, we may earn a small commission at no extra cost to you. This helps us keep creating free content.

A demand response event on a residential air conditioner comes down to one question at the hardware level: for a set window, that compressor runs less than you told it to, and either a utility-operated switch made that call or your own thermostat did. Which of the two it is decides everything else, because the app, the text alert and the bill credit all sit on top of that one mechanical fact.

Two control models, and they behave very differently

Utilities run demand response through one of two mechanisms. Direct load control (DLC) puts a switch the utility can trigger on a specific circuit, usually the air conditioning compressor, the water heater element, or an EV charger. Price-based programs instead send a signal, an event notification or a rate change, and leave the decision to your thermostat, your energy management system, or you.

The distinction matters because it changes who has final authority over the device during an event. With DLC, the utility's switch takes precedence over your automation. With price-based signals, your system reads an event and decides how to respond, so a poorly configured automation can simply ignore it.

Demand Response Programs: What Utilities Ask For β€” practical guide overview
Demand Response Programs: What Utilities Ask For

OpenADR: the protocol most price-based programs run on

Most modern price-based demand response uses OpenADR (Open Automated Demand Response), an open communication standard published as IEC 62746-10. OpenADR defines a client-server relationship: a Virtual Top Node (VTN), operated by the utility or an aggregator, publishes an event; a Virtual End Node (VEN), running inside your thermostat or energy management system, subscribes to that event and decides how to act on it. Signals move as XML payloads over HTTP or XMPP.

OpenADR 2.0b is the version most residential and commercial DR programs specify. California's Demand Response Auction Mechanism, which requires the state's investor-owned utilities to procure demand response capacity from third-party aggregators, mandates OpenADR 2.0b for every resource enrolled through it. If your thermostat lists OpenADR 2.0b certification, that is what makes it eligible for bring-your-own-thermostat programs in the first place.

What to check before enrolling: Look up whether your thermostat model carries OpenADR 2.0b certification, not just "smart" or "Wi-Fi enabled." A thermostat without it can usually still respond to a basic setpoint nudge sent through the manufacturer's own app integration, but it will not appear in a utility's list of qualifying devices for a formal program.

CTA-2045: the port that turns a water heater into a grid resource

Electric water heaters use a different mechanism. The ANSI/CTA-2045 standard, published by the Consumer Technology Association, defines a modular communication port built into the appliance, conceptually similar to a USB socket, that lets a plug-in module talk to the heating elements without the manufacturer building networking into every unit. A utility-supplied or third-party module plugs into that port and can shed load or shift heating to off-peak hours based on grid conditions.

Demand Response Programs: What Utilities Ask For β€” step-by-step visual example
Demand Response Programs: What Utilities Ask For

This is not a hypothetical standard. Washington State House Bill 1444 requires electric storage water heaters manufactured on or after January 1, 2022 to include a CTA-2045-A compliant port. Oregon adopted a similar requirement effective July 2023. If you bought a new electric water heater in either state after those dates, it likely already has the port, whether or not you have anything plugged into it.

EV chargers: throttling instead of switching

Level 2 EV chargers rarely get cut off entirely during a demand response event. More often, the charger throttles its output, dropping from a higher amperage to a lower one, or delays the start of a session until a signal clears. This runs through the Open Charge Point Protocol (OCPP) on chargers that support remote management, or through the charger manufacturer's own cloud API tied into a utility program. The car keeps charging, just more slowly, which is why EV-specific programs tend to have looser participation rules than compressor cycling.

What you actually give up when you enroll

Enrollment hands the utility, or its program partner, a defined amount of control over a device you own, for a defined set of conditions. What that looks like varies by program, but the shape is consistent:

  • A notice window before an event starts, which can range from same-day text alerts to no advance notice at all on emergency programs
  • A maximum event duration and a cap on how many events can run per season
  • Rules for whether and how you can override an event from your thermostat or app
  • A data-sharing agreement, since the utility or aggregator needs usage data to verify the load reduction actually happened
Demand Response Programs: What Utilities Ask For β€” helpful reference illustration
Demand Response Programs: What Utilities Ask For

Ask about exemptions at this point rather than after enrolling if anyone in the house depends on cooling or on a powered medical device, because events are called on exactly the hot afternoons when the grid is strained, which are also the hours that dependence matters most.

None of these terms are standardized across utilities. A cooperative in one state and an investor-owned utility two counties over can run the same device type through completely different notice windows and override rules.

Where automations built before enrollment tend to break

If you already have a thermostat schedule or an automation tied to occupancy, enrolling in DLC can create a conflict the automation was never designed to handle. A schedule that drops the setpoint at 5pm for arrival will fight a DR event that is actively limiting compressor runtime at the same hour, and the result is usually a warmer house than either system intended on its own, with no error message explaining why.

Check whether your thermostat's automation engine treats a DR event as a temporary override that resumes the normal schedule afterward, or as a schedule change that has to be manually restored. The two behave very differently the first time an event actually fires.

Demand Response Programs: What Utilities Ask For β€” detailed close-up view
Demand Response Programs: What Utilities Ask For
Common mistake: Assuming an opt-out during one event cancels future participation. Most programs treat an override as a single-event exception. The next event still fires unless you formally withdraw through the enrollment portal of whoever signed you up, which is the aggregator rather than the utility in a good share of residential programs.

Demand response is not the same thing as a time-of-use rate

These two get confused constantly because both change how your electricity is priced or controlled around peak hours. A time-of-use rate changes the price you pay for electricity at different times of day, every day, with no direct control over your equipment. Demand response, whether DLC or price-signal based, is event-driven: it activates on specific days when the grid operator or utility calls an event, not on a fixed daily schedule. You can be on a time-of-use rate without ever being enrolled in demand response, and the reverse is also common.

Finding your utility's actual terms

The only source that binds is your own utility's program page, not a national average or a program another state runs. The U.S. Department of Energy's Federal Energy Management Program maintains profiles of demand response programs and time-variable rates by utility, which is a reasonable starting point for locating the right program page, but the program page itself, not the federal summary, is where notice windows, override rules, and eligible devices are actually defined.

QuestionWhere to find the answer
Which devices qualifyUtility's DR program page, usually under "energy efficiency" or "ways to save"
Notice window and override rulesProgram terms and conditions document, not the marketing page
Whether a device is OpenADR or CTA-2045 certifiedManufacturer spec sheet or the certification body's public product list
How to withdraw from a programAccount portal of whoever holds the enrollment, utility or aggregator, under program management, not the app that controls the device

Utilities versus aggregators: who actually holds the contract

Not every demand response program is run directly by the utility that bills you. Many residential programs are operated by a third-party aggregator under contract to the utility or to the regional grid operator, with the aggregator handling enrollment, the app, and event dispatch, while the utility handles metering and billing. This matters because the entity that can answer a question about your specific enrollment is not always the one whose logo is on your electric bill. If a device stops responding to events, checking the aggregator's status page is often faster than calling the utility's general customer service line.

What enrollment gains and costs, side by side

  • Gain: A defined bill credit or rate reduction tied to program participation, structured however your specific program document sets it out
  • Gain: On a price-based program, final authority over the device stays with your own thermostat or energy management system, which is not true of direct load control
  • Cost: Reduced control over one circuit or device during defined event windows, on a schedule you do not set
  • Cost: A data-sharing relationship with the aggregator or utility, since load reduction has to be measurable to be credited
  • Cost: Coordination overhead with any existing automation on that same device, which needs to be checked, not assumed to work

Reading a program before you say yes

Before enrolling any device, confirm three things directly from the utility: which specific device or circuit the program controls, what the maximum event duration and frequency look like for the current season, and whether you can override an active event from your own app without penalty. If a program page cannot answer those three questions clearly, call the utility rather than enrolling from an assumption. This is where the honest answer costs a phone call and the invented one costs nothing until the first event fires and the house is warmer than you expected.

Sources: U.S. Energy Information Administration, "Electricity delivery to consumers" (eia.gov/energyexplained); U.S. Department of Energy, Federal Energy Management Program, "Demand Response and Time-Variable Pricing Programs" (energy.gov/cmei/femp); OpenADR Alliance, OpenADR 2.0 specification documentation; Washington State House Bill 1444 (2019), water heater CTA-2045 requirement effective January 1, 2022.

⚑Disclaimer: This article is for informational purposes only. Smart home installations may involve electrical wiring and must comply with local building codes. Electrical work should only be performed by a licensed electrician.

Published by the SmartHome Automate editorial team. Published November 18, 2026.

Editorial responsibility: see Imprint.

Spotted an error or have something to add? corrections@smarthomeautomate.com

Found this helpful? Share it:
energydemand responseutility programs
πŸ“–

Explore more

All articles on SmartHome Automate β†’

🏠

Smart Home Tips, Delivered

New guides, device reviews, and automation ideas β€” every week in your inbox.

🎁 Free bonus: Smart Home Starter Checklist (PDF)

🧭Part of our topic hub: Planning & Getting Startedβ†’

Comments (0)

Leave a comment

Comments are reviewed before publishing.