Version 0.7.0 of NodeLink added a Location module.  This can be used with the mobile app Locative or something like Tasker to indicate to the ISY whether you're home or away.

 

Once the module is loaded you'll see the corresponding REST calls required to set the ISY variable.

• Rest Calls: You would enter these calls into your location software.  If you want to call these outside your LAN you will have to figure out the correct external address.
• Port: This is the port the module web server runs on (to receive the calls).  I made this different than standard NodeLink ports to limit and security threats if you decide to open the port up through your router.

There are plenty of other location options for the ISY.  I created this one because it took all of about an hour and allows you to set location on your ISY without reliance on the cloud, and without opening the main ISY or NodeLink port up to the public.

FYI - Your notes on the location tab give the internal IP for the ISY instead of the NodeLink IP - the xxx happens to be my ISY - If I change it to the NodeLink IP it works fine  

 

 

HTTP Calls (GET or POST) Home: http://192.168.2.xxx:8995/home Away: http://192.168.2.xxx:8995/away

Yep, fixed in next version

io_guy, can this module work with a number of different devices(phones) that are distinct from each other?  There are times that my wife or kids are home and I am not, do I don't want to create a geofence that's tagged to just my phone.  I can program the logic for seeing if EVERYONE is gone, but I'm not sure how to accommodate multiple people.

Right now it can't. I really made this as a simple REST location to fire off my Tasker app. I wanted something on its own port so I didn't have to worry about opening up the ISY and/or NodeLink main. Didn't think anyone would actually use it.

 

That being said, in the next release I'll add support for multiple calls. Within NodeLink you'll specify the number of devices you want and it'll create a subnode for each device (and provide a different REST call for each device).

@io_guy: I'm getting the following error when attempting to add a new "Location" device in NodeLink Server v0.8.2:

2017-10-24 12:38:35 - ISY Error: Status 400 (INVALID_NODE_ADDRESS): ns/1/nodes/n001_n001_loc1_dev01/add/LocationDevice?primary=n001_loc1&name=Device01&nls=113LD

It looks like maybe there's an extra `n001` in the node name?

 

I can add the node manually in the Admin Console @ n001_loc1_dev01; however, no status is available.  Trying to add it manually @ n001_n001_loc1_dev01 gives a "Bad Request" error.

 

Anything I can do or is this a bug in the software?

Bug, I'll get it fixed in the next couple days.