Update OPENNEM parser to v4

[BastienBigue]

The OPENNEM parser uses an v3 endpoint from opennem that was migrated to the v4.
The v4 endpoint offer more flexibility and we should migrate to keep up to date.

Any contribution is welcome :)

Thank you

[eliascham]

Hey hey @BastienBigue ! In OPENNEM.py, looks like the endpoint is already using V4:
url = f"https://data.openelectricity.org.au/v4/stats/au/{network}{region}/power/{duration}.json"

Is there something missing here?

[VIKTORVAV99]

Hey hey @BastienBigue ! In OPENNEM.py, looks like the endpoint is already using V4: url = f"https://data.openelectricity.org.au/v4/stats/au/{network}{region}/power/{duration}.json"

Is there something missing here?

It's using a undocumented stats endpoint right now (carry over from v3), we would like to fully migrate the the endpoints documented here: https://docs.openelectricity.org.au/api-reference/overview

We would like to start with price as that should be a 1:1 change in the returnd data.

[eliascham]

I see, thanks for the clarification. Let me see what I can do

[eliascham]

Quick question, whats the easiest way that we're keeping API keys for the different sources? The V4 requires an API key to function (can be generated for free). How / where do we want to keep this key?

Note: made good progress on this will start testing soon

[VIKTORVAV99]

Quick question, whats the easiest way that we're keeping API keys for the different sources? The V4 requires an API key to function (can be generated for free). How / where do we want to keep this key?

Note: made good progress on this will start testing soon

It should be stored as a ENV variable, we will use our own keys in production.

Look how the ENTSO-E, Nordpool or EIA parsers does it.
For example:

    token = get_token("ENTSOE_TOKEN")

[eliascham]

Quick question, whats the easiest way that we're keeping API keys for the different sources? The V4 requires an API key to function (can be generated for free). How / where do we want to keep this key?
Note: made good progress on this will start testing soon

It should be stored as a ENV variable, we will use our own keys in production.

Look how the ENTSO-E, Nordpool or EIA parsers does it. For example:

token = get_token("ENTSOE_TOKEN")

Sounds good, I saw that theres documentation on other API tokens here: https://github.com/electricitymaps/electricitymaps-contrib/wiki/Create-tokens - Ill add a section for the OPENELECTRICITY_TOKEN since that seems to be missing even though the repo already uses it under electricitymap.contrib.capacity_parsers.OPENELECTRICITY.py

[VIKTORVAV99]

@eliascham could you provide an update on your progress?

[eliascham]

@eliascham could you provide an update on your progress?
Almost done testing the pricing portion of the API - will have to update the production pull from the API to make that working before pushing any changes

[VIKTORVAV99]

@eliascham could you provide an update on your progress?

Almost done testing the pricing portion of the API - will have to update the production pull from the API to make that working before pushing any changes

What do you mean by production pull? I would really like if the first PR was just scoped to price information as it will take a lot longer to review otherwise.