Thank you for building this integration, it works flawless.
I’d like to contribute my lovelace representation.
Features are:
- Minimalist design suitable for mobile, using the HACS multiple-entity-row card and conditional cards
- Traffic sensor using the Waze Travel Time integration, conditional on whether I am home or not.
- Since the VW API is not the best one in the world, I included more last-updated information (both of when you started the climatization and when VW last acknowledged that through a change of the climatization state)
Please excuse the Dutch and my car name 
- The car is not charging but is climatizing
- the car is charging but not cooling
type: entities
entities:
- type: conditional
conditions:
- entity: binary_sensor.volkswagen_id_wolkje_plug_connection_state
state: 'on'
row:
entity: sensor.volkswagen_id_wolkje_state_of_charge
type: custom:multiple-entity-row
name: Laadpercentage
icon: mdi:ev-plug-type2
secondary_info:
entity: sensor.volkswagen_id_wolkje_range
name: 'Bereik:'
unit: km
- type: conditional
conditions:
- entity: binary_sensor.volkswagen_id_wolkje_plug_connection_state
state: 'off'
row:
entity: sensor.volkswagen_id_wolkje_state_of_charge
name: Laadpercentage
type: custom:multiple-entity-row
secondary_info:
entity: sensor.volkswagen_id_wolkje_range
name: 'Bereik:'
unit: km
- type: conditional
conditions:
- entity: sensor.volkswagen_id_wolkje_charging_state
state: charging
row:
entity: sensor.volkswagen_id_wolkje_target_state_of_charge
type: custom:multiple-entity-row
name: Te laden
unit: '%'
entities:
- entity: sensor.volkswagen_id_wolkje_charge_power
name: Vermogen
- entity: sensor.volkswagen_id_wolkje_charge_rate
name: Snelheid
- entity: sensor.volkswagen_id_wolkje_remaining_charging_time
name: Resterend
- entity: button.volkswagen_id_wolkje_start_climate
type: custom:multiple-entity-row
name: Airco aan/uit
show_state: false
secondary_info:
entity: sensor.volkswagen_id_wolkje_climatisation_state
attribute: last-updated
name: 'VW Server:'
entities:
- entity: button.volkswagen_id_wolkje_start_climate
attribute: last-updated
name: Aan- / uitgezet
- type: conditional
conditions:
- entity: sensor.volkswagen_id_wolkje_climatisation_state
state_not: 'off'
row:
entity: sensor.volkswagen_id_wolkje_climatisation_state
type: custom:multiple-entity-row
name: Airco
icon: mdi:thermometer-lines
entities:
- entity: binary_sensor.volkswagen_id_wolkje_front_window_heating_state
name: Voorruit
icon: mdi:car-windshield
state_color: true
- entity: binary_sensor.volkswagen_id_wolkje_rear_window_heating_state
name: Achterruit
icon: mdi:car-windshield
state_color: true
- entity: binary_sensor.volkswagen_id_wolkje_zone_front_left_enabled
name: Linksvoor
icon: mdi:chair-rolling
state_color: true
- entity: binary_sensor.volkswagen_id_wolkje_zone_front_right_enabled
icon: mdi:chair-rolling
name: Rechtsvoor
state_color: true
- type: conditional
conditions:
- entity: person.jelle
state: home
row:
entity: sensor.naar_kantoor
type: custom:multiple-entity-row
icon: mdi:office-building-marker
title: Wolkje
state_color: true
show_header_toggle: false
EDIT: Updated the climatizing line since I’ve now used it a few times. The switch on the right hand side wasn’t working properly, the button to press to activate the climatization is now the icon in the left-most column.
Note the Waze integration is having some stability issues, I wanted to add a last-updated for this but the entity does not have that attribute.
2 Likes
After the first installation i entered username and password and i get this error, Any ideas?
Version 0.0.13
Any help here please trying to set up for 1st time with no luck.
ID4 arrived at weekend using the we connect id app which has been working fine.
integration installed via hacs V4.4.54 fill in all the login details where i get msg “Could not login to Volkswagen We Connect, please check your credentials and verify that the service is working”
trying for 3 day same msg every time, im in the UK (England) using alpha-2 code of GB only thing i can think is if a different sever is being used and that should be the code for somewhere eles?
can you get GitHub - tillsteinbach/VWsFriend: VW WeConnect visualization and control to work?
if not, then the problem is most likely with your crendetials and/or account.
what do you mean by “using alpha-2 code”?
there also seem to be connection problems with we connect currently (see Volkswagen ID. Drivers Club | Facebook) - maybe you are affected by those
thanks for the reply ill look in to the GitHub - tillsteinbach/VWsFriend: VW WeConnect visualization and control now.
regards alpha-2 its the last box on the login that the integration asks for.
hello everyone, brand new under HA, this is my first integration! and… i did it!!! 
thank you for all the posts that allowed me to understand almost everything!
small question: is it possible to activate or not a charge?
Many thanks again!!!
SOLVED
I was using the Android application We Connect ID and I had made all the registrations from the application
Instead, you must explicitly accept the terms of contract and service that appear by going to the myvolkswagen.de site even if you are from other countries such as Italy in my case.
2 Likes
Is there any plans to implement a controller to start and stop changing. Like to toggle in the We Connect ID app?
1 Like
Just forget it. It’s allready there
1 Like
I have scoured and scoured and still cant figure this out. How do you get charging control to start and stop charging?
1 Like
As above - I found it!
1 Like
You need to call a service for this function, the API is to slow to make it into a switch 
service: volkswagen_we_connect_id.volkswagen_id_start_stop_charging
data:
vin: WVGZZZA1ZMP001337
start_stop: start
service: volkswagen_we_connect_id.volkswagen_id_start_stop_charging
data:
vin: WVGZZZA1ZMP001337
start_stop: stop
2 Likes
Hi - I really like this integration, thanks. It’s saved me from the serious bugs in ID 2.4 that stop the car based charge timing from work.
I do seem to have an issue in that it stops working after a couple of days and in order to get it to work again I need to restart HA. The debug logging shows no failures, it just stops.
All my other HA integrations carry on working ok.
I’m on HA 10.4 and OS 9.2 with the component integrated through HACS.
Is there any additional debugging that I can do to try and resolve the issue?
Thanks.
Hey @hassio40 I have the same error, can you please tell me where exactly i can accept the terms of contract and service
I suggest you remove your car’s vin number from public display!
Can anyone see the values of this sensor? It is always unknown to me…
‘sensor.id_3_pure_performance_odometer_in_kilometers’
even in miles.
This value is not exposed in <3.0 software. So likely you are still on 2.4?