Yes it works, thank you

Sorry for the late reply. I haven't had time to test the profile.

Today I tested the template while the car was charging. I could not get any valid values.

CAN is online and responding, but I only get timeouts for the relevant PIDs.

@th84sl Have you tried this with the ignition on or off?

Hi all - wanted to follow up on this thread with more confirmation of a working profile. I have just connected a WiCAN-OBD-3 to my Vauxhall Corsa-e and can confirm the e-208 profile works just fine with this model too (expected since they are same car platform.) I can also confirm no adapter cable is required as I have updated my car firmware which enables the standard CAN bus pins (6,14) on the connector.

Now experimenting with exactly what state the car needs to be in to generate battery data - I can get a response for a short time just by pressing the lock button on the remote key fob even if the car is already locked - maybe only odometer data however? I get all data by unlocking the door and of course pressing 'start'. I begin to wonder if there is some CAN bus command to wake up the required ECU module that we can send from the meatPi... clearly the key fob receiver can do exactly this. I will update you on what I find.

Here is my evcc config for the car:

`vehicles:

• name: "mokkawican"
  title: "Mokka-WiCAN"
  type: custom

  soc:
  source: mqtt
  topic: "wican/mokka/soc"
  jq: '.soc'
  scale: 1 # No scaling needed if the SoC is already in percentage format
  timeout: 30s # Adjust as needed

  capacity: 46 # Akkukapazität in kWh (optional)
  icon: car # Icon in der Benutzeroberfläche (optional)
  phases: 3 # Die maximale Anzahl der Phasen welche genutzt werden können (optional)`

this, you have to setup mqtt for evcc aswell.... then this will read the SOC from the topic.

WiCAN config:

`Protocol: AutoPID
Automate: -> Custom PIDs:

Custom Initialisation:
ATZ;ATE0;ATH1;ATSP6;ATS0;ATM0;ATAT1;ATSH6B4;ATFCSH6B4;ATFCSD300000;ATFCSM1;ATCRA694;

Name Init PID Expression Period(ms) Type Send_to
soc 22D4101 (B4*256+B5)/512 1000 MQTT_Topic wican/mokka/soc`

@moritzklein Thanks a lot! I've made more progress than before. However, things aren't quite working yet. The SoC in MQTT Explorer never changes. In evcc I can't see the SoC at all and I get the notification "Garage: vehicle soc: outdated". Can you see what I did wrong?

Here's my yaml code, including mqtt lines:

mqtt:
  broker: 192.168.178.69:1883
  user: Astra801
  password: xxxxxxx

vehicles:
- name: opelastra
  type: custom
  title: Opel Astra
  capacity: 51
  soc:
    source: mqtt
    topic: wican/astra/soc
    jq: '.soc'
    timeout: 30s

@moritzklein Any idea?

@moritzklein Es war dann doch ganz einfach. Da in den "Vehicle Specific" in der WiCAN Konfiguration unter SOC der "Name: SOC" in Großbuchstaben steht, habe ich in der evcc.yaml lediglich in der Zeile jq: '.soc' auch den SOC groß geschrieben: jq: '.SOC'
Es klappt!
Natürlich mit der bekannten Einschränkung, dass der tatsächliche SoC vom ODB Adapter nur übermittelt wird, wenn die Zündung läuft. Zwar passiert das nur, wenn ich Zuhause ankomme, aber das reicht, denn ab da errechnet sich evcc den Wert selber und zeigt in der evcc-Oberfläche, was er soll. Allerdings bringt er jetzt weiterhin eine Fehlermeldung in orange: "Opel Astra: vehicle soc: outdated (ignored by estimator)" Umgehe diese Meldung, indem ich das timeout des soc in evcc.yaml auf 480m gesetzt habe.

@tqma1 do you these parameters in car scanner app?

This works now for me:

AT= Ambient temperature
BT= Battery temperature

  {
    "Name": "AT",
    "Init": "ATSH6A2;ATFCSH6A2;ATCRA682;",
    "PID": "22D4341",
    "Expression": "B4",
    "MinValue": "",
    "MaxValue": "",
    "Period": "5000",
    "Type": "Default",
    "Send_to": ""
  },
  {
    "Name": "BT",
    "Init": "ATSH6A2;ATFCSH6A2;ATCRA682;",
    "PID": "22D8EF1",
    "Expression": "B4",
    "MinValue": "",
    "MaxValue": "",
    "Period": "5000",
    "Type": "Default",
    "Send_to": ""
  },
  {
    "Name": "min_mV",
    "Init": "ATSH6B4;ATFCSH6B4;ATCRA694;",
    "PID": "22D86F1",
    "Expression": "[B4:B5]",
    "MinValue": "",
    "MaxValue": "",
    "Period": "5000",
    "Type": "Default",
    "Send_to": ""
  },
  {
    "Name": "max_mV",
    "Init": "ATSH6B4;ATFCSH6B4;ATCRA694;",
    "PID": "22D8701",
    "Expression": "[B4:B5]",
    "MinValue": "",
    "MaxValue": "",
    "Period": "5000",
    "Type": "Default",
    "Send_to": ""
  }

So is this profile correct and should work?

eUlysse.json

@tqma1 looks good but parameters "BT" "max_mV" "AT" "BT" should be added to params.json if they don't already exist