Open gwilford opened 8 months ago
I'm now pretty sure the start_time entity config is being ignored/overriden as the following sensor template causes the card to work as expected, i.e. shows the delayed start time when in waiting mode:
- name: Dishwasher state
state: >
{{ states('sensor.402100530466009091_bsh_common_status_operationstate') }}
attributes:
start_time: >
{% set relhm = states('sensor.402100530466009091_bsh_common_option_startinrelative') %}
{{ (now() + as_timedelta(relhm + ":00")).isoformat() }}
end_time: >
{{ states('sensor.402100530466009091_bsh_common_option_remainingprogramtime') }}
with this simplified config:
type: custom:timer-bar-card
entities:
- sensor.dishwasher_state
active_state: BSH.Common.EnumType.OperationState.Run
waiting_state: BSH.Common.EnumType.OperationState.DelayedStart
icon: mdi:clock-end
translations:
BSH.Common.EnumType.OperationState.Ready: Ready
BSH.Common.EnumType.OperationState.Finished: Finished
BSH.Common.EnumType.OperationState.DelayedStart: Starting at
BSH.Common.EnumType.OperationState.Run: Run
Hope this helps...
You're right! Thanks for digging into this. The waiting state is using the attribute instead of the entity.
I'll fix this for the next release.
Describe the bug "Invalid Date" is displayed instead of the start time while in waiting state:
Both start_time and end_time entities are defined and are of type device_class: timestamp:
Is the start_time entity config being ignored or overriden by the main entity state/start_time attribute?
Your card configuration
Debug information