Beginner's Guide

[KT]

Hi everyone-

I just purchased a couple of these PIR sensors and have a few newbie questions.  Thanks everyone.

My environment: 

- Dropcam

- Nest Thermostat

- RTI XP-8 Home Automation controller

Questions:

1.  Is there a way I can use the 2-way tcp/ip driver for my RTI to query information from the wireless manager?  How about a restful api from the wireless manager?

2.  If I use the "if motion detected, use the temperature of the sensor in the same room", does this mean I have to enable IR sensor arming?  Would this cause my alerts to go off?

3.  If I associate the same thermostat to multiple sensors, how does it know when to turn on the thermostat?  What is the logic here?

4.  Is it better to use the scripts or IFTTT?

5.  I'd like to use motion detection for turning on lights AND motion detection when I'm away for security purposes.  Is it possible to do both or am I limited to just 1 type of use for the detection?

Issues:

1.  I find the IOS app doesn't always take my setting changes.  For instance, temperature ranges or associated thermostats.  I would change it and it says it would change, but it would stay the same in app.

[KT]

Anyone?

[Stephen Ronan]

This focuses specifically on setting up a motion sensor tag in
conjunction with a live mouse trap... but could be useful as a general
beginners guide, at least in respect to motion sensors:
http://www.banglueboards.org/take-action/downloadable-materials/category/1-posters-pamphlets.html?download=14:settingupwirelesstagsensorsforpestcontroluse

On Thu, Feb 18, 2016 at 12:08 AM, KT <tran...@gmail.com> wrote:
> Anyone?
>
> --
> You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.
> To post to this group, send email to wireless-s...@googlegroups.com.
> Visit this group at https://groups.google.com/group/wireless-sensor-tags.
> To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/f2ddfd4b-baa8-4884-b127-ff5973ca2589%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Senyo]

Hey there it. Welcome to the world of wireless tag.
Right so let's see if we can help you a little bit.
Questions
1. This one is too advanced for me mate, try someone else
2. There is a way writing an arm/disarm protocol withing each kumoapp, I have manages to get it to work once but only once give it ago and see how you get on. http://wirelesstag.net/kumoapp/18/days-of-the-week-time-of-the-day
3. Ditto
4. Scripts are faster, but I find ifttt easier and more robust for non time critical events.
5. Yes this is possible I have a tag pro.2 on my keys so when that goes out of range it activate my security protocol, and deactivate's it when I get home.

Issues
1. Use the web app interface.

Hope this has helped.

[Pete]

Questions:

1.  Is there a way I can use the 2-way tcp/ip driver for my RTI to query information from the wireless manager?  How about a restful api from the wireless manager?

There are currently no supported methods for directly querying the tag manager.

2.  If I use the "if motion detected, use the temperature of the sensor in the same room", does this mean I have to enable IR sensor arming?  Would this cause my alerts to go off?

The"motion detected" event will not fire unless the sensor is armed.  Any additional actions you have tied to that event will also fire.

3.  If I associate the same thermostat to multiple sensors, how does it know when to turn on the thermostat?  What is the logic here?

I no longer have a linked thermostat so I'm going off memory but I believe what this KumoApp does is when motion is detected, the thermostat's comfort zone (high and low targets) are transferred to the tag (which fired the motion event) and temperature monitoring is turned on (which will control the ON/OFF function of the thermostat).  So the motion sensor's comfort zone is now mirrored to what your thermostat settings were.  This happens for each sensor that is tied to the thermostat..so it really just depends on which sensor is the LAST one to trigger the motion event.  The last tag is the one controlling the thermostat.

4.  Is it better to use the scripts or IFTTT?

I got scolded the last time I posted my opinion on this so I'll just say my preferred option is to avoid both of these and use other means...mainly,  the tag's built in URL calling and the available web API.  I'm currently running openHAB, on a RPi2, as my home automation controller. I utilize an OAuth token to query my tag's temperature, humidity & battery level via the web API.  I also use the tags built in URL calling functions to report the tags' open/close/motion events to openHAB.  These tags are VERY reliable when used in this way.

5.  I'd like to use motion detection for turning on lights AND motion detection when I'm away for security purposes.  Is it possible to do both or am I limited to just 1 type of use for the detection?

You could probably write a KumoApp to check your location when motion events fire to do something different when you're home vs when you're away but I don't think this functionality exists out of the box or with any canned KumoApps (but I haven't looked through the published KumoApps in a long time).

[Senyo]

I use this one to arm particular tags when multiple tags are out of range, and then use the kumoapp.log to trigger events in ifttt. Ie:- ismart alarm, nest, hue lights off etc.

var sensors = <#Tags Going Out Of Range_[12|13|52|72|21]_N#>;
var num_outofrange=0;
sensors.forEach(
function (sensor) {
if(sensor.outOfRange)num_outofrange++;
sensor.inRange=function(){num_outofrange--; }
sensor.outRange = function () {
num_outofrange++;
if(num_outofrange>=<%Number Of Tags Out Of Range To Arm_N%>)
<#Tags To Be Armed_[12|13|52|72|21]_N#>.forEach(
function(tag){
try{ tag.arm(<%1 to reset closed angle_N%>==1) }catch(e){KumoApp.Log(JSON.stringify(e)); }
{KumoApp.Log("Selected Tags are out of range"); };
}
);
};
});

[Senyo]

I use this on my front door sensor, so when motion is detected it prompts a search for the specified tags to update. That way as soon as you get back in range the system is notified.
var sensors = <#Tags that can triger the update_[12|13|52|72|21]_N#>;
sensors.forEach(
function (sensor) {
sensor.detected=sensor.opened=sensor.closed=sensor.moved = function () {
<#Tags to be updated updated_[12|13|52|72|21]_N#>.forEach(
function(tag){
tag.update();
}
);
};
});

[Senyo]

(When multiple tag are out of range send kumoapp.log to ifttt)
READ THIS THREAD FOR MORE INFO.