Control 2 chargers on same circuit

[Mats1717]

Question

I have 2 chargers on the same circuit so controlling them idividually by circuit_dynamic_limit is not possible. What is the best way to cotroll them individually in a sheduling automation. I will not run them on the same time due to effect fee

What version of the integration are you using?

Latest

Anything in the logs that might be useful for us?

No response

Additional information

No response

[olalid]

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 charging starts or just once a minute or so (if you call the service it will only call the API if the limit is different from what is already set, so no harm in doing that).

But, also if you want to limit power, setting the circuit dynamic limit does mean that the power is limited for both chargers total power. I.e if you set the limit to anything less than 12A then only one charger will start since the minimum current for one charger to start is 6A. You would not know which one of the charger starts fist though.

A third way would be to pause the charger you do not want to start...

I do not have this kind of setup myself so I have never tried any of these methods.

[Mats1717]

What do you think of using switch.easee_garaget_charger_enabled. Is that a bad idea.

[olalid]

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 risk of wearing out the flash memory if the setting is changed too often.

[AMajland]

I am seeing something a bit weird on a circuit with two chargers on the same circuit. On the pictures the left is a master and the right is a slave.

The slave is limited to 10A in the static charger limit Dyn charger, Dyn circuit, Max Charger, Max Circuit, Offline

As expected the master is using 32A as the limit and the slave 10A

But when i set the Dyn Curcuit Limit to i.e 6A it is only reflected on the master and not on the slave.

Looking at the attributes of the slaves dynamic_circuit_limit they are newer changed by calling the easee.set_circuit_dynamic_limit with the circuit_id: as data. Only the masters dynamic_circuit_limit are updated.

Both easee home chargers are at firmware v318

I was just helping another with two chargers and two cars that wanted to charge with surplus from solar and had issues. I have not testet with my own car yet whether the slaves honors the circuit limit of i.e 6A in this example when it shows that it will use the higher Max Charger Limit

[olalid]

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 both dynamic circuit values changes for both of the chargers if they are on the same circuit...

So are both chargers actually configured to be on the same circuit? One way to verify is to look at the attributes of the charger "status" sensor and check the "Circuit ID". If it is the same number on both chargers they are on the same circuit. If not they where not correctly configured during installation.

Are you using the "output limit" sensor to display the "Used limit" in the pictures above? (Maybe not, since cable lock is off and output limit is normally 0 when the car is not connected)?

[Mats1717]

The slave is not updating, but it have the value set shown on master. Had this config for some time. Se below

[AMajland]

Yes they are on the same circuit - Both shown in easee.cloud and have the same circuit_id shown under dynamic_circuit_limit for both chargers.

I'll test how it behaves with a car connected tonight when it gets home.

If was just puzzled by the master updating without a car connected while the slave was not .... But when i connect a car i would expect the slave charge to honor the circuit maks as shown by the master.

I normally just change it in an automation but the charger card is easy to visualize what is going on what sets the limit

Btw the Used limit is - entity_id: calculated and the reason that it is not showing correctly i probably that the slave chargers dynamic circuit is still at 40A even trough the it is set lower

[Mats1717]

It will use the value of the master but i dont think it will update anyway when charging. I use charger_enabled for automation by schedule so it wont update so often. If you have 32 A circuit you can set upp both as master and the then it will work if you have cars that only can charge max 16 A AC

[olalid]

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 the same with dynamic_circuit_limit on slave chargers if does not actually work... Are you aware of other sensors that does not work on slaves?

"calculated" is not a sensor name that is provided by this integration, unless you have renamed it, so not sure what you mean there...? As I stated above, the sensor called "output_limit" will show you what limit is actually used by the charger. Hopefully that works on both master and slave. But it will always be 0 until charging starts. It might provide some clue to what limit is actually used.

[enoch85]

Didn't we already discuss this? https://github.com/nordicopen/easee_hass/issues/256#issuecomment-1774147335

[AMajland]

The car got home and we are now after 21 where the transport tarifs goes from 1.2388 DKK/kWh to 0,4129 DKK (~0,17€ €/KWh to ~0,06 €/KWh)

• The car is connected to the slave
• The dynamic circuit max is set at 0
• The slave shows dynamic circuit max on the attribute of CHARGERID_dynamic_circuit_limit as 40 (as above)

And the slave charger status is PAUSED/AWAITING START with the reason MAX DYNAMIC CIRCUIT TO LOW

Setting the dynamic circuit max to 6A starts charging at the slave with "CHARGERID_output_limit at 6A

So all works as expected but i was just puzzled by the slave showing nonsense values for dynamic_circuit_max.

The "calculated" is in the https://github.com/tmjo/charger-card and does not take into account that the dynamic max for a slave is not updated.

Master (nothing connected)

Slave:

The purpose is a bit different than the other thread as i was trying to help someone with an automation to charge two cars simultaneously with surplus solar power . He has a big array and on clear days it generates enough surplus for that enstead even here in January. (better than selling it at spotprice with a deduction (indfødnings tarif don't know how to translate). )

He started with a blueprint from someone else and today when the sun came out it mostly worked (that is the first car/charger started/stopped as it should but the second did not stop charge as expected). But the error most be somewhere else as the easee_hass as my test shows that the slave charger respects the masters dynamic circuit limit even trough the slaves enity does not show it

I think that it will be a good idea to remove them from slave as it was done for the circuit_current - then it wont confuse anybody else :-)

The following are not updated either

• Equalizer limit
• Max circuit limit
• Offline circuit limit

[olalid]

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

[olalid]

The non-working sensors mentioned above are now removed in the latest release.