Make workday sensor configurable due to lack of calender option in systemsensor

[ImC0mmanda]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.
• I will participate in further discussion about this feature and can test it (if requested) once it's done.

Proposal

It is not possible to configure what workday sensor (entity) is used.
The system sensor does not consider calendars (unbelievable - but another topic) so most people would use a templatesensor for a proper workday sensor.

Additional info

Please make the entity of the used workdaysensor configurable.
There are several options configurable through yaml, that would be finde for the used workdaysensor-entity too.

[ErikSteiner]

Hi there, I use the blueprint Calendar Notifications & Actions to set my own workday sensor to weekend (not workday), if specific strings are mentioned in a appointment. This way, I can trigger a vacation and my thermostats use the weekend schedule.

I would like to see the possibility, to use my own binary_sensor, that sets my own workday.

One option would be, to configure it in the schedule integration itself, like the configuration options you would choose for the workday integration. Perhaps it would be better, to set it in the schedule card itself in the Options tab, when you create a new schedule.

What do you think?

EDIT: I solved it, by setting the schedule to everyday and add a condition with my own custom workday sensor. This way, the schedule can be set to only being active on workdays or non-workdays.

I can not see any advantages for implementing an option to set a custom sensor already in the scheduler component.

[sirarikako]

Hi there, I use the blueprint Calendar Notifications & Actions to set my own workday sensor to weekend (not workday), if specific strings are mentioned in a appointment. This way, I can trigger a vacation and my thermostats use the weekend schedule.

I would like to see the possibility, to use my own binary_sensor, that sets my own workday.

One option would be, to configure it in the schedule integration itself, like the configuration options you would choose for the workday integration. Perhaps it would be better, to set it in the schedule card itself in the Options tab, when you create a new schedule.

What do you think?

EDIT: I solved it, by setting the schedule to everyday and add a condition with my own custom workday sensor. This way, the schedule can be set to only being active on workdays or non-workdays.

I can not see any advantages for implementing an option to set a custom sensor already in the scheduler component.

When the schedule is set to daily and the binary sensor is configured via conditions, control can indeed be achieved. However, since the schedule is set to daily, the UI cannot display the next action time. Therefore, if you want the UI to display correctly, you need to specify the binary sensor to be used in the configuration.