OBD2 to evcc with Wican, SoC, odo, etc.

[JabeBRD]

Bought Wican to retreive data from OBD2 over wifi, to be used in evcc with MQTT messages.
setup vehicle as custom

vehicles:
  - name: my_car
    type: custom
    title: Mein Auto # display name for UI
    capacity: 50 # byttery capacity (kWh)
    soc: # battery soc (%)
      source: # plugin type
      # ...
    status: # optional charge status (A..F)
      source: # plugin type
      # ...
    range: # optional electric range (km)
      source: # plugin type
      # ...
    odometer: # optional odometer (km)
      source: # plugin type
      # ...
    climater: # optional climate status (true/false)
      source: # plugin type
      # ...
    wakeup: # optional vehicle wake up command
      source: # plugin type
      # ...
    maxcurrent: # set charger max current (A)
      source: # plugin type
      # ...

Found some good info under this soc_helper tool https://forum.openwb.de/viewtopic.php?p=91886&sid=69c76a001924bcd539633a4807df0453#top

I have managed to get SoC and odometer reading from e-Up (2022) and Passat GTE (2020).
Both raw values are calculated in Home Assistant and send to evcc.

For e-Up request for soc {"bus":"0","type":"tx","frame":[{"id":2021,"dlc":8,"rtr":false,"extd":false,"data":[3,34,2,140,170,170,170,170]}]}
and for odometer, this requires two messages, first {"bus":"0","type":"tx","frame":[{"id":2021,"dlc":8,"rtr":false,"extd":false,"data":[3,34,2,189,170,170,170,170]}]} second { "bus": "0", "type": "tx", "frame": [{"id": 2021,"dlc": 8, "rtr": false, "extd": false, "data": [48,0,0,170,170,170,170,170]}]}

And for passat soc {"bus":"0","type":"tx","frame":[{"id":2015,"dlc":8,"rtr":false,"extd":false,"data":[2,1,91,170,170,170,170,170]}]}
odometer also two messages, first { "bus":"0","type":"tx","frame": [{"id": 402391163,"dlc": 8,"rtr": false, "extd": true, "data": [ 3, 34, 2, 189, 170, 170, 170, 170 ]}]} second {"bus":"0","type":"tx","frame":[{"id":402391163,"dlc": 8,"rtr": false,"extd": true,"data": [ 48, 0, 0, 170, 170, 170, 170, 170 ]}]}

For odometer messages received, first "data": [ 16, 13, 98, 2, 189, 86, AA, BB ], second "data": [ 33 ,CC , 0, 0, 91, 143, 105, 92 ] and calculated as AA*65536+BB*256+CC

Anyone using this? Would like to know how to enable climate, to heat car in winter times and read climate status, and how to read charge status (A..F) to be used in evcc.

[atze09]

Bought Wican to retreive data from OBD2 over wifi, to be used in evcc with MQTT messages. setup vehicle as custom

vehicles:
  - name: my_car
    type: custom
    title: Mein Auto # display name for UI
    capacity: 50 # byttery capacity (kWh)
    soc: # battery soc (%)
      source: # plugin type
      # ...
    status: # optional charge status (A..F)
      source: # plugin type
      # ...
    range: # optional electric range (km)
      source: # plugin type
      # ...
    odometer: # optional odometer (km)
      source: # plugin type
      # ...
    climater: # optional climate status (true/false)
      source: # plugin type
      # ...
    wakeup: # optional vehicle wake up command
      source: # plugin type
      # ...
    maxcurrent: # set charger max current (A)
      source: # plugin type
      # ...

Found some good info under this soc_helper tool https://forum.openwb.de/viewtopic.php?p=91886&sid=69c76a001924bcd539633a4807df0453#top

I have managed to get SoC and odometer reading from e-Up (2022) and Passat GTE (2020). Both raw values are calculated in Home Assistant and send to evcc.

For e-Up request for soc {"bus":"0","type":"tx","frame":[{"id":2021,"dlc":8,"rtr":false,"extd":false,"data":[3,34,2,140,170,170,170,170]}]} and for odometer, this requires two messages, first {"bus":"0","type":"tx","frame":[{"id":2021,"dlc":8,"rtr":false,"extd":false,"data":[3,34,2,189,170,170,170,170]}]} second { "bus": "0", "type": "tx", "frame": [{"id": 2021,"dlc": 8, "rtr": false, "extd": false, "data": [48,0,0,170,170,170,170,170]}]}

And for passat soc {"bus":"0","type":"tx","frame":[{"id":2015,"dlc":8,"rtr":false,"extd":false,"data":[2,1,91,170,170,170,170,170]}]} odometer also two messages, first { "bus":"0","type":"tx","frame": [{"id": 402391163,"dlc": 8,"rtr": false, "extd": true, "data": [ 3, 34, 2, 189, 170, 170, 170, 170 ]}]} second {"bus":"0","type":"tx","frame":[{"id":402391163,"dlc": 8,"rtr": false,"extd": true,"data": [ 48, 0, 0, 170, 170, 170, 170, 170 ]}]}

For odometer messages received, first "data": [ 16, 13, 98, 2, 189, 86, AA, BB ], second "data": [ 33 ,CC , 0, 0, 91, 143, 105, 92 ] and calculated as AA*65536+BB*256+CC

Anyone using this? Would like to know how to enable climate, to heat car in winter times and read climate status, and how to read charge status (A..F) to be used in evcc.

How did you transfer the soc to EVCC? MQTT publish, or can the soc automatically polled from EVCC?

[JabeBRD]

I used mqtt_statestream service on HA.
First setup sensor to get data and convert it to right format, then publish that sensor in mqtt for evcc to use, it will publish every time sensor updates.
There is beta firmware for Wican, that could do that also, havent use that.

Currently i have managed to get, while charging active

• soc (e-up, passat gte)
• odometer (e-up, passat gte)
• range (passat gte)
• status (e-up)

Still trying to figure status for Passat, range for e-up and climater for both.

[JabeBRD]

Just plain numbers, example 60.
https://github.com/user-attachments/assets/751c8590-1f4c-47cf-951a-ed7157fa0226

Looking at your screenshot, your value seems to contain \"60\"
How is your expression (mqtt filter) in wican setup?

[atze09]

Just plain numbers, example 60. https://github.com/user-attachments/assets/751c8590-1f4c-47cf-951a-ed7157fa0226

Looking at your screenshot, your value seems to contain \"60\" How is your expression (mqtt filter) in wican setup?

In mqtt it is a plain number that's why i am confused:
But here is my setup:

1. Wican Firmware 3.20 Filter:
   
2. Home assistant sensor in configuration YAML:
   • name: "Wican Corsa soc"
     unique_id: "sensor.wican_corsa_soc"
     state_topic: "wican/dc547550cd49/can/rx"
     value_template: "{{ value_json.SOC3|float()| round(0) }}"
     icon: mdi:battery
     unit_of_measurement: '%'
     payload_available: "true"
     payload_not_available: "false"
3. Automation for mqtt publish of soc as plain number:
   alias: wican soc publish
   description: ""
   trigger:

• platform: time_pattern
  seconds: /5
  condition: []
  action:
• service: mqtt.publish
  metadata: {}
  data:
  qos: "0"
  topic: wican/dc547550cd49/can/corsasoc2
  retain: true
  payload_template: " "{{ (states('sensor.wican_corsa_soc') | float | round(0)) }}""
  mode: single
  

4. EVCC Poll soc from mqtt

• type: custom
  title: Corsa24
  icon: car
  capacity: 46
  soc: # battery soc (%)
  source: mqtt
  topic: wican/dc547550cd49/can/corsasoc2
  identifiers:
  • 2
  • 3
  • 0
    name: ev8

Could you please provide your detailled config, or double check mine with yours?
Thank you!

[atze09]

Error is still the same:
[lp-1 ] ERROR 2024/08/16 07:52:24 vehicle soc: wican/dc547550cd49/can/corsasoc2 invalid: '"76"'

[JabeBRD]

You have double " " in mqtt publish payload_template, remove first and last symbol, then it should work.

[atze09]

You have double " " in mqtt publish payload_template, remove first and last symbol, then it should work.

You are the best it works! Thank you, didn't recognize it, stupid me.

[HaareistNase]

You can read the SOC direct from your brooker, if you published it somewhere as plain number
So I export the Soc again, after I read it from Wican.

Here my evcc.yaml.

vehicles:

- type: custom
  identifiers:
  - Upita
  name: ev2
  title: E-Up
  icon: car
  phases: 3
  capacity: 32
  soc:
    source: mqtt
    topic: export/e-up

@JabeBRD
How will you read climate-status from Wican, while Car is in Sleep-Mode? All the data can only be gathered while charging or when ignition is on.

[JabeBRD]

I havent got that part figured out yet.
Here https://www.goingelectric.de/wiki/VW-e-up-OBD2-SGBD
22 1D E6 should have that information, but i allways get 3 no request ad answer.
I read when charging.

[typxxi]

For climate control you need to get access to the comfort can bus which you can not via obd dongle
It can only be achieved via OCU unit or so and Thomas Karlsen is working on that

This will require a different approach and hardware I guess cause at the end he explains how to get access to the ocu which is behind the instrument cluster if I got it right - he says it should be easy but who knows.

Here is his connection described:
https://github.com/thomasakarlsen/e-golf-comfort-can/blob/main/pages/the-comfort-canbus.md#physically-connecting-to-the-comfort-canbus

[JabeBRD]

I got workaround for reading climater status, i read currents climater uses, when above 0 climater is active.
But id like to have possibility to read timers and change those. Havent had time to investigate that part.