Tag queries or turn light on/off

[garybixler]

@Jimbo I have noticed a few discrepancies with some of the Tag parameters that doesn't follow the WEB sight. If a query or set light on/off is done the 'Seconds Since Update' always goes to 3600 until its regular update.

If going out of range  'Seconds Since Update' will restart at 0 when 'Out Of Range' goes True. On the WEB site the count continues with no reset.

Also the 'Signal dbm' doesn't reflect properly.

I was thinking of using the 'Seconds Since Update' parameter in some programs but it is not consistent.

Just a little feedback.

Thanks Gary

 

 

[Jimbo.Automates]

Thanks, will take a look:  https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/43

 

[Jimbo.Automates]

Hey @garybixler, I've been working on this, check the issue link above.  I've not been able to get a tag to report as out-of-range yet.  I've configured the notifications and reporting time as instructed here https://wirelesstag.net/webapp.html#step4 in the logging section, then removed the battery and waited, but no report.  Is there another trick?

 

[garybixler]

@JimboNot sure if removing the battery will result in out of range. What I do is wrap the tag tightly in aluminum foil for testing. Usually the tag is in my car for determining if it is home or away. I set the tag to record every 30 seconds to give the fastest response and if out of range to search every 5 minutes. I query the tag from a driveway sensor so it would never need to wait the 5 minutes. As the out of range may take 5 minutes or more I tried using the 'seconds since update' but was to inconsistent. Hopefully the update will work better.

Thanks gary

[Jimbo.Automates]

ok, will try that, but how does it know the difference of out-of-rang or if the battery is removed/dead?

[garybixler]

I couldn't say. I have never tried removing the battery.

[Jimbo.Automates]

For the signaldBm I created a new issue, nothing I can do about that for now:

https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/45

 

[Jimbo.Automates]

I couldn't say. I have never tried removing the battery.

Well I'm baffled, I tried with tinfoil and it stopped reporting but I never get out of range. Tried with it armed and disarmed.

Sent from my Pixel 6 Pro using Tapatalk

[garybixler]

That's odd, I have just tested the 'Seconds Since Updates' and all seems to be working perfectly.  I Covered the tag with foil and after 5 mins or so it went out of range. There may be up to a 30 second delay until the NS server gets the out of range. I assume that is the polling interval and out of range doesn't trigger an immediate update.

Thanks Gary

[Jimbo.Automates]

Great, I implemented a fix but couldn't test it.  Can you do a "Download Log Package" and send me that in a PM so I can see what it looks like?

There shouldn't be a delay for NS polling, the OOR is pushed from the tag manager directly with no polling.

 

[DennisC]

8 hours ago, Jimbo said:

ok, will try that, but how does it know the difference of out-of-rang or if the battery is removed/dead?

Don't know if this helps, but the only time I have seen out of range is when the battery has died and the time exceeds the reporting window.

 

 

[DennisC]

25 minutes ago, garybixler said:

That's odd, I have just tested the 'Seconds Since Updates' and all seems to be working perfectly.  I Covered the tag with foil and after 5 mins or so it went out of range. There may be up to a 30 second delay until the NS server gets the out of range. I assume that is the polling interval and out of range doesn't trigger an immediate update.

Thanks Gary

I can confirm seconds since update going to 3600 after a query. Saw it happen today.

[Jimbo.Automates]

Just now, DennisC said:

I can confirm seconds since update going to 3600 after a query. Saw it happen today.

Should be fixed in latest version 3.0.14 and beyond.

[DennisC]

2 minutes ago, Jimbo said:

Should be fixed in latest version 3.0.14 and beyond.

I installed v 3.0.13 this morning. I will check it out tomorrow.