React works with ThingHTTP, ThingTweet, and MATLAB® Analysis apps to perform actions when channel data meets a certain condition. For example, you can have a mobile app report your latitude and longitude to a ThingSpeak™ channel. When your position is within a certain distance of your house, have ThingHTTP turn on your living room lights.
If you use the
React app with the Test
Frequency set to On Data Insertion when using
Bulk-Write JSON Data, your
React is triggered once per bulk-update request. It is
triggered when Condition matches
ConditionType, even if the Condition
is matched more than once.
If you set your
React to run on a specific Test
Frequency with a specific Condition Type, be
cautious of how your
React is triggered. The data is now
collected over time and updated as a batch, and the Condition
Type that triggers the
React can vary within a
single batch of data.
Define Reactions to Channel Data
Select Apps > React.
Click New React.
Click Save React.
ThingSpeak channels support numeric sensor data, text, strings, status updates, and geo location information. Use these condition types to specify conditions that trigger reactions based on your channel data.
This condition tests a text string with ASCII characters in a ThingSpeak channel field. For example, “If Channel 1, Field 1, is equal to blue, then set my light to blue.”
Check the data with these constraints when testing for strings:
is equal to
is not equal to
This condition tests a ThingSpeak status in a channel. The status field is similar to the text in a tweet. You can search the status for a word, and send a ThingHTTP request when the test condition is met.
Check the data with these constraints when testing for ThingSpeak channel status:
is equal to
is not equal to
If you have sensor data or numeric data in the fields of a ThingSpeak channel, use the numeric condition. For example, if your power use is over 300 watts, use a numeric condition to post this tweet using the ThingTweet app:
“I am using too much power”
Also, you can send a control command to another service or device that accepts HTTP requests using ThingHTTP.
Check the data with these constraints when testing for numbers in a ThingSpeak channel field:
is greater than
is greater than or equal to
is less than
is less than or equal to
is equal to
is not equal to
This condition checks the location data in a ThingSpeak channel. For example, if you have mobile app reporting your latitude and longitude to a ThingSpeak channel, you can turn on your living room lights when your position is within a certain distance of your house.
Check the data with these constraints when testing for location information on a ThingSpeak channel:
is farther than
No Data Check
This condition checks whether the ThingSpeak channel is receiving data at the specified interval. If no data updates occur within the specified time range, the action selected in your React app is triggered. For example, if a power outage interrupts your device and your channel is not updating, you can trigger an action. Specify the amount of time that your channel does not receive new data before triggering the action.
Select the frequency at which you can test for the specified condition.
On Data Insertion: Test each time data is inserted. You cannot have more than one React configured with
On Data Insertionfor the exact same conditions.
Every 10 minutes: Test every 10 minutes, on the clock. For example, a React created at 10:08 a.m. triggers at 10:10, and every 10 minutes after.
Every 30 minutes: Test every 30 minutes, on the clock.
Every 60 minutes: Test every hour, on the clock.
You can pass data to your apps using replacement keys. The following table summarizes the standard and custom replacement keys you can use. Some keys are specific to a particular type of request, as indicated in the last column.
|ThingHTTP replaces this custom replacement value with data in the trigger request that has the label "YOUR_CUSTOM_LABEL".
|The last value of the specified channel and field. Replacement requests to private channels not owned by the same user as the ThingHTTP request return blank values.
The latest value is %%channel_12_field_1%%.
The latest value is 2.5.
|The full date and time when the TimeControl or React ran.
The date and time the event occurred is %%datetime%%.
The date and time the event occurred is 2014-09-24 5:32 p.m.
|TimeControl or React
|The name of the weekday when TimeControl ran.
The day the event occurred is %%day%%.
The day the event occurred is
|The zero-based index of the weekday starting on Sunday.
The number of days used this week is %%day_index%%.
The number of days used
this week is 3.
|The hour of the day when TimeControl ran.
The hour that the event occurred is %%hour%%.
The hour that the event occurred is 5.
|The minute of the hour when the TimeControl ran.
The minute the event occurred is %%minute%%.
The minute the event occurred is
|The value that triggered React.
It is way too hot in here at %%trigger%%
It is way too hot in here at 40
|The channel ID that triggered React.
The channel that tweets is %%channel_id%%.
The channel that tweets is 1256.
Run action only the first time the condition is met: Trigger the action if the condition was previously false and is currently true.
Run action each time condition is met: Trigger the action every time that the condition is true.
React App with MATLAB Analysis Code Errors
When you have MATLAB Analysis code that uses a React, React stops running if there are a number of consecutive errors in the MATLAB Analysis code. You can choose to receive an alert via email by checking the box Notify me via email if this MATLAB Analysis fails when triggered by TimeControl or React in the MATLAB Analysis app.