garybixler

I am getting version 3.0.11 from the store. Thanks

Just a thought. The waiting seems to be on the tag mac addresses through the tag manager. The manager can only run at 10mb half duplex. Just wondering if it may be getting overwhelmed during install. Thanks Gary

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

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

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

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

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

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

This log is rather large but it is from a new reinstall. New Text Document.txt

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

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

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

Same problem. @bpwwerfigured it out and showed me the method in which to show and Kill the duplicate NSs. I thought I tried rebooting but may be mistaking on that.

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

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.

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

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

@Jimbo Last night I updated to PG3's latest version and this morning discovered that ELK basically stopped running. I included some of the log. I did try reinstalling but it never gets a connected status. Thanks Gary New Text Document.txt

Thanks so much. Everything looks perfect.

This is the log from the start in PG2. New Text Document.txt

This is what's returned when I do http://192.168.30.63/v1/current_conditions. New Text Document.txt

Update: The log wasn't in debug. A new log after restart. New Text Document.txt

After installing the new version it started but basically hung up on node 2. I included the log. Thanks Gary New Text Document.txt

@bpwwer Yes, the unit itself has an indoor temp and humidity sensor. I was wondering because the PG2 version has an indoor node. Only node one is loaded into the PG3 version. I added a couple of snippets from the PG2 version. Thanks Gary

@bpwwer Hi, Weather link has been running for about a day on PG3 but it stopped updating at about 3 AM. I copied the log shortly before the updating stopped. Also restart didn't work. Had to stop start restart. Thanks Gary New Text Document.txt