Enhancement suggestion: support HA named set points

[kalmatthew]

By supporting the climate device named set points (eco, away, boost, comfort, home, sleep, activity) a number of things would be easier. Voice assitants would be eaiser to use "alexa set living room radiator to comfort" person doesn't require you to remember what temperature is comfortable. It also means schedules could use the set points allowing for temperatures to be consistent and modified in one place.

I suggest that the values are set in the automation paramaters apart from away which should always be the wiser away temperature

[msp1974]

Can you elaborate more on expectation. I'll explain why.

1. Eco, comfort and away are all current wiser functions but they work at the hub level and not the room level. So are these now custom room functions to set predefined temps? Do they also override auto mode and set to manual? Or just operate until the next schedule change?
2. Do you expect to be able to set these values on a room by room basis or at the system level? Is comfort temp the same in all rooms for example?
3. How do you see schedules working? The schedule is stored on the hub not in the integration therefore what happens if you change these temps, would you expect it to know that 21C on the lounge schedule is from comfort mode and change this schedule?

I have a fear this is very complicated and possibly outside the remit for this integration. There are other ways to achieve this as you are the only person asking for it. Maybe poll the user forum and see if more people need it, define it better and we will see if something we can invest time to do.

Thanks

[kalmatthew]

Hi,

The naming overlap is unfortunate and I'm honestly not sure how this can be resolved.

I was expecting these to be effectively global variables so at the system level. As such I'd expect setting the temperature to one just to operate as if you had set a manual temperature in HA or the wiser AP so just until the next schedule change. For a schedule set from the app rather than from the integration I guess in an ideal world it would be able to do the reverse lookup but I could see a use case that would just write back a temperature as normal.

Even without these being available in the scheduler at all the voice/UI benefits would remain (Thermostat cards for example often have buttons to activate these temperatures). I'll try and and get something posted in the user forum to see if there is a wider intrest.

[msp1974]

Any further update on this or should I close?