Implement IEEE 2030.5 Function Set 11 (Load Shed) to receive and execute demand response load curtailment commands from a utility

Verified steps

1. Discover the EndDeviceList resource at /edev on the IEEE 2030.5 server; retrieve or create an EndDevice resource for your controllable load and confirm that the server has associated it with a MessagingProgram or DemandResponseProgram (Function Set 11 uses the DemandResponseProgram path /drp).
2. GET the list of DemandResponsePrograms at /drp; each program contains a primacy value (lower = higher priority) and links to EndDeviceControls or LoadShedAvailability resources — retrieve the active program's DemandResponseProgramList.
3. Poll for active EndDeviceControl resources at the program's /drp/{id}/edc endpoint; each control specifies dtstart (UTC epoch seconds), duration, randomizeDuration (up to which delay is permitted before executing), and deviceCategory (bitmask indicating target device types).
4. When a control is received and within its active window, apply load curtailment to the target devices within the randomization window: shed load no earlier than dtstart and no later than dtstart + randomizeDuration; send a Response resource to the server's /rsps endpoint indicating execution status.
5. Implement control cancellation: if a subsequent GET returns that a previously active EndDeviceControl has been superseded (via a newer control with higher primacy or an explicit cancellation), restore shed load and send a Response with status indicating cancellation acknowledged.
6. Maintain the LoadShedAvailability resource at /lsa with your DER's current available curtailment capacity (in watts), updated on change or at a configurable interval; utilities use this to verify dispatchable capacity before issuing controls.