Domoticz

Occationally Domoticz get's sensor data that is clearly wrong. This is by no means specific for Domoticz; any smart sensor occationally mess up and report wrong data, signals aren't perfect, and so on.
..but why not an option to automatically discard data that is clearly wrong?

- Temperature drops instantly over/under 30 degrees, when the rest is stable, and there is no fire, nor being in a freezer.
- kWh meters steady on 1-200W, and sudden spike of 100 000 000 Watt - or negative values.
- Lux reading indicating a god descended in the bathroom..

For me 99% of the time it's network issues and/or sensors messing up.
Like everyone else I do occationally experiment, try out new devices, or similar more or less smart things, where I would want to know if something is way outta line. Turning this on for a Motion detector, Fire Alarm, Flood Sensor, or similar, would also obviously be a bad idea, hence the optional toggle per device.

I guess it would also be smart to have a counter for values out of sanity, and/or a message in log - so that it's possible to get notification if it happens too frequent.

While trying to figure out logs after a z-wave node crashed, I realized Domoticz already does this to some extent:
"2021-04-08 15:09:44.075 Error: OpenZWave: Invalid counter value received!: (-16106127.000000) Node: 3 (0x03), CommandClass: METER, Instance: 1, Index: 0, Id: 0x34C8012"
What I tried to suggest, was a way to further limit what Domoticz sees as valid/invalid values - like not all nodes can have negative values, detect outliers too far off norm, and so on. I'm not suggesting to remove these, beyond what Domoticz does today; just the option to set the limits for what Domoticz accept as valid values.

Like Alverta writes

(that the material's creator was thinking rationally, applying sanity)

it is the user which functionally determines the sanity of a situation:
Domoticz (or any other software) might be an aide, if the user programs the check according his/her rationale.

I don't fully agree.....

I have 12 temperature sensors 433mhz and 3 temp sensors running on z-wave. Cheap Ali sensors and expensive brand sensors, they all seem to never give a false reading(knock on wood ).

But still I understand your desire to have the functionality to automatically get rid of the most extreme spike readings if and when the might occur.
That said, who decides what sanity would be. Temperature you could automatically get rid of below -50 and above 60 but what about if the temperature go's in 5 minutes from 25 to 10 degrees celcius.... could in some circumstances be right but could also be false. "Sanity" is not that easy to program

Hi,

I'm have similar problems.
I have some temp sensor that sometimes report 70C
I have some wallplug energy meters that sometimes report negative values of eg 7000kWh in a hour.

Optional limits on a sensor would be a nice thing to have. Of course it is up to the user to set correct limit values.