We already discussed this several times where I was asking for option to show absolute one.
HA in many places (ie the most recent time of sensor update) shows relative time to current one. for example 11 minutes ago, yesterday etc.
I prefer a real (absolute) time: 2025-08-07 16:35
Ok, that would be
or strftime
are you mentioning programming method or itās already an option available to choose?
Well, seeing that @Mariusthvdbās persistent notification message came from a template, Iām talking about all the values that templates provide. relative_time being the one you mentioned.
Yes. Except this notification is ancient thoughā¦ never changed in all of these years.
Ya, you just got unlucky with the repeating 3. Murphys law
ha probably yesā¦
it from the here travel time integration
and I dont round these values either
message: >-
<person> is op {{states('sensor.thuis_<person>_distance')}} km van huis,
en is over {{states('sensor.<person>_naar_huis_duration')}} minuten thuis!
so yeah, probably should add that now to prevent Murphy again
For sure, because .4333333333 minutes is 26 seconds. The repeating numbers will happen on all the following seconds in a minute:
1, 2, 4, 5, 7, 8, 10, 11, 13, 14, 16, 17, 19, 20, 22, 23, 25, 26, 28, 29, 31, 32, 34, 35, 37, 38, 40, 41, 43, 44, 46, 47, 49, 50, 52, 53, 55, 56, 58, 59
If you want to see for yourself:
{%- for i in range(61) %}
{{ i }}: {{ i / 60 }}
{%- endfor %}
Haha cool.
Yes. Will do. Maybe travel time could limit that in the integration ? What is the point in this case ā¦
Duration sensors can be hours, minutes, or seconds. While it may make sense to handle this on minutes, with hours it would drastically skew the result.
of course.
these are in minutes though, and I dont think the integration offers different units, so it could take that into consideration.
Ill just |int those for the notifications. theyāre way off anyway, so clean up the notification and the Intercom 
I enjoy reading the release notes even when new stuff is not immediately relevant to me.
One request: when writing something like " Integration page gets an overhaul" could you please provide something that helps the reader find what you mean by āintegration pageā. I went to what I thought to be the integration page (Settings/Devices & services/Integrations, with which Google AI agreed) and it still looks the same as before this release (despite a browser refresh). Now I donāt know if I have the right page or I am using a screen too small for the new look or what. I just canāt find a page that looks anything like the example in the release notes. I am not asking for the release notes to be more detailed, just for writers to be sensitive that terminology that may be obvious to them may not be to all readers. Often, a single hyperlink is all that is needed.
More generally, one of the challenges getting up to speed with a system that is so well developed over a relatively long period is the evolving terminology. I think I have nearly mastered integration, platform, component, device, sensor, entity etc. and can handle their inconsistent use in historic writings, but can get stuck on āsimpleā things like above!
Click on an integration on that page that has more than one device.
In my very subjective point of few, only one term in HA has many meanings - ābadgeā.
Thanks @tom_l. I tried all my multiple device integrations: MQTT, Apple iCloud, Shelly, ZHA and I canāt see anything new. Tried a big screen as well as phone. I should read the detailed notes now. (But I still think my point about terminology is valid.)
In the current official documentation that may be true. But if you search for something in everything ever written online it is not! Also, after reading the code for a number of integrations and their helpers, I think that some of the code confuses integration, component and platform (and/or I still do.)
Thank you @tom_l - your rapid, thoughtful, clear and concise replies are always appreciated.
On this occasion I must apologise for wasting your time on what turned out to be my rooky error. Of my two instances of HA I was looking at the one that had not been upgraded to 2025.7.
The new integration page will save me a lot of jumping between the integration devices page.
Funny, ESPHome is the integration that bugged me with the new UI too.
Maybe if it defaulted to collapsed or retained collapsed sections. As it is Iāve found it more difficult to identify a device since I have to scroll further and reorient. Even a ācompactā view might do the trick. Overall, I can see improvements, and with sub devices it makes sense. I will remain hopeful for some additional tweaks.
there is a clash (still) in the version of protobuf that gets installed and the version thah esphome/aioesphome/apple_tv and others want.
I my case I have to manually force protobuf 5.29.5
