As yet another month comes to a close, there have been quite a few updates at SEQUEmatic.
Following on from the success of the Tuya Smart Life integration, you can now link directly with eWeLink to control your eWeLink and Sonoff devices from your SEQUEmatic sequences. Direct integrations to SEQUEmatic are proving popular, so if there are any other services you’d like to see added please post in the comments below, the Q&A Forum or contact me directly.
Next, you may have noticed the live chat icon in the bottom right corner has recently changed. If you click that button you can now chat directly with the SEQUEmatic bot! Even though he’s busy running your sequences, he can always find time for a chat to help you work your way around SEQUEmatic so go ahead and ask him your questions.
The bot works best if you ask questions like you would to a person, and has some context of what you’re currently doing. For example when you’re editing a step you can ask him questions about that particular step and he’ll explain how to set it up. If he’s not able to help, he will offer to transfer your chat to me so we can chat in realtime.
Expanding on the features available in sequences, weather triggers and conditions are now directly built into SEQUEmatic. Previously you had to go via IFTTT which could be quite complicated, but now you can check the temperature, wind, rain and many other conditions directly from within a sequence. The weather can either trigger your sequence or you can use it within a sequence to check conditions before proceeding.
There are a lot of options available in this new step type, so be sure to check the docs for the full details.
Finally, an update has been made to the way sequences are logged. Navigate to the sequence log and click the magnifying glass next to the sequence to you want to view in detail. Previously the log showed you the steps which ran, but now it also provides information on the value of variables and other elements of the sequence as they were when the sequence ran. This can be very helpful in debugging your sequences. Note that this only applies to sequences which ran from now onwards – any sequences which ran prior to today will still display in the old log format.
Well, that’s it for this month but more is on the way! As always, post your questions and feedback in the Q&A forum, ask the bot your questions or contact me directly if you need help.
Sometimes you want an IFTTT applet to only run once every hour, but this can be tricky when there’s only one condition available in the applet. Paired with SEQUEmatic, you can limit your IFTTT to run only once per hour (or day or any other frequency you’d like)!
We’ve built a shared sequence to help get you started, so click this link and import it into your account. Then, we’ll take a look below at what this sequence does as well as the settings you need in IFTTT to make it work.
Let’s run through the sequence step by step:
ran_within_hour and only continues if it is false (ie it didn’t run in the last hour)ran_within_hour is set to true so that the condition in step 2 will fail if the applet fires again in the next hourran_within_hour is reset to false so that if the applet is triggered again the sequence can runTo get this running, you will need to create two IFTTT applets which are described below.
You probably already have a working IFTTT applet and this is what you’re wanting to limit to once an hour. We’re going to break that applet into two separate applets, with the SEQUEmatic sequence in between.
Your IF THIS applet can have any type of trigger. In this example we’re going to use the location applet when I enter a certain area. The important part here is the THEN THAT component which will use the webhook service to make a web request. When setting up the web request you only need to provide the URL. This should be copied from the trigger step in your SEQUEmatic sequence. Leave everything else with the default settings. You can view the full applet here.
You will need to create a second applet to take care of the THEN THAT component. Here the trigger should be the webhook service when it receives a web request. The event name should match the event name in step 3 of the sequence. In our example this was trigger_event. You can use any meaningful name here, as long as it matches in both IFTTT and SEQUEmatic.
For the action you can use any other IFTTT service – this would be the THEN THAT step from your original applet. I’m going to have it turn on my Philips Hue balcony light. You can view the full applet here.
That’s just about it. Be sure to enable both your IFTTT applets as well as the SEQUEmatic sequence. If you haven’t used IFTTT with your SEQUEmatic account before then you’ll also need to set up your IFTTT key in your account settings. You can read more about this here.
Finally, if you want to use this for multiple IFTTT applets, you will need to use a different variable name otherwise the sequences will interfere with one another. You can just duplicate your sequence, or import the template again, and modify the variable ran_within_hour in steps 2, 4 and 6 to any other variable name.
If you have any questions, post in the Q&A forum, leave a message in the comments below or contact me directly. Happy automating!
Following the positive reception of the Tuya Smart Life integration last month, I’m please to announce you can now also control your eWeLink or Sonoff devices directly from sequences. Read on to learn how to link your account.
Login to your account and navigate to the linked services page. Here’ll you find a number of services which are available to link to your account. Click Link account next to eWeLink / Sonoff to begin.
You’ll be taken to a page where you should enter your eWeLink credentials. Either your email address or phone number is required, depending on what you used when creating your eWeLink account, along with your eWeLink password. Once you’ve entered your credentials, click Authorise to link your account.
You will be redirected back to the linked services page, and it will show that your eWeLink account has been refreshed. If at any time you no longer wish to have your eWeLink account linked to SEQUEmatic, simply click unlink account to break the connection.
Controlling eWeLink devices from your sequences is simple. Just select smart device from the list of step types and a list of available devices will appear. For a single channel switch, there will be only one property which is switch, however others may have more than one channel which you can select.
In general, the only action available is to turn the device on or off. Click save once you’re done and you’re ready to go!
As always, if you have any questions post in the Q&A forum, leave a message in the comments below or contact me directly.
Many users are creating very powerful sequences using the custom webhook trigger. This feature allows you to trigger a sequence from another service via a webhook request, and you can even pass through JSON data. People are using this to trigger sequences from events on their Emby media server or based on weather updates.
In the past month there have been two important updates to this feature.
To help debug sequences, it’s now possible to view the content of the payload which was sent to SEQUEmatic in the webhook call. Head to your sequence log and click the magnifying glass to view the detailed log of that sequence run.
Next to the trigger step you’ll see a link to ‘view the payload’ which will display the JSON which SEQUEmatic received. Note that this is only available for custom webhook requests which pass a JSON payload.
The key benefit of using the custom webhook trigger is the ability to pass additional data into SEQUEmatic. In the case of the Emby media server this could be the playback event or film title. In the case of a weather service it could be the current temperature or upcoming forecast.
SEQUEmatic allows you to access this data in your sequence using sequence parameters. Take a look at the JSON below:
Perhaps this payload is sent to SEQUEmatic every time a student walks through the door at Hogwarts. It provides information including their name and house. When this comes through into SEQUEmatic, you can access the data by enclosing the variable names in curly brackets, for example {House} to get the value Gryffindor.
Now, you can also get the value of second (and third, fourth, fifth, etc) level variables by connecting their names with a hyphen, such as {Student-FirstName} to get the value Harry.
This can be used in most steps which take text inputs, for example in checking a variable value, in the content of an email alert or stored in a variable for use in another sequence, as in the example below.
You can read more about this in the docs.
So, what are you waiting for? Go ahead and see what you can create with the custom webhook trigger. I’d love to hear how you’re using this in the comments below, and as always if you have any questions just ask in the Q&A Forum or contact me directly.
IFTTT applets can be really powerful in automating your home, but sometimes you want them to run only during a certain time of day. Yes, you could enable and disable the applet throughout the day, but that seems to defeat the purpose of automation. Using SEQUEmatic, you can limit the time that your IFTTT applet runs so it only triggers during a certain timeframe or perhaps only at night or during the day. Read on to learn how.
The sequence itself is quite straightforward, and to help get you started you can import this shared sequence into your SEQUEmatic account. Here’s a screenshot of what it looks like.
Breaking this down, here’s what the sequence does:
Let’s go through what is required in IFTTT to make this work. In this example, I want my Philips Hue lights to turn on when I arrive home but only between 6pm and 10pm.
To trigger the sequence, I need to create an IFTTT applet which is triggered by location and then uses the webhook service to run my SEQUEmatic sequence.
In the IF THIS component, select the location service and set the location you need to enter.
In the THEN THAT component you select the webhook service and populate the URL field with the URL provided in the trigger step of your SEQUEmatic sequence. Apart from the URL, you can leave the other settings with their default values.
That’s all there is to the IFTTT trigger applet. You can view the full applet here.
The final piece you need in IFTTT is an applet which will control your device. SEQUEmatic will trigger this applet if the time conditions are met.
In the IF THIS component, select the webhook service to receive a webhook request. The event name should match the name provided in your SEQUEmatic sequence. In this example it was named trigger_device.
In the THEN THAT component, select whatever service you want to run. In my example I want my Philips Hue lights to be turned on as you can see in the screenshot below.
And that is all you need. Your applet here might look quite different depending on which service you trigger, however if you’d like to look at the full applet you can find it here.
In summary, what you’ve now created is:
Hopefully this has been helpful in getting you started, and you can now modify and expand on this set up for your own scenario.
As always, if you have any questions post in the Q&A forum, leave a message in the comments below or contact me directly. Also, if you’ve found this helpful share your use case in the comments!