Wow! How is it possible I never heard about Tronity before? Gives you so much more info than the My Cupra app, and best of all I can link it to ABRP to have a realtime SOC without needing to use an OBD dongle. And yes, it is still free for Born owners, at least for now.Elea4 wrote:People also use Tronity for the same purpose. For a while (maybe still?) Tronity was free for Born owners
Cupra Born Support in Home Assistant
- mluisbrown
- Posts: 202
- Joined: Wed Mar 08, 2023 4:46 pm
- Location: Lisbon, Portugal
2023 Born 58kWh, Glacial White, 19" Typhoon Copper, Skyline, Blue Dinamica electric seats, Cargo, Privacy, Pilot M+, Tech M
2003 Audi A3 8L 1.9TDi PD 130 with 360,000kms.
2003 Audi A3 8L 1.9TDi PD 130 with 360,000kms.
Latest version of the HA custom component here with various fixes to support older cars more effectively: https://github.com/daernsinstantfortres ... upport.zip
And no, I've not found any way to extract historical data from the APIs, which only ever return the current status of the vehicle. If you're collating in HA, you have a lot more control over what you do with this data of course!
And no, I've not found any way to extract historical data from the APIs, which only ever return the current status of the vehicle. If you're collating in HA, you have a lot more control over what you do with this data of course!
- mluisbrown
- Posts: 202
- Joined: Wed Mar 08, 2023 4:46 pm
- Location: Lisbon, Portugal
It seems like Tronity also cannot collect historical data. But Tronity collates it for you and allows you to export it too.
2023 Born 58kWh, Glacial White, 19" Typhoon Copper, Skyline, Blue Dinamica electric seats, Cargo, Privacy, Pilot M+, Tech M
2003 Audi A3 8L 1.9TDi PD 130 with 360,000kms.
2003 Audi A3 8L 1.9TDi PD 130 with 360,000kms.
Don't use it myself, but I'm quite sure it would work just fine as node red is just an orchestration layer on top of the normal HA entities. Interested to hear your own experiences when your car turns up.
-
- Posts: 29
- Joined: Mon Apr 24, 2023 2:33 pm
I got a bit confused by trying this via HACS first, but then worked perfectly once I just downloaded the ZIP and installed manually. Great to see support for our new Born in HA, so thanks very much for your efforts on this @daern.
I notice in a previous screenshot that there are controls for heating, charging, and Stop Climate. I only get controls for the climate and charging targets. Are these extra switches or should they be there by default? Thanks!
I notice in a previous screenshot that there are controls for heating, charging, and Stop Climate. I only get controls for the climate and charging targets. Are these extra switches or should they be there by default? Thanks!
Born V2, 77kW, e-Boost, Vapour Grey
Yes, HACS not supported and makes a bit of a mess. Need to fix this at some point...
They are actually buttons that you can add to the dashboard: button.cupra_born_start_climate, button.cupra_born_stop_climate, button.cupra_born_start_charging and button.cupra_born_stop_charging
Personally, I wrap these into template switches instead which gives a nicer UI:
Code: Select all
switch:
- platform: template
switches:
car_heating:
friendly_name: "Heating"
value_template: "{{ is_state('sensor.cupra_born_climatisation_state', 'heating') }}"
turn_on:
service: button.press
target:
entity_id: button.cupra_born_start_climate
turn_off:
service: button.press
target:
entity_id: button.cupra_born_stop_climate
icon_template: >-
{% if is_state('sensor.cupra_born_climatisation_state', 'heating') %}
mdi:radiator
{% else %}
mdi:radiator-off
{% endif %}
- platform: template
switches:
car_charging:
friendly_name: "Charging"
value_template: "{{ states('sensor.cupra_born_charging_state') in ['charging'] }}"
turn_on:
service: button.press
target:
entity_id: button.cupra_born_start_charging
turn_off:
service: button.press
target:
entity_id: button.cupra_born_stop_charging
icon_template: >-
{% if states('sensor.cupra_born_charging_state') in ['charging'] %}
mdi:car-electric
{% else %}
mdi:car-outline
{% endif %}
-
- Posts: 29
- Joined: Mon Apr 24, 2023 2:33 pm
Ooh, I didn't know template switches were even a thing. That's brilliant. I've added the buttons successfully, but you're right about the switches being nicer. I'll give it a go. Thanks!
Born V2, 77kW, e-Boost, Vapour Grey
To be fair, because of the enormous latency between issuing a command to the Born and it responding to say that it's accepted it, the template switches do behave a little weirdly. When you click on it, it moves briefly to "on" (which triggers the command to the car), but then returns to its original position and remains there until the car responds to accept the change, at which point the switch will move to the "on" position. The same then happens when you switch it off again. It really needs a three position switch with a "pending" state, but to be fair, I've not really looked into how this could be done although, knowing HA, someone out there will have done it!
-
- Posts: 29
- Joined: Mon Apr 24, 2023 2:33 pm
Ah OK, makes sense. I've just installed slider-entity-row which looks like it could handle a tri-state setup - it's currently showing my zappi charging mode (four options), but it seems to act solely as an input selector to change the state, rather than reflecting the current state too. My zappi is charging at the moment, but the slider just shows the most recent value assigned to it, rather than the current state of the sensor:
Born V2, 77kW, e-Boost, Vapour Grey