Hi everyone, a number of updates again in the month of November! Here's a summary of what has changed. As always, if you have any feedback let me know.
The sequence log has been enhanced making it much easier to search and filter through the logs. In particular I had received feedback that seeing disabled sequences in the log made it difficult to find relevant entries for active sequences. Now you can hide disabled sequences, and apply many more filters!
On the sequence log page just click the show filters button at the top and you'll then be able to filter by sequence, variable and status. Here's a preview of what it looks like now. As always, click the magnifying glass icon next to an entry to see specific details of what ran. The update in August also improved the detailed logs so you can see additional information, such as new variable values, through the sequence log.
SEQUEmatic works with an increasing number of external services, and sometimes they may not be available. You can now check on these services from the status page. If your external devices aren't triggering or your weather steps don't seem to be working, check this page to see if there is a problem with one of external services.
The text comparison step was previously case sensitive. Now you have the option to make this case insensitive which means values such as open and Open can be considered the same.
When setting a pause you can either set a pause time or use the value of a variable. Previously if using the value of a variable the pause was in seconds. Depending on where the variable value comes from, you may not be able to convert it to seconds so now you can select either seconds, minutes or hours when using a variable value in a pause.
One of the more common triggers people use is to run a sequence at regular intervals. You can do this with the periodically trigger, however when this was added it set the frequency from the moment you saved the step. If you were setting up the sequence at 1:15pm but wanted it to run every hour on the hour you would have needed to come back and edit it again at 2pm so it would run on the hour.
Now, it's possible to set the first instance the sequence will run. Subsequent runs then occur based on the frequency you set so you could schedule it hourly from the next hour and it will always run on the hour!
When calling a variable webhook, previously it provided a status such as success. The output now includes the previous and new values of the variable which you could then reference back in the calling system as well. Below is an example of the new JSON structure of the variable webhook response.