Escaping string in 'when' clause

[rossko57]

@Aaargh

That doesn’t work at all.

Humm. My own experience is with OH1 where
Item SomeStringItem changed to “blah”
was both working and understandable.
This year old post suggests that got broken in OH2

String state handling

All, In OH1 I used a rule triggered by a string state: rule "Abus Status monitoring Set" when Item Abus_Status changed to "Set" then ... This rule was not triggered in OH2 until I changed it to: (removing the “”) rule "Abus Status monitoring Set" when Item Abus_Status changed to Set then ... So obviously the state handling of strings changed, right?

Obviously that’s no good, as it’s not going to work for strings with e.g. spaces or keywords like “or”. This is a regression in OH2

I thought it had been fixed in OH2, but nope, see outstanding issue.

Event-based Triggers not working with strings

I guess every OH2 user is using the workaround, trigger on changed only and then do the analysis within the rule body with if()