Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Operator (with authorisation) disable alarm trigger #1556

Open
Wall-E1271 opened this issue Jan 3, 2025 · 4 comments
Open

[FEATURE] Operator (with authorisation) disable alarm trigger #1556

Wall-E1271 opened this issue Jan 3, 2025 · 4 comments
Labels
feature New feature

Comments

@Wall-E1271
Copy link

Describe the feature
After you confirm the alarm, when the process value returns to the normal range again (there is no alarm value at this time), the value of "toack" will change to 1, and then immediately 0 again, which will generate an alarm. I want it don't change to 1 again, because it will disturb operator.

Describe the solution you'd like
Let the "toack" to stay 0.

Additional context
no

@unocelli unocelli changed the title [FEATURE] [FEATURE] Operator (with authorisation) disable alarm trigger Jan 4, 2025
@unocelli
Copy link
Member

unocelli commented Jan 4, 2025

Hi, you mean that it would be a feature to be able to disable an alarm for a specified time.

@unocelli unocelli added the feature New feature label Jan 4, 2025
@Wall-E1271
Copy link
Author

Hi, you mean that it would be a feature to be able to disable an alarm for a specified time.

I'm sorry my description is not clear, what I mean is that I need to quote the value of toack of api/alarms to judge whether I need to generate an audible alarm, when the process value exceeds the alarm value, the value of toack will change from 0 to 1, this is an audible alarm, after confirming the alarm, the value of toack becomes 0, and the alarm will not continue to be generated. However, when the process value returns to the abnormal value, the value of toack will change to 1 for a short time, and then change back to 0, so that the alarm sound will be sounded again. What I want is that when the process value returns to normal, the toack stays at 0, and then changes to 1 when the next process value exceeds the alarm value again.

@unocelli
Copy link
Member

It seems to me that what you have described is the reaction of an alarm for which the whole flow (activ-passiv-ack) takes place at two different times so it is two alarms. i think you should try to handle this in the same script where you activate the audiable alarm, e.g. by managing a list of alarms already triggered in a certain interval.

@Wall-E1271
Copy link
Author

Thank you, I'll try to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants