When posting something like this, or a log, it is very helpful to use code fences so that the formatting is preserved… and readable.
Everything looks OK. The only thing I could not recreate is the name of your rule. I’m not sure if the forum did something odd without formatting, or if there might be a strange character. When I use the degree symbol in a rule name, it shows as a degree symbol in the JSON, and the rule still works. If that’s not it, have you tried recreating the rule, and do you have the same issue?
Sorry you’re right, now is really better
About the degree symbol is like that also in the json, I double checked, but I think that is the problem, a few days ago I added in the item dimension “temperature” just 'cause I wanted to display °C after the value… so it’s probably just a problem with rules with temperature item…
Thank you, in the end I was able to solve the problem, using the temperature group item that doesn’t have the °C symbol in the value.
Thanks again for your tips, now everything is working like a charm and I have a clean json rules file
Hold up a sec. I’d like to see if the problem is reproducible. In your JSON, I only saw a degree symbol in the name of the rule. Are you saying you were trying use a Condition to compare the state of a Number:Temperature Item? I haven’t tried that in Paper UI.
OK… I’ve tested this, but not with the same results as you. It looks like Conditions are not working if they contain an Item with a dimension. I’ve tried comparing the state to just a number, and to a number with a unit. More testing needed, but I’ll open an issue if I can confirm. The rule always initialized after saving or disabling/enabling.
That is my experience as well. Conditions using UoM defined Items do not appear to work in PaperUI. It’s one of the many things on my list to circle back on and look more into. But it has popped up on the forum more than once over the past couple of months.
In my case, the item gTemperature is a number based on AVG function
If I use directly the item linked to the temperature sensor, I have to select the blank option in the dimension field of the item.
I’m just starting to figure out UoM stuff myself so I wasn’t sure whether it was an ID-10-T problem or something real. But when I read your response I’d say for once it wasn’t a self inflicted problem.
I should also mention that I don’t think UoM works with Actions either, unless you happen to be using the same units as the default. But I’ve not played with that much either. I do remember though trying to use “send command to an Item” for a Number:Temperature that I think uses degrees C as the default using an F and it not working. But I did so much that day, I can’t remember if it errored out or I got the wrong result. My main focus was on exploring the possible so I let a lot of that sort of thing slide.
I’ve always felt that support for UoM in Rules was always a little under documented. Perhaps no one has even looked at UoM in relation to the JSONDB Rules. They are working in JSR223 though, right?
