Closed val123456 closed 4 years ago
The issue is likely that determining a message is unique currently requires the checksum, which in most cases would be different if any of the unknown fields are changed. I would recommend writing your own mechanism in your collection system to ignore messages you don't want.
Just got a new Neptune R900 water meter, and am integrating it into my monitoring solution. I use the
-unique=true
flag but noticed what looked like duplicate messages. It appears unique means all fields match AND it only compares to the last message. However, my meter flops the Unkn1 field . . . sample below.Would it may sense to only match the known fields???