Last Update Time Sensors?

[Ilpo55]

Is this correct idea?

I have two last_update_time template sensors.

last_update_time_api
This sensor use api_timestamp of
sensor.volvo_xc40_average_energy_consumption
This api_timestamp is updated every time when the api-call to server has been sucessfull.

last_update_time_car
This sensor use api_timestamp of
sensor.volvo_xc40_charging_connection_status
This api_timestamp is updated every time when the car had a connetion to the api server.

[thomasddn]

Good catch with sensor.volvo_xc40_average_energy_consumption! A bit weird though that the API returns the current timestamp for each request.

I'm not sure about the sensor.volvo_xc40_charging_connection_status. Does that also update if the car is not charging?

You can put this in the Developer Tools > Template box to see all timestamps.

{% for ent in device_entities(device_id('sensor.volvo_xc40_average_energy_consumption')) %}
  {{ state_attr(ent, "friendly_name") }}: {{ state_attr(ent, "api_timestamp") }}
{%- endfor %}

[ivanfmartinez]

I think that with sort we can understand better how the data cames from car and API

{% set data = namespace(list=[]) %}
{% for ent in device_entities(device_id('sensor.volvo_YOUR_CAR_ID_average_energy_consumption')) %}
{% set data.list = data.list + [(state_attr(ent, "api_timestamp") | string) + " : " + state_attr(ent, "friendly_name")]  %}
{%- endfor %}
{% for l in ( data.list | sort) %}
{{ l }}
{%- endfor %}

For me also the avg enrgy comsumption appear to have wrong timestamp showing the update/request time.

Today I just connected the car on the charger and opened the door to show for a person, only this entities updated that time

2025-01-10 13:23:28.899000+00:00 : Volvo XXXXX Car connection
2025-01-10 13:23:28.899000+00:00 : Volvo XXXXX Engine status
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Central lock
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Door front left
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Door front right
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Door rear left
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Door rear right
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Hood
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Reduced guard lock
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Sunroof
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Tailgate
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Tank lid
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Window front left
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Window front right
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Window rear left
2025-01-10 13:27:27.028000+00:00 : Volvo XXXXX Window rear right
2025-01-10 13:27:31+00:00 : Volvo XXXXX Battery charge level
2025-01-10 13:27:31+00:00 : Volvo XXXXX Charging connection status
2025-01-10 13:27:31+00:00 : Volvo XXXXX Charging status
2025-01-10 13:27:31+00:00 : Volvo XXXXX Est. charging time
2025-01-10 13:27:31.671000+00:00 : Volvo XXXXX Distance to empty battery

[ivanfmartinez]

@thomasddn looking at this dates I found other thing :

The API request count are using the config_entry date like battery capacity, I understand that capacity does not change without reconfiguration, but the request count should use the current timestamp to indicate the real time where it was updated.

That should be the newest time from the integration component as it is updated after all calls are made.

[thomasddn]

I need to use another attribute for timestamp that don't come from the API, because that is misleading. It was already on my todo list. Battery capacity does not change at all (I think, unless it will show its degeneration, but I would be surprised if they did that).

[ivanfmartinez]

@Ilpo55 I have made some tests and if you want the time that the information was updated by integration you can use the last_reported value https://www.home-assistant.io/docs/configuration/state_object/

The api_count should be updated every time even if some of the requests fail. This can be a reference if the integration is ALIVE

{{ states['sensor.volvo_XXXXX_api_request_count'].last_reported }}

Also someone maybe want to know the newest and oldest timestamps that came from API, newest timestamp I think that is a good reference from last time car was "seen" by the volvo servers, maybe this can be a good sensor to have on the integration instead of making by template (what you think @thomasddn ?)

When testing this I found that now my car have not updated any information for more than 12 hours while its parked this night.

{% set entity = 'sensor.volvo_XXXXX_average_energy_consumption' -%}
{%- set data = namespace(list=[]) -%}
{%- for ent in ( device_entities(device_id(entity)) | reject('match','.*(api_request_count|average_energy_consumption)') | list) -%}
{%- if (state_attr(ent, "api_timestamp") | string) != "None" -%}
{%- set data.list = data.list + [(state_attr(ent, "api_timestamp") | string)] -%}
{%- endif -%}
{%- endfor -%}
{%- set data.list = (data.list | sort) -%}
oldest data - {{ data.list[0] }} - {{ (as_timestamp(now()) - as_timestamp(data.list[0])) | timestamp_custom('%H:%M') }}
newest data - {{ data.list[(data.list | length)-1] }} - {{ (as_timestamp(now()) - as_timestamp(data.list[(data.list | length)-1])) | timestamp_custom('%H:%M') }}

[Ilpo55]

And times in local timezoon like this?

oldest data - {{ as_timestamp (data.list[0]) | timestamp_custom("%d/%m/%y %H:%M") }}
newest data - {{ as_timestamp (data.list[(data.list | length)-1]) | timestamp_custom("%d/%m/%y %H:%M") }}

[ivanfmartinez]

And times in local timezoon like this?

oldest data - {{ as_timestamp (data.list[0]) | timestamp_custom("%d/%m/%y %H:%M") }} newest data - {{ as_timestamp (data.list[(data.list | length)-1]) | timestamp_custom("%d/%m/%y %H:%M") }}

You have to use local=True for local time with timestamp_custom as indicated by docs : https://www.home-assistant.io/docs/configuration/templating/#time

[Ilpo55]

"the use of a local timezone is the default.", so local =True is not needed.

[github-actions[bot]]

This discussion has been closed due to inactivity.