LDK Not Sending Push Notifications

[Siberwulf]

Hey folks, I'm struggling a bit and people tell me I'm "smart" sometimes.

I've setup a new Apex, hooked it up to Fusion, and things are mostly working how I want them to.

Here's what I'm working with

• Configured my FMM
• Two LDKs
• Two Optical Sensors (Sump Hi/Low)

I'm *trying* to get my LDKs to send a Push Notification when they see water. I've setup the Opticals to do this, and it's working just fine. Here's my Alert config:

Set OFF
If LD_Sum CLOSED Then ON
If LD_Flr CLOSED Then ON
If Smp_Lo OPEN Then ON
If Smp_Hi CLOSED Then ON

The LD_Sum and LD_Flr are the LDKs, and the Smp_Lo and Smp_Hi are the Opticals.

Am I missing something here? I do see in Fusion that the indicators go to "CLOSED" when the water is detected by the LDK, I just don't see any of push notification.

 

[SuncrestReef]

Does your Apex have an active alarm? If it does, that will block the Apex from sending you any new alarm notifications until that first alarm condition is cleared. For example, does your pH, salinity, or temperature probes currently have alarm thresholds defined under those Inputs and something is out of range? That will override your EmailAlm programming.

Take a look at your Alarm Log to see the most recent alarm condition.

Read my Apex Alarms tutorial for tips on how to best optimize your alarms so things like leak sensors have a higher priority than a probe value:

Neptune Apex Programming Tutorials, Part 6: Alarms

Neptune Apex Programming Part 6 of our series: Alarms.

www.reef2reef.com

 

[Siberwulf]

Does your Apex have an active alarm? If it does, that will block the Apex from sending you any new alarm notifications until that first alarm condition is cleared. For example, does your pH, salinity, or temperature probes currently have alarm thresholds defined under those Inputs and something is out of range? That will override your EmailAlm programming.

Take a look at your Alarm Log to see the most recent alarm condition.

Read my Apex Alarms tutorial for tips on how to best optimize your alarms so things like leak sensors have a higher priority than a probe value:

Neptune Apex Programming Tutorials, Part 6: Alarms

Neptune Apex Programming Part 6 of our series: Alarms.

www.reef2reef.com

That was one of the first things I checked, actually! I disabled my probes, and then tested the Optical. It showed the alarm, which meant it was the only thing in the alarm state. Then I cleared the alarm. Then I tested the LDK by putting it in water. No push notification, but it did show up as "CLosed" in the status.

Just now, I looked at my FMM, and see both LDKs are configured here. Would this interfere with the alarm task?

 

[SuncrestReef]

That was one of the first things I checked, actually! I disabled my probes, and then tested the Optical. It showed the alarm, which meant it was the only thing in the alarm state. Then I cleared the alarm. Then I tested the LDK by putting it in water. No push notification, but it did show up as "CLosed" in the status.

Just now, I looked at my FMM, and see both LDKs are configured here. Would this interfere with the alarm task?

No, any programming you have on the EmailAlm output operates completely independently of other outputs which might also have programming using the same sensors.

I know you listed your alarm code in the first post, but could you post a screenshot of your EmailAlm program like you just did for the FMM output?

 

[Siberwulf]

No, any programming you have on the EmailAlm output operates completely independently of other outputs which might also have programming using the same sensors.

I know you listed your alarm code in the first post, but could you post a screenshot of your EmailAlm program like you just did for the FMM output?

Here ya go:

 

[SuncrestReef]

The code looks correct. If you're certain there is no other active alarm, and LD_Sum or LD_Flr is CLOSED, then the Apex is malfunctioning. This can happen if you have any duplicate names anywhere within your system (such as 2 outlets named "Unused") or even if a module is named the same as an output. In fact, I just went back to look at your screenshots and see that you have an Output named "FMM" on the Module named "FMM". So you need to correct that duplicate (and any others you find), save the changes, then reboot the Apex to reload the corrected config.

 

[Siberwulf]

The code looks correct. If you're certain there is no other active alarm, and LD_Sum or LD_Flr is CLOSED, then the Apex is malfunctioning. This can happen if you have any duplicate names anywhere within your system (such as 2 outlets named "Unused") or even if a module is named the same as an output. In fact, I just went back to look at your screenshots and see that you have an Output named "FMM" on the Module named "FMM". So you need to correct that duplicate (and any others you find), save the changes, then reboot the Apex to reload the corrected config.

Well holy smokes, that was it. I renamed the FMM Output to "FMM_Output", restarted things, and then it works. That's so random (And I'd love some UI feedback this was the case!).

Thank you much!

 

[SuncrestReef]

Well holy smokes, that was it. I renamed the FMM Output to "FMM_Output", restarted things, and then it works. That's so random (And I'd love some UI feedback this was the case!).

Thank you much!

Excellent! Glad it's working.

Yes, it would be nice if the Apex prevented you from creating duplicate names. But whenever I hear about unexplained problems like you described, that's the first thing I check for.

If you haven't seen them, take a look at my whole series of Apex Tutorials:

Articles by SuncrestReef

www.reef2reef.com