Not working for eUP! after migrated to the new Volkswagen API

AlexJacu commented 11 months ago

Is your feature request related to a problem? Please describe. After closing old API and migrate eUP! to new API the eUP is not working using this integration

wherzig commented 2 months ago

You may try what I did today:

volkswagen_we_connect_id # diff -u __init__.py.old __init__.py
--- __init__.py.old 2024-08-17 12:51:01.000000000 +0200
+++ __init__.py 2024-08-17 17:03:49.029374797 +0200
@@ -33,7 +33,7 @@

 _LOGGER = logging.getLogger(__name__)

-SUPPORTED_VEHICLES = ["ID.3", "ID.4", "ID.5", "ID. Buzz", "ID.7 Limousine"]
+SUPPORTED_VEHICLES = ["ID.3", "ID.4", "ID.5", "ID. Buzz", "ID.7 Limousine", "e-up!"]

 @dataclass
@@ -67,6 +67,8 @@
         for vin, vehicle in _we_connect.vehicles.items():
             if vehicle.model.value in SUPPORTED_VEHICLES:
                 vehicles.append(vehicle)
+            else:
+                _LOGGER.error("UNSUPPORTED vehicle '%s'. Skipped ", vehicle.model.value)

         domain_entry: DomainEntry = hass.data[DOMAIN][entry.entry_id]
         domain_entry.vehicles = vehicles

volkswagen_we_connect_id # diff -u number.py.old number.py
--- number.py.old   2024-08-17 12:51:01.000000000 +0200
+++ number.py   2024-08-17 14:03:03.521105950 +0200
@@ -77,7 +77,7 @@
         return int(
             get_object_value(
                 self.data.domains["charging"]["chargingSettings"].targetSOC_pct.value
-            )
+            ) or 0
         )

     async def async_set_native_value(self, value: float) -> None:

Problem was that e-Up does not support self.data.domains["charging"]["chargingSettings"].targetSOC_pct.value .

Right now many of the sensors seem to work:

Not all Sensors are supported. I did also not test if there is any way to change configuration.

And yes. It is just a quick hack. No warranty!

But for me it seems sufficient.

wherzig commented 2 months ago

mitch-dc / volkswagen_we_connect_id

Not working for eUP! after migrated to the new Volkswagen API #227