Hi,
While I do like many aspects of the Belchertown skin (with its live data
and the awesome graphs), I am still attached to the Seasons skin (No
offence Pat!).
What I love about the Seasons skin is that everything is available on my
screen on mobile (all graphs etc) without having to scroll
Is there a way to include logwatch additions which are preserved when weewx
is updated??
I find that I always have to update the logwatch script to ignore
ftpgenerator: ftp'd
raw: deleted
historygenerator.pyc: Generated
messages when I update weewx. I used to just keep a backup of the script,
what command do you use to start weewx??
wee_debug has used weewx.conf, and unless you are using an unusual command
weewx will also use weewx.conf, so changing one of your other weewx.conf
files will not have any effect unless you copy the changed file to
weewx.conf
you also need to stop and
It seems that "strikes_total" represents the counter that returns to "0"
after it hits "127". I don't see a packet that represents the actual total
of lightnings strikes. Or maybe I don't have my Sensor Map correct.
Everything else seems to be tracking fine.
sudo tail -f /var/log/syslog
I think that’s the problem. When I installed weewx it made three weewx.conf
files. The weewx.conf, weewx.conf.20145798, and a def_config.conf file
I run weewx and it read my Acurite fine and posted to the local html file. So
with nano I looked and the weewx.conf file and the
The wee_debug report suggests CWOP is not enabled. Any chance there are
multiple config files on your system? (have you ever installed WeeWX via
different methods?). Are you sure you have been looking at correct weewx.conf?
The beauty of wee_debug is that by default it processes the weewx.conf
I see that is has CWOP not enabled but In the config file I have it enabled?
pi@raspberrypi:~ $ sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jul 21 15:04:56 raspberrypi weewx[22450]: engine: Using binding
Ok, I suggest you edit weewx.conf, set debug = 1, save weewx.conf then restart
WeeWX. Let WeeWX run for 10 minutes then take a copy of the log from when you
restarted WeeWX until the 10 minutes have passed. Post the log extract here
making sure you have the full startup. Also, run wee_debug
Hi Gary
Yep confirmed the files were where they should be so as you mentioned it
got me thinking about permissions and it maybe useful for others.
To cut a long story short my web server only hosts windows type web sites
which need a web.config file to give it clues as to what to do with certain
I'll be darned... That did the trick. Thank you so much!
On Sunday, July 21, 2019 at 1:16:32 AM UTC-5, gjr80 wrote:
>
> In this case hierarchy matters not indenting, try:
>
> [[SteelSeries]]
> skin = ss
> HTML_ROOT = public_html/ss
> [[[CheetahGenerator]]]
>
In this case hierarchy matters not indenting, try:
[[SteelSeries]]
skin = ss
HTML_ROOT = public_html/ss
[[[CheetahGenerator]]]
search_list_extensions = user.forecast.ForecastVariables
Gary
--
You received this message because you are subscribed to the
11 matches
Mail list logo
