[Feature]: Support for TIMESTAMP entities/attributes

[peyn]

Requirements

• I checked the README.
• I have updated entity-progress-card to the latest available version.
• I did a search to see if there is a similar issue.

Is your feature request related to a problem?

Hi,

It would be terrific if the card could handle the TIMESTAMP type entities/attributes by default.
By handle I mean countdown to the timestamp value from the entity/attribute.

The image pasted above shows an washing machine end time entity. The card could show a progress bar being filled as NOW() timestamp gets closer to the washing machine end time.

Kind regards,
Mateusz

Describe the solution you'd like

1. Add a timestamp entity/attribute to the card
2. By default the card compares the current timestamp from NOW() with the assigned timestamp and fills the bar while NOW() gets closes to the assigned timestamp
3. It could also be useful to have another setting for the comparison timestamp, default value would be NOW()
4. If assigned timestamp >= comparison timestamp (NOW() by default) then bar = 100%

Describe alternatives you've considered

I am aware I could do it with some additional custom sensors defined. But it would be very helpful if the card did it on its own. Helpful and a lot more user-friendly than the custom sensors.

Additional context

No response

[francois-le-ko4la]

Hello @peyn

100% agree !

I have another request that is similar on "time" and my standard answer is here: #38 (comment)
I take a look on it this we.

TY.

[francois-le-ko4la]

I did not forget your request. Multiple ideas in this request...

and also multiple case to considere:

Case 1: End Time (completion_time / end_time)

sensor.appliance_completion_time: End timestamp
sensor.appliance_start_time: Start timestamp (or estimated)

Progress = ((Current Time - Start Time) / (End Time - Start Time)) × 100

Case 2: Start Time + Duration / Completion time + duration

Progress = ((Current Time - Start Time) / Duration) × 100

Case 3: Remaining Time Only (remaining_time)

• sensor.appliance_remaining_time: Remaining time in minutes
• input_number.cycle_duration: Total cycle duration (manually configured)

Formula: Progress = ((Total Duration - Remaining Time) / Total Duration) × 100

Case 4: End Time Only (Estimated)

Estimated Start = End Time - Average Duration
Progress = ((Current Time - Estimated Start) / Average Duration) × 100

As a consequence:
current min/max are not enough, and we will need new option like:

• time_start
• time_end
• time_duration
• time remaining

[peyn]

Hi,

Would it be possible to have the time_start value set automatically when time_end changes from a time in the past to a time in the future?

Kind regards,
Mateusz

[francois-le-ko4la]

hello @peyn,

I fully understand your question.
Currently missing the start_time component when end_time transitions from past to future.

1. First: Identify your integration

Question: What's the name of your integration providing the end_time sensor?
Different integrations might provide:

• Hidden attributes (last_changed, last_updated)
• Complementary sensors
• Accessible internal states

I see in your screenshot only one sensor and I am sur you have only one but let me check your integration.

2. (a) If we can improve that part - integration is easy
3. (b) If the integration cannot be improved -> Template sensor for state change detection

Best approach - Create a dedicated sensor that captures the exact transition moment:

• Home Assistant automatically manages last_changed -> automatic history
• Persists after restart
• Zero performance impact

3. ❌ Last resort: History API
   Really plan Z (last last last resort) - Should be avoided:

• Degraded performance
• Heavy repeated queries
• Frustrating user experience

[peyn]

Hi @francois-le-ko4la

It's the Samsung SmartThings integration and this is a washing machine sensor showing when the current washing cycle will end.
The sensor is updated multiple times, as the time of the cycle is updated during the washing.

I know I can create a custom helper sensor. I read your tutorial about it. It's very well described there.
But maybe, just maybe :-), it would be possible to avoid it and have the logic incorporated into the logic of your custom card?

If it is not possible, or just too much work, then I will go with the custom helper sensor.

Kind regards,
Mateusz