[feature request - Improvement] Additional visibility condition for dashboard elements

[BBE-FR]

The dashboard GUI provides some very interesting visibility option,

• for cards:
  

• or for entities inside tile or header cards:
  

I miss one option, and I think it could be an interesting addition: a way to easily set "time" condition.

This could be added, in the same manner it is available for automation (only for time, as the two other are manageable through entity state):

This would allow easy customisation of dashboard with regard to the time !

Otherwise a condition like before fixed time or after fixed time is not easy to create.
There are some use case, especially with kids where you have some information interesting to show "before school time" or "after school return" for example

[BBE-FR]

I tried to find a way around this but adding the integration with the sensor sensor.time does not allow to test if the value is below or above a fixed time value because it returns HH:MM which can not be numerically tested in the available visibility tests.

If you want to adjust the visibility of a card for a certain period of time (example after school, lets say if time is after 16:30 or 4:30PM) there is no straightforward option for the time being :

• you can create a scheduler and test its state, but if you have various different "time zone" to define you will need various schedulers for each card
• you can create a template boolean sensor with the same remark as before for the scheduler
• you can extract the HH content of the time (HH:MM) in a sensor and check only HH (as a numerical entity) to check if you are before or after 16:00 which is the best I managed to achieve with the following sensor template: {{ (states('sensor.time').split(':')[0]|int) }}

[BBE-FR]

I would love to see a visibility test that would simply be before or after and set a time...

Or if somebody finds a better way than mine to perform it, please share...
It must be possible to create a template to have time in a float format like HH,MM, but I am not fluent enough in Jinja2 to make it and I believe I am not the only one ...