Support for Matter EVSE

[lboue]

Proposed change

Support for Matter EVSE - EnergyEvse cluster

Matter 1.3’s energy features enable new energy-centric devices, the first of which is Electric Vehicle Supply Equipment (EVSE).

• This enables EV charging equipment manufacturers to present a consumer-friendly way to control how and when they charge their vehicles.
• It features the ability to manually start or stop charging, adjust the charging rate, or specify how many miles of range to be added by a set departure time, leaving the charging station to automatically optimize the charging to happen at the cheapest and lowest carbon times.

As discussed with Marcel, the second step would be to create a specific entity for EVSE in Home Assistant for better integration.

Supported attributes:

• EnergyEvse.Attributes.State
• EnergyEvse.Attributes.SupplyState
• EnergyEvse.Attributes.FaultState
• EnergyEvse.Attributes.CircuitCapacity
• EnergyEvse.Attributes.MinimumChargeCurrent
• EnergyEvse.Attributes.MaximumChargeCurrent
• EnergyEvse.Attributes.UserMaximumChargeCurrent

Add command_timeout attribute in MatterButtonEntityDescription class. This is mandatory for EnergyEvse commands.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

Testing

Testing with Matter Linux Energy Management Example device from SDK.

Enable charging with chip-tool

./chip-tool generaldiagnostics test-event-trigger hex:000102030405060708090a0b0c0d0e0f 0x0099000000000000 <nodeID> 0
./chip-tool generaldiagnostics test-event-trigger hex:000102030405060708090a0b0c0d0e0f 0x0099000000000002 <nodeID> 0
./chip-tool generaldiagnostics test-event-trigger hex:000102030405060708090a0b0c0d0e0f 0x0099000000000004 <nodeID> 0
./chip-tool energyevse enable-charging null 2000 30000 <nodeID> 1 --timedInteractionTimeoutMs 3000

Enable charging with WebSocket

{
  "message_id": "example",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "node_id": 23,
    "payload": {
        "ChargingEnabledUntil" : null,
        "MinimumChargeCurrent": 2000,
        "MaximumChargeCurrent":30000
    },
    "cluster_id": 153,
    "command_name": "EnableCharging",
    "timed_request_timeout_ms": 3000
  }
}

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/matter, mind taking a look at this pull request as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign matter Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[lboue]

All lights are green. Tests are now successful.
I had to close the #133457 because I have conflicts with the branch/PR and I was not able to fix it.

[marcelveldt]

Marked as draft, awaiting the translation keys for the enum sensors