Ola Lidholm

Yes, you can use an automation to write the current price to Easee. I do not think that will mean that the price will be logged correctly throughout a charging...

Can you show how your automation looks?

You can not use an entity_id: as input to cost_per_kwh. You must provide a value, and you can do that with a template, similar to what I wrote above. In...

This works for me: ``` - id: elbil_laddkostnad alias: Elbil laddkostnad trigger: - platform: state entity_id: sensor.elpris_total action: - service: easee.set_charging_cost data: charger_id: EHxxxxxx cost_per_kwh: "{{ states('sensor.elpris_total') }}" vat: 0...

Ok, I do not think there is anything we can do about that. What we do is call the API to change the price setting and monitor changes sent back...

I guess setting the charger dynamic limit would be one way. It is automatically reset though when charging starts so you would have to make sure to set it when...

It should work I guess, but since it is a charger configuration setting it might be so that it is written to flash in the charger. So there is a...

I do not have this kind of setup myself, so not completely sure how the sensors normally behave under these circumstances... But it would make a lot of sense if...

We know since before that the circuit_current sensor does not update on slave chargers (so we decided some time ago to remove it on slave chargers). Perhaps we should do...

See https://github.com/nordicopen/easee_hass/pull/384