PG3 Update to 3.0.44 causing Index error

[vbPhil]

I performed the 3.044 update to PG3 and it created some problems. Relating to WT is; I'm now getting emails from the Tag Manager every couple of minutes.

Could not call URL for 'Quad Leak Sensor' at event update due to following error

Index (zero based) must be greater than or equal to zero and less than the size of the argument list., URL attempted to call: http://192.168.1.158:33009/update?tmgr_mac=341A7A7179B1&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8}

I logged on to PG3 and found I couldn't get any Details for any of my Node Servers. So with that and the WirelessTag emails I tried to Restore PG3 to an earlier version. I'm not sure the Restore took because PG3 is still labeled as 3.044. Now I can see Details for the NS but I'm still getting the emails from the Tag Manager.

Seems to be hosed pretty good now.

Any ideas on what to do?

 

[Jimbo.Automates]

That's bizarre, they just added the signaldBm and txpwr to their servers for us last week.  The upgrade is not due to PG3, it's because when PG3 was restarted it checks and updates all NS's to the latest, and that change was released to the WT NS about 9 days ago.  So it looks like they didn't add those settings for the Quad Leak Sensor, I will ping them on the support ticket.

 

[Jimbo.Automates]

Sometimes they don't respond to support tickets for a few days, so I'll have to generate a new release that exclude those setting for the leak sensor, will try to do that tonight.

 

[vbPhil]

43 minutes ago, JimboAutomates said:

That's bizarre, they just added the signaldBm and txpwr to their servers for us last week.  The upgrade is not due to PG3, it's because when PG3 was restarted it checks and updates all NS's to the latest, and that change was released to the WT NS about 9 days ago.  So it looks like they didn't add those settings for the Quad Leak Sensor, I will ping them on the support ticket.

 

I checked PG3 info and I do have 3.0.44 installed. Weird. Not sure what happened this morning. Something got updated because I saw the messages roll by. I did do a PG3  restore to an earlier backup and now when I check on doing an update it says my packages are all up to date. So much for that Restore. Anyway, I stopped the WT emails by stopping the NS and unchecking the URL Calling entry in the Tag Manager. Just stopping the NS didn't stop the emails.

Quote

When tag sends a temperature/humidity/brightness update - {0}: Tag name, {1}: Tag ID, {2}: temperature in °C, {3}: humidity/moisture (%), {4}: brightness (lux), {5}: timestamp, {6}: battery voltage, {7}: signal strength (dBm), {8}: transmit power (1~255)

 

[vbPhil]

@JimboAutomatesI re-started WT NS and it looks like the Quad Sensor is getting all data now? At least I don't see the error emails like before.

Oooops, I may have spoken too soon. Didn't have my email client running. I now see some of the same emails so I guess we're still not functional.

Edited March 9, 2022 by vbphil
Oooops

[Jimbo.Automates]

3 hours ago, vbphil said:

@JimboAutomatesI re-started WT NS and it looks like the Quad Sensor is getting all data now? At least I don't see the error emails like before.

Oooops, I may have spoken too soon. Didn't have my email client running. I now see some of the same emails so I guess we're still not functional.

No worries.  I've not heard back yet from support, and I'm heading out of town for a few days in the morning, so probably won't have time to put in a fix for this tonight.  In the meantime you'll have to edit that URL and remove the singnaldBm and txpwr from the url manually, or turn it off.

[BamBamF16]

I just updated my Polisy and I think the tag NS.  I am now getting similar emails:

 

URL: GarageDoor

Index (zero based) must be greater than or equal to zero and less than the size of the argument list., URL attempted to call: http://10.0.1.71:41171/update?tmgr_mac=D244789C9054&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8}

Sent at: 3/10/2022 2:46:41 PM.

 

The 10.0.1.71 is my polisy address.  I assume the 41171 is the port for the NS. 

 

[Jimbo.Automates]

I just updated my Polisy and I think the tag NS.  I am now getting similar emails:
 
URL: GarageDoor
Index (zero based) must be greater than or equal to zero and less than the size of the argument list., URL attempted to call: http://10.0.1.71:41171/update?tmgr_mac=D244789C9054&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8}
Sent at: 3/10/2022 2:46:41 PM.
 
The 10.0.1.71 is my polisy address.  I assume the 41171 is the port for the NS. 
 

What tag type is that? I'll try to find time when I return home to exclude the new options from it.

Sent from my Pixel 6 Pro using Tapatalk

[BamBamF16]

[Jimbo.Automates]

That's odd, looks like a tag type 12 which is working fine for me.  Does it show like this in the admin console?

[BamBamF16]

Here is what I have:

[Jimbo.Automates]

Ok, then I'm not sure what is going on since this way works with my tag type 12 and supposedly this was a server side update so everyone should see it...

Can you try rebooting your tag manager, then restart the Node server and see if it goes away?

 

[Jimbo.Automates]

Support finally got back to me and said:

I found the issue. The signal and transmit power were not supplied if the "buffer multiple data point" option is enabled. It is all fixed now, please try again.

Sent from my Pixel 6 Pro using Tapatalk

[vbPhil]

@JimboAutomatesWas there anything we have to do to the NS to effect the change? I did a restart and verified that my Quad Sensor URL Call has the full value including signal dbm and power. So far, no emails from the Tag Manager so it looks like it may be fixed.

[Jimbo.Automates]

@JimboAutomatesWas there anything we have to do to the NS to effect the change? I did a restart and verified that my Quad Sensor URL Call has the full value including signal dbm and power. So far, no emails from the Tag Manager so it looks like it may be fixed.

No, that's it. Glad they found and fixed the issue.

Sent from my Pixel 6 Pro using Tapatalk

[garybixler]

Thanks @JimboAutomates

I was able to add back the leak sensor and all works great now. There is one unimportant issue. The Tx power on the Admin Console doesn't match what is shown at the tag web site. The AC value is roughly doubled plus.

Thanks again.

Gary

[vbPhil]

45 minutes ago, garybixler said:

Thanks @JimboAutomates

I was able to add back the leak sensor and all works great now. There is one unimportant issue. The Tx power on the Admin Console doesn't match what is shown at the tag web site. The AC value is roughly doubled plus.

Thanks again.

Gary

I'm not sure what the Transmit power represents. I don't see that value anywhere in the WirelessTag application.

My values are all over the place from nothing to 70. (2, 2, 4, 5, 12, 12, 15, 16, 70) It sort of follows the distance from the Tag Manager, with the 70 probably the farthest away tag.

[garybixler]

Using a browser and hovering over the dBm value it will show TX power. Don't see it on the app however.

[vbPhil]

1 minute ago, garybixler said:

Using a browser and hovering over the dBm value it will show TX power. Don't see it on the app however.

Ok, thanks. So it's a percentage and the value isn't agreeing with the NS, i.e. the WT shows 12% and the NS 70.

[Jimbo.Automates]

I created this issue a while back, will try to look into it.
https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/52

Sent from my Pixel 6 Pro using Tapatalk