Support for more Electricity price sensor (make it more universal)

[CasparTheBridge]

During configuration of the integration you need to select a 'Electricity price sensor' but it is not defind how the structure of the sensor should be. I use the standard EnergyZero integration but the output of the service call is not accepted as an input for this integration:

The content of the output of the service call in the sensor looks like this:

Please make it configurable where you can find the data in the sensor, so you can define keys how the data is accessable within the attributes.

(the ENTSO-e integration you have linked to in the documentation seems not maintainted anymore, so more possibilities of your integration will help to keep using your integration)

[andreasd]

we've had this discussion here: #231

tl;dr - it was suggested to support a generic sensor format which can be used in combination with template sensors. with those template sensors, you can reformat lots of different price sources into the generic format (see my example in the linked thread).

but so far, no response about the implementation of a more generalized sensor.

[CasparTheBridge]

The issue is there is no documentation in which format the data needs to be delivered.
And the structure to get it working is probably quite specific as with some templating I was unable to get it working with your integration.

So best option I thing is to have during the setup/configuration a sort of selection mode of the data input and in which format it is.
The other option is to have a clear description on how the data should be delivered to the integration (and I think the way it is now is to specific and to difficult to create with template sensors)

[andreasd]

there currently is no option to get data from any other source than the pre-defined ones. even if you get it in the exact same format and name the variables like one of the supported extenions, the extension won't be able to pick it up. it will need modifications in ev_smart_charging to get this working.

the issue with just asking for the variables and attributes during setup is, that there is no standard in how prices over time can be delivered. every extension does this differently. so even if you ask for variable and attribute names, only a small fraction of price providers will be supported.