If one want’s to write A Blueprint orientated around the “Climate” domain, it is currently very difficult to accomodate for different people using that blueprint with “Centigrade”, “Fahrenheit” & “Kelvin”.
In A Blueprint you want to set Min & Max temperature’s, but don’t want these numbers to cross over (because of math’s & templating {& end-user idiosyncrasy} problems down the track).
E.g. 24°C = 75.2°F = 297.15°K
Recommendation:
- The GUI Selector, just has a end-user option of what to use, & the yaml requires & converts “°C”, “°F” or “°K”
- The trigger requires “°C”, “°F” or “°K” suffix