Hello dear hhamedk and jommi,
I want to give some clarification on your questions.
If I understand your cases correctly, you want to consider valid only those sensor values that were obtained by the beginning of the unit's movement. If so, your cases are fully covered by the current functionality. And I'll explain by giving you an example. (I wiil use your first example).
While the unit was standing, it sent a weight sensor value equal to, for example, 10 tonnes. Then the unit starts to move and sends sensor values equal to 9.8, 10.5 tonnes and so on. For you, only a value equal to 10 tonnes is valid (i.e.the value that was obtained before the movement began).
For the other values to be considered invalid, the validator must be set up. I will consider speed validation.
To do this, I will follow the algorithm:
1. create a custom digital sensor with the parameter "Speed".
2. create a calculation table in the following form: x = 0, a = 0, b = 1; x = 1, a = 0, b = 0.
3. for the weight sensor, activate the validation by the sensor with the Custom sensor type, validation type — Not-null check (In addition, please see the attached screenshots).
As a result, all received values will be checked for speed and will become invalid.
And as tata wrote above, such values will be replaced by the last valid value. This scheme works if the "Last message" option is not activated.
Please let me know if I got your request wrong.
A screenshot is not enough to explain why your values are not replaced by the last valid ones.
There can be many reasons for this system behavior. If, for example, you use earlier versions of Local, then some settings may work differently.
For a detailed analysis of the situation, please write to our technical support with a full description of the problem and the sensors settings. (email@example.com)
I hope this information is helpful.
Business Analyst, Wialon