Issue of the topic: Since the update to the newest openHab Version, lots of sensors have extreme unrealistic values like 390 degree Celsius. These values stay for some minutes up to some hours. These items were added via the configuration.
2018-01-01 12:32:06.063 [vent.ItemStateChangedEvent] - ZWaveNode7010F0B01100200_SensorTemperature changed from 20.17 to 390.0
Yes - if you set this, then you will get the debug information added to the standard openhab.log file - this will be fine. You can use the log viewer here to view the logs (I think it will decode multi-level-sensor data).
31 = command class (sensor multilevel)
05 = command (report)
01 = sensor type (temperature)
0A = size=2, scale=1 (degF), precision=0
0203 = value (515)
Converting 515 with precision 0 is still 515. Scale = 1 (F), converting this to C is 268.
So unless I missed something, it looks to me like the binding is correctly interpreting the data. Either the sensor send the data incorrectly, or the message got corrupted somewhere. We can say that it was correctly passed from the controller to the binding as the checksum on the packet is ok.
thanks for the great clarification. But now I still have the issue with these values. What could be the next step to find the issue? With the old version I never had something like that. I’m sure of that because the charts with the persisted data were readable. Now I have a long line with some spikes (these high and low values)
I would reset the device to see if it solves it. You could check to see if there is any correlation with polling as we’ve seen int the past bugs in some Aeon devices where polled responses are corrupt but unsolicited responses are ok (this wasn’t the case with the log you sent yesterday as I checked that).
This isn’t a binding issue, so it’s not version related.