Alarm Logging

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

I agree, its possible to find out when you deep dive, but its very time consuming and not the easiest. if in the Log they added the input that triggered it, that would be helpful. I have an alarm that goes off every now and then and trying to figure it out is never fun.
 
I also get them where the alert output type outputs will trigger and show an alert on my lights controlled by the Hydros in the living room, but before I can get the app open they go off and there is no record or indication of what the issue was and a push notification or email was never sent since it does not last long enough. It would be nice to log anything that would also trigger those outputs even if it didn't last long enough to trigger a push notification or email.
 
Definitely needed! Trying to track down those super-short, intermittent alarms is a nightmare when all the log gives you is a generic ON/OFF.
Having the trigger input logged (like pH Sensor 7.9 or Level Sensor A < min) is essential for actual troubleshooting, especially for those of us who use the alarm outputs to trigger visual indicators.
You can explore the free tool as well. Online Alarm Clock
 
Absolutely needed!! Going to expand upon this a little further logging notifications AND outputs. Simple enough... i.e. (Sample ATO) Turned OFF Input1 DRY or (Sample ATO) Turned OFF Fallback Input1 unavailable or (Sample Kalk) Turned ON pH Input Low.
 
Hydros currently only logs alert outputs as ON/OFF, which makes tracking short or intermittent alarms hard. A useful improvement would be to log the actual trigger, like which sensor or input caused the alert, even if it’s too brief to trigger a notification. This would make troubleshooting and monitoring much easier.
 
Sole83 said:
Hydros currently only logs alert outputs as ON/OFF, which makes tracking short or intermittent alarms hard. A useful improvement would be to log the actual trigger, like which sensor or input caused the alert, even if it’s too brief to trigger a notification. This would make troubleshooting and monitoring much easier.
Click to expand...
Most inputs do have alert settings for when they get out of range. If an output is getting triggered and has multiple inputs and I suspect a particular one I can setup an out using that particular input and set the minimum on time for the output for a few minutes so it is long enough to register in the log if do trigger.
 
+1 for alert logging. Capturing what triggered an alert—and exactly when—is essential for future improvements.

At the moment, I’m dealing with a phantom error that sets off an audible alarm without any accompanying notification or email, which makes it difficult to diagnose and pretty frustrating. Adding an alerts log would provide much-needed visibility into what’s happening behind the scenes.
 
tree said:
+1 for alert logging. Capturing what triggered an alert—and exactly when—is essential for future improvements.

At the moment, I’m dealing with a phantom error that sets off an audible alarm without any accompanying notification or email, which makes it difficult to diagnose and pretty frustrating. Adding an alerts log would provide much-needed visibility into what’s happening behind the scenes.
Click to expand...
If it is audible then it has to be an alert level that has audible turned on. Normally that would be a red alert. How many inputs or outputs have a red alert set for a alert level on your system?
 
You must log in or register to reply here.
Back
Top