Out of range taking a long time.

[Gary]

For a week or so it has taken 1 hour plus if ever to detect out of range. Good old reliable cloud based systems.

[steve]

Hi Gary

on the web interface under "Updated" to can custom each tag from 5mins, 10min up to 2 hours"

[Gary]

Yes I have always set to 30 seconds.

[Bradley Britton]

When I have mine set to 30 seconds it can take 30 minutes to send out the out of range notification, which is not what is shown on the demonstration video on the tag website. It shows that the last update was 30 minutes ago on my account, but does not show the across against the signal and no notification. It doesn’t seem to work as it should. It will decide to send the notification but after a much longer time than what it should. When the update time is 30 seconds, why does it sometimes take 30 minutes to send the notification? Other times can be much shorter, so the times can be all over the place. Would be good to have a fix for the problem.

[Michael West]

What is your tag "Auto-update" set to? Looks like this:

 

 

--

Michael West

https://mwe.st

--

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 http://groups.google.com/group/wireless-sensor-tags.

To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/6e937a9c-d89c-4a37-b87a-9209c8669875%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Bradley Britton]

It's set to every 30 seconds the same as in that image. I can't work it out. It can at times send the notification in about 2 minutes, normally will take about 12 minutes and then can take as long as 30 minutes. The times vary quite a lot. I was assuming it was the system taking a long time to verify the tag is gone. It will show that the tag has not been updated for the length of time such as 30 minutes, but for some reason is still may not be considered out of rage for some time. So the system know the tag has not been updated for 30 minutes, so why would it not be sending the out of range notification?

[Zhiheng Cao]

Thanks for the feedback. We will review this problem. Can you PM me the name of the tag, tag manager serial number and the date/time when it took ~30 minutes to become out of range? 

On Tue, Jul 14, 2015 at 5:20 PM, Bradley Britton <bradbr...@gmail.com> wrote:

It's set to every 30 seconds the same as in that image.  I can't work it out.  It can at times send the notification in about 2 minutes,  normally will take about 12 minutes and then can take as long as 30 minutes.  The times vary quite a lot.  I was assuming it was the system taking a long time to verify the tag is gone.  It will show that the tag has not been updated for the length of time such as 30 minutes,  but for some reason is still may not be considered out of rage for some time.  So the system know the tag has not been updated for 30 minutes, so why would it not be sending the out of range notification?

--
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 http://groups.google.com/group/wireless-sensor-tags.

To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/27dbd5a7-42e2-48df-b401-b0168fe70d69%40googlegroups.com.

[Gary]

I just did an out of range test on one of my tags that is set for 30 seconds and it responded with out of range in 2 to 3 minutes. That is what I normally see when all is working well on the server side.

Thanks

[Bradley Britton]

It can take around 2 minuets to send the out of range notification but still is consistently taking up to 30 minuets.

[Bradley Britton]

The support team has resolved the issue, out of range notification is now working