The Easee chargers operate based on current limits that can be set by various sources (such as equalizer, schedule, operator control or this integration). The lowest limit at a given time is what controls the charging current and it is what is going to be signalled to the car while charging. The car will then limit the current it draws from the grid to less than that amount (it can draw less if it wants to). If a limit is less than 6A, charging will be stopped until it increases above 6A again (this is limited by the standard that car charging follows).

The sensor "output_limit" will always show the limit value that is controlling charing at a given time, and the sensor "reason_for_no_current" will display a message about what is limiting the current at the moment.

There are some info on the Easee developer site that is useful to read before you venture out in to controlling the charger: https://developer.easee.com/docs/api-command-and-control and https://developer.easee.com/docs/api-smart-charging

General hints:

Pause and resume are the commands you should use, not start and stop. Start and stop controls authentication of the charger from the cloud (instead of by RFID etc). If your charger is not set up with authentication enabled, start and stop will do nothing.

To control the charging current, using the circuit dynamic limit usually works best for most users. Set it to less than 6A when you want charging to pause and set it to 6A or more when you want it to charge. If you set 2 of the phase limits to 0 and the charger is in automatic phase mode, it will switch to single phase charging on the phase where the charging is allowed. (Note that there is no interface to tell the car more than one current limit, so setting different current limit on the phases serves only the purpose of telling the charger when to switch over to single phase charging, you can not tell the car to draw different amount of current on different phases, trying to do so will only result in a lower current on all of the phases).

If you have more than one charger, you may want to use the charger dynamic current instead. It will allow you to control when each charger is allowed to charge and it works in much the same way as circuit dynamic limit. A difference is however that it is automatically reset when a new charging session is started, so any automations needs to take that in to account.

It is also possible to set other limits through this integration, but only the ones called "dynamic" are recommended to use on a regular basis since the others ones are stored in flash memory and therefore risks to wear out the flash if used too often.

If the service to set a limit is called with the same exact current as already registered in the cloud, the API will not be called at all. This allows for running automations on regular intervals and set the current limits every time it runs, without causing an excess of calls to the API.