Jump to content

Help With Resource Editor


garybixler

Recommended Posts

Posted

Hi,

I am not able to get the following to work in the Isy but I am able to get it to work in Chrome's Poster. As I know almost nothing about programing I was wondering if something here is incorrect. On Poster I did need to add the URL Parameter (Method HTTP/1.1) but that seems to be present in the ISY automatically. The messages I get are:

TCP Client Read Response Failed (Net Module Rule:67) and

TCP Client Request Failed (Net Module Rule:72:401)

This is how I have the editor configured:

 

Protocol Information:

HTTP POST Host: www.mytaglist.com PORT: 80 Path: /ethClient.asmx/PingTag Encode URL (not checked)

Timeout 500 Mode Raw Text

 

Headers:

POST /ethClient.asmx/PingTag HTTP/1.1

Host: www.mytaglist.com

Content-Length: 14

Content-Type: application/json; charset=utf-8

 

Body:

{

"id":"0"

}

 

 

Sorry couldn't get the image posted.

 

 

Not sure but I don't think any cookies are involved as I deleted all before testing with Poster and it is using normal HTTP.

Also the signin API seems to work from the ISY as I get no errors just an http 1.1 response.

 

Thanks for any insight.

Gary

Posted

Gary-

 

I believe the Tag manager requires a cookie for authentication - not supported by ISY.

 

Sorry.

 

-Xathros

Posted

Yes that is what I thought but I don't see where it is used in Poster. I did delete the cookies in Chrome and used Poster after that without doing any logon. So, not sure what is going on.

Posted

Hmmm. That would lead me to believe that a cookie is NOT needed . Can you test poster from another machine where you have never logged into the tag manager from to verify?

 

The cookie requirement was posted here last week by another user (larrylix maybe...)

 

-Xathros

Posted

-Xathros

Unfortunately you are right. I get an authentication failed using a different computer that has never be logged on to tags.

Also it is Postman I am using not Poster, my error.

Thanks Gary

Posted

Well, that pretty much proves it then. It bugs me that these outfits are forcing us into their cloud to access a device on the LAN. Nest, Ubi Tag Manager, Nexia and much more I'm sure. These guys need to allow us local access for our integration and let us worry about security on the LAN side of things.

 

-Xathros

Posted

BTW, because the login from the ISY seems to work is it possible to also include the PingTag post in the body of that request. Just grasping for straws.

Posted

Hehe. Sooo many people here - with my aging memory, it gets hard to keep track.

 

-Xathros

Guest
This topic is now closed to further replies.

×
×
  • Create New...