Dispatch smart-charging power limits to an OCPP 2.0.1 charge point using SetChargingProfile
domain: openchargealliance.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
From the CSMS, send SetChargingProfile specifying chargingProfilePurpose (e.g. TxDefaultProfile or ChargingStationMaxProfile) and a stackLevel
Define a chargingSchedule with one or more schedulePeriods and a power/current limit
Match the schedule's chargingRateUnit (W or A) to the unit the charge point advertised in its BootNotification/device model
Read back the effective composite schedule via GetCompositeSchedule to confirm the applied limit
Use ClearChargingProfile to remove a profile once the smart-charging constraint no longer applies
Known gotchas
Profiles with conflicting purpose/stackLevel combinations silently override one another at the charge point — verify precedence rules rather than assuming the last-sent profile wins
Sending a schedule in the wrong unit (W vs A) relative to what the charge point expects results in an incorrect or rejected limit without an obvious error
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?