Stringify.com just announced support for IFTTT but now I want more. 
https://search.stringify.com/things
Seems like a great thing for HA to support natively.
I just started looking into Stringify for doing chained commands. Wouldnāt you be able to use the maker channel in IFTTT with this to send commands to HA?
Yes. 100% ā¦ I was just thinking about more direct support in case there were any delays introduced via IFTTT.
I only looked briefly, but I thought that Stringify had itās āmakerā type channel. Was pretty sure I saw it but Iām on my way out the door so Iāll have to check later. But I thought there was a method for sending post/get requests directly from Stringify.
That would be interesting! I didnāt see that ā¦ and didnāt even think of it since I thought the Flows had to be made on the mobile device (which is annoying).
I just got signed up and connected my accounts and there is indeed a "makerā channel for sending GET/POST/PUT requests via HTTP.
2 Likes
THATāS GREAT THEN! Iām sure the IFTTT component can be modified pretty easily to create a Stringify Componentā¦ to just get another logo for the HA website.
2 Likes
Any update on this?
I have been using this for a while now. Basically, you just use the āMakerā thing to do api calls to a script or a switch or whatever in HA. Its a lot more versatile and reliable than IFTTT. For example, I am using it to create a flow, that turns on my door light using the location sensor in my iphone, when I come home, but only if its passed a certain time. So it would be like: turn on my door light when I am within 300 meter range from home, but only if its after 5 PM.
With IFTTT, I could only create one condition and one action, but with Stringify, I could create many conditions and many actions in a single flow. I have even gotten it to work with voice commands with Google Home, but I still prefer to use IFTTT for that.
Itās slightly a bit different in the way you would set it up IFTTT, as you would need to put the API call within the URL of your HA server. If you try to put the API call within the āField NAMEā field, stringify will set off every device in you YAML file. It was a nightmare trying to shut everything down. If you put the call in the URL, every runs as smooth as butter and a lot quicker than IFTTT.
Could you expand on this for me, please?
Iāve been using Stringify for about 8 months now & I really like it.
But I have run into a few issues with IFTTT. I have quite a few Sonoff devices and use IFTTT as a way to issue commands to the server used by Itead.
Is there a way to get Stringify to issue commands directly to Home Assistant?
Iād still want to use Stringify as my main platform for my automationās as Iāve already got everything built & working, my plan would be to flash the Sonoff devices with Tasmoda & host them locally on a Pi running Home Assistant (cutting out the IFTT & the Itead server).
If this can this be done can anyone expand on the post above?
Looks as if no one answered your question. This quick answer is that stringify still does not have a Home Assistant āthingā available to control home assistant entities directly. You need to make an API call using the āmakerā thing.
I still have yet to figure out how to use it with entities other than the ones in the āscriptā domain. If I try to use it directly with lights or switches (for example), it will launch every light or switch entity within your home assistant. So if you want to use Stringify to turn on your porch lights when you come home, youāll have to create script to turn on your lights, and then use the API function in Stringify to launch that script.
Here is an example of what I have:
In Stringify, add and open the āmakerā thing. Within URL type:
http://<your_external_URL:8123>/api/services/scripts/<your_script_name>?api_password=<your_ha_password>
Data: JSON data
Authentication Type: None
Leave everything else blank.
You can test it out using the ābuttonā thing as a trigger.
Good luck!
1 Like
Many thanks for your reply.
I spent a fair bit of time getting this to work but finally managed it a few weeks ago.
I tried using <your_script_name> in the URL but found that it triggered every script in my scrips.yaml file.
So I replaced <your_script_name> with the (iirc) 13 digit number thatās used as the ID in the scripts.yaml file and that seems to do the trick. Everything else is left blank in the Maker thing.
Itās been fully up and running for about 3 weeks or so now & im really impressed, so much better than using IFTTT 
.
How do you pass parameters here? I tried filling in the json data but I donāt appear to be receiving this parameters in my script.
All sorted, was just doing something a little wrong.
also the following line has a mistake:
Should be following. scripts = script
http://<your_external_URL:8123>/api/services/script/<your_script_name>?api_password=<your_ha_password>
Could you please clarify the syntax? Your comment does not make sense. Should it read : http://<your_external_URL:8123>/api/services/scripts = script/<your_script_name>?api_password=<your_ha_password> ? Please supply a working example.
not a working example, but an example of what a real world api call in stringify would look like:
http://bob.duckdns.com:8123/api/services/script/script.living_room_lights?api_password=mypassword
alternatively, you could also try something like:
http://bob.duckdns.com:8123/api/services/light/turn_on?api_password=mypassword
and putting the following in the field(s) as json data:
{
"entity_id":"light.living_room_lights"
}