Changes:
DiginGridTariffAPI.v1_0.json: Changed description for StartTime, EndTime and Range in tag TariffQuery.
gridtariffapi.v1_0.common.schema.json and all example files:
Changed MeteringPointsAndPriceLevels to contain currentFixedPriceLevel and meteringPoints, to attach lastUpdated to meteringPoints and not currentFixedPriceLevel.
Changed CurrentFixedPriceLevel.levelId.description and MeteringPointDetails.lastUpdated.description.
Changed FixedPrices.pricelevel to FixedPrices.pricelevels and changed PowerPrices.pricelevel to PowerPrices.pricelevels to reflect that they are arrays.
Background:
Here are the most important changes and the reasoning behind them:
-
meteringPointsAndPriceLevels.currentFixedPriceLevel.id has a value (IS NOT NULL) only if the time of the api call is between StartTime and EndTime or within Range(Range=today). This is due to the fact that the connection between meteringPointId and a tariff is only valid/certain at the time of the api call. If there are only historical or future prices in the response, it could be misguiding to give an id to a fixedPrice.
-
meteringPointsAndPriceLevels.currentFixedPriceLevel.levelId has a value (IS NOT NULL) only if there has been performed a calculation of consumption this month. Typically it will be NULL for a period of time after midnight on the 1st of every month, until the grid company has performed the first consumption calculation.
-
meteringPointsAndPriceLevels.meteringPoints.lastUpdated has a value (IS NOT NULL) only if there has been performed a calculation of consumption this month. Typically it will be NULL for a period of time after midnight on the 1st of every month, until the grid company has performed the first consumption calculation based on either real meter measurements or estimates. lastUpdated gives the timestamp of the last received basis for a performed consumption calculation, regardless of this being a real meter measurement or an estimate.