I've upgraded a number of things on my Windows 10 system including passwords, Java, and ISY to 4.3.26.

My Tasker Actions have started failing and I cannot determine why.  They seem to hang altogether without returning a completion code.

 

I was using Restask and I've also tried a straight HTTP GET from Tasker.  It looks to me like Java is hosed but I can't tell why.  I've rebooted my desktop where the ISY instance lives and my phone as well.  Any ideas or suggestions on how to further troubleshoot?  Warning:  I am somewhat knowledgeable but by no means a programmer, keep that in mind please.

 

 

Thanks much!

Edited November 22, 20159 yr by theojt

Hi theojt,

 

The REST command to ISY is not complete.

 

With kind regards,

Michel

It appears that way in the picture but here is the full REST statement that I am attempting (look closely to validate):

 

http://192.168.2.151:8151/rest/time

 

I thought this was valid?

 

I get no error return, no nothing, it just hangs.  Is there a way I can look at incoming statements (and perhaps handling) on the ISY side?

 

Thanks again.

Is here not login information required each GET?

Hi theojt,

 

Ah, I didn't see /time at the end.

 

Yes, open the Event Viewer, change the level to 3, and then issue the commands a few times. Then download Tools | Error Log and check the traffic.

 

With kind regards,

Michel

Is here not login information required each GET?

 

Yes, and I usually have it specified by Restask.  I'd be happy however if I'd just start getting an error code back which I'd expect if I attempt an unauthorized request.

Got the error log, but it doesn't state much.  As you can see, I get updates from a different source (192.168.2.150) that sets state variables.    However, Tasker (running on 198.168.2.209) just hangs.   I don't even see any log entries from it.  I'm wondering of Tasker isn't even seeing the GET command.

Edited November 22, 20159 yr by theojt

After a lot of testing, I came to the conclusion that this was not an ISY issues but a Tasker/network issue.  Just re-installed Tasker, Restask, rebooted and I am functioning again - guess it was just one of those network burps!