Text alerts when not neccesary.
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
Text alerts when not neccesary.
I have been getting ph alerts that say I am above my alarm level but when I check the app or the datalog at home and it reports that it is normal. Any idea what causes this? I used my existing ph probe when I setup the RA. It is only 4 or 5 months old.
As an example I got a text that said PH was 6.83 just now but my banner shows 6.56.
Any insight would be helpful.
Thanks!
-Mark
As an example I got a text that said PH was 6.83 just now but my banner shows 6.56.
Any insight would be helpful.
Thanks!
-Mark
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
Re: Text alerts when not neccesary.
The reef angel monitoring software. I have it running on one of my servers.
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
Re: Text alerts when not neccesary.
Yea its showing spikes. I might try replacing the probe. The spikes seem intermittent.
Re: Text alerts when not neccesary.
I get similar spikes. I have replaced both the probe and the controller board itself but it made no difference.
Eventually I replaced one of my ATO switches and it helped a lot, but they still happen.
I believe it has to do with the noisy electrical environment you get around pumps / heaters / etc. It helped me when I moved my probe from my sump to my overflow. They still happen, but less often.
Don
Eventually I replaced one of my ATO switches and it helped a lot, but they still happen.
I believe it has to do with the noisy electrical environment you get around pumps / heaters / etc. It helped me when I moved my probe from my sump to my overflow. They still happen, but less often.
Don
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
Re: Text alerts when not neccesary.
Would it be possible to write some code that ignores values outside of a range in a given amount of time?
Say PH is 6.5 but half a second later its at 6.8 and then back down to 6.5 in another half second. Its not possible to change the ph that fast so even if the sensor says it as such the data should be ignored.
Say PH is 6.5 but half a second later its at 6.8 and then back down to 6.5 in another half second. Its not possible to change the ph that fast so even if the sensor says it as such the data should be ignored.
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
Re: Text alerts when not neccesary.
When I first set it up I was getting them. I just set the alert value higher and it wasn't an issue till recently. The last 3 days I have gotten constant texts 
Roberto if its smoothed out and still showing spikes is it possible that one or more readings is way high and therefor causing the burp even if they are smoothed. Would eliminating outliers improve the smoothing or does it already do this?

Roberto if its smoothed out and still showing spikes is it possible that one or more readings is way high and therefor causing the burp even if they are smoothed. Would eliminating outliers improve the smoothing or does it already do this?
Re: Text alerts when not neccesary.
Curt had implemented that check on temp probes but not for pH.
It is true that if one is a really high spike, it would affect the average.
Can you check if the float switches are not interfering with the readings by introducing ground loop?
Check for any broken lead wires or possibly removing them to see if the spikes go away.
It is true that if one is a really high spike, it would affect the average.
Can you check if the float switches are not interfering with the readings by introducing ground loop?
Check for any broken lead wires or possibly removing them to see if the spikes go away.
Roberto.
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
-
- Posts: 159
- Joined: Thu Nov 24, 2011 9:50 pm
- Location: Golden, CO
Re: Text alerts when not neccesary.
Problem was resolved.
Expansion hub had a bad wall wart that ended up causing the interference.
Expansion hub had a bad wall wart that ended up causing the interference.