In/Out of Range

[emil...@quintela.com.br]

Hi,

I am new to the group and notice some already experienced my problem, but not sure if solved.

My tags (v. 2.0) are configured to Out of Range after 5 minutes and auto-updates every 30 seconds. Out of range is not issue, but when I get back in range, than I have problems. 

Takes 10, 15 minutes so the Tag Manager can recognize that Tags are back in rage. Several times I had to ping manually otherwise it won't identify.

Was wondering if I need to change any configuration or if this just won't work. I would need this to be quite at the same instant it is back in range (using to turn lights on when I get close to house garage entrance).

Regards,

[Bradley Britton]

Mine does the same thing, I have it set to search every 5 minutes but a hour can pass and it still has not found it. The way I got around this as 5 minutes is to long for what I want anyway was to have a armed tag, such as the garage or front door trigger the update of the tag coming back into range. The advantage here for you could be as soon as you open your garage the lights should come over within about 30 seconds or so. You will find even if the search every 5 minutes did work, which it doesn't, its not going to do what you want it to do anyway as the chances for it to be looking for your tag while you are still outside the house but still close enough to be in rage are very slim. I have put the kumo app below with what I use and it worked every time very well.

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();
}
);
};
});

Post if you have any further questions. This will get around the problem but just a quick note the tag triggering the update must be armed. I hope this helps.

[emil...@quintela.com.br]

Hi Bradley,

Thanks, it is partially a good solution to my problem.

The reason why is partial is because I don't open a garage that would then trigger the Kumoapp. What happens is that I arrive at my house side entrance (bike entrance) using a dark pathway (on a daily basis, few times a day).

So I don't actually open anything that could trigger this. My intention is that, just as I approach the house (or this pathway) the "In Range" would trigger a WeMo Switch (that the lights are attached to) and I could then open the door without having to turn on any lantern on my phone or something to find the key hole. I could just buy a light fixture with motion sensor, but then the light would turn on every time someone passes thru the same pathway, which is not my intention.

Still looking for a solution...

thanks

[Bradley Britton]

The shortest time that they are allowed to have the tag manager search for a missing tag is every 5 minutes. I have not tested it, but maybe have a PIR sensor as your trigger. So when it detects motion it send for a update on that tag. I have not tested this, but just another thought.

[emil...@quintela.com.br]

Yes, that might be one possible workaround for that. thanks!

it is a matter on how fast the triggers would work, but there is a chance this can work.

On Wednesday, November 18, 2015 at 10:32:50 PM UTC+1, emil...@quintela.com.br wrote:

[emil...@quintela.com.br]

An update:

I could manage to get this working for now, as long as the KumoApps stay reliable. I used the nice sugestion from Bradley to update the Tags.

So, the setup is:

. All Tags updating every 30 seconds

. Out of Range at mininmun value (5 minutes)

. Narrow Band (long distance)

. I am not using temperature or motion monitoring in the Tags that are in the keychain, so battery is not an issue here

. 1 fixed Tag

So, I have 1 Wireless Tag outside of my house that I use to take temperature. Based on Bradley suggestion below, I made a KumoApp to update all other tagas as this one is auto-updated (every 30 seconds).

var tags = <#tags_[12|13|21|32|52|62|72]_N#>;

  tags.forEach(

function (tag) {

    tag.updated = function () {

<#Tags to be updated_[12|13|52|72|21]_N#>.forEach(

    function(tag){

        tag.update();

    }

);

};

});

If they are out of range, ok, nothing happens. If they are In Range, than the system will recognize them.

And then, I have another KumoApp to turn on a WEMO, as the keychain tags enters In Range (based on above).

var sensors = <#Motion Sensor or Reed Sensor_[12|13|32|21|52]_N#>;

sensors.forEach(

    function (sensor) {

        sensor.inRange = function () {

            <#WeMo_[82]_1#>.lightOn();

        };

        KumoApp.setTimeout(function(){

                wemo.lightOff();

            }, <%Turn of in Seconds_N%>*1000);

});

With that, I still hve a risk that within the 30 seconds I will reach the pathway where the lights should be on before the next update. I made two attempts today, and in both the lights were on before, meaning that most of the times I will probably be succesful in having lights before I enter in the pathway.

In the future I will add a PIR sensor in before the entrance of the pathway with a Kumoapp also to update all others, just to make sure the 30 seconds will be no issue.

For now, thanks Bradley. Hope this also help others looking for the same "In Range" kind of automation.

Rgds,
Emiliano

On Wednesday, November 18, 2015 at 10:32:50 PM UTC+1, emil...@quintela.com.br wrote:

[Bradley Britton]

I'm glad that you have it working, but thought that I would say that the only tag you want set to 30 second update is the tag on your keyring, not the other tags. Having the 30 second update will drain the battery faster, so there is no point having the tags not leaving the house going flat faster. You can set a auto update time for each separate tag. I have the all other tags set to 30 minutes.

[emil...@quintela.com.br]

Actually for me is the inverse. The one in the key can be set to 30 minutes, for example. The one fixed (who triggers the updates) is the one that I need updating every 30 seconds. This way, even if the one in the key will not update, the system will trigger it to update every 30 seconds. But I am using it for a month like this (updating every 30 seconds) and battery is at 92%. Think good enough for now.

Anyway, thanks. Helped a lot!