Hi Sebastian,
if you have defined your items in Paper UI you could try to delete and recreate the item. Sometimes this helps (and is necessary) if an internal item definition was changed.
If the problem occurs if you change a value directly in PaperUI resp. Basic UI then I would assume that there is an error in the binding and I would recommend to create an issue.
Martin
Martin
Wow!!! Use a timer. See:
This is where your problem may lay:
WZ1_Heizung_SetTemp.sendCommand((WZ1_Heizung_PresetTemp.state as QuantityType<Number>).doubleValue)
If WZ1_Heizung_SetTemp is a Number:Temperature then you need to convert it to a DecimalType
Converting it to a Number Type will not change anything as a QuantityType is a child of Number TYpe
The issue is probably related to the ESH #6512 and #6544 Homematic PRs.
There was actually also a fix in ESH (#6513) for improving backwards compatibility when dimensions get added to channels. It should not be necessary to remove/add Things when UoM is introduced in a binding.
Hi Martin,
sorry, this topic is still some days ago…
But I never created the items with PaperUI. I use Item files to create these.
Sebastian
Can you post your items and the rule that’s failing, please
HI,
actually I downgraded my openHAB system. So it is working again. But this item for example did the problem with M6. Also without working a rule, it was not possible to assign manually a new SV to Homematic device.
Number Wohnzimmer_FBH_SV "Soll Temperatur" <temperature> (gT_SV) {channel="homematic:HM-TC-IT-WM-W-EU:e7adadb7:MEQ1574558:2#SET_TEMPERATURE"}
You will need to change the item to:
Number:Temperature Wohnzimmer_FBH_SV "Soll Temperatur" <temperature> (gT_SV) {channel="homematic:HM-TC-IT-WM-W-EU:e7adadb7:MEQ1574558:2#SET_TEMPERATURE"}
Once that’s done then we can have a look at the rules
This is what I tried after reading the documentation.
But also didn´t work to me. Same error message.
Regarding the error created by the rule: Actually I faven´t this error anymore, due to my downgrade to M5. I cannot remeber in detail. Sorry for that.
Well, you are going to have to bite the bullet and upgrade again and work your way through the errors.
It’s likely to be the same error everywhere. So once we solved one, you’ll be able to do the rest.
BUT
Change you homematic items to add the unit, just as above
Then in the rules, whenever you are working with an item state do this:
(item.state as QuantityType<Number>).doubleValue
To convert the UoM value to a plain number
Also get rid of your Thread::sleep for 30s. BAD IDEA
Use a timer instead:
case "4" : {
logInfo(filename, "Wohnung Heizmodus: Aus (Sommer)")
WZ1_Heizung_Mode.sendCommand (3)
WZ2_Heizung_Mode.sendCommand (3)
KU1_Heizung_Mode.sendCommand (3)
KU2_Heizung_Mode.sendCommand (3)
SZ_Heizung_Mode.sendCommand (3)
BD_Heizung_Mode.sendCommand (3)
EZ_Heizung_Mode.sendCommand (3)
BR_Heizung_Mode.sendCommand (3)
createTimer(now.plusSeconds(30), [ |
WZ1_Heizung_SetTemp.sendCommand(tempOff)
WZ2_Heizung_SetTemp.sendCommand(tempOff)
KU1_Heizung_SetTemp.sendCommand(tempOff)
KU2_Heizung_SetTemp.sendCommand(tempOff)
SZ_Heizung_SetTemp.sendCommand(tempOff)
BD_Heizung_SetTemp.sendCommand(tempOff)
EZ_Heizung_SetTemp.sendCommand(tempOff)
BR_Heizung_SetTemp.sendCommand(tempOff)
])
}
Yes, you are right. I need some time to do the upgrade and the investigation. Maybe end of this week.
The Thread::sleep came from another user, I know about these behaviours and try to use timers if necessairy.
Thanks for your support.
Sebastian
I was asking Wouter, how to downgrade the homematic binding back to M5.
For those who want to keep M6 within the older rules: follow the instructions below.
Yes you could try the M5 version again by:
/addons directoryAnother way is to use that download URL for updating the bundle to the M5 version using the Console.
This is what it looks like when reverting a SNAPSHOT version of the binding to the M5 version again:
openhab> bundle:list|grep Homematic
209 │ Active │ 80 │ 0.10.0.201811171951 │ Eclipse SmartHome Homematic Binding
openhab> bundle:update 209 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
openhab> bundle:list|grep Homematic
209 │ Active │ 80 │ 0.10.0.oh240M5 │ Eclipse SmartHome Homematic Binding
In the mean time there have been some fixes for the binding, e.g. https://github.com/eclipse/smarthome/pull/6565 , but I am not sure whether they will solve this problem. But you can try install the latest version of the Homematic binding manually.
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
just a note: Since M5, there have been several PRs on the [homematic] binding, so maybe one of them broke this HomematicThingHandler for your case. You can check which recent ones were included in the M7 here.
I didn’t find a similar Issue open on https://github.com/eclipse/smarthome/issues?q=homematic
Maybe this is worth posting an Issue there. You have all the info for a developer to reproduce this.
Jep, I will post an issue in the ESH repo. Just wanted to give an update here. Maybe you could keep in mind that this is currently broken and should be fixed before Openhab 2.4 is released (or just ship the binding version included in the M5 build for a release build).
I don’t think that this is possible 
There have been many bug fixes implemented since M5 in the binding. They need to check your situation and fix it.
I am not 100% sure that your rule is correct… I will try to check some stuff and post more info.
Meanwhile, plz go ahead and post your configs on the ESH github issue.
Opened issue for reference:
I am facing the same Problem. Even when i change the Temp from Paper UI i get the Same error. So i think its an Problem with the Binding and not with the Config.
im faced with exact the same error, too.
After upgrading from 2.3 to 2.4 M6, I have exactly the same problem and cannot set the temperature 