Ga naar hoofdinhoud

building_post_grid_limit_schedule

POST 
/public-api/buildings/:uuid/schedules/grid_limits/

Pre-requisites​

  • uuid: You need a (building) uuid for this endpoint. You can get a list of buildings with GET /buildings/.

Creates one or more GridLimitSchedule occurrences for the specified building.

A 201 Created means the occurrences are stored and the Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. is asked to retrieve them. It does NOT confirm that the Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. applies them; for example, scheduled grid limits have no effect when they are not enabled on the load balancer of the building. Use the execution_status of GET /buildings/{uuid}/schedules/grid_limits/ to see whether the Envi.Baseenvi.baseDe energiecontroller van Envitron die apparaten uitleest, aanstuurt en data opslaat achter de hoofdaansluiting. applied an occurrence, once it has started.

The request body is an array of items. Each item defines a time window and limits. Occurrences may touch but must not overlap (either with each other in the same request or with existing occurrences in the database).

Validation & business rules​

  • Quarter-hour alignment is enforced on both timestamps.
  • Earliest start: start_timestamp ≥ now_utc + 15 minutes.
  • Horizon: end_timestamp ≤ 00:00:00 UTC of the 8th calendar day from now.
  • Duration order: end_timestamp > start_timestamp.
  • Per direction: delivery_limit_watts and return_delivery_limit_watts are optional individually, but at least one must be provided.
  • No overlaps:
    • Within the same request payload (items may touch, not overlap).
    • With existing occurrences for the building (any intersection is rejected).
  • Limit: Maximum 100 items per request.

Request​

Responses​