Ola Lidholm

Well ok. Then that plan failed I guess. Another approach could be to set the price with the service easee.set_charging_cost every 15 minutes. The cloud should save the total cost...

Yes, sorry I was thinking about RobinDevogeles case above where it depends on solar production what the price is going to be for each 15 minute period.

As I said above setting the price is already supported, where the price information comes from is not in our scope I think. Regarding creating a sensor we are experimenting...

What I am seeing is that a session may or may not be included depending on how I specify the cut of time/dates, even though the session falls within that...

If I remember correct the standard for car charging says you should only output PWM signals that indicate an integer amount of current and the car should also interpret it...

See https://github.com/fondberg/easee_hass/pull/222

There is now a time_to_live option for the set_circuit_dynamic_limit service.

Finally I got around to removing the polling completely. (Well it falls back to polling if the SignalR stream does not connect, but otherwise not).

Is the phase mode set to automatic?

The circuit id can be found under the attributes in the status sensor for each charger. You need to use that specific number, it is for sure not going to...