Not notifying when going out of range

[claireb...@gmail.com]

Hello, I am having an issue with the new tags I just purchased not notifying when going out of range by the specified settings. I have the new tags on our keyrings to automatically arm and disarm other tags when going in and out of range. When I set the tag for example to 2 minutes and Immediately Notify, the tag system will not send a notification that the tag is out of range for 38 minutes, well passed the settings. I am not sure why I am starting to have this problem now when I have not been having problems like this with my tags.

 

Can you please help me with a resolution?

[Darrin Calcutt]

Can you give me more detail on what you're trying to do?

I'm not sure if your method of using a tag to activate other tags when going out of range is the best method

Personally I use the Kumo app on my iPhone when it's outside the proximity area to activate tags automatically

[claireb...@gmail.com]

I like using the tags to arm and disarm my tags as it doesn’t rely on the location service of the phone and I have the kumo app to only arm the tags when two or more selected tags go out of range. When working it is a quick and reliable method to arm and disarm tags.

 

What I need is to have the setting within the tag System work as set, so when I set an out of range time it is at least close to this time rather than substantially out. This was working correctly until recently.

 

Can you please help tag support? Last time I had this issue it required you to change a setting on your end to fix it, there is nothing more I can do on my end. Ticket #8640

 

 

 

 

 

 

(The code to use your tags for arming)

 

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

                                                                    }

                                                                );

                                };

});

[claireb...@gmail.com]

I have looked into the issue further given there was no resolution and found the following. If I use Wireless Sensor Tag (with Temperature) to go in and out of range to arm and disarm my system, with the tag set to a update time of 2 minutes and Immediately Notify, the tag system will not send a notification that the tag is out of range for 38 minutes. When I use a Wireless Sensor Tag Pro with the tag set to a update time of 2 minutes and Immediately Notify the tag will show out of range in 4 minutes. Both the same settings, however very different results which I would assume is a setup issue with the tag server.

On a last note the new Wireless Sensor Tag (with Temperature) suffer from the old stuck out of range issue where once they go out of range it is highly likely that you will need to take out the battery and put it back in to have the tag reconnect.

I thought I would get the less expensive tag for the key rings, however it looks like the only tag to go in and out of range produced is the Pro Tag only.

On Wednesday, 26 April 2017 22:00:43 UTC+10, claireb...@gmail.com wrote:

[Zhiheng Cao]

This does not make sense. Is the tag with temperature one shipped after July 2016 that fixed the radio stuck problem?

--
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.
For more options, visit https://groups.google.com/d/optout.

--

Sent from MetroMail

[claireb...@gmail.com]

Yes the tags were purchased this year, so there is still a issue

On Wednesday, 26 April 2017 22:00:43 UTC+10, claireb...@gmail.com wrote:

[Julian Chua]

Hi, sorry for reviving a really old post. I was trying to do something similar with the Wireless Sensor Tag Pro (have the out of range event trigger call an URL). But it only really becomes "out of range" after more than 30 minutes or so. What setting do I have to adjust to let the notification be sooner? Even after 10 minutes is better.

Thanks! 

[ned...@googlemail.com]

Where are you carrying the tag that is going out of range? I experimented with this a while ago and found that if the tag was attached to my keyring out of range notification was very unreliable. Not sure why - possibly the proximity of metallic objects in my pocket. When I carried the tag separately (in the breast pocket of my jacket) it worked very well.

[ned...@googlemail.com]

Sorry - should have mentioned - I have the hub set to poll all tags every five minutes (the "record" setting - top left on the wireless tag app home page).

[Zhiheng Cao]

Just reduce the record interval and turn off "buffer multiple points" option so the tag transmits more often. The system relies on receiving periodic tag transmit to determine if it is out of range when the transmission stops.

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/8ba258e3-57b7-4b8e-a9ad-0262be6d8be0%40googlegroups.com.