I have a pretty serious issue with alarm reporting for things like Ph, or temp, that are sampled at a very high rate. Typically, when the reading goes into an alarm state it hovers around that value, at least for a while. So if I have a temp alarm at 80 degrees, for example, the sensor will read 79.9, then 80, then 79.9, etc - for quite a while. This means that I get an email/text dozens of times in a short period, while the sensor goes in and out of the alarm state before it ends up settling above or below the alarm reading.
How do other people deal with this? Is there a workaround that I'm not thinking of? The way that I think it should work, which isn't how it appears to be designed currently, is that the alarm wouldn't re-enable until it went further away from the alarm value. So if you have an alarm set to 80 degrees, and the sensor reads 80, then the alarm wouldn't re-enable until it went below 79.5.
How do other people deal with this? Is there a workaround that I'm not thinking of? The way that I think it should work, which isn't how it appears to be designed currently, is that the alarm wouldn't re-enable until it went further away from the alarm value. So if you have an alarm set to 80 degrees, and the sensor reads 80, then the alarm wouldn't re-enable until it went below 79.5.