Salt alarms driving me nuts

[boozeman27]

Ok, so I know this has been discussed before as I have searched and read all of the related posts. I am brand new to Apex and its in a new tank that is still cycling so there are no fish in it. How do I shut off this stupid false alarm for my salt. It keeps telling me it's greater than 37ppt even though it's not. I have turned off the alarms and back on, I have adjusted the value to 38, I have moved the probe in case of micro bubbles. Don't know what else to do. Someone said add a defer statement but I don't see where there is an area to add lines of code to the probe? Please help I get an alert every hour.IMG_0250.jpgIMG_0248.jpgIMG_0249.jpgIMG_0251.jpg

[Frogfish]

Post the code for your alarm. Is your alarm set to auto or is it set to on?

[boozeman27]

Post the code for your alarm. Is your alarm set to auto or is it set to on?

Alarm of s set to auto

here is code

IMG_0252.jpg

[iamchadster]

Can you inspect the probe for something that might be causing the reading to go all over the place? Look up the business end with a small light and see if anything might be in there. I had this happen once and small piece of sludge was in there. I took some of the canned air that you use to clean keyboards etc, and gently blew it out.

[reeferandy]

This may seem like an obvious thing, but I experienced the same problem until I figured it out. After you changed the alarm trigger point to 38 did you click the button to send the updated information to Fusion? The little button in right upper corner.

[boozeman27]

Thank you for the replies. Yes I have updated the apex after making changes. I have changed the thresholds, unchecked the alarms all together, I have cleaned the probes and made sure nothing was stuck in them. I still get the exact same alert every single hour! 24 times a day! No matter what my salt level is. It is very annoying

[reeferandy]

I believe when this happened to me - the same thing happened to me when I first installed it - I rebooted the Apex controller and that solved the problem.

[boozeman27]

I believe when this happened to me - the same thing happened to me when I first installed it - I rebooted the Apex controller and that solved the problem.

That's a fantastic idea. Cant believe I haven't tried that yet.

[reeferandy]

Please let me know if it works!