Jonas Karlsson

The three currently supported price sources as well as EPEX Spot mentioned by @andreasd all have very similar formats. When I added the second (and the third) price source I...

@johny-mnemonic I made a template sensor to try out how the integration would react to that, but in one of the validation steps, the integration checks that there exist in...

@johny-mnemonic How would you make the templete sensor? I have experimented with the following templete sensor. It mimics the format of the Entsoe price integration. But it has one inconvenient...

@andreasd Can you contruct a template sensor that takes the output from your price data source and provies the state and attributes price_today and price_tomorrow?

I have plans to add a sensor with the accumulated charging cost. And then one could use the [Utility Meter](https://www.home-assistant.io/integrations/utility_meter/) to get daily, monthly, yearly costs. Now, you ask for...

I plan to implement this using an entity from the charger that contains the total energy (in kWh) consumed by the charger. And a first sensor that will contain the...

It is planned, and I have started to implement it. However, some other things with higher priority needed to be done, so there has not been any progress lately.

I understand your situation, but this kind of improvement will make the integration much more complex. It is also related to similar tariffs schemes were your monthly fee depends on...

Thanks for quick reply! To use the service `easee.set_circuit_dynamic_limit`, does that assume that no schedules have been configured? So the follow two actions could be used in the automations to...

@andreasd, finally I got some time to test your template sensor above. For me it seems like it will not select today's and tomorrow's prices in the local time zone,...