Hi,
i have Zwave LC13 thermostatic radiator valve devices that are set via an selection item in between 10 and 28 degree. I only need to to say FULL SPEED or FULL STOP.
After some time i now realize that selection is too cumbersome for daily change so my hope/idea is to remove the selection item and transform it somehow to ON OFF swithc item? So if it is OFF it would be 10Degree and if it is ON it would be my current 28Degree.
I’m sorry but i’m completely clueless what is required. From what i know about Openhab mostly it can all be done in one step…somehow Switch item and mapping but i’m not sure if this could fit the requirement or if still a rule like below needs to be in place?
Right now it looks like this:
Sitemap: Selection item=LivRoSelect mappings=[0="10°C", 1="28°C"]
Rule: rule "Heating TempSelect" when Item LivRoSelect received command then switch(receivedCommand) { case 0 : LC13thermoLivRo_Setpoint.sendCommand(10) case 1 : LC13thermoLivRo_Setpoint.sendCommand(28) } end
And what seems to be the problem?
What is the definition of the item LivRoSelect? I assume it’s a Number item.
You put the receivedCommand between brackets which will make it into a boolean true or false
Rewritten rule so that is can be read:
rule "Heating TempSelect"
when
Item LivRoSelect received command
then
switch receivedCommand {
case 0 : LC13thermoLivRo_Setpoint.sendCommand(10)
case 1 : LC13thermoLivRo_Setpoint.sendCommand(28)
}
end
That’s not what ( ) does. Like { }, ( ) is a way to define a context, only the context is a little different. It’s kind of like a way to say “treat everything between the () as one thing.” Another way to look at it is that it’s a way to control order of operations, just like in math.
That’s why, for example, if you want to call .intValue on a Number Item’s state you need the parens.
(MyNumber.state as Number).intValue
The parens force the cast to Number first and then you can call .intValue.
You see the parens involved with an if statement because you need the conditionals to evaluate before the if statement so the parens force that to happen.
In the context of the switch statement, it’s kind of a noop (i.e. does nothing). But, in this case you may need to do something. receivedCommand is a State and not necessarily a Number. I don’t know if the Rules engine will be smart enough to treat it as a Number or not. So I would keep the parens and cast receivedCommand to Number.
Tried that one, but it does not really work / Openhab does not like it at all.
I now did a switch item that is related to a rule…
seems to work in iOS but the webbrowser+Classic UI makes the GUI almost not respond…something is going on, but i have no idea why. The rule itself is not that komplex i guess…
rule “Heater TempSelect”
when
Item LRsel_Switch received command
then
switch(receivedCommand) {
case OFF : LC13thermoLivRo_Setpoint.sendCommand(10)
case ON : LC13thermoLivRo_Setpoint.sendCommand(28)
}
end
