Hi, I have the Wireless Tag NS up and running. There seems to be a miss match between tag id 1 and 2. I have tag 1 updating every 30 sec and tag 2 updating every 5 min. What is puzzling is that the names are reversed from what is configured at the Tag web server. The other 2 tags are correct. When the NS is first installed it only gets 2 tags out of 4. Later I go in and do a discover and sometimes the other 2 tages will appear. It may take several tries to find the other tags. I have rebooted and reinstalled but always the same. Maybe this is because I have associated a tag that isn't defined yet. The new leak sensor.

Thanks for any assistance.

Gary

Edited January 24, 20223 yr by garybixler

Hi, I have the Wireless Tag NS up and running. There seems to be a miss match between tag id 1 and 2. I have tag 1 updating every 30 sec and tag 2 updating every 5 min. What is puzzling is that the names are reversed from what is configured at the Tag web server. The other 2 tags are correct. When the NS is first installed it only gets 2 tags out of 4. Later I go in and do a discover and sometimes the other 2 tages will appear. It may take several tries to find the other tags. I have rebooted and reinstalled but always the same. Maybe this is because I have associated a tag that isn't defined yet. The new leak sensor.
Thanks for any assistance.
Gary

I'm having similar weirdness, it was working fine on my dev environment when installed locally and I wasn't able to install and test from the store until today.

Sent from my Pixel 6 Pro using Tapatalk

This should be fixed in 3.0.8.

 

Unfortunately the results are the same in version 3.0.8. I deleted the NS and reinstalled. Restarted the Admin console but only the first two tags were installed. Can't get the others through discovery and the first two aren't updating even though I have Monitor Tags true. I attached the entire log.

Thanks Gary

New Text Document.txt

Update: After the third restart the nodes are updating but where tag id 1 and 2 names are reversed. Also I was able to then discover and get the last two tages. The tags are not accurately updating however.

 

CORRECTION: I think the tag names are correct according to the temp readings when I query the tag. But they aren't' updating any data.

Edited January 25, 20223 yr by garybixler

I included the admin screen shot. The Seconds Since Update should be no longer that 30 secs.

There is an issue with the UDI interface, I'm working with Bob to fix it.

Sent from my Pixel 6 Pro using Tapatalk

Everything should be fixed with 3.0.10, there was a udi_interface issue and a silly bug created during PG3 conversion.

 

Unfortunately not quite working. Only the first two tages are loaded even though they are all shown in the log which I attached. Also the temps are show in celsius. Also the update timer isn't being updated unless the tag is queried. I did get the other two tags to load with a couple of discoveries. Also very strange after they loaded all tags displayed in fahrenheit. Nothing gets updated in the Admin console unless they are queried. Monitoring tags is true. 

Thanks Gary

New Text Document.txt

Maybe some good news. After changing the short poll timer from 5 to 15 seconds and doing a restart things may be working better. The tags seem to be getting updated. Will need to keep checking to verify however.

Thanks Gary

Shortpoll shouldn't matter because the tags are no poll'ed the changes are pushed to the NS by the tag manager.

 

I did a reinstall and copied the log where the NS seems to come to halt. The first two tags only loaded. Will need to do several restarts and a discover or two to get all the tags and updating.

Thanks Gary

New Text Document.txt

First issue is setting shortPoll is broken, it's done differently in PG3 and guess I never tested that, so just set it in the PG UI.

Second issue is strange, seems things just stop... Can you download the main PG3 log and send that to me?  I'll try to clear out my inbox again.

 

This log is rather large but it is from a new reinstall.

New Text Document.txt

Did you mean the Real-time Polyglot log file? If so it doesn't load into the log area.

Did you mean the Real-time Polyglot log file? If so it doesn't load into the log area.

Yes, and that's a bummer, hopefully that'll be fixed soon. I'll look at the NS log you posted.

Sent from my Pixel 6 Pro using Tapatalk

After about 40 minutes the log file popped up as a text file to save. I do have the file but it is 123 MB. Dare I attach such a large file? I could copy paste the desired time span.

Thanks Gary

Thanks for the Log, it just seems PG3 stops, no idea why.  I'm discussing with @bpwwer to see if we can figure it out.

OK, found the issues, should really be fixed in 3.0.11.  It's actually common code in all my nodeservers so now I need to fix them all.  It doesn't occur all the time, only if the ISY is slow to add a new node, which happens...

 

 

I tried 3.0.11 but still having issues. When first coming up after authorization it seemed to stall after loading one tag. I attached that log. I tried setting Monitor Tags = true but still didn't continue. Did a restart and then discover on admin and all tags loaded.  But not all data is correct. Temp is in Celsius or some number close to that for one tag. Probably a restart will fix it.

Thanks Gary

 

 

UPDATE: I think I see multiple node servers running. Will try rebooting.

New Text Document.txt

Edited January 27, 20223 yr by garybixler

GOOD NEWS! I think everything is now working. I had 4 copies of each NS running. I checked earlier today and there were no duplicates. Don't know how additional NSs got started. I will try a fresh install later and see how that goes.

Thanks so much for all your effort.

Gary

Awesome! Yes multiple copies of NS running seems to be happening a lot.

Sent from my Pixel 6 Pro using Tapatalk

I have a theory about that but will need to test out.

 

Bad News. I did a reinstall of the WT NS and the results are pretty much the same as before. The tags didn't get loaded. I set monitor tages true and only one tag got loaded. Log shows something waiting to complete. Probably restarting and discovering will be required. No duplicate WT NS however.

Thanks Gary

Update. After 600sec two more tags loaded and waiting resumes. Attachment shows the waiting periods.

 

New Text Document.txt

Edited January 27, 20223 yr by garybixler

Ok, bummer, and yes I've been discussing this issue with Bob, not sure yet what we can do, but will try to figure it out soon.