Actually, the Easee Chargers are compatible with the Open Charge Point Protocol (OCPP) v.1.6j. This is a legal requirement for larger installations, an also a requirement for most public subsidies for charging infrastructure.
OCPP contains a server that can exchange information with chargers (clients) in order to fully control the chargers.
Therfore, we could install a local OCPP server (python ocpp, chargepi, MicroOCPP, SteVe, I have no idea which one works best) on the same computer that runs our Openhab system and control our Easee Boxes fully, without the Easee Cloud.
For this to work, we first have to point the Easee Boxes to our own intranet-ocpp-server (a hyperlink to the intranet ip-address of our openhab box - no internet connection necessary). This is in principle possible, but currently requires that we register as “service operators” with Easee, because the input field for the ocpp link is only visible to service operators. Note: Easee is working on this being a “user” feature, but this is yet to be released.
But the Problem is: Despite OCPP being an open protocol, there is currently no Openhab OCPP binding! I was surprised to learn that. However, in theory it should not be too difficult to make such a binding, should it. Someone is working on this, but it seems there is not much progress:
Openhab OCPP binding
So, not all hope would be lost, if Easee gave up the Cloud API.