Fix for duplicate (& orphan) devices

Fix for issue #14

Thanks @IngmarStein for reporting this - learned something new about HA today ;-)

Cause of recent changes in the identifiers object (of the DeviceEntry) (multiple) orphan devices might have been created - these orphan entries will be removed automatically with this release (cleanup could take a couple of seconds after the HA restart)

BREAKING CHANGE! (but only for users of multiple go-eChargers)

The DeviceRegistry Identifier has been changed (again) - this will create a new DeviceRegistry Entry per configured Charger - So IF you have multiple go-eChargers in your HA installation - you must adjust your automations (again) - since the deviceid's going to change - I am sorry for this inconvenience.

BREAKING CHANGE! (but only for users of multiple go-eChargers)

I have decided for an alternative (better) approach to support sending surplus PV data to multiple go-eChargers
#13

With the new implementation the Service GUI mode will work again - also if multiple configurations of the integration are configured (in order to support multiple chargers (with different serial numbers).

So IF you have multiple go-eChargers in your HA installation - you must adjust your automations (again) - I am sorry for this inconvenience.

Features Requests #12 #13 implemented [v2]

#13 - Surplus data with multiple goechargers
#12 - Add 'cll' (Current Limit List)

Features Requests #12 #13 implemented

#13 - Surplus data with multiple goechargers
#12 - Add 'cll' (Current Limit List)

Adjustments for latest HA release (get rid of warning)

2024.7.0

use 'async_forward_entry_setups' & 'async_unload_platforms'

Added Cloud-API Support

When your Wallbox is not part of your HA-Network, then you can now make use of the Cloud API Version of this integration.
https://github.com/goecharger/go-eCharger-API-v2/blob/main/cloudapi-en.md

Please note, that might be that not all features are supported [I am currently aware of the RESET functionality - but there might be more]

Solves #8

Just maintenance

Just discovered that binary sensors can have device classes - so just let use them

Adjustments to latest go-eCharger App

The latest go-eCharger app have some additional settings/fields:

• go-eController-Scan always active
• last Controller-Scan
• Random max. delays:
  • Scheduler start
  • Scheduler end
  • Flexible Tariff start
  • Flexible Tariff stop
  • After power outage

• adjustments to the documentation (new screenshots, how to enable local HTTP API v2)

Fix: Detected blocking call to open inside the event loop by custom integration

removed 'local' reading of manifest.json

+fix-it

Little update

'Simulate unplugging (short)' is now enabled by default (and 'Simulate unplugging permanently' is now hidden by default)