Topic: Notifications false triggering - null to 0 help needed
I am in need of some help, it might be that there is a simple solution, but I have not been able to find it yet.
We have notifications set to both states of a custom digital sensor, but when we use a command that causes the telematics unit to give a GPRS answer, the parameter value is null, so after being null the parameter changes back to the digital value, the notification triggers as if it has changed values.
To summarise: notification triggers as if a change of value has happened when the value goes from 0 to null to 0 again.
What I have tried:
- ''Last message only' - I have used this in the sensors, and it does change the shown value to 'N/A', but the notification still triggers.
- Not-null check - I validated against another sensor that becomes null at the same time, but the notification still triggers when it returns to the actual value which is the same before the GPRS answer.
I hope that makes sense and I can get a solution. Of course if I find one myself, I will say it here.