WeeWX, WD, and Saratoga templates
Daniel Rich
For example:
- The instructions aren't all that specific. I'm a sysadmin by day so used to digging around to figure out how to do things, but it took quite a bit of playing to figure out how to get the templates installed and working.
- Out of the box, there are more than a few things that don't work in the Saratoga templates. I've gotten my graphs and wind rose on-line now, but have others fought this same battle and just not mentioned it? I found one or two messages that mentioned problems but that's about it.
- There are things that are just plain broken. I've seen a few posts with the class 'NameMapper.NotFound' error for example.
So how have other people gotten it up and running? Should there be a wiki page with more explicit instructions?
I'm also willing to post my patches if people are interested. Mostly they are to get the graphs working and to enable the wind rose in WeeWX-WD.
If you want to look at what I've done, my site is at http://www.lapseofthought.com/Weather/.
gjr80
https://bitbucket.org/ozgreg/weewx-wd/wiki/Weewx-WD%20v0.9.2%20Installation%20Instructions
Would appreciate any info on the things that are just plain broke. Can be raised as in issue on bitbucket or posted here if you wish.
Gary
vds
- The instructions aren't all that specific. I'm a sysadmin by day so used to digging around to figure out how to do things, but it took quite a bit of playing to figure out how to get the templates installed and working.
- Out of the box, there are more than a few things that don't work in the Saratoga templates. I've gotten my graphs and wind rose on-line now, but have others fought this same battle and just not mentioned it? I found one or two messages that mentioned problems but that's about it.
gjr80
As for install instructions I have run through them multiple times using a plain vanilla Weewx install with both US and World Saratoga templates and not an issue with either US customary or metric databases. So if there are any issues it would be nice to get the details.
Gary
drich
As vds mentioned, there are a lot of assumptions made in the instructions about your familiarity with the software. I still didn't know what clientraw and testtags were for until I started digging into the Saratoga php code. The instructions themselves are straight forward enough (although I initially created a user subdirectory in $BIN_ROOT/user, just reading it as copy the bin folder to $BIN_ROOT/user).
It actually took me a while to realize that "WD" was "Weather Display" and that was the version of the Saratoga templates I should download. That was probably the most confusing part for me. It also wasn't clear initially that the Saratoga files (I really shouldn't call them templates since they are just php code) get dumped into the HTML_ROOT, not into the skins directory. Once you know how everything works it makes sense, but it's not a good place for a beginner to start.
How hard would it be to integrate with the weewx setup.py extension installer (not sure how ugly that is to integrate with, I've only used it once).
One thing that might be nice is knowing that you can omit HTML_ROOT altogether if you want this to be your default template.
As for the errors I ran into, let me write those up a bit later, I have to head out to catch the train home.
---
Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/ | "Step up to red alert!" "Are you sure, sir? | It means changing the bulb in the sign..." | - Red Dwarf (BBC)
vds
- packaging saratoga itself as an extension would be relatively easy. It's just a big bunch of files. I don't remember anymore if there were any issues getting all the right packages for its php expectations installed or not. I don't 'seem' to remember too much confusion there but it's been a while.
- packaging weewx-wd as an extension is I think possible, but it's pretty invasive re: what it does to the databases and the steps you need to follow. I'd suggest it's possibily not worth packaging up quite yet, or until it's rearchitected to be in its own database(s). The instructions Gary+company have are pretty good now, although the code seems a little fragile vs. changes in weewx as both move forward over time and change slightly.
- set up a github repo of a pre-configured Saratoga tree known to have all the pieces in the right places
- then folks could just cd to their HTML_ROOT and 'git clone http://some.site.name/somepath'
- then they'd just need to follow the weewx-wd instructions so the data files get generated by weewx and put in the right places
vds
- I have weewx in /var/www/weewx
- I have saratoga in /var/www/saratoga
- weewx-wd writes to /var/www/weewx/WD
- so my Settings-weather.php file points $SITE['WXtags'] at ../weewx/WD/testtags.php
gjr80
I guess the underlying assumption we have made is that a Weewx-WD user is capable of downloading and installing the Saratoga HTML templates with the WD plugin. Setup of Saratoga is editing one (or if you are unlucky two) php settings files. Appreciate that there is a need for a 'bigger picture' page/document that ties Weewx-WD and Saratoga together, picking up on key config issues/gotchas etc but I am loathed to start packaging up a pre-configured Saratoga suite given there are three flavours of Saratoga (US, Canada and World). I see issues like Saratoga changing code because the likes of, say, NWS changes their forecasting output, this would have no impact on Weewx-WD whatsoever but we then (potentially) have one, two or three packages to update. I have found the Saratoga install and setup instructions easy to follow, I think it just needs some context with Weewx-WD. I seem to remember seeing some words on some Wewx docs some time ago along the lines of 'if you intend to use Weewx you should not be afraid to edit config files etc' (can't seem to find them anymore though), I see a similar expectation when using Weewx-WD with Saratoga.
Packaging Weewx-WD was considered a while ago when the packaging threads were alive, we considered it and ruled it out for the time being, mainly because of the subclassed services that Weewx-WD uses and the need to get them right in the likes of weewx.conf. Things start to get complex pretty quick if Weewx-WD is pulling one way and another package is pulling another. Once we see Weewx take on a multi-database architecture we may see far less subclassing which I hope will make Weewx-WD less complex, more robust and a better candidate to package.
Of course though, it is Greg's project so he may have a different view......
Gary
drich
I've done some editing on the original Saratoga code as well, I'm going to chat with the maintainer and see if he's interested in collaborating on a WeeWX-WD "version" of the templates. I've chatted with him in the past, he and I had shared some ideas at one point about what I was doing with wview (and we only live 20 minutes away from each other after all! :-)
For my site I went ahead and added a WeeWX type in the code so I could get the correct windrose and other graphs. I'm not a big fan of the WD graphs anyway. I find them really hard to read.
The more I think about the documentation issue, the more I think it's just an "assumptions" issue rather than a problem with the docs. I think if it had been clear that WeeWX-WD isn't really a skin but a framework for other skins, most of my confusion wouldn't have happened in the first place.
---
Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/ | "Step up to red alert!" "Are you sure, sir? | It means changing the bulb in the sign..." | - Red Dwarf (BBC)
--
You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
sesy...@gmail.com
the webpage on mine is now ~/public_html
the saratoga files are in ~/public_html/WD/ which is also where weewx-wd writes to.
Since my Settings-weather.php file is in the same directory I just left the WXtag as default. Do I need to put the explicit directory name there?
My syslog is showing the namemapper.notfound, along with NotFound: cannot find 'SkinVersion' while searching for 'Extras.SkinVersion.Version' and others.
I must have missed something, but I did follow the weewx-wd instructions exactly and have attempted to follow the saratoga instructions as well. I imagine I will get there in the end, but it could be a bit more straight forward.
Steve KD2OM
sesy...@gmail.com
Steve KD2OM
Oz Greg
sesy...@gmail.com
Steve KD2OM
Shaggy
**** Traceback (most recent call last):
**** File "/home/weewx/bin/weewx/cheetahgenerator.py", line 274, in generate
**** print >> _file, text
**** File "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in __str__
**** rc = getattr(self, mainMethName)()
**** File "_home_weewx_skins_Clientraw_customclientraw_txt_tmpl.py", line 593, in respond
**** NotFound: cannot find 'SkinVersion' while searching for 'Extras.SkinVersion.Version'Daniel Rich
[[Clientraw]]
skin = Clientraw
HTML_ROOT = xxxxx
[[[Extras]]]
[[[[SkinVersion]]]]
Version = 0.9.2
--
You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/
Daniel Rich
What permissions errors are you seeing?
--
You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/
gjr80
As Daniel has shown the flexibility of Weewx is such that there is more than one way to skin the cat.
Gary
[Extras]
[[SkinVersion]]
#SteelGauges Version Control String
Version = 11
sesy...@gmail.com
You mentioned some patches to get the wind rose and graphs working. Mine are not working yet. My biggest issue was that I hadn't installed php-curl installed. When I checked by typing curl from the command line it showed that it was there. I didn't realize that the correct curl wasn't there. It took nearly a day to figure that out.
Steve
sesy...@gmail.com
My Saratoga page doesn't update except manually. Is there a configuration for that?
Steve
gjr80
Yes there is, it's setup in the file ajaxWDwx.js which should be in the folder with all your other Saratoga files. There are a couple of settings early on that cover how often it refreshes and for how long it auto refreshes. Think there is also something in Settings.php that sets the ajaxXXwx.js file to use. Not 100% on these as I am away from my PC.
That being said though, the present weewx-wd architecture is a little limited as the clientraw and testtags files are only generated every archive period. In simple terms, testtags.php contains the data to populate the Saratoga pages and clientraw.txt contains the info to dynamically update certain fields on the Saratoga dashboard (main page). If clientraw.txt is only generated every 5 minutes then updating from it every 10 seconds is not going to do much. If your autoupdating is working you may well see some info changing colour in the top right of the page but as the autoupdate only updates fields that have changed, you will likely not see any activity elsewhere on the page.
I do have a service running that binds to loop records and generates a clientraw.txt manually. It's still rather clunky but works. Probably something we will take forward when we see how multi-database weewx goes - expect that will result In a lot of changes for weewx-wd.
Gary
drich
Gary,
Isn't that just the timing for the ajax data refresh? From a quick look at the page source, it will reload the clientraw data which should refresh the data on the page, but won't refresh any images (such as the thermometer) or other content. Unless there is some javascript somewhere that I didn't find yet that also forces a page refresh periodically. Every 10 seconds is somewhat pointless with WeeWX since it only updates the files every 5 minutes... I just updated mine to every 30. I tried going for every minute (60000), but it completely stopped updating -- I'm wondering if it's a signed short internally in javascript so can't be greater than 32767 (no time to play with numbers this morning to debug it).
Looking at my logs, I do see it pulling clientraw.txt every 30 seconds, but updated time on the page never changes. I think the data may be changing, but it's hard to tell since there is such a minor change from update to update -- even with the flash I don't see anything change.
If you want a full page refresh I think you're going to have to put a meta tag into the Saratoga top.php file. I was playing around with it last night, and added this right after the '<meta name="description"...' line:
<meta http-equiv="Refresh" content="300" />
That would cause your browser to reload the page every 5 minutes.
As an added bit of fun, I put in some code that expires my banner image every 15 minutes. I auto-generate that from a webcam up at Lick Observatory on Mt. Hamliton, so it seems a waste to not force it to update when the page refreshes! :-)
---
Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/ | "Step up to red alert!" "Are you sure, sir? | It means changing the bulb in the sign..." | - Red Dwarf (BBC)
gjr80
Isn't that just the timing for the ajax data refresh? From a quick look at the page source, it will reload the clientraw data which should refresh the data on the page, but won't refresh any images (such as the thermometer) or other content. Unless there is some javascript somewhere that I didn't find yet that also forces a page refresh periodically.
Every 10 seconds is somewhat pointless with WeeWX since it only updates the files every 5 minutes... I just updated mine to every 30. I tried going for every minute (60000), but it completely stopped updating -- I'm wondering if it's a signed short internally in javascript so can't be greater than 32767 (no time to play with numbers this morning to debug it).
Looking at my logs, I do see it pulling clientraw.txt every 30 seconds, but updated time on the page never changes. I think the data may be changing, but it's hard to tell since there is such a minor change from update to update -- even with the flash I don't see anything change.
If you want a full page refresh I think you're going to have to put a meta tag into the Saratoga top.php file. I was playing around with it last night, and added this right after the '<meta name="description"...' line:
<meta http-equiv="Refresh" content="300" />
That would cause your browser to reload the page every 5 minutes.
As an added bit of fun, I put in some code that expires my banner image every 15 minutes. I auto-generate that from a webcam up at Lick Observatory on Mt. Hamliton, so it seems a waste to not force it to update when the page refreshes! :-)
Gary
sesy...@gmail.com
I had to do it for the original page weewx generates. Dan, I looked at your page last night and saw that it was showing a night photo, but didn't see it change. Perhaps you were making changes then. I put a pan image from my phone on mine but need to compress it quite a bit. The page loads quite slowly as it is, it is intolerable with a 2.6mb image.
Still no graphs nor wind rose. I also want to add my lightning counter. It is sure more tricky to add items than in the "stock" skin...
Steve
drich
You wouldn't have seen the image change last night, I had pulled out the meta tag for the refresh while I was playing with the ajax code. Gary is right, there is a camp in the web world who is violently opposed to meta refresh tags (with reason, ajax is a much better way to go).I would much rather do it with ajax, if I have time I'll play with that a bit tonight when I get home.
There's no reason I can't hack some code into the page to refresh the image as well -- in my copious free time...
I really need to get my barometer sensor fixed and relocate my station first so the rain gauge works again (the poll it is on has bent so I don't get any readings currently). Being in northern California, I don't have to worry about rain 'til sometime in Oct or Nov anyway. :-)
---
Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/ | "Step up to red alert!" "Are you sure, sir? | It means changing the bulb in the sign..." | - Red Dwarf (BBC)
--
sesy...@gmail.com
Steve
drich
There is a pair of patches -- one to add the graphs to the graph page, and one to enable the windrose. Let me look those up when I get home tonight. I've been working a P1 outage here at work for the past 4 hours so won't have time to dig up the data 'til I get home.
---
Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/ | "Step up to red alert!" "Are you sure, sir? | It means changing the bulb in the sign..." | - Red Dwarf (BBC)
Daniel Rich
I'll look at the thermometer code when if I get some time later this evening. I don't really want that reloading every 30 seconds, the temperature had better not be changing that fast! :-) I'm sure I can leverage the same code for reloading my header image.
Thanks again for the pointers!
--
You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/
gjr80
I went ahead and pulled out my meta refresh, fixing the clientraw path (just removing the leading / since it is in the same directory) got the data refreshing going. That might be a good tip to have in the wiki, I'm not sure I ever would have thought of that!
I'll look at the thermometer code when if I get some time later this evening. I don't really want that reloading every 30 seconds, the temperature had better not be changing that fast! :-) I'm sure I can leverage the same code for reloading my header image.
Thanks again for the pointers!
No probs. Bit of a fine line between repeating what is included in Saratoga install instructions and what is in Weewx-WD. Locations/paths has been a bit of a gotcha so will certainly be covering it to some degree when I update/create a few wiki pages.
Daniel Rich
<?php if($SITE['WXsoftware'] == 'WD') { // Weather-Display graph names ?>
replace everything between that and the line that contains "// end WD graph names ?>" with the following:
<h2><a href=#"" onclick="set_ajax_uom('dayplots',true);set_ajax_uom('weekplots',false);set_ajax_uom('monthplots',false);">Last 24 Hours</a>
<a href="#" onclick="set_ajax_uom('dayplots',false);set_ajax_uom('weekplots',true);set_ajax_uom('monthplots',false);">Last Week</a>
<a href="#" onclick="set_ajax_uom('dayplots',false);set_ajax_uom('weekplots',false);set_ajax_uom('monthplots',true);">Last Month</h2>
<div id="dayplots">
<h1><?php langtrans('Last 24 Hours'); ?></h1>
<img src="daytempdew.png" alt="temperatures" />
<img src="daytempchill.png" alt="heatchill" />
<img src="dayrain.png" alt="rain" />
<img src="daywind.png" alt="wind" />
<img src="daybarometer.png" alt="barometer"/>
<img src="daywinddir.png" alt="Hi Wind" />
<img src="dayinside.png" alt="Inside" />
<img src="daywindvec.png" alt="Wind Vector" />
<img src="dayrx.png" alt="day rx percent"/>
</div> <!-- End id "plots" -->
<div id="weekplots" style="display: none;">
<h1><?php langtrans('Last Week'); ?></h1>
<img src="weektempdew.png" alt="temperatures" />
<img src="weektempchill.png" alt="heatchill" />
<img src="weekrain.png" alt="rain" />
<img src="weekwind.png" alt="wind" />
<img src="weekbarometer.png" alt="barometer"/>
<img src="weekwinddir.png" alt="Hi Wind" />
<img src="weekinside.png" alt="Inside" />
<img src="weekwindvec.png" alt="Wind Vector" />
<img src="weekrx.png" alt="week rx percent"/>
</div>
<div id="monthplots" style="display: none;">
<h1><?php langtrans('Last Month'); ?></h1>
<img src="monthtempdew.png" alt="temperatures" />
<img src="monthtempchill.png" alt="heatchill" />
<img src="monthrain.png" alt="rain" />
<img src="monthwind.png" alt="wind" />
<img src="monthbarometer.png" alt="barometer"/>
<img src="monthwinddir.png" alt="Hi Wind" />
<img src="monthinside.png" alt="Inside" />
<img src="monthwindvec.png" alt="Wind Vector" />
<img src="monthrx.png" alt="month rx percent"/>
</div>
For the wind rose you need to do two things.
- Find dirplot.gif in WD-trends-inc.php and replace it with daywindrose.png.
- Edit skins/Testtags/skins.conf and add user.imageStackedWindRose.ImageStackedWindRoseGenerator to the "generator_list =" line.
After you restart weewx it should generate daywindrose.png the
next time it runs. You may have to tweak WD-trends-inc.php to
point it to the right place to find where the generator puts the
image (I have everything in the same directory).
-- Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/
gjr80
Still a few documents to catch up on though.
Gary
sesy...@gmail.com
I am working through these. First I get this in the syslog:
Jun 4 00:08:25 raspberrypi weewx[12930]: **** File "/home/weewx/bin/weewx/reportengine.py", line 298, in start
Jun 4 00:08:25 raspberrypi weewx[12930]: **** self.run()
Jun 4 00:08:25 raspberrypi weewx[12930]: **** File "/home/weewx/bin/user/imageStackedWindRose.py", line 54, in run
Jun 4 00:08:25 raspberrypi weewx[12930]: **** self.setup()
Jun 4 00:08:25 raspberrypi weewx[12930]: **** File "/home/weewx/bin/user/imageStackedWindRose.py", line 60, in setup
Jun 4 00:08:25 raspberrypi weewx[12930]: **** self.image_dict = self.skin_dict['ImageStackedWindRoseGenerator']
Jun 4 00:08:25 raspberrypi weewx[12930]: **** File "/usr/lib/python2.7/dist-packages/configobj.py", line 567, in __getitem__
Jun 4 00:08:25 raspberrypi weewx[12930]: **** val = dict.__getitem__(self, key)
Jun 4 00:08:25 raspberrypi weewx[12930]: **** KeyError: 'ImageStackedWindRoseGenerator'
Jun 4 00:08:25 raspberrypi weewx[12930]: **** Generator terminated...
I assume I must have missed something in the installation. The imageStackedWindRoseGenerator.py is in the user directory.
My graphs are in the public_html directory and WD is in public_html/WD/. So I have had to change the directory in wxgraphs.php to reflect that difference. It is still not working, maybe it will be easier to move everything to the public_html directory.
gjr80
I expect you will are missing the [ImageStackedWindRoseGenerator] section in the skin.conf that is calling the generator. If you have a look in Weewx-WD v0.9.3 under skins/WD/StackedWindRose you will find a skin.conf with the required settings in it. Copy and paste will do it. I revised the section in v0.9.3 so the settings should be fairly self explanatory though the defaults will probably do. In the process of getting the install instructions finalised, checked and posted on the Weewx-WD wiki but they are probably 1-2 Gary days away :)
Gary
sesy...@gmail.com
Steve
sesy...@gmail.com
On Wednesday, June 4, 2014 12:38:04 AM UTC-4, gjr80 wrote:
gjr80
On Wednesday, 4 June 2014 15:50:57 UTC+10, sesy...@gmail.com wrote:
Now to get the lightning counter showing up and there is an issue with my owfs driver in regards to rain rate.
You're on you own with that one :)