Open GreyCivic opened 1 month ago
This shows maybe better, what i mean.
Like, i want a Input selecter, and then the defined tasks are valid.
Dear @GreyCivic thanks for this issue, I would have the similar request.
Actually, the scheduler only allows you to manage one schedule per card, doesn't it?
I would also like to understand if it is possible to manage smartworking days: if I sent a helper that I work from home, the scheduler should work as other days (e.g. as weekend).
Dear @GreyCivic thanks for this issue, I would have the similar request.
Actually, the scheduler only allows you to manage one schedule per card, doesn't it?
I would also like to understand if it is possible to manage smartworking days: if I sent a helper that I work from home, the scheduler should work as other days (e.g. as weekend).
Yes, i have around 20-30 settings, which makes it confusing.
I have e.g. for the main room, 1 setting for weekdays, 1 for weekend, 1 for away, 1 for no school. And this for 6 rooms.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Push
Schedule is a great addon. But I would also love to see this rather than having multiple cards for the same entity. It's hard enough to get a non techy wife to get use to HA, and this will keep the interface simple for the non techy ones out there.
Checklist
Proposal
1.) Multiple timers To have it easier to setup, would be good, if you make more time schedules in one card possible. For thermostat makes it a lot sense, to have a better overview, and all needs solved in one card.
Heater room1: Workdays - Time schedule Weekend - Time schedule
Input Entity: e.g Holiday activated Holiday - Time scheduule
Input Entity: e.g. Away activated Away - Time schedule
Input Entity: e.g. Window open Windows Open - Dummy schedule -> Trigger for switch off the heater
So you have a lot of possibilties, solved in one card.
2.) Option entity reaction e.g. in this use case, when i switch off the main heater, it need to be observed, when a entity is from TRUE -> FALSE, that all time schedules inactive, and one last signal is send to the thermostat, to switch off.
Additional info