Sensor.Community Binding - values not more reliable, or?

[scheuerer]

Since more that a week I’m pulling now values from to different sensor to my OH4.3-2 installation.
It was it looks nice.

Since yesterday I’m not more sure if I can reliable on thoose values from two DIFFERENT sensors.

One is for “air preasure” the other shows me the “durst in the air”.

The graphs look like this:

and this:

The change to an other sensor this morning show the same effect and the end of the bar.
Only up and down from the value…

Anyone has an Idea?

[JimH]

I can’t help with why the sensor is returning weird values, but you can use a profile in the item’s definition to filter out those values. Back on OH3 I used a Ruby profile to exclude unreasonable values from an item. But based on this thread this feature may be built in to OH4.

Reasonableness constraints

You can use a profile written in jruby (which works on openhab 3.4) or wait for openhab 4. The state of this in openhab4 is still up in the air. Currently there’s SCRIPT profile that can let you do this (not sure if it’s in M1 but for sure it’s in SNAPSHOT), but if my PR is accepted, this will go away and be replaced with a language-specific profile, i.e. JS, RB, DSL, etc. in its place. Example with a jruby profile: Your item definition: Number:Temperature My_Temp_Sensor { channel="xxxxxxx" […

The approach I’m using requires some Ruby code in $OPENHAB_CONF\automation\ruby\profiles and profile= specified on the item.

Item definition:

Number:Temperature OfficeTemperature "Office Temperature [%.0f%unit%]" (gTemperature {channel="zwave:device:39d5999999:node48:sensor_temperature" [profile="ruby:discard_anomalies", min="0 °F", max="300 °F"]}

$OPENHAB_CONF\automation\ruby\profiles\discard_anomalies.rb

profile(:discard_anomalies) do |event, state:, configuration:|
  next true if state && state >= QuantityType.new(configuration["min"]) && state <= QuantityType.new(configuration["max"])
  
  false # discard it
end

HTH,
Jim

[jimtng]

In OH 4.3.2 you can also use the Basic Profiles addon. It includes a State Filter profile which does what the Ruby profile example above does.

You can use the Ruby profile way too of course.

Another alternative is to use script transformation profile.

[scheuerer]

Thanks for you help with the basic profile.
But I’m not a developer or scripter, I can only usw the UI and click somthing together

I’m still wondering whey it was working very well for more than a week and from on eto the other day the binding receives all thi kind of wrong values…

As the values coems from the sensor.community service two rootcauses are possible.

1. The binding get’s the addinoal to the right once, wrong values with the TOP.
2. The service sends wrong values.

I have added more sensors from differnet city, and all of them have the same problem.

I have already deleted the items, the thing and the binding, and have created them new.
Without success. Meanwhile the graph look linke this:

BR
Jochen

[scheuerer]

Meanwhile I received this mail:

Hello Mr. xxx,

we were able to restart one of our data servers only the night before yesterday. I forgot to reactivate the copying of the data file to this server. As a result, the two servers did not deliver the same data. Theoretically, however, this should not be a problem, as the date and time are also delivered for each measurement. However, this does not seem to be taken into account in the bindings.

In the meantime, however, the current values should be delivered from both servers again.

Best greetings from Stuttgart,
Rajko Zschiegner
DevOps @ Sensor.Community
[Rajko@Sensor.Community]