Fix a scenario were measurements were provided after the last limit change. But if the interval is set >15s and measurements even came in after 15s timeframe, this was considered to be invalid.
To fix this, every time measurements are provided and the limitUpdate timestamp is not zero, meaning a limit was set, consider data to available by setting limitUpdate to zero again.
Some EEBUS wallboxes like the PCMP do report the OSCEV usecase to be available, but it doesn’t provide the necessary recommendation limit data.
This change adds checks for this case.
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.
- Update SHIP and EEBUS libraries to latest dev code
- Support IPv6 connections and devices only reporting IPv6 mDNS addresses
- Re-Add support for overwriting the IP address in the charger config, also added to the meter config (just in case)
- Make sure to use VWVAS feature only if the vehicle reported SoC is 25% or higher, as charging via this feature in a Taycan only works if the vehicle internal MinSoC is reached which can’t be lower than 25%
- For detecting if the EV is charging, use the reported power data first, and only use currents if no power data is available
Some EVSEs using EEBUS sometimes do not provide any current charging limits and also do not provide valid ranges just ignore these scenarios and hope for the best.
- Check if sending the heartbeat even more often helps
- Use avahi as mDNS provider if available. this might help finding the Elli device after disconnections quicker and maybe even ones own mDNS entry better
- Fix a small bug with resetting recommendation limits to inactive when using VAS EVs
- Tested with Elli Charger Pro Gen 1
- Handle missing power and use current data in evcc instead of eebus library
- Check for use case scenario availability for power and current data
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 golang mock package has been archived and is now maintained by uber.
> Update, June 2023: This repo and tool are no longer maintained. Please
> see go.uber.org/mock for a maintained fork instead.
[1] https://github.com/golang/mock
[2] https://github.com/uber-go/mock
- Make sure the check using an external meter is identical to using an internal meter
- Fix check using internal meter to compare sum of all charge currents to idlefactor * min. single phase charge current
* Ignore a max number of meter no data errors
When an EV is connected, measurements are not available right away, as the initial communication is not done. And due to bugs in the Elli software, the EEBUS stack can not generally wait for data being available and only then set the EV as being connected.
This change ignores a maximum amount of specific EEBUS `no data available` errors, and only propagates them if the error occured more often.
The error will come anyway, if evcc is startet while an EV is connected to the Elli wallbox!
* Check for connection before fetching data
* Check if an EV is connected first
This new check does not only check for the EEBUS charge state but also checks if a minimum dataset is available.
This helps in situations where the charge state already provides data, but measurements, loadlimits etc. are not yet available and thus cause evcc to return errors.
* Fix crash when no vehicle is assigned to loadpoint
* Update EEBUS cemd to v0.2.1
* Update error message
* Increase initial timeout to 90s
This should help Elli wallboxes a bit due to their software often crashing on first connection
* Update eebus libraries
- Update to intertermedia versions pending 0.1.7 release
- Fix crash when removing non existing entities
- Initiate connection via IP addresses before using hostname
- Update randomizer seed usage which fixes linter warning and still providing 1.18 compatibility
- Change log level for ev (dis)connect states
* Update charging limits if they changed
* Update eebus libraries to v0.1.7
* Migrate EEBUS to enbility/eebus-go
- adopt enbility/eebus-go library
- fully compatible with existing EEBUS setup
- centralize EEBUS certificate generation for configure and certificate creation cmds
- automatically utilizes native avahi mDNS setup if installed, which does not have missing IP issues as zeroconf library
- mDNS discovery and announcement is fully handled by the library
- improved double connection and reconnection handling over previous library
- logging now fully supported evcc log levels
- tested with Elli Connect and Porsche Mobile Charger Connect
