M7 still has the described problem. I did some further testing, here are the results:
M7, M6, M5 fail with the following setup:
Item definition:
Number:Temperature HM_Wohnzimmer_RTherm_SetTemp "Set Temperature" (gTemperatureSet) {channel="homematic:HM-CC-RT-DN:ccu:OEQ2084718:4#SET_TEMPERATURE"}
Rule:
rule "TestSwitch"
when
Item TestSwitch changed to ON
then
TestSwitch.sendCommand(OFF)
var test = 20.5|°C
logInfo("Test", "set " + test.toString + " " + test.class.toString)
logInfo("Test", "get " + HM_Wohnzimmer_RTherm_SetTemp.state.toString + " " + HM_Wohnzimmer_RTherm_SetTemp.state.class.toString)
HM_Wohnzimmer_RTherm_SetTemp.sendCommand(test);
end
Log output:
2018-12-01 21:08:53.026 [INFO ] [.eclipse.smarthome.model.script.Test] - set 20.5 °C class org.eclipse.smarthome.core.library.types.QuantityType
2018-12-01 21:08:53.035 [INFO ] [.eclipse.smarthome.model.script.Test] - get 20.5 °C class org.eclipse.smarthome.core.library.types.QuantityType
2018-12-01 21:08:53.055 [WARN ] [ematic.handler.HomematicThingHandler] - Can't convert type QuantityType with value '20.5 °C' to FLOAT value with DecimalTypeConverter for 'OEQ2084718:4#SET_TEMPERATURE', please check the item type and the commands in your scripts
M5 works with the following setup:
Item definition:
Number HM_Wohnzimmer_RTherm_SetTemp "Set Temperature" (gTemperatureSet) {channel="homematic:HM-CC-RT-DN:ccu:OEQ2084718:4#SET_TEMPERATURE"}
Rule:
rule "TestSwitch"
when
Item TestSwitch changed to ON
then
TestSwitch.sendCommand(OFF)
var test = 20.5
logInfo("Test", "set " + test.toString + " " + test.class.toString)
logInfo("Test", "get " + HM_Wohnzimmer_RTherm_SetTemp.state.toString + " " + HM_Wohnzimmer_RTherm_SetTemp.state.class.toString)
HM_Wohnzimmer_RTherm_SetTemp.sendCommand(test);
end
Log output (no error):
2018-12-01 21:13:11.626 [INFO ] [.eclipse.smarthome.model.script.Test] - set 20.5 class java.lang.Double
2018-12-01 21:13:11.641 [INFO ] [.eclipse.smarthome.model.script.Test] - get 21.5 class org.eclipse.smarthome.core.library.types.DecimalType
I installed the homematic binding included in the M5 build of Openhab into an M7 Openhab installation as mentioned by @alkaline above. So the issue is definitely in the binding and not in other components of Openhab. If I should test anything else, just let me know.
Link to the homematic binding included in the M5 build: https://openhab.jfrog.io/openhab/libs-milestone-local/org/eclipse/smarthome/binding/org.eclipse.smarthome.binding.homematic/0.10.0.oh240M5/org.eclipse.smarthome.binding.homematic-0.10.0.oh240M5.jar