Single state change causing multiple events (possibly due to data source reset)
One of our data points changed state, triggering an event. Everything executed as expected, except that it continues to create events and sending out alerts.
Event logs show "Data point disabled" in the status field (see attached). This may likely be the result of our serial port reset work-around, but should I expect a new event each time the data point/source is enabled? Is there a better way to avoid these "new" events?
Or is there something else going on I don't understand?
phildunlap last edited by phildunlap
No. if the data point is disabled, the event is no longer active. If the point is still in the active state when the point is resumed, the event is raised. This is purposeful. You could use a meta point to eliminate that noise if you intend to be toggling the point with the state detector a lot, or you could point link it to a virtual point (which you will never disable) and do the event detecting on the virtual point. Or find another solution than toggling the source point on and off.
I've created a meta point, and that seems to resolve this.
For future reference (and I'll add a feature request) it would be helpful to have a comment-type field with such datapoints, explaining their reason to be, so the next unfortunate soul to come across this would understand why such a point was created, etc. And as my college professor would often remind me, in the context of commenting, in a few short months I qualify as that new unfortunate soul with no context to understand why it was done that way.
phildunlap last edited by
For a meta point, you can always do comments in the script.
uhhh... yeah. I knew that.