IFTTT recipe checking wrong variabe? [SOLVED]

Ok, this is odd… I have a Core in my basement doing two simple checks with an AM2301.

In my Setup() I have:

Spark.variable("temp", &temp, DOUBLE);
Spark.variable("humidity", &humidity, DOUBLE);

I have four recipes in IFTTT:

  1. If humidity on “SumpMon1” is Greater 45, then send a notification
  2. If temp on “SumpMon1” is Less 50, then send a notification
  3. If SumpMon1 is Online, then send a notification
  4. If SumpMon1 is Offline, then send a notification

3 and 4 work perfectly with little delay. 1 and 2 seem to work mostly except for about twice a day rule 2 triggers showing me a temp of around 32-33. The problem is this is NOT the temp, it’s the humidity! When I check manually right after the alert it is clearly swapping the variables. The temp never gets even close to 32-33, but the humidity is smack on those values at the time the alert is triggered.

So my question is, how do I troubleshoot this? It seems to me like the Core is reading perfectly and IFTTT is the one with a bug somewhere. I will have to set up a log of this data to prove this conclusively, but I would be very surprised if the Core, code on the Core, or the AM2301 is to blame here since they seem to have proven reliable so far. It’s only the IFTTT recipes that are behaving strangely.

I think eventually I will change to SSE and have IFTTT only handle the alerts and leave the logic entirely to the Core, but that will take some more time. That said, IFTTT should work as-is.

@Dave any thoughts?

i wonder if the event name you are using is too generic and someone else is also publishing using the same name…

But it should be a private event publish tagged to your account so there shouldn’t be any conflict…

Maybe you can observe the events published by your core and match them against the alerts :slight_smile:

I don’t think he’s using SSE yet. These should be the variable calls.

@ssstraub, have you perhaps got an old recipe which uses the same variables? They’re known to cause conflicts sometimes. Could you try renaming your variables to something you haven’t used before?

1 Like

Oh yes totally. my bad!

Hi @ssstraub,

I suspect you’re hitting this old bug in the firmware:

I’ll bring this up with the firmware team again.


1 Like

I have definitely used those variable names before, so I’ll try renaming them first and see if that clears it up. Thanks!


It’s been 2 days now with not a single false alert. That’s more like it! :sunglasses: Thanks for the help!

1 Like