This cluster allows a client to manage the power draw of a device. An example of such a client could be an
Energy Management System (EMS) which controls an Energy Smart Appliance (ESA).
In most deployments the EMS will be the client, and the ESA will host the Energy Management Cluster server.
Figure 15. Example of the how an EMS is a client of multiple ESAs Energy Management clusters.
This cluster is intended to be generic in nature and could apply to any electrical load or generator (e.g. a
Battery Electric Storage System - BESS, solar PV inverter, EVSE, HVAC, heat pump, hot water heater, white goods
appliances etc).
It consists of the following areas which shall be supported by all devices implementing this cluster:
• Description of ESA and its capabilities & power limits (sometimes referred to as a nameplate)
• Current state of operation (including user opt-out, safety limitations / alarms) There are some optional
capabilities that some ESAs may be able to offer:
• Ability to control the load or generation
• Forecast data, including when it can be flexible (i.e. modify the power or time period)
• The ability to have their power profile adjusted by an EMS, and to provide an updated Forecast back to the
EMS.
This allows the EMS to manage multiple home loads and where ESAs can be flexible, continuously optimizing the
home energy to minimize cost, reduce CO2 impact, maximize self-consumption of solar PV and provide Demand Side
Response (DSR) Grid services.
It is likely that the ESA may also use the Pricing Cluster to obtain incentive signals such as 'grid carbon
intensity', 'time of use' or 'type of use' tariffs to schedule its operation to run at the cheapest and greenest
times.
Figure 16. Example of the how an HVAC may use multiple clusters
NOTE
Grid Services are market dependent and will use other protocols ([OpenADR] / [IEEE2030.5]) to communicate grid
events to the EMS. These are outside the scope of Matter.
NOTE
Different markets may follow different approaches, but the UK [PAS1878] and [EUCodeOfConduct] give examples of
how ESAs may be mandated to support these features in the future.
NOTE Support of Device Energy Management Cluster is provisional.
Per the Matter specification you cannot use DeviceEnergyManagementCluster without enabling certain
feature combinations. You must use the with factory method to obtain a working cluster.
This cluster allows a client to manage the power draw of a device. An example of such a client could be an Energy Management System (EMS) which controls an Energy Smart Appliance (ESA).
In most deployments the EMS will be the client, and the ESA will host the Energy Management Cluster server.
Figure 15. Example of the how an EMS is a client of multiple ESAs Energy Management clusters.
This cluster is intended to be generic in nature and could apply to any electrical load or generator (e.g. a Battery Electric Storage System - BESS, solar PV inverter, EVSE, HVAC, heat pump, hot water heater, white goods appliances etc).
It consists of the following areas which shall be supported by all devices implementing this cluster:
• Description of ESA and its capabilities & power limits (sometimes referred to as a nameplate)
• Current state of operation (including user opt-out, safety limitations / alarms) There are some optional capabilities that some ESAs may be able to offer:
• Ability to control the load or generation
• Forecast data, including when it can be flexible (i.e. modify the power or time period)
• The ability to have their power profile adjusted by an EMS, and to provide an updated Forecast back to the EMS.
This allows the EMS to manage multiple home loads and where ESAs can be flexible, continuously optimizing the home energy to minimize cost, reduce CO2 impact, maximize self-consumption of solar PV and provide Demand Side Response (DSR) Grid services.
It is likely that the ESA may also use the Pricing Cluster to obtain incentive signals such as 'grid carbon intensity', 'time of use' or 'type of use' tariffs to schedule its operation to run at the cheapest and greenest times.
Figure 16. Example of the how an HVAC may use multiple clusters
NOTE
Grid Services are market dependent and will use other protocols ([OpenADR] / [IEEE2030.5]) to communicate grid events to the EMS. These are outside the scope of Matter.
NOTE
Different markets may follow different approaches, but the UK [PAS1878] and [EUCodeOfConduct] give examples of how ESAs may be mandated to support these features in the future.
NOTE Support of Device Energy Management Cluster is provisional.
Per the Matter specification you cannot use DeviceEnergyManagementCluster without enabling certain feature combinations. You must use the with factory method to obtain a working cluster.
See
MatterSpecification.v13.Cluster § 9.2