Skip to content

Tire info not available #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lagge78 opened this issue Jan 7, 2025 · 4 comments
Closed

Tire info not available #22

lagge78 opened this issue Jan 7, 2025 · 4 comments
Labels
problem Something isn't working volvo api issue The issue is caused by a problem with the Volvo API

Comments

@lagge78
Copy link

lagge78 commented Jan 7, 2025

What happened?

Hello, great addon (coming from volvo2mqtt), love the possibility to remote start engine and have several accounts.

I have tested to add one XC40 MY25 and one XC60 MY24 and get around 70 entities per vehicles, but I dont get any tire info entities for either of the vehicles, I saw that tire status was mentioned on the info page so I thought I let you know.

Thanks!

API availability

OK

Car connection

Available

Additional information

No response

Diagnostics

No response

@lagge78 lagge78 added the problem Something isn't working label Jan 7, 2025
@thomasddn
Copy link
Owner

The problem is most likely related to the car's software. Since v3.3.16 I stopped receiving the tyre info.

The tyre info is also missing on https://www.volvocars.com/uk/account/my-cars/.

We'll have to wait until Volvo fixes it.

@thomasddn thomasddn added the volvo api issue The issue is caused by a problem with the Volvo API label Jan 7, 2025
@thomasddn thomasddn closed this as not planned Won't fix, can't repro, duplicate, stale Jan 7, 2025
@thomasddn thomasddn pinned this issue Jan 7, 2025
@thomasddn thomasddn marked this as a duplicate of #93 Feb 18, 2025
@Palmdale95
Copy link

Well, this is really interesting because the tire info is still sent over Volvo to mqtt. Just switched from there to your integration in the morning due to several issues and on my petrol car, the information is still present to your integration, but for my electric car it’s not in addition what I am missing is the time to end for charging which was presented by the MQTT at on as well. Any news on that topic Thanks for the great integration and keeping it up while the other has been deprecated due to your great work

@thomasddn
Copy link
Owner

I would be surprised if volvo2mqtt could still show the tyre information because it uses the same API as I do. You probably just see the latest value it received. To try out, you should deflate your tyre and see if the value changes. 😄 Jokes aside, it's probably model and/or car software version related. If I go to the website mentioned above, then I see "N/A" for tyre status.

You can create a helper sensor to get the time to end:

  1. Go to the helpers section in HA
  2. Click the "Create helper" button and choose Template and then "Template a sensor"
  3. Give it a name and choose "Timestamp" as device class
  4. Fill in the code below as the template. It will show end time in increments of 15 minutes. Replace the entity name with your entity name.
{% set charging_time = states('sensor.volvo_xc40_estimated_charging_time') | int(0) %}
{% if charging_time > 0 -%}
  {% set new_time = now() + timedelta(minutes=charging_time) %}
  {% set current_time = this.state | as_datetime %}
  {% if not current_time or (as_datetime(new_time) - current_time).total_seconds() | abs > 900 %}
    {{ new_time }}
  {% else %}
    {{ this.state }}
  {% endif %}
{%- else -%}
  {{ this.state }}
{%- endif %}

@Palmdale95
Copy link

Yeah, you are probably right. :-) Anyway thanks. I solved my topic with an automation and creating an input_datetime helper already.

alias: Ladeendzeit berechnen
description: Zeigt das Ladeende im Dashboard an, wenn der XC40 geladen wird
triggers:

  • entity_id: sensor.volvo_xc40_estimated_charging_time
    trigger: state
  • entity_id: sensor.volvo_xc40_charging_connection_status
    to: connection_status_disconnected
    trigger: state
    actions:
  • choose:
    • conditions:
      • condition: state
        entity_id: sensor.volvo_xc40_charging_connection_status
        state: connection_status_disconnected
        sequence:
      • target:
        entity_id: input_datetime.xc40_charging_endtime
        data:
        datetime: "1970-01-01 00:00:00"
        action: input_datetime.set_datetime
    • conditions:
      • condition: template
        value_template: >
        {{ states('sensor.volvo_xc40_charging_connection_status') !=
        'connection_status_disconnected' }}
        sequence:
      • target:
        entity_id: input_datetime.xc40_charging_endtime
        data:
        datetime: >
        {{ (now() +
        timedelta(minutes=states('sensor.volvo_xc40_estimated_charging_time')
        | int)).strftime('%Y-%m-%d %H:%M:%S') }}
        action: input_datetime.set_datetime
        mode: single

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working volvo api issue The issue is caused by a problem with the Volvo API
Projects
None yet
Development

No branches or pull requests

3 participants