My incoming IFTTT portal resources stopped working... on March 16 or 17...

 

Just in case, I created a new one - and it also fails.  This is what it looks like when I put the URL into Chrome:

 

(The status code is 404 - File Not Found)

 

My 'Goodnight' function worked fine on the 16th - and not since...

 

 

The URL in IFTTT matches the URL that the portal indicates. As far as I can tell - none are working.

 

Did anything change in the portal regarding this in the last maintenance release?

Edited March 22, 20178 yr by MWareman

My incoming IFTTT portal resources stopped working... on March 16 or 17...

 

Just in case, I created a new one - and it also fails.  This is what it looks like when I put the URL into Chrome:

 

portal.PNG

 

My 'Goodnight' function worked fine on the 16th - and not since...

 

runlog.PNG

 

The URL in IFTTT matches the URL that the portal indicates. As far as I can tell - none are working.

 

Did anything change in the portal regarding this in the last maintenance release?

 

The maintenance was on the 19th, in the morning.

 

There were no changes to IFTTT APIs.

 

I will test that and get back to you.

 

Benoit

OK - Thanks!

Info only: I'm not experiencing any difficulty with IFTTT and the ISY.

Info only: I'm not experiencing any difficulty with IFTTT and the ISY.

Via the portal?

I also am having no difficulty with IFTTT talking to ISY via the ISY portal. (I just set up Google Home > IFTTT > Maker Channel > ISY > SimpleControl to control AV).

Michael,

 

I tested it, and it worked just fine. I also see plenty of successful requests in the logs.

 

Please make sure to use a POST in your recipe. GET will not work.

 

Benoit

Info only: I'm not experiencing any difficulty with IFTTT and the ISY.

 

Via the portal?

 

Yes.

I hadn't used IFTTT in about 10 months.  It wasn't working well then and I had other priorities.  I'm back at it now.  At first, I couldn't get it to work at all.  Finally, I changed the key and it was working like a champ!  But that's when I was clicking on [Check Now].  

 

I found that IFTTT would take 2 or more hours to react when left to do it on its own.

 

My trigger is gmail, waiting for a specific subject with certain words in the body of the email.

 

This is not acceptable for my purpose.  I suspect that it has to do with IFTTT checking gmail.  Is there another trigger I could use besides email?

Update. My recipes are working fine now. Not sure why.

 

Just to clarify - these are Google Have me instant triggers running a Maker channel request to ISY Portal. The run log was showing a 404 error from the portal. It's working fine now.

 

Anyway, problem solved....

Update. My recipes are working fine now. Not sure why.

 

Just to clarify - these are Google Have me instant triggers running a Maker channel request to ISY Portal. The run log was showing a 404 error from the portal. It's working fine now.

 

Anyway, problem solved....

 

A 404 means that the request did not match any of the the portal endpoints.

 

So this could be a typo in the URL path, or if using a GET instead of a POST. 

A 404 means that the request did not match any of the the portal endpoints.

 

So this could be a typo in the URL path, or if using a GET instead of a POST.

Yeah, I know what 404 mans. It's just that the rule was working for a couple of months f months, stopped working (with 404) for a few days, then started working again - all without changing the URL at all. So, something must have changed portal side...

Michael,

 

No updates were done on portal, except for the announced update on sunday the 19th.

 

I believe your ISY was offline during that period. 

 

I'm sending you a log in a PM.

 

Benoit

Just to confirm from our PM discussion. I only got 404 when testing not from a browser because I was issuing a GET. Portal requires a POST.

 

The actual error was something else (5xx) and it looks oks like this was caused by my ISY being offline (dns issues). A reboot of the ISY solved the issue.

 

What was odd was my extensive Pushover notifications were all working fine, so it took a while before I thought to look presentable n the dns client direction. Seems ISY was able to generally resolve DNS, just couldn't resolve the Portals address... Not sure why...

 

So, issue resolved by rebooting ISY...