Noel, Meant to reply earlier but time got away from me.
When changing weewx-aprs code (called aprs.py) you have to uninstall the > extension, change the code and reinstall the extension. When uninstalling > an extension it wipes out the original downloaded weewx-aprs source so you > have to rebuild all of this from scratch. > The documentation on the use of the wee_extension utility is not quite as thorough as perhaps it should be. Generally speaking if you install an extension using wee_extension that is what you should use to upgrade the extension and (if desired) ultimately remove the extension. This works well when you have an extension author that publishes updated versions. If this is not the case, or you just decide you want to change some of the code, there is no need to uninstall the extension - you can make changes to the installed .py files or config stanzas in weewx.conf directly. A weeWX restart will be required for these changes to take effect but defintely no need to uninstall/change/install. The problem with this approach is that you have now likely compromised the extension installer and any subsequent use of wee_extension may result in an unpredictable outcome or loss of your changes. For example, if you have made local changes to some of an extensions files and the the extension author publishes a new version of the extension, the use of wee_extension to install the new version will result in loss of any local chnages. As a rule of thumb, once you make local changes you are best not to use the extension installer but rather install upgrades to that extension manually. Other extensions are not affected. New versions of an extension are normally installed by simply installing the new version using wee_extension. If local changes have been made to .py files these will be lost, but if you are making local changes you should be using wee_extension. Changes to the extensions config stanza in weewx.conf (if used) will be preserved and a backup copy made and saved. I made those changes to the original aprs.py. When the upgrade came along > a couple weeks ago it unchanged aprs.py back to the original . > I guess you mean the weeWX 3.8.0 upgrade changed aprs.py? If so I am stumped, the weeWX installer does not make chnages to bin/user, its contents are left alone during an upgrade. The only things that should be making changes to bin/user are the user and wee_extension. Gary On Sunday, 17 December 2017 23:12:00 UTC+10, Noel Petit wrote: > > Found the problem to be two things in weewx-aprs extension file (aprs.py) >> > > 1) Wind in the original code is "wind_average" which is not reported by > Acurite. Change that to "windSpeed" > 2) Symbol for wind speed in the original code is "c" and should be "/" > Change that > > When changing weewx-aprs code (called aprs.py) you have to uninstall the > extension, change the code and reinstall the extension. When uninstalling > an extension it wipes out the original downloaded weewx-aprs source so you > have to rebuild all of this from scratch. > > I made those changes to the original aprs.py. When the upgrade came along > a couple weeks ago it unchanged aprs.py back to the original . > > Thanks for those who made suggestions. > > Noel Petit > WB0VGI-1 > Harris, MN > > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
