Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various non-working channels in CarNet for VW E-Up (2022) #10

Open
kaaresl opened this issue Nov 6, 2022 · 0 comments
Open

Various non-working channels in CarNet for VW E-Up (2022) #10

kaaresl opened this issue Nov 6, 2022 · 0 comments

Comments

@kaaresl
Copy link

kaaresl commented Nov 6, 2022

First of all: Thank you for this binding. With this I'm mostly able to get feature parity with the information and control in the native We Connect app.

But there are some channels that isn't working or responding as expected on my E-Up. I use the 20220930 snapshot org.openhab.binding.connectedcar-3.3.0-SNAPSHOT.jar. The channels are:

  • status#maintenanceRequired: This is always ON, though no indication of required service is shown in the car or in We Connect.
  • status#vehicleLights: No data, always NULL.
  • status#parkingLight: Ditto. Always NULL. This is reported in We Connect, so I assume it should be available.
  • control#climater: Dumps error to log. More on this below.
  • control#targetTemperature: This is a read only value on this binding, though I am able to set the climater temp in We Connect.
  • status#doorsClosed: No data. Always NULL. Not sure if this supposed to work. The individual doors, hood and hatch are reported correctly.
  • control#targetChgLvl: Unable to control, always NULL.
  • control#charge: It works, but dumps error to log. More on this below.

The control#climater channel error

This is the most important show-stopper. Automating or controlling the climate from openhab is a must have.

When turning this on and off the following error log is dumped:

2022-11-06 22:37:28.402 [INFO ] [ar.internal.handler.ThingBaseHandler] - VW_EUp: Status from service rclima_v1.P_START_CLIMA_EL: API call failed POST https://msg.volkswagen.de/fs-car/bs/climatisation/v1/VW/DE/vehicles/****/climater/actions (HTTP 400 Bad Request), result = {"error":{"errorCode":"gw.error.validation","description":"Invalid payload"}}

The error code, pretty printed:

{
    "error": {
        "errorCode": "gw.error.validation",
        "description": "Invalid payload"
    }
}

The control#charge error

When flipping this switch, the following stack trace is dumped to log:

2022-11-06 23:03:06.510 [WARN ] [ar.internal.handler.ThingBaseHandler] - VW_EUp: General Error: queuePendingAction(): requestId must not be empty!
java.lang.IllegalArgumentException: queuePendingAction(): requestId must not be empty!
        at org.openhab.binding.connectedcar.internal.api.ApiRequestQueue.queuePendingAction(ApiRequestQueue.java:70) ~[bundleFile:?]
        at org.openhab.binding.connectedcar.internal.api.carnet.CarNetApi.queuePendingAction(CarNetApi.java:531) ~[bundleFile:?]
        at org.openhab.binding.connectedcar.internal.api.carnet.CarNetApi.sendAction(CarNetApi.java:510) ~[bundleFile:?]
        at org.openhab.binding.connectedcar.internal.api.carnet.CarNetApi.controlCharger(CarNetApi.java:405) ~[bundleFile:?]
        at org.openhab.binding.connectedcar.internal.handler.CarNetVehicleHandler.handleBrandCommand(CarNetVehicleHandler.java:105) ~[bundleFile:?]
        at org.openhab.binding.connectedcar.internal.handler.ThingBaseHandler.handleCommand(ThingBaseHandler.java:311) [bundleFile:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
        at org.openhab.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [bundleFile:?]
        at com.sun.proxy.$Proxy432.handleCommand(Unknown Source) [?:?]
        at org.openhab.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:80) [bundleFile:?]
        at org.openhab.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:48) [bundleFile:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
        at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]

But the car do respond to starting and stopping the charger, so this trace is related to something else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant