If a limit has been set, a measurement is expected to provided within 15s. If this is not the case, then show a warning and return an error.
Also add support for the Elli Connect Pro internal meter again.
This should now lead to those EEBUS wallboxes not providing measurements, to fall back to the actual limit being assumed as being the current measurement. And the user is informed about non function metering in the wallbox.
The meter values are not provided reliably and evcc would have to add logic to invalidate old meter values. The better solution is to always use an external meter for these wallboxes.
This updates the eebus charger implementation to use the latest version of cemd, eebus, spine and ship.
Only use OSCEV if the a wallbox with ISO15118-2 VW VAS is connected, and the EV is using this. This also enables full charging control and putting the EV to sleep. All other current implementations of the usecase are basically wrong and are no different than using OPEV.
The OBO Ion charger is based on the EcoHarmony (formerly Viridian EV)
EVSE Protocol Controller (EPC) 2.0 Plus (EPC20P10). This is documented
in an illustration in the documentation of the OBO Ion charger. The
Modbus register documentation of both devices also matches.
The EPC 2.0 Plus charge controller is sold to manufacturers of chargers
and might have been directly sold in chargers by EcoHarmony. Therefore,
it is possible that other chargers with this charge controller exist and
that the OBO Ion charger is just an example of a charger that uses this
charge controller.
In order to ensure backwards compatibility, it seems best to continue to
use the name "obo" internally. If there are notable other chargers with
this charge controller, the driver could be added with additional names
in the registry or it could be renamed internally.
Viridian EV seems to have changed its name to EcoHarmony. Therefore, it
seems best to include both names to make it easier to find the charge
controllers under both names.
