@michikrug
Hi Michael… A short question…
What exactly is the targetHeatingCoolingMode depending on? According to the docs, it´s either “heat, cool, on or off”. It can be set by a Numer item or a String…
Pleas correct me if I´m wrong, but isn´t the targetHeatingCoolingMode a state to tell, if the heater is On/Off or Heating/Cooling, and in Google Home app it will change the visual color from red to blue? (heating/ cooling or on/off) ?
Reason I ask is, my underfloor heating setup is not having an exactly specific Mode. It´s a simple temperature sensor, and the logic just detamins if the temperature is above or below the setpoint. If temperature is above setpoint (incl thresshold), then turn off the actuator/telestat. If it´s below, then turn on the actuator/telestat…
Just plain and simple heating control system.
Now I wonder… Thinking about the above, shouldnt the actuator be used to set the actual targetHeatingCoolingMode then? I´m pretty sure it is suppose to work like this. But there is a slight problem. The actuator/telestat is a Switch type item, not a Number and not a String.
So in order to make this work, we will need the targetHeatingCoolingMode to have a Switch type option as well.
Couldn´t/shouldn´t it be done like this?
EDIT:
I just tried the above by using a String “proxyitem” for targetHeatingCoolingMode, and a rule which change the item to either “heat” or “cool” when the actuator/telestat changes… And it works exactly as descriped above… In Google Home app, the thermostat will change color, red when “heat” and blue when “cool”.
This is the rule:
rule "heatingmode"
when
Item telestat1_stort_bad changed
then
if (telestat1_stort_bad.state.toString == "ON" ) {
stort_bad_Mode.postUpdate("heat") }
else {
stort_bad_Mode.postUpdate("cool") }
end
So it does work as it is now. But if we could have a Switch type item for targetHeatingCoolingMode, then we wouldn´t have to use a rule to do this and not even a String, as the telestat/actuator can be used to set tagetHeatingCoolingMode.