garybixler

OK also this is what the AC shows.

Basically the AC is blank. It doesn't appear that any changes are loaded into the NS from the tag. I raised the temp on the tag but no changes were seen at the NS. Also GV12 doesn't change when wet.

I already had the leak sensor installed but the NS doesn't seem to see it as a leak sensor after update. It acquires the tag type of the last tag viewed. I tried deleting the node in the NS reboot and discover but can't get the NS to recognize the leak sensor. Basically no data is loaded into the ISY. I think it is present in the NS. I attached a snippet. Thanks Gary

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 couldn't say. I have never tried removing the battery.

@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 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 GREAT NEWS! I installed version 13 and clicked "Monitor Tags True" and everything loaded right away with all correct date. Thanks so much for all your hard work. Gary

Thank you so much. Some NSs where deleted in PG2 but not uninstalled which are now. I don't think that made any difference however. Gary

It should be visible as the name assigned to your tag manager at your wirelesstag account. Mine was Home.

It will be located on the Tag Manager page of the Admin Console.

Hi, This is the procedure I used to get the tags loaded and working. Thanks Gary -Install -Authorize Added TM node Halted with 'Discover thread is done' -Set monitor tags true Added one tag with incomplete data. Waiting for add to complete. Six minutes later added second tag with incomplete data. Waiting again for add to complete. Continued with next step at this point. -Restart The two tags got correct data. -Did discover on tag manager node page. All tags loaded but with some incorrect data. Restart All tags have correct date and working.

The store says 3.0.12 but the tagmanage NS say 3.0.11 after installed.

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