Audi MMI support

Hi Fabio,
here is the code for my cards…

First card:

type: vertical-stack
title: Audi Q5 55 Sportback TFSI e
cards:
  - type: entities
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_model
        name: Model
      - entity: sensor.audi_q5_sportback_tfsi_e_last_update
        name: Last Update
  - type: entities
    entities:
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_doors
        name: Doors
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_hood
        name: Hood
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_trunk
        name: Trunk
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_windows
        name: Windows
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_sun_roof
        name: Sun roof
      - entity: sensor.audi_q5_sportback_tfsi_e_doors_trunk_state
        name: Doors/trunk state
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_doors_lock
        name: Doors lock
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_trunk_lock
        name: Trunk lock
      - entity: binary_sensor.audi_q5_sportback_tfsi_e_parking_light
        name: Parking light
  - type: entities
    entities:
      - entity: lock.audi_q5_sportback_tfsi_e_door_lock
        name: Door lock
  - type: entities
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_climatisation_state
        name: Climatisation state

Second card:

type: vertical-stack
cards:
  - type: entities
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_mileage
        name: Mileage
      - entity: sensor.audi_q5_sportback_tfsi_e_service_inspection_distance
        name: Service inspection distance
      - entity: sensor.audi_q5_sportback_tfsi_e_service_inspection_time
        name: Service inspection time
      - entity: sensor.audi_q5_sportback_tfsi_e_oil_change_distance
        name: Oil change distance
      - entity: sensor.audi_q5_sportback_tfsi_e_oil_change_time
        name: Oil change time
  - type: entities
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_range
        name: Total range
      - entity: sensor.audi_q5_sportback_tfsi_e_primary_engine_type
        name: Primary engine type
      - entity: sensor.audi_q5_sportback_tfsi_e_primary_engine_range
        name: Primary engine range
      - entity: sensor.audi_q5_sportback_tfsi_e_tank_level
        name: Tank level
      - entity: sensor.audi_q5_sportback_tfsi_e_secondary_engine_type
        name: Secondary engine type
      - entity: sensor.audi_q5_sportback_tfsi_e_secondary_engine_range
        name: Secondary engine range
      - entity: sensor.audi_q5_sportback_tfsi_e_state_of_charge
        name: State of charge
  - type: entities
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_max_charge_current
        name: Max charge current
      - entity: sensor.audi_q5_sportback_tfsi_e_charging_state
        name: Charging state
      - entity: sensor.audi_q5_sportback_tfsi_e_plug_state
        name: Plug state
      - entity: sensor.audi_q5_sportback_tfsi_e_remaining_charge_time
        name: Remaining charge time

Third card:

type: picture-elements
image: /local/audi_q5_55_tfsie.png
style: |
  ha-card {
    border-radius: 10px;
    border: solid 1px rgba(100,100,100,0.3);
    box-shadow: 3px 3px rgba(0,0,0,0.4);
    overflow: hidden;
    width: 120%;
    --my-color-door: {% if states('sensor.audi_q5_sportback_tfsi_e_doors_trunk_state') == "Open" %} yellow {% else %} white {% endif %};
    --my-color-window: {% if states('binary_sensor.audi_q5_sportback_tfsi_e_windows') == "Open" %} yellow {% else %} white {% endif %};
  } 
elements:
  - type: image
    image: /local/bg2.png
    style:
      left: 50%
      top: 90%
      width: 100%
  - type: icon
    icon: mdi:car-door
    entity: sensor.audi_q5_sportback_tfsi_e_doors_trunk_state
    tap_action: more_info
    style:
      color: white
      left: 10%
      top: 86%
      size: 100%
  - type: state-label
    entity: sensor.audi_q5_sportback_tfsi_e_doors_trunk_state
    state_color: false
    style:
      left: 10%
      top: 95%
      color: var(--my-color-door)
  - type: icon
    icon: mdi:window-closed
    entity: binary_sensor.audi_q5_sportback_tfsi_e_windows
    tap_action: more_info
    style:
      color: white
      left: 30%
      top: 86%
  - type: state-label
    entity: binary_sensor.audi_q5_sportback_tfsi_e_windows
    state_color: false
    style:
      color: var(--my-color-window)
      left: 30%
      top: 95%
  - type: icon
    icon: mdi:oil
    entity: sensor.audi_q5_sportback_tfsi_e_oil_change_time
    tap_action: more_info
    style:
      color: white
      left: 50%
      top: 86%
  - type: state-label
    entity: sensor.audi_q5_sportback_tfsi_e_oil_change_time
    state_color: false
    style:
      color: white
      left: 50%
      top: 95%
  - type: icon
    icon: mdi:room-service-outline
    entity: sensor.audi_q5_sportback_tfsi_e_service_inspection_distance
    tap_action: more_info
    style:
      color: white
      left: 70%
      top: 86%
  - type: state-label
    entity: sensor.audi_q5_sportback_tfsi_e_service_inspection_distance
    style:
      color: white
      left: 70%
      top: 95%
  - type: icon
    icon: mdi:speedometer
    entity: sensor.audi_q5_sportback_tfsi_e_mileage
    tap_action: more_info
    style:
      color: white
      left: 90%
      top: 86%
  - type: state-label
    entity: sensor.audi_q5_sportback_tfsi_e_mileage
    style:
      color: white
      left: 90%
      top: 95%
  - type: custom:circle-sensor-card
    entity: sensor.audi_q5_sportback_tfsi_e_tank_level
    max: 100
    min: 0
    stroke_width: 15
    gradient: true
    fill: '#909090'
    name: tank
    font_style:
      font-size: 1.0em
      color: white
    style:
      top: 5%
      left: 0%
      width: 85px
      transform: none
  - type: custom:circle-sensor-card
    entity: sensor.audi_q5_sportback_tfsi_e_state_of_charge
    max: 100
    min: 0
    stroke_width: 15
    gradient: true
    fill: '#909090'
    name: charge
    font_style:
      font-size: 1.0em
      color: white
    style:
      top: 5%
      left: 85%
      width: 85px
      transform: none
  - type: custom:bar-card
    name: Range
    direction: up
    width: 20px
    min: 0
    max: 600
    style:
      top: 55%
      left: 8%
    card_mod:
      style: |
        ha-card {
          background: transparent;
          border-style: none;
          border: 0px;
          box-shadow: none;
        }
    positions:
      icon: 'off'
      indicator: 'off'
      name: outside
      value: outside
    severity:
      - color: green
        from: 150
        to: 600
      - color: orange
        from: 50
        to: 150
      - color: red
        from: 0
        to: 50
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_range
  - type: custom:bar-card
    name: Range
    direction: up
    width: 20px
    min: 0
    max: 60
    style:
      top: 55%
      left: 92%
    card_mod:
      style: |
        ha-card {
          background: transparent;
          border-style: none;
          border: 0px;
          box-shadow: none;
        }
    positions:
      icon: 'off'
      indicator: 'off'
      name: outside
      value: outside
    severity:
      - color: green
        from: 20
        to: 60
      - color: orange
        from: 10
        to: 20
      - color: red
        from: 0
        to: 10
    entities:
      - entity: sensor.audi_q5_sportback_tfsi_e_secondary_engine_range
1 Like

So - since some days I can’t start/login the integration anymore. I tried to use several forks (as suggested in the thread) - no success either.
Anybody has an idea how to fix this ?

@gotschi

I just installed ioBroker again and at least a can start the VW instance - also login is successful. Probably not data yet because the ignition is off at the moment.

However- how do you connect the ioBroker instance to the MQTT broker (this is the HA integration, isn’t it ?) ?

setup the mqtt broker (server) in iobroker and bridge your main mqtt to the iobroker one.

you can do this via

connection bridge-01
address iobroker:9883

topic iobrokervw-connect/# both 0

else you can also feed your main broker by using the iobroker mqtt as client but that made trouble for me.

@laola

Is it fair to say that this integration no longer works in the states? Mine hasn’t worked or connected for months. Assuming this is another removal and decrease in features we can use like the demise of MYQ.

It works for me (in the UK).

I don’t want it to be removed obviously but it definitely looks like Audi like to change things regularly to make it hard for the integration to keep working.

There are 2 integrations which still work.
GitHub - arjenvrh/audi_connect_ha: Adds an audi connect integration to home assistant and GitHub - cyr-ius/hass-audiconnect: Adds an audi connect integration to home assistant

Thanks. Tried the second one that wasn’t 4 years old and asking for someone to take it over. Setup but found no cars.

Hi , also purchased Audi, I see indeed 2 integrations… witch one is the most stable/best ? I see they are both active?

This integration uses the latest audi api and is working.

1 Like

do you have a q4 etron? did you try “on demand” functions from myaudi app ? this should be hackable too , right? :slight_smile:

I have a regular etron. I have not tried the on demand functions yet.

ok,

what options can you enable on demand?

the options on demand require credit card payment or something similar. I doubt this is something you can do through the integration.
But the packs I see are:
Light technology
Driver Assistance Systems
Audi Connect

Ah, don’t have the Q4 yet, ordered yesterday:-)

What are those driver assistance systems?

So, looks like the audi_connct_ha is alive again, was a release 3 days ago. I am still using the fork hass_audiconnect (that currently doesn’t work) but is now wondering if I should switch back to audi_connect_ha. Anyone knows?

i’m back on audi_connect_ha, it’s being maintained and under development by multiple people to get all functionality working again.

1 Like

That’s great… Does anyone have the Q4 E-tron? Does it work ?

I’ve tried re-installing audi_connect-ha, but when I do the configuration screen (Register your account), it says:" user_already_configured". This prevents the integration from getting installed.

I deleted all audi connect files under custom components, but don’t know where this audi “user” is stored.

Any suggestions?
Thanks!

Maybe you need to restart HA first?