Closed AndyKirby closed 8 months ago
AndyKirby
commented
9 months ago I am not sure how much of the proposals solution would be the card component or the scheduler component so have posted this request to both as i suspect there might be an element of both needed to do this. Apols if one is unnecessary.
nielsfaber
commented
8 months ago The switch entities created per schedule control the enabled/disabled state for the schedule. This is similar to automations and scripts in HA.
I completely disagree with your request of having this switch control the entity targeted in the schedule instead. In fact, most users control their heating systems with it, there is no simple toggle action possible for such devices.
In addition, there are no such things as 3-way toggle switches in HA (to switch between on/off/auto). Schedule entities would become input_select entities or similar which are represented via a dropdown list in the UI.
For me this seems very clunky, I don't feel anything for this.
Clearly not on the same page on this project, I don't see any grounds for further discussion about this, sorry.
AndyKirby
commented
8 months ago Nils thanks for looking at this.
A standard function of heating controls is advance/boost which does as I describe. Even noddy electro mechanical timers do this. If this is not something you wish to implement that is fine I will need to find something else that fits the need. As will anyone else needing similar.
3-Way switches aside and whether HA has them yet or not. This was a suggestion as it is what I had in Nodered and it worked great. How you might chose (or not) to implement an advance/boost to a schedule in HA is up to you.
Being on the same page is a function of shared context which is unlikely when comparing an experienced developer on their home turf and a mere user. That it should be taken as the grounds for refusing further discussion is sad, but perhaps inevitable.
Cheers
Andy Kirby
On 21/02/2024 17:54, Niels Faber wrote:
The switch entities created per schedule control the enabled/disabled state for the schedule. This is similar to automations and scripts in HA.
I completely disagree with your request of having this switch control the entity targeted in the schedule instead. In fact, most users control their heating systems with it, there is no simple toggle action possible for such devices.
In addition, there are no such things as 3-way toggle switches in HA (to switch between on/off/auto). Schedule entities would become |input_select| entities or similar which are represented via a dropdown list in the UI. For me this seems very clunky, I don't feel anything for this.
Clearly not on the same page on this project, I don't see any grounds for further discussion about this, sorry.
— Reply to this email directly, view it on GitHub https://github.com/nielsfaber/scheduler-card/issues/795#issuecomment-1957519424, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACF75XKZ2AAUXTRFQT3XY3YUYYFFAVCNFSM6AAAAABCW7C5LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGUYTSNBSGQ. You are receiving this because you authored the thread.Message ID: @.***>
-- @.*** www.kirbyand.co.uk
Checklist
Proposal
The current switch item on the schedule card enables/disables the schedule and this can fight with other manual control of the scheduled entities. Notably when controlling lights or security lights making the user experience either sub optimal or clunky.
The proposal is to modify the switch from a bi positional switch to a tri positional switch featuring On/Off/Auto positions. Instead of the current enable/disable schedule.
Additional info
Where the 3 positions can be one of the two following (Selected in the options for the schedule)
Option 1 Manual/Auto:- On, Scheduled entities switched on and the schedule ignored. Off, Scheduled entities switched off and the schedule ignored. Auto, entities switched as per schedule.
Option 2 Advance/Auto:- On, Scheduled entities switched on until next scheduled off and then switch returns to auto. Off, Scheduled entities switched off until next scheduled on and then switch returns to auto. Auto, entities switched as per schedule.
I guess it might be useful to expose the switch in some way as an entity for automation purposes too.
It will also have the side effect of making the UI less cluttered removing the need for both separate schedule and manual controls by rolling the function into one easier to use item.