API call via Workflow iOS app

---

Hello everyone.

Hoping to find some iOS user that has been able to invoke Pimatic API via HTTP request from Workflow app. Idea would be to create workflows to update variables, enable/diaable rules or control devices.

I managed to do it but it works once or twice and then it stops working and all http requests simply time out.
If I change something in the variable I aim to update directly in Pimatic, it seems to work a couple of times more, but then it starts timing out again.
Note that no changes are carried out in the workflow between working and not working.

I’m not 100% sure how to call API in Workflow with ‘Get contents of URL’, so any help would be great.

Here’s a simple workflow that aims to update a variable and always times out: https://workflow.is/workflows/15ab199dde61457b97a10cac8283d9e6

Thanks in advance for any help.

Sorry im not a Apple user but i think i do stuff that you want with the Android app “tasker”.

I had made this little Guide

https://forum.pimatic.org/topic/2797/examples-for-using-andriod-app-tasker-with-pimatic

This works perfect for me…i dont if anything in this helps you but maybe there is something that helps you.

Thanks a lot for the insights.

Does anyone know if there is any kind of API usage limitation that may be causing these http request timeouts when calling API from Workflow?

No message in pimatic when this happens (or in pimatic-daemon.log), would there be any log on these API calls? Not sure if the issue is on pimatic side or Workflow app side.

Thanks in advance.

Last tests seem to show that the requests timed out may be caused by requesting PATCH without any GET first.

Once I do a GET (no matter which one), then I’m able to do PATCH without issues.

Is this “limitation” in pimatic?

Thanks again for any input.

For anyone that might be interested, I managed to make this work properly, by always doing a get call to a dummy variable I created in Pimatic. After that, API calls all work properly without timing out.