Skip to content

Create new extension - ENTSOE agent #3

Description

@igorrutka

A new stand-alone extension that can be used to load day-ahead electricity prices from the ENTSOE transparency platform.

European Network of Transmission System Operators for Electricity (ENTSOE):
https://transparency.entsoe.eu

The initial concept is:

  • An agent that connects with the ENTSOE API to retrieve the day-ahead electricity prices.
  • An agent link is used to link an attribute of choice (e.g. EMS tariff attribute) to receive the day-ahead prices, those are added to the predicted asset data-point table of the attribute.

Activity

  1. ebariaux commented on Jan 20, 2026

    @ebariaux
    Contributor

    Agent attributes should only be used to represent the configuration of the agent (+ status) but not to contain the output of the agent processing.
    An attribute link is used to another asset's attribute to contain the output.

  2. pierrekil commented on Jan 20, 2026

    @pierrekil
    Member

    Might not be a bad idea from a usability point of view, avoiding the dependancy on an asset type?

  3. ebariaux commented on Jan 21, 2026

    @ebariaux
    Contributor

    @pierrekil I don't understand your comment ? What's not a bad idea, not updating agent attributes ?

    And that does not mean in some cases having a specific asset type wouldn't make sense.

    Or you're saying the opposite and that having some specific attributes already on the agent that would automatically receive values from the agent execution would then avoid the need for specific asset types.

  4. ebariaux commented on Feb 13, 2026

    @ebariaux
    Contributor

    Initial requirement was

    An attribute on the agent for day-ahead electricity prices.
    The day-ahead prices are added to the predicted asset data-point table of the attribute.
    Attribute updates every 15 minutes with the new current price.

    Additionally an agent link that can be used to link an attribute of choice (e.g. EMS tariff attribute) to get the same functionality as the attribute on the agent.

    This is now changed to not update an attribute on the agent
    As for updating the current value, this can be taken care of using the ApplyPredictedDatapointService

  5. ebariaux commented on Feb 16, 2026

    @ebariaux
    Contributor

    For now, parameters to call ENTSO-E API are as follow:

    • documentType hardcoded to A44
    • contract_MarketAgreement.type hardcoded to A01
    • baseURL at agent level with default value
    • securityToken at agent level
    • polling at agent level with default value
    • periodStart automatically set to time of call
    • periodEnd automatically set to time of call + 1d
    • zone at attribute link, used for in_Domain and out_Domain
  6. ebariaux commented on Mar 18, 2026

    @ebariaux
    Contributor

    Also see documentation PR: Documentation for ENTSO-E agent

  7. linked a pull request that will close this issueENTSO-E agent #15on Mar 18, 2026
  8. ebariaux commented on Mar 18, 2026

    @ebariaux
    Contributor

    Code was initially developed in main repo, branch is still available (until the PRs are merged) if required: openremote/openremote at feature/entsoe-agent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

FeatureDevelopment of new feature

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions