feature request: make UsageCost structured

[paul-pedal]

It would be useful for UsageCost to have a consistent format and be attached to each connection rather than the root.

suggestion:

UsageCost: {
      currency: 'GBP',
      perKwh: 0.3,
      connectionCharge: 1.0,
      min: 1.8,
      timeLimit: 60,
      overtime: 5,
      notes: 'xxxxxxx',
}

[webprofusion-chrisc]

Thanks, increasingly we're looking to align our data model with other standards, so identifying something in OCPI etc. that we could replicate would make sense for interoperability.

[iboboc]

I miss the same feature. A structured way to retrieve the charging cost/price.
Just a note, charging price should be differentiated by plug (sometimes AC is different than DC) - as mentioned, linked by connector, and should include also starting fee.
This will help also fixing issue #133 by filtering by price from free (0) to any.

Thanks.

[iboboc]

I am tempted to work on the change myself, once we agree on the architecture (data structure, flow, etc)... but it is quite a job (84 files to modify) :) And I am not really familiar with the system, I will not be able to test much.
I assume it will be straight forward for a current maintainer/contributor and less prone to errors.