The Stringify team sent out a message on Monday 8th that the service will be shut down in June 2019. Based on the reaction of many users, that was bad news.
To send a clear message, we just wanted to reassure you we're not intending to follow the same path as Stringify, so don't fear!
Apilio started off as a personal project with a basic, but versatile feature set. In the last few months we have been very busy in the background, trying to determine how best to grow and support our amazing user base. In order to deliver our plans, we recently succeeded in raising funding to incorporate and build ourselves into a stable service provider you can rely upon. That's not to say there won't be changes in the future - at some stage we may have to introduce charges to keep the platform and the operation sustainable - but we will do so in a fair and transparent way that keeps the Apilio community making amazing things happen, when they're supposed to and how they're supposed to.
If you have any comments or questions it would be great if you could put them on our discussion forum, so everyone can follow the discussion. But of course you can always use the other channels available.
Have you ever worried about your automation setup to do something in an unsuitable moment? Or hesitated to automate something because you think its rule would apply more often than desired? Then worry no more - Apilio will help you out!
Say you have a setup that lights up your house when you are coming home at night. You probably don’t want that to happen when you come home after a long night and your family is sleeping peacefully?
Or you have an automatic watering system for your garden which set’s off in the middle of your garden party… Well, your guests at least will have a story to tell.
However elaborate you automation rules are, there will always be the exception to the rule. This applies even to the most advanced AI powered systems - because even those systems cannot read your mind (luckily) or collect all data needed to foresee every exception.
A novelty on Apilio might be exactly what you have been waiting for. With the addition of different “execution modes”, Apilio now offers a way to handle the “exception to the rule”.
The default mode on Apilio is still to trigger actions immediately without warning or asking you for permission. But with the modes “Warn” and “Suggest” you have more options to control the workflow.
With the mode “Warn”, Apilio will send you a push notification before an action is triggered. But it does not only warn you, but it also gives you the option to intercept the actions with a single touch.
If you are even more cautious, you can use the mode “Suggest”. In this mode, Apilio become more like a helpful assistant that suggests probably fitting actions. You can accept those too with a simple touch on your smartphone.
Get more detailed information an setup instruction in the documentation for execution modes.
I’m eager to see if you like this feature as much as I do!
I’m very happy to announce release “Therwid” (an acronym of The Release With many Delays). I gave it the name not only because of the functionality added, but because it was planned to be ready much sooner.
This is one of the most requested features and it finally made it to production.
With this newest release you can define up to 6 actions per Logicblock!
Just click "Add IFTTT Action" to add more actions.
Custom delays between the actions are not yet implemented because that needs some additional work in the backend. For the time being, the actions will be executed in the order as seen on the Logicblock with a short delay of 1 second (to make quite sure that IFTTT will receive them in the correct order).
But rest assured, the Multi-Actions are already prepared for delay configuration and that feature will be the next!
I tried to find an easier way make to call your IFTTT Applets (formerly known as recipes) from Apilio. Instead of fumbling with URLs, you can now work with easy-to-remember event names.
The goal of the re-make was to make it easier to integrate Apilio with IFTTT. As I learnt from some users, this was quite a hurdle for some of you.
With the old version, you had to configure the Positive/Negative action on the logicblock with the complete external URL:
With the new release, the same configuration looks like this:
I was able to make a script that updates all existing users and logicblocks to the new format. So no work for you on that side!
I hope you also like the updated version!
At the end of every logic you implement with Apilio there's one crucial task to do: Making a link to an IFTTT Maker Channel recipe in order to trigger any result. With the new update coming, this is going to be a lot easier!
The old method: Pasting in a complete link
To bring Apilio online as quick as possible and to keep thing simple I had decided to implement the link to IFTTT as simple as possible: A single URL field for each possible outcome (positive and negative).
While this solution is straight forward and works ok, I quickly learned that it was quite a roadblock for some users. This is the case because first you have to compose the URL by yourself and then copy it to Apilio.
The new method: All you need is the name
Once you have stored your API key, triggering an action on IFTTT is as easy as writing down the event name of your IFTTT recipe.
This reduces the number of clicks and jumps to create a new setup on Apilio a lot and should be more convenient for newcomers.
The new feature is currently hidden but available for beta testers. But even after that, the existing logicblocks will continue to work just as before.
If you want to try out the new feature just drop me a line so that I can give you that special "beta-tester" flag!
This week IFTTT published an interesting article with stats about the IoT on the IFTTT platform. There are many interesting numbers stated in the article but two of them caught my full attention.
1.5 Million connected IoT channels
I think the possibility to combine multiple triggers and conditions is especially valuable for IoT users!
While unintended actions in the digital space are easily dismissed and reversed (e.g. a wrong photo saved), they can be annoying or costly in the real world (e.g. air conditioning running purposelessly while no one's at home).
And for devices with sensors: By combining the information from multiple sensors and other inputs from the digital space you can greatly improve the correctness of the decision taken by a ruleset.
This is not a theoretical scenario, as the following number demonstrates: Among those IoT users, 21% have more than one IoT Channel connected.
For every one of those users, combining the inputs from multiple devices boosts the value of their personal IoT ecosystems to a whole new level.
The Swiss are most the active IoT users on IFTTT
There is a nice list of the countries with the highest IoT adoption rate on IFTTT with Switzerland at the top! 45% of Swiss IFTTT users own a connected device.
I wasn't expecting that Switzerland is first in this statistics, but actually it is not so surprising. The Swiss are well connected to the internet (Akamai State of the Internet Q1 2016 , Swiss broadband statistics) and IoT early adopters. Futhermore, they seem to love new technologies and expensive gadgets (like Teslas and Apple Products).
To sum all up: The birthplace of Apilio is not just coincidence.
Made in Switzerland and loved around the world :-)
I was quite excited when I heard that Amazon is selling a modified special version of its Amazon Dash Buttons. While the normal Dash buttons cannot do anything else than order one thing on Amazon, the AWS IoT Button is “programmable”, meaning you can set it up to connect to everything that is reachable via the internet. But what sets it apart from other options?
What's so great about the AWS IoT Button?
What are the negative points?
The AWS IoT Button needs a cloud counterpart, which is the AWS IoT Platform. From there you can program it to connect it the internet, i.e. to IFTTT via the Maker Channel and from there to Apilio, of course :-). As you can see by looking at some step by step guides (links at the end of the article), this is quite complicated and not manageable by the average consumer (who don't seem to be the target market anyway).
Another drawback is the battery which is said to last for about 1’000 button presses. After that, you can’t use the button anymore because the battery is not replaceable (well, it might be possible, but you have to break open the case: )
The current version of the AWS IoT Button is an interesting piece of hardware - nobody else has managed to pack the functionality in such a small case and sell it for 20 dollars! But It’s not ready yet for the mass market because of the non-replaceable battery and the geeky setup procedure.
A dream for tinkerers, a glimpse into the future for consumers.
Step-by-step guides on how to setup the AWS IoT Button and connect it to IFTTT