No VEN clients defined yet. Create one to start fetching DR events from a VTN.
+ {% endif %} +| Name | +Trigger (UTC) | +Targets | +Limits | +Sensors | ++ |
|---|---|---|---|---|---|
| {{ cfg.config_name }} | +{{ cfg.utc_trigger_time }} | +{% if cfg.targets %}{{ cfg.targets | join(", ") }}{% else %}—{% endif %} | ++ {% if cfg.fetch_import_capacity_limits and cfg.fetch_export_capacity_limits %} + import + export + {% elif cfg.fetch_import_capacity_limits %} + import + {% elif cfg.fetch_export_capacity_limits %} + export + {% else %} + — + {% endif %} + | +
+
+ {% if cfg.fetch_import_capacity_limits and cfg.import_sensor_id %}
+
+ Import sensor
+
+ {% endif %}
+ {% if cfg.fetch_export_capacity_limits and cfg.export_sensor_id %}
+
+ Export sensor
+
+ {% endif %}
+
+ |
+
+
+
+ Edit
+
+
+
+ |
+
No polling schedules defined yet.
+ {% endif %} ++ These are the static connection settings that the VEN uses to authenticate with and + reach the VTN. They are shared across all polling schedules for this VEN client. +
+ ++ Configure the static connection settings that the VEN needs to authenticate with and + reach the VTN. These fields rarely change once set up. + After creating the VEN client you can add polling schedules to start fetching DR events. +
+ ++ Configure when to poll the VTN for DR events, which targets to filter on, and + which capacity-limit types to retrieve. A FlexMeasures sensor is created automatically + for each selected limit type to store the retrieved beliefs. +
+ + +