Use sensor values for comfort temperature
Checklist
- [X] I have filled out the template to the best of my ability.
- [X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
- [X] This issue is not a duplicate feature request of previous feature requests.
Is your feature request related to a problem? Please describe.
I would love to be able to set the min and max comfort temperatures to a sensor value, that way I could pull the min and max temp from my thermostat.
Describe the solution you'd like
Have the ability to use a sensor value instead of static temp levels.
Describe alternatives you've considered
Nothing
Additional context
Nothing
I was wondering the same. It would avoid having to enter the same data in 2 different places.
I would love to be able to set the min and max comfort temperatures to a sensor value, that way I could pull the min and max temp from my thermostat.
Do you mean to extract the values from the attributes of a climate entity? As this seems easy from the outside it adds more complexity to it than adjusting two sliders in the option menu. Not all climate entities nor sensors are created with the same attribute names, so to make it work for everyone the code needs to be clever enough to extract the two temperatures from the assigned entity.
An option where two separate entities like sensor, or input numbers are used can be considered. An option where the integration provides you with some input numbers can also be considered to make it more easily to automate the values without going to the options menu.
I see what you mean, the climate attributes aren't easily extracted. I think just having the option for a entity would good enough, then if users want to try it, they can make a trigger template or something similar to extract the target min/max from climat for themselves, depending on device.
Or just having a global input number, to use for multiple shades.
if we could allow for a templated value, then it would be up to us to figure out how to extract the value correctly.