I had a look at KEBA, so at least this I guess (* added by me based on API)
Binary Sensors:
Online state,
plug state,
Charging state
failsafe mode state (think this is a feature made if lost contact with charger, perhaps not possible?)
Lock:
Authorization (like with the RFID card).
Sensors:
current set by the user,
target energy/SOC set by the user,
charging power,
charged energy of the current session
charged energy of the total energy charged.
*voltage
*currentFirmware
*availableFirmware
*cableLocked
*smartCharging
Services:
authorize,
deauthorize,
set energy target,
set the maximum allowed current and manually update the states.
*start
*stop
*resume
*pause
*override_schedule
I haven’t tested everything, but I read out a lot of values. Personally I’m a “the more the marrier” guy, so I don’t mind adding most of what is available in the API and rather let the user decide which one should be added to his or her HA. Especially sensors, since they are not too complicated. When it comes to functionality it may be more tricky and can be looked at in a step 2 if neccessary (add/get/delete basic_plan for instance).
Seems Easee organizes everything in Sites consisting of Circuits consisting of Chargers, so I believe a wise choise would be to build classes around this? They are also planning something called Equalizers which is supposed to be their own Tibber Pulse for reading and loadbalancing with power meter in the house (AMS).