docs: explain new fields defining peak prices

Signed-off-by: F.N. Claessen <felix@seita.nl>

flexmeasures/api/v3_0/sensors.py

@@ -300,9 +300,12 @@ def trigger_schedule(
 
 
         The battery consumption power capacity is limited by sensor 42 and the production capacity is constant (30 kW).
-        Finally, the site has a physical power capacity of 100 kVA, but the production capacity is limited to 80 kW,
+
+        Finally, the (contractual and physical) situation of the site is part of the flex-context.
+        The site has a physical power capacity of 100 kVA, but the production capacity is limited to 80 kW,
         while the consumption capacity is limited by a dynamic capacity contract whose values are recorded under sensor 32.
-        Breaching capacities in either direction is penalized heavily, with a price of 1000 EUR/kW.
+        Breaching either capacity is penalized heavily, with a price of 1000 EUR/kW.
+        Finally, peaks over 50 kW in either direction are penalized with a price of 260 EUR/MW.
 
         Note that, if forecasts for sensors 13, 14 and 15 are not available, a schedule cannot be computed.
 
@@ -337,7 +340,11 @@ def trigger_schedule(
                     "site-production-capacity": "80 kW",
                     "site-consumption-capacity": {"sensor": 32},
                     "site-production-breach-price": "1000 EUR/kW",
-                    "site-consumption-breach-price": "1000 EUR/kW"
+                    "site-consumption-breach-price": "1000 EUR/kW",
+                    "site-peak-consumption": "50 kW",
+                    "site-peak-production": "50 kW",
+                    "site-peak-consumption-price": "260 EUR/MW",
+                    "site-peak-production-price": "260 EUR/MW"
                 }
             }