* 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
- Don’t use a timeout for reading spine messages
Receiving no SPINE messages is absolutely valid scenario and there should be no timeout to check this.
In fact this is the cause why the Elli chargers are disconnected after a 10 minute connection
- Remove (non) "Elli" workaround
