The option unit_system is included in new, fresh, installs, but it is not injected into old config files. You must have started, somewhere, with a fresh install.
Think of unit_system as a shorthand for a bunch of unit group settings. NB: this is still in flux. The option may be moved to sit under [[Defaults]], instead of directly under [StdReport]. On Mon, Nov 22, 2021 at 6:42 AM 'Cameron D' via weewx-development < [email protected]> wrote: > Thanks Tom, > Now for the next issue, although I can't recall precisely what I did when. > Only after yesterdays post did I notice that the wind vector plots were > missing, so I thought I'd try to apply your patched code. I may have done > completely the wrong thing, but it was all I could think of instead of > waiting for the next beta release. > > I downloaded the development code from github as at 2021-11-22 05:15:00Z > I updated all the newer bin/weewx python files and merged the skin changes. > Python files updated were: > > - defaults.py, > - cheetahgenerator.py, > - units.py, > - manager.py, > - restx.py, > - reportengine.py > > After the normal upgrade via .deb file to beta 7, I am sure the graphs > were displaying in my required units. > However, after the most recent changes the graphs are now in US units. > > I see a setting has appeared in my weewx.conf, saying "*unit_system = > us*". I know I'm getting old, but I don't recall putting it in there - > did it happen automatically as part of the 4.6.0 upgrade? > Did I miss reading some documentation about changing the way units are > specified? > I had up to 4.5.1 used a section in my weewx.conf overriding the > Unit-Groups section. This is partly because the Australian standard system > reports wind in km/h and rain in mm (half metric, half metricwx) I put the > groups under: > [StdReport] > [[Defaults]] > [[[Units]]] > [[[[Groups]]]] > > with my *Defaults *being the last section of *StdReports*. Is the order > important? My group definitions seem to get ignored, although commenting > out the *unit_system = xx* line seems to revert to the old pattern and > it falls back to using my Group definitions. > On Sunday, 21 November 2021 at 10:24:20 pm UTC+10 Tom Keffer wrote: > >> Yes, that is the intention. >> >> Another option is to override [DisplayOptions] and, for that matter, >> [ImageGenerator], in weewx.conf. That way, if a new version of a skin comes >> out, you don't have to do anything. Just slip the new version in place. >> Unfortunately, that's not always possible because some things cannot be >> overridden. In particular, the templates themselves. >> >> Thanks for giving it a thorough try! >> >> >> >> On Sun, Nov 21, 2021 at 1:08 AM 'Cameron D' via weewx-development < >> [email protected]> wrote: >> >>> I see for beta6 you were asking for experience on customising Seasons >>> skin. I have a renamed and customised Seasons skin so I thought I try it >>> out. Customisations are fairly trivial - graph size, colours, content of >>> each graph, one extra dataset from mem.py >>> >>> Debian 10, mysql DB system. >>> Upgraded system from .deb file - no problems with my customised systemd >>> unit files. >>> >>> I did a normal package upgrade from 4.5.1 using the .deb file and >>> retained all existing settings. Then did a few diffs to merge in new >>> parameters. >>> I noticed weewx.conf had a the huge chunk of stuff missing from >>> [[defaults]] - units, labels and such. I think that has been picked up >>> already so I carried on with my old content. >>> >>> This then ran using my old Seasons-x skin folder and looked OK. >>> I switched to default new Seaqsons and it was OK as well. >>> >>> Duplicated the Seasons folder and merged my config changes into the new >>> skins file. The changes were nearly all in places that were similar to the >>> old format, so it was all quite straightforward. >>> >>> The only thing I found initially a bit confusing was the >>> "DisplayOptions" section where it says I can override the values in the >>> config file. My impression is that I need to edit the rest of the skin >>> config file anyway in order to manipulate the graphs so it made more sense >>> to me to simply edit the DisplayOption parameters in place. Is that the >>> intention? >>> >>> Cheers, >>> Cameron. >>> On Sunday, 7 November 2021 at 8:33:09 am UTC+10 Tom Keffer wrote: >>> >>>> Pretty much the same as beta-6, except it fixes a few annoying bugs: >>>> >>>> - Search list no longer grows without bounds. >>>> - All images are no longer regenerated with every reporting cycle. >>>> - Data types that are null at the beginning of the year, but later >>>> non-null, are now properly displayed. >>>> >>>> http://weewx.com/downloads/development_versions/ >>>> >>> -- >>> >> You received this message because you are subscribed to the Google Groups >>> "weewx-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-development/10232fa9-3c7e-48b3-83e4-8651a574a7d4n%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-development/10232fa9-3c7e-48b3-83e4-8651a574a7d4n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "weewx-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-development/778f9cbb-221b-45cb-948a-0c98e79b9d2dn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-development/778f9cbb-221b-45cb-948a-0c98e79b9d2dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/CAPq0zECgtn0ibt6-JmBpgVNq%3DSFAFWMvBYAUU37neoT1ZqMW6Q%40mail.gmail.com.
