- 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)
- Fixes and improvements regarding connection handling, e.g. handling reconnections
- Fixes a second EEBUS wallbox going into fallback mode when both had an EV connected and one of the EVs was disconnected
- Fixes for LPC and LPP nominal max value usage
If a websocket connection was closed, e.g. due to i/o timeout error or remotely denied connection attempt, then a reconnect was only initiated if the remote service announced its mDNS entry again and the code relied on the remote service to initiate the connection. Especially the Elli Connect/Pro devices do not do that, and this situation can appear if the device is connected via WLAN.
This update now uses to currently known mDNS entries upon a disconnect to initiate a connection itself.
- 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
Update EEBUS spine-go library to send heartbeat messages 1s earlier than needed. Maybe the Elli sofware interprets the heartbeat not according to the spec and wrongly falls back into failsafe mode.
Maybe this also helps with Elli Gen 1 issues reported in https://github.com/evcc-io/evcc/issues/14839
Update EEBUS library to not actively send read messages if measurement values provide no or an “old” timestamp.
Maybe this also helps with Elli Gen 1 issues reported in https://github.com/evcc-io/evcc/issues/14839
- 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.
