When the OpenADR Alliance hosted a webinar on AHRI 1380 this March, over 200 people from HVAC manufacturers, utilities, testing labs, and regulators across 20+ countries registered to attend. The session ran 14 minutes over its scheduled hour. Attendees submitted 36 questions. That level of engagement signals something important: the HVAC industry is paying close attention to demand response compliance, and many OEMs are still working out what the standard actually requires of them.

The panel brought together Codibly’s Spencer Borison, Rolf Bienert of the OpenADR Alliance, Eric Olson from the Northwest Energy Efficiency Alliance (NEEA), and Jim Zuber from QualityLogic. What follows is a practical breakdown of what was covered, what the audience asked, and what HVAC OEMs should be doing right now.

What AHRI 1380 Actually Requires

AHRI Standard 1380, published in 2019, defines what it means for a residential or small commercial HVAC system to be demand-response-ready. It applies to variable capacity systems (both two-stage and variable-speed) with capacities of 65,000 Btu/hr or less.

At its core, the standard requires two things: a communication protocol that connects the HVAC unit to utility demand response signals, and a set of operational behaviors that govern how the system responds.

The Protocol Stack: OpenADR, CTA-2045-B, and HCA

The current version of the standard recognizes two DR protocol certification pathways: OpenADR 2.0b and CTA-2045. OEMs must implement at least one. OpenADR handles the communication between the utility (or aggregator) and the device, while CTA-2045 provides a standardized physical communication port that connects the appliance to external modules.

Beyond the protocol itself, the standard specifies operational requirements: general curtailment (limiting to 70% of rated load power), critical curtailment and off mode for more significant load reductions, customer-configurable temperature offset constraints, and a manual override so homeowners can opt out of any event.

What Changed in the Proposed 202X Revision

The AHRI 1380 working group is actively drafting the next version of the standard. Eric Olson, who sits on the committee, shared that the revision proposes three significant protocol additions: updating CTA-2045-A to CTA-2045-B, adding OpenADR 3.1 as an additional non-proprietary protocol option, and incorporating the Home Connectivity Alliance (HCA) standard. OpenADR 2.0b remains in the standard.

The committee is also tackling dual fuel heat pump optimization, reducing post-event snapback, improving customer comfort during events, and clarifying lab testing requirements. The drafting is running slightly behind schedule as more topics surface, but it signals that the standard is evolving to reflect both technology maturity and real-world deployment experience.

For OEMs starting implementation today, this means designing for extensibility. A system that only implements the bare minimum of the 2019 spec may need rework when the revision drops.

The Compliance Timeline Every OEM Should Have on the Wall

Year Milestone What It Means for OEMs
2019 Standard published: AHRI 1380 (I-P) released Defines DR-ready requirements for variable capacity residential and small commercial HVAC. Protocols: OpenADR 2.0b or CTA-2045.
2026 Self-compliance + CEE Tier 1: Manufacturers can self-declare conformance Products listed in AHRI directory as CEE Tier 1. Utility incentive programs begin referencing these tiers. Lower barrier to entry.
2027 Lab certification required: Third-party testing by UL, CSA, or Intertek Higher compliance bar. Lab procedures and reporting requirements still being finalized by the working group.
202X Revised standard (drafting): AHRI 1380-202X Adds CTA-2045-B, OpenADR 3.1, and HCA. Addresses snapback, dual fuel optimization, and lab testing clarity. Design for extensibility now.

2026: Self-Compliance and CEE Tier 1

As of January 2026, HVAC manufacturers can self-comply with AHRI 1380. This means the manufacturer notifies AHRI that their products meet the standard, and AHRI lists them in their product directory as meeting CEE (Consortium for Energy Efficiency) Tier 1 for connected variable-speed equipment. Products are classified by Path A (northern climate) or Path B (southern climate), or both if they qualify.

Self-compliance does not mean no testing. It means OEMs take responsibility for their due diligence in verifying conformance. Purpose-built test tools for the standard’s specific signaling scenarios are now available in the market, making this process more rigorous and defensible than ad hoc testing against a generic OpenADR test harness.

2027: Lab Certification Raises the Bar

Starting in 2027, AHRI will require certification through an approved lab such as UL, CSA, or Intertek. This is a meaningful step up from self-compliance: third-party labs will run standardized test procedures to verify conformance. The details of how lab testing will work are still being finalized by the working group.

The practical takeaway is that the 2026 window is a lower-friction entry point. OEMs who self-comply now establish their products in the CEE Tier 1 directory, can begin participating in utility incentive programs, and position themselves ahead of the 2027 certification requirement.

How the Industry Is Testing for Compliance

Testing was one of the most discussed topics during the webinar, and for good reason. The distinction between OpenADR protocol certification and AHRI 1380 compliance testing is one that many OEMs initially miss.

The standard OpenADR 2.0 test harness is designed to certify protocol conformance. It spins up a test environment, runs a test case, and tears it down. AHRI 1380 testing is a different exercise: it requires maintaining a live demand response signaling session with the device under test while lab technicians physically measure load reduction, temperature behavior, and system response across multiple curtailment scenarios. The 1380 standard includes signaling scenarios that are not covered by the OpenADR certification test suite alone.

Purpose-built AHRI 1380 test tools are now entering the market to fill this gap. These tools simulate the required DR signaling from a VTN to the HVAC system (acting as a VEN), covering the specific curtailment modes and operational behaviors the standard defines. They serve two audiences: OEMs performing self-compliance testing in 2026, and labs preparing to offer due diligence assessments on behalf of manufacturers.

As the 202X revision adds new protocol options, the testing landscape will expand further. OEMs should plan for the possibility that certification testing in 2027 will cover a broader set of signaling scenarios than what is required for self-compliance today.

Three Paths to a DR-Ready Product

Every HVAC OEM evaluating AHRI 1380 faces the same fundamental decision: how to get from “no DR capability” to a certified, market-ready product. There are three approaches, each with distinct tradeoffs.

Approach Timeline Best For Key Tradeoff
Build from scratch: Implement OpenADR or CTA-2045 internally using the protocol specification 4–8 months OEMs with deep protocol engineering teams and long planning horizons Full control, but high certification risk and extended time to market
Pre-built SDK/components: Integrate a third-party communication module or SDK 2–4 months OEMs who want protocol coverage without building protocol expertise Faster than scratch, but may introduce vendor dependency on the SDK provider
Pre-certified accelerator: Deploy a certification-ready codebase (e.g., Codibly’s OpenADR accelerator) 4–6 weeks OEMs under time pressure or entering DR for the first time Fastest path to certification. Full source code ownership. Requires integration with OEM’s control logic.

Building from scratch gives full control but requires deep protocol expertise, extended timelines, and carries certification risk. Pre-built components and SDKs provide the protocol layer out of the box, reducing the integration scope to connecting the communication module to the HVAC system’s control logic. And a pre-certified OpenADR accelerator approach delivers the fastest path to certification, using a codebase that has already passed certification testing and can be customized to the OEM’s specific product architecture.

In one recent engagement, a manufacturer used Codibly’s OpenADR accelerator to achieve certification in 6 weeks, with a 40% reduction in development time compared to a from-scratch implementation.

The right choice depends on internal engineering capacity, timeline pressure, and how many protocol variants the OEM plans to support. With the 202X revision adding CTA-2045-B, OpenADR 3.1, and HCA, designing a decoupled protocol abstraction layer from the start avoids rework later.

There is an important step that comes after meeting the protocol requirements, and it is one that OEMs frequently underestimate. AHRI 1380 compliance alone does not unlock demand response program participation. OEMs still need to integrate with the aggregator platforms that facilitate utility DR programs: EnergyHub, Uplight, Leap, Virtual Peaker, and others. That strategic and contracting work is a separate track that should run in parallel with the technical implementation.

The Regulatory Map: Which States Are Moving Fastest

AHRI 1380 is not a federal mandate. Adoption is driven by state-level regulatory activity and utility program design. Here is where the strongest movement is happening:

  • California — The California Energy Commission (CEC) is advancing flexible demand appliance standards (FDAS) rulemaking that will likely include HVAC systems. No firm requirement yet, but proceedings are active and the CEC sent three representatives to the webinar.
  • Pacific Northwest — NEEA is one of the most active players. Their work on advanced demand response for heat pumps directly references AHRI 1380, and Eric Olson’s involvement in the working group reflects the region’s commitment to moving this forward.
  • Northeast (New York, Massachusetts) — Both states are incorporating DR-ready equipment into efficiency program specifications. The CEE tier structure is the mechanism that connects state utility programs to the AHRI 1380 standard.
  • Mountain West (Colorado, Minnesota) — Earlier-stage rulemaking and conversations, but the direction is clear.

The practical implication: if you sell HVAC equipment in any of these markets, compliance is becoming a competitive differentiator. Utility incentive programs reference CEE tiers, and products that meet Tier 1 can offer those incentives to customers. Products that do not are at a disadvantage when competing against those that do.

For a broader view of how HVAC demand response fits into the energy flexibility landscape, including the European market trajectory, Codibly has covered this separately.