garybixler

A tag motion event and other events from taglist are sent to the ISY using REST in a local URL. Example: http://admin:admin@192.168.0.55:2000/re ... /set/2/2/2 So if you have no need for the ISY to send commands to the tags nothing else is needed. I only send from the ISY via EventGhost to the taglist to speed up sensing back in range by using their API ping command. To use their APIs requires an authentication cookie. At this time the ISY doesn't support the use of cookies.

You can send REST commands directly to the ISY from your account on mytaglist. URL calling to your ISY can be from tag motion, out of range, temperature, etc. But if you would like to use their APIs to send a command to the tags from the ISY you would need to use EventGhost. The ISY can't save a login authentication cookie needed to send a POST request. What I did was write a script in Python which runs in EventGhost that can deal with authentication cookies in HTTP requests. So basically from a program I have the ISY send a TCP event to EventGhost which will then run the script to send an HTTP POST request to login and do a command like ping to the tag. I would be glad to provide additional info or examples if you desire the ISY to send commands to the tags.

starhome I have been successfully using wirelesstag.net for that exact purpose. The system is cloud based but can send events to the ISY using REST commands you configure on their web site. For the ISY to send commands like ping to the tags requires the network module and the use of EventGhost running on a PC. This can reduce minimum back in range detection from up to 5 min. to 2 or 3 seconds by having the ISY send a ping when triggered by a driveway sensor for example. Gary

Hi Michel This one stopped running after 2:00 AM: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 3 minutes Set Elk Zone 'OutLightLevel' Query Voltage Else - No Actions - (To add one, press 'Action') And this one didn't run but it was set for 2 AM so I changed it to run at 1:45AM from now on. If Time is 2:00:00AM Then Set Scene 'Outside Lighting / Low Voltage Lighting' Off Else - No Actions - (To add one, press 'Action') Gary

Thanks l very much Michel for your reply. I didn't put the length in because the ISY always seems to figure that out and enter it into the content length. I'm not sure how to figure that out. Do you just count the characters in the body? Also I would be greatly thankful if you could show a sample of what the parameters might look like. Been at this in different ways now for about two weeks including trying to use Python in EventGhost. Thanks. Gary

Hi I have the following in the Resource Editor that is set for 'post' and 'raw text': POST /ethAccount.asmx/SignIn HTTP/1.1 Host: urlname Content-Type: application/json; charset=utf-8 Content-Language: json Connection: keep-alive User-Agent: Mozilla/4.0 { "email" : "myemail", "password" : "mypass" } POST /ethClient.asmx/Ping HTTP/1.1 { "id" : "0" } I think the first part works as I get a return of HTTP 1.1 2 without the second post attached. What I would like to do is attach the second request to the first in order to use the same logged in session. I know it is a lot more complex then just adding a post. One time the editor came back with a string starting with 'Request ..... but I failed to wright it down. The data{} is what is required in the APIs So, I guess the question is whether or not this is possible? Thanks much for any assistance. Gary l

Hi I've just been adding some basic functions for it do from voice commands like arm/disarm the ELK and turn ON/OFF local lights as you can't be to far away from it right now. I sometimes use the timer function and play music. I'm kinda waiting for the production version that will supposedly add a lot more functionally

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.

I have mentioned that on their forum but I am sure it fell on deaf ears.

-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

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.

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

Hi Xathros Yes, that is one way I was going to go and in fact I have all the parts to do that. 1. A timer that can be adjusted for pulsing and pulse duration to trigger the trigger link. Runs on 12v 2. The trigger link or open/close sensor. Runs on 1.5v 3. Power converter to go from 12v to the 1.5 for the trigger link. Hasn't arrived yet. The only think I don't know yet is how many milliamps this setup will draw. Another that I have the parts for is a mini Ethernet to Wi/Fi module using the USB power converter for use in the car. The problem is the ISY can't send and receive a ping command at least maybe until version 5. The other problem is that it draws 95 mA. which would be a little high especially if you don't drive your car for several days. I really like the wireless tag over the others because there would be a lot of things the ISY could control making it a really robust system. Plus the battery drain would be negligible.

-Xathros I have found out from wireless tag that the logon to the tag manager requires a cookie and won't accept the basic authorization header. This was the response from wireless tag: "Just call the signin API and get the cookie and attach that cookie to ping method. Any browser will automatically do this you just need to find how to support cookie from ISY." Checking the forum I found that the ISY does not support cookies. It seems that logins always foil my attempts to automate across platforms. So much for open architecture. Not even sure why login would be necessary for local requests to the tag manager as no ports are open to the tag manager from the outside anyway. However the system does have great potential for tracking vehicles. A tag in the vehicle could be powered with larger parallel 3V batteries to greatly extent the battery life or even power it from the car battery. Sensing the vehicle is gone takes about 3 min if Auto-Update is set for 1 min. That amount of time is fine. The issue that I have is that it doesn't sense the return of the vehicle for maybe 15 min. even though the search time is set for 5 min. That it why I was hoping the ISY could reduce that time to seconds and execute immediate actions. So I guess I will continue in this direction and hope that something can be worked out between the tag manager and the ISY in the near future. Gary

Thanks for your help. I'll be doing a lot of trial and error today, but not much hope that I'll get this request to work. I'll reply if a success or not. Gary

Thanks -Xathros I hadn't seen that before but now where to add it. After Post, Host:, User-Agent: or Connection-Type?

The rest part does work. When I test the API from the ISY I get 'TCP client read response failed' (Net Module rule 67) They also state that the ping and other commands require a login. When trying to do that from the ISY I just get 'Request Failed' So this is about as far as I can go with this not knowing if responses are necessary or not. Thanks

I am thinking that the ping request goes to the tag manager that actually does the ping but I have no idea if any conversation is required beyond that. My only reply is that the tag is back in range via rest to the ISY.

Hi I was wondering if anyone has been able to ping a wireless tag on the wireless tag system using the ISY network module? http://wirelesstag.net/ I have copied their API into the ISY for doing that but it may be hung up on expecting a login which I haven't been able to get to work either. As their sensing a previously out of range tag may take a long time I would like to do a ping using the ISY to considerably reduce that time. Basically I would like to do a ping on missing tags (restoring in range and sending a rest command to the ISY) that are located in vehicles when the driveway sensor is tripped thus immediately being able to respond with some actions. Thanks Gary

Hi Bill Your custom behavior is correct except there should be a space between 66 and 1 in your nodes. This would be a GET command which is the default. Also it probably would not be a good idea to use port 80 as your router may assume it is for him. I use port 5010 and you would need to forward that through the router to your ISY's local address. And also configure the ISY to reflect that port as well or translate port 5010 to 80 in the router if you want to keep 80 as your ISY port.

Hi Bill Yes you can have the Ubi send HTTP Rest commands to the ISY to control your Insteon and other devices. Here is an example for turning a light on. (http://user:pass@your Internet address:port/rest/nodes/1F F7 5C 1/cmd/DON) At this time you would need to enter your Internet ISP address and port number to the ISY as the Ubi doesn't do local HTTP but may in the future. Gary

Hi Michel Super good news. Thanks Gary

Hi I was hoping to be able to ping small WiFi modules located in vehicles to determine their presence or absence. It would require being able to receive the response. Thanks

Hi Just wondering if there will be any ping capability in the network module at anytime. thanks Gary

Hi Things that I know for now. The HTTP requests come from their servers and need to be set up as if the request is coming from outside your local network. However I have not been able to send a REST command this way either. They are saying that they hope to allow the Ubi to make local requests in the near future. Also APIs should be coming out in several weeks that would allow requests to be sent directly to the Ubi like text to voice.