enen
Ongoing project

General acceptance criteria Matter

Although the Matter 1.4.1 specification introduces foundational support for EVSE, it does not yet provide complete functionality for all required flexibility use cases, particularly for FEID types beyond EVSE. Therefore, this work package will also address the current limitations of the standard and define a roadmap for necessary extensions or adaptations. The goal is twofold: • To deliver a fully functional, Matter-based software foundation for EVSE interoperability based on existing clusters and device types; and • To define and document the message structures, clusters, and interactions required within Matter to enable the three residential energy flexibility use cases. 

Acceptance criteria Matter - HEMS side

  1. Demonstratedcommissioning of a Matter-compliant EVSE device. 
  2. Ability to issue control commands (SetTargets,EnableCharging,DisableCharging, EnableDischarging) and subscribe to telemetry (State, SupplyState, NextChargeRequiredEnergy, NextChargeTargetSoC, SessionEnergyCharged, SessionEnergyDischarged). 
  3. Clear demonstration of Matter Interaction Model functionality.
  4. End-to-end integration with the device-side implementation via a shared Fabric.
  5. Explicit mapping of Matter messages (attributes, commands, events)requiredto support the three use cases. 

Acceptance criteria Matter - device side

  1. Successful commissioning with a Matter controller using PASE or CASE.
  2. Implementation of the Energy EVSE Cluster and selected optional clusters. Correct interpretation of control commands:SetTargets,EnableCharging, DisableCharging, EnableDischarging. 
  3. Accurate reporting of attributes: State,SupplyState,NextChargeRequiredEnergy, NextChargeTargetSoC, SessionEnergyCharged, SessionEnergyDischarged. 
  4. End-to-end communication with the HEMS-side implementation.

Acceptance criteria Matter- cloud based monitoring 

For cloud-based monitoring, a Matter-compatible gateway is needed that enables monitoring and control of Electric Vehicle Supply Equipment (EVSE) devices connected to a local Matter fabric. Matter is not a cloud-native protocol and does not support direct device-to-cloud communication. Therefore, work is needed that focuses on building a secure, standards-compliant local gateway that acts as a Matter controller or commissioner, while exposing a cloud API for remote interaction. 

  1. Establishesa secure Matter fabric and commissions at least one EVSE node (Device Type 0x0099). 
  2. For EVSEs,demonstratesfull support for:
    – Commands: SetTargets, EnableCharging, DisableCharging, EnableDischarging
    – Attributes: State, SupplyState, NextChargeRequiredEnergy, NextChargeTargetSoC, SessionEnergyCharged, SessionEnergyDischarged 
  1. Provides a secure API/protocol (e.g. S2 if possible, otherwise HTTPS or MQTT) that allows external clients to send control commands and receive telemetry.
  2. Ensures end-to-end security and reliability from the cloud interface to the Matter device.
  3. Gateway architecture and implementation must be documented as extensible, with guidance for integratingadditionaldevice types and clusters. 
  4. Explicit mapping of Matter messages (attributes, commands, events) to cloud API endpoints and request formats, supporting the following three use cases.