This is detail of Roborock S7 device. As you see, “2 128s” is not much informative. Could you please display it as “0h 35m 28s” instead?
One word: templates.
@nickrout thanks, however, I’m not sure I could use templates in the device view. Anyway, this feature request is to display time values clearly as default, so you don’t have to use templates on every single time field.
What integration and which card? I don’t see roborock in the integrations list.
Device page. Go to Settings - Devices & Services - Devices tab - choose any device with time entity (in my case Roborock S7), and check the time entities shown as on the screenshot I posted.
Roborock is added via Xiaomi Miio integration.
It might not be that simple.
What is a good format to show time in one instance, might be a bad one in another.
Like a router have a uptime value that can many times be in days or even years, so a format of days hours:minutes:seconds would be wanted, while a timer for an automation would probably be more useful with a format of seconds:microseconds, where seconds count above 60.
Where as a date for a calender would require something, like date month year or date month year hours:minutes or some other variant.
It should be able to auto adjust.
Based on what information?
Good point @WallyR . It could use the same system used for degrees Celsius vs Farenheit, or km vs miles. It could just allow you to select whether you want “days hh:mm:ss”, “hh:mm:ss”, “s”. I think “hh:mm:ss” should be used as default anyway, but you’d have the oportunity so set it to your linking for any time entity.
The total should give it away, if it is over 60, express it in min:sec, if it is over 3600 express it in hours, mins, secs. If it is over 86400 then days, hours, mins, secs
Those are global settings, which means your uptime values would be shown, like 165:23:59, but also your calendar dates as 1368765:23:59 (time after new year 1970)
@nickrout , as @WallyR said, in some cases you need to see “452s”, not minutes. And that would be solved by using the similar converter as is used for km vs miles. That way you’d be able to see normal “human” time (00:32:25) in most cases, and also you’d be able to set it to “527s” in some special case.
Yes true. If time based entities could have a choice of units, like seconds, minutes, hours, display human readable etc. And as an added bonus, a pop up which displays in a number of different ways.
Then again the FR is for an area of HA that you don’t look at on a daily basis. Lovelace is fully configurable, the settings pages don’t have to be, and should have minimal overhead.
I know, there is possibility to do that in dashboard via template. But what’s the whole point of automation? To get rid of these manual steps, however small. So it would be great if the software in which you do the automation, doesn’t force you to use these little manual things, but allowed you to do it all in GUI on 2 clicks. And when you set the format on entity, that format is then used in all places, all dashboard you use it. With templates, you have to do it again and again in each dashboard.
No you don’t, create a template sensor with the data you need (once) and use that sensor instead in Lovelace.