We¿re trying to put together a simple M2X integration. We have an Android phone that sends one of two discrete values to and M2X stream. E.g. "1" or "2". We would like to detect either of these values and trigger a callback URL.
In the M2X web UI we¿ve configured a Trigger to send a POST to a callback URL. We¿re having a problem getting the trigger to work as expected. It seems to "miss" conditions that should cause it to fire. We¿ve tried several different trigger configurations including a ¿condition¿ or ¿on change¿ and "frequency" of ¿continuous¿, as well as other things like condition != 0, or condition <=1, reset >=2, and then manually sending a 2 from android immediatly following every 1 or 12. None of these seem to work consistently.
For example, using a trigger with "condition" set to ¿on change¿ and "frequency" set to ¿continuous¿ and a callback URL set, sending a value of 2 to the stream results in an entry to the stream¿s ¿Values Log¿ (as expected), however the ¿Trigger Log¿ will often not show a trigger event. Sometimes it does, but the majority of the time it fails to fire for its conditions.
Perhaps we are missing something obvious. Please advise. Thank you.
Can you share more information about this? (Device id, trigger id, time of occurrence), we need those to look into the logs.
I've checked the account on your username and it doesnts seem to have any triggers, but we have some reports of trigger callback urls responding with a `500` error and we would like to know if that could be the case or not.
I also encounter the same problem (Trigger not firing).
I'm trying to come out a simple demo using Beaglebone Black, M2X and IFTTT. I have a Beaglebone Black Board that sends binary values to a M2X streams. E.g. either "0"or "1". I would like to detect "0" and trigger a callback URL.
In the M2X web UI we¿ve configured a Trigger to send a POST to a callback URL. We¿re having problem getting the trigger to work as expected. It doesn't activate the trigger when the conditions met. I have tried the test trigger button and it works fine.
We've reviewed your account and found that the trigger you are referring to has a callback URL which is returning a response code of 301, which is the response returned by Requestb.in when a bin no longer exists.
Try updating the definition of your Trigger with an active Requestb.in URL to see if that resolves the issue.
The Callback URL utilized in the Trigger definition should be configured to accept an HTTP POST request. I've just created a test trigger using the URL you mentioned (https://www.tumblr.com/dashboard) as the Callback URL, and this resulted in a `302` error response.
If you're just trying to test things out you can create a request.bin which is by default configured to accept a POST request, and use the request.bin URL as your Callback URL in the Trigger definition. This will result in a `200` success response.
I have created a URL in request.bin and use this URL as my callback URL in my Trigger setting. It's still doesn't activate the trigger when the condition met. There's no response code of my Callback URL in the Trigger Log of the M2X Developer Portal.
Can you please help to advise the things that you have done to make the Trigger works? Did I miss out anything while setting a Trigger in the M2X Developer Portal?
Can you share the configuration for the trigger you are having trouble with, along with the Device ID?
The issue you are having may be that the trigger's notification frequency is set to "Single". If that is the case, the trigger will only be activated once when the conditions are met - any datapoints received thereafter that also satisfy the conditions will not result in a notification, until a datapoint is received that does not meet the conditions (in which case the trigger is reset). You could set the notification frequency to "Continuous", if you'd rather receive a notification whenever any datapoint is received which continues to meet the conditions.
I've checked your account and the device doesn't seem to be registering new values.
The only recent entry on the Trigger Logger is from 2016-03-15T02:12:02.863Z (UTC) and for that case, Requestb.in coincidentally responded with a `503` as if they were some problems with the service at that moment.
I tried to check what happened with older values but I see no recent datapoints registered by the device, all the existing datapoints are from the year 2010.
Can you please log some new values so we can check the problem?
Please confirm that you want to flag this content as inappropriate.
Please confirm that you want to delete this content.