[weewx-user] Re: Weewx, WMR300 and RaspberryPi "altimeter: none, barometer: none" no view ...?

[Cameron D]

If you look at my data from 16-Jan-2018, when the house lost power from 
approx 7:00 until 10:00, you will see the same effect - history results 
from the battery-backed console are logged on Wunderground at one-minute 
intervals.

On Sunday, 28 January 2018 16:21:36 UTC+10, Cameron D wrote:
>
> ..
> I see this morning you presumably restarted weewx and loaded 1-minute 
> interval history data from 6:40 to 9:54. Then again from 10:20 to 10:40.
>
> ...
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx, WMR300 and RaspberryPi "altimeter: none, barometer: none" no view ...?

[Cameron D]

Hello Yngve,
I don't think the time interval should make a problem - I have been running 
3.7.1 for ages at 1 minute log interval.
The Wunderground station is IBRISBAN102 . 
Rapidfire is off.
log_success = False
DIsplayed data is updated once a minute (as seen on the Wunderground web 
page), but it only saves data every 5 minutes.  I'm not sure if I have any 
control over that.

I don't think I have ever lost a pressure reading.

Curiously, the Wunderground pressure displayed does not agree precisely 
with the weewx data, but I think that relates to rounding errors as it is 
converted to US units and back to metric.

I see this morning you presumably restarted weewx and loaded 1-minute 
interval history data from 6:40 to 9:54. Then again from 10:20 to 10:40.

Soon I will be upgrading to 3.8.0 so we will see how that goes.

Cameron.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: minor documentation issue

[Chris Richmond]

Well... it looks like I've got rev 3.6.2, but if the switch changed over
time, that's fine.
Thx, Chris

On Sat, Jan 27, 2018 at 4:32 PM, gjr80  wrote:

> On Sunday, 28 January 2018 10:05:37 UTC+10, tomn...@frontier.com wrote:
>>
>> To whom it may concern...  :^)  There are a few spots in the
>> Customization guide referencing this;
>>
>> wee_database weewx.conf --rebuild-daily
>>
>>
>> Hi,
>
> That is exactly correct, --rebuild-daily is the correct action,
> --backfill-daily was used in wee_database until weeWX 3.7.0 was released.
> WeeWX v3.7.0 and later uses --rebuild-daily instead of --backfill-daily.
>
>
>> but the help from wee_database actually supports
>>  Actions:
>>   --backfill-daily  Rebuild the daily summaries from the archive database.
>>
>
> Are you sure that the wee_database you are using (or your weeWX install)
> is not 3.6.2 or earlier? I have just checked the 3.7.0, 3.7.1 and 3.8.0
> release copies of wee_database and there is definitely no --backfill-daily
> anywhere in the file.
>
>
>>
>> --rebuild-daily failed when I tried last week, but since the summaries
>> rebuild when weewx starts up
>> anyway, I let it go.
>>
>
> Just be careful here, you will see a line like:
>
> Jan 28 10:21:14 stretch22 weewx[1279]: manager: Starting backfill of
> daily summaries
>
> in the log, whilst it is true weeWX is backfilling the daily summaries it
> is only from the last time the daily summaries were updated until the
> timestamp of the latest record in the archive; nothing is done with any
> historical daily summaries. On the other hand, the --rebuild-daily action
> in wee_database will (in most cases) rebuild the entire daily summaries
> from the very first record in the archive. So for normal operation the
> rebuild during startup is all that is needed, but if you have done
> something that altered historical data (eg deleted some nonsense data) then
> you really need to use wee_database and do a --rebuild-daily.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/WsJ4kOyY5SI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx failing again

[Rune Laegreid]

Hi,

Please see the enclosed debug report.

Rune.

lørdag 27. januar 2018 23.28.29 UTC+1 skrev gjr80 følgende:
>
> Hi,
>
> You have errors from at last 2 extensions in the log extract you provided 
> so I am thinking there may be a wider issue here. So we can get a clear 
> picture of what your are running can you please post a wee_debug (
> http://weewx.com/docs/utilities.htm#wee_debug_utility) report, make sure 
> you check the report for any sensitive info before posting. Can you also 
> set debug=1 in weewx.conf then restart weeWX and post the log from startup 
> until a couple of archive records have been processed.
>
> One other thing, I have found these sorts of errors frequently occur when 
> some observations are missing ie None. I see part of you log extract 
> (22:02:03-22:02:07) seems to indicate this, apart from the log errors is 
> your station functioning as it should and displaying all observations?
>
> Gary
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


weewx.debug
Description: Binary data

[weewx-user] Re: minor documentation issue

[gjr80]

On Sunday, 28 January 2018 10:05:37 UTC+10, tomn...@frontier.com wrote:
>
> To whom it may concern...  :^)  There are a few spots in the Customization 
> guide referencing this;
>
> wee_database weewx.conf --rebuild-daily
>
>
> Hi,

That is exactly correct, --rebuild-daily is the correct action, 
--backfill-daily was used in wee_database until weeWX 3.7.0 was released. 
WeeWX v3.7.0 and later uses --rebuild-daily instead of --backfill-daily.
 

> but the help from wee_database actually supports
>  Actions:
>   --backfill-daily  Rebuild the daily summaries from the archive database.
>

Are you sure that the wee_database you are using (or your weeWX install) is 
not 3.6.2 or earlier? I have just checked the 3.7.0, 3.7.1 and 3.8.0 
release copies of wee_database and there is definitely no --backfill-daily 
anywhere in the file.
 

>
> --rebuild-daily failed when I tried last week, but since the summaries 
> rebuild when weewx starts up
> anyway, I let it go.
>

Just be careful here, you will see a line like:

Jan 28 10:21:14 stretch22 weewx[1279]: manager: Starting backfill of daily 
summaries

in the log, whilst it is true weeWX is backfilling the daily summaries it 
is only from the last time the daily summaries were updated until the 
timestamp of the latest record in the archive; nothing is done with any 
historical daily summaries. On the other hand, the --rebuild-daily action 
in wee_database will (in most cases) rebuild the entire daily summaries 
from the very first record in the archive. So for normal operation the 
rebuild during startup is all that is needed, but if you have done 
something that altered historical data (eg deleted some nonsense data) then 
you really need to use wee_database and do a --rebuild-daily.

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] minor documentation issue

[Thomas Keffer]

The documentation is correct. The option used to be called --rebuild-daily,
but this was changed to --backfill-daily with Version 3.7.0 (released
11-March-2017).

I think you are reading the new documentation, but using an old version of
weeWX.

-tk

On Sat, Jan 27, 2018 at 5:05 PM,  wrote:

> To whom it may concern...  :^)  There are a few spots in the Customization
> guide referencing this;
>
> wee_database weewx.conf --rebuild-daily
>
>
> but the help from wee_database actually supports
>  Actions:
>   --backfill-daily  Rebuild the daily summaries from the archive database.
>
> --rebuild-daily failed when I tried last week, but since the summaries
> rebuild when weewx starts up
> anyway, I let it go.  Added something else today, got the same failure,
> and spent a few extra seconds to
> figure out why,
>
> Thx, Chris
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Wind data wrong

[gjr80]

On Sunday, 28 January 2018 09:06:40 UTC+10, Nicolas Cazan wrote:
>
>
> sorry it's in french
>

Must be French-lite - I could read it :)

Ok, that error indicates either /var/tmp/backup.sdb does not exist or if it 
does not exist it does not have a table named archive, in either case 
/var/tmp/backup.sdb is not a copy of your live weeWX database. The wiki 
entry gives specific comamnds for a number of tasks but only describes 
making a copy of your weeWX database, what did you do to make the copy? Did 
you:

   - stop weeWX using

$ sudo systemctl stop weewx

   - copy your weeWX database using (paths adjusted to suit your install):

$ cp /home/weewx/archive/weewx.sdb /var/tmp/backup.sdb

   - does /var/tmp/backup.sdb exist and is it identical in size to you live 
   weeWX database?

Assuming all is OK try the problem command again, if you get the same error 
let's have a look at what is in /var/tmp/backup.sdb using the following 
commands:

$ sqlite3 /var/tmp/backup.sdb
sqlite> .tables

This should result in output similar to:

archive   archive_day_outTemp
archive_day_ETarchive_day_outTempBatteryStatus
archive_day_UVarchive_day_pressure
archive_day__metadata archive_day_radiation
archive_day_altimeter archive_day_rain
archive_day_barometer archive_day_rainBatteryStatus
archive_day_consBatteryVoltagearchive_day_rainRate
archive_day_dewpoint  archive_day_referenceVoltage
archive_day_extraHumid1   archive_day_rxCheckPercent
archive_day_extraHumid2   archive_day_soilMoist1
archive_day_extraTemp1archive_day_soilMoist2
archive_day_extraTemp2archive_day_soilMoist3
archive_day_extraTemp3archive_day_soilMoist4
archive_day_hail  archive_day_soilTemp1
archive_day_hailRate  archive_day_soilTemp2
archive_day_heatindex archive_day_soilTemp3
archive_day_heatingTemp   archive_day_soilTemp4
archive_day_heatingVoltagearchive_day_supplyVoltage
archive_day_inHumidityarchive_day_txBatteryStatus
archive_day_inTemparchive_day_wind
archive_day_inTempBatteryStatus   archive_day_windBatteryStatus
archive_day_leafTemp1 archive_day_windDir
archive_day_leafTemp2 archive_day_windGust
archive_day_leafWet1  archive_day_windGustDir
archive_day_leafWet2  archive_day_windSpeed
archive_day_outHumidity   archive_day_windchill
sqlite>

If you don't see output like this then something is wrong with your 
database copy. You can exit sqlite3 with the .quit command:

sqlite> .quit
$

See how you go with the above.

Also, if you are using PuTTY you should be able to select text/output on 
the PuTTY screen (this automatically copies the selected text/output to the 
clipboard) and paste it into your Google Groups post, much easier for us to 
read than taking and posting 'picture' of the screen/terminal.

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] minor documentation issue

[tomnykds]

To whom it may concern...  :^)  There are a few spots in the Customization 
guide referencing this;

wee_database weewx.conf --rebuild-daily


but the help from wee_database actually supports
 Actions:
  --backfill-daily  Rebuild the daily summaries from the archive database.

--rebuild-daily failed when I tried last week, but since the summaries 
rebuild when weewx starts up
anyway, I let it go.  Added something else today, got the same failure, and 
spent a few extra seconds to
figure out why,

Thx, Chris

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Wind data wrong

[Nicolas Cazan]

sorry it's in french


Le samedi 27 janvier 2018 23:58:16 UTC+1, gjr80 a écrit :
>
> Can you please post a screen capture of exactly what you are typing and 
> what is returned/what error you see. Descriptions are good but screen 
> captures are better.
>
> Gary
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Wind data wrong

[gjr80]

Can you please post a screen capture of exactly what you are typing and what is 
returned/what error you see. Descriptions are good but screen captures are 
better.

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Wind data wrong

[Nicolas Cazan]

yes but I get  Error: near line 1: no such table: archive


Le samedi 27 janvier 2018 23:33:32 UTC+1, gjr80 a écrit :
>
> Hi,
>
> Have a look at the wiki (
> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data). You 
> might also want to look at implementing some appropriate MinMax limits in 
> [StdQC] in weewx.conf (
> http://weewx.com/docs/usersguide.htm#%5B%5BMinMax%5D%5D)
>
> Gary
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] 2 StandardReports ?

[Thomas Keffer]

>From your note, it wasn't clear where your second skin lives, so let's use the
example

from the Customizing Guide. In this example, the USReport ends up in
public_html, with the MetricReport underneath it, in the subdirectory
public_html/MetricReport

Say you wanted to FTP only MetricReport, but not USReport. Your FTP section
would look like:

[[FTP]]
  skin = Ftp
  ...
  HTML_ROOT = public_html/MetricReport


The FTP report recursively sends everything from
public_html/MetricReport downward.
Because the US Report is above it, in public_html, it will not be sent.

If you wanted to do it the other way around, that is, send only USReport
and not MetricReport, you would have to either reverse their positions, or
put the two reports in completely different subdirectories, say
public_html/US and public_html/MetricReport.

Hope this helps.

-tk

On Sat, Jan 27, 2018 at 1:26 PM, plock yaa  wrote:

> Hi Tom,
>
> That's exactly what I was looking for. Thanks. My bad I did not see it in
> the documentation. Works great now.
>
> Now, is it possible to use an alternative/different skin for the data to
> be published on the external web server? I added the following in weewx.conf
>
> [[WebReport]]
> skin = StandardWeb
> HTML_ROOT = /var/www/html/web
>
> and copied skins/Standard into skins/StandardWeb and started to edit
> index.html.tmpl.
>
> Unfortunately, it looks like only Standard is being taken into account by
> the engine. Any hint, if possible, on how to use 2 different skins, one for
> local and one for the external webpage?
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Wind data wrong

[gjr80]

Hi,

Have a look at the wiki 
(https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data). You might 
also want to look at implementing some appropriate MinMax limits in [StdQC] in 
weewx.conf (http://weewx.com/docs/usersguide.htm#%5B%5BMinMax%5D%5D)

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx failing again

[gjr80]

Hi,

You have errors from at last 2 extensions in the log extract you provided so I 
am thinking there may be a wider issue here. So we can get a clear picture of 
what your are running can you please post a wee_debug 
(http://weewx.com/docs/utilities.htm#wee_debug_utility) report, make sure you 
check the report for any sensitive info before posting. Can you also set 
debug=1 in weewx.conf then restart weeWX and post the log from startup until a 
couple of archive records have been processed.

One other thing, I have found these sorts of errors frequently occur when some 
observations are missing ie None. I see part of you log extract 
(22:02:03-22:02:07) seems to indicate this, apart from the log errors is your 
station functioning as it should and displaying all observations?

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Wind data wrong

[Nicolas Cazan]

Hello, I have a problem, I use Weewx 3.7.1 and it has just recorded a burst 
at 737 km / h (tornado !!) How can I delete this data wrong?
Thank you in advance for your help.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx failing again

[Rune Laegreid]

Hi,

My weewx WD / steel series installation on RPi with Vantage is pretty 
unstable and being an amateur in this game, I am not able tell if this is 
hardware related or my installation that is failing.

Can anyone tell based on the log below?

Jan 27 22:01:11 WeatherPi weewx[4043]: reportengine: copied 14 files to 
/home/weewx/public_html
Jan 27 22:01:11 WeatherPi weewx[4043]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Jan 27 22:01:11 WeatherPi weewx[4043]:   list index out of range
Jan 27 22:01:11 WeatherPi weewx[4043]:   Traceback (most recent 
call last):
Jan 27 22:01:11 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 140, in run
Jan 27 22:01:11 WeatherPi weewx[4043]:   obj.start()
Jan 27 22:01:11 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/reportengine.py", line 170, in start
Jan 27 22:01:11 WeatherPi weewx[4043]:   self.run()
Jan 27 22:01:12 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 143, in run
Jan 27 22:01:12 WeatherPi weewx[4043]:   ngen = 
self.generate(gen_dict[option_section_name], self.gen_ts)
Jan 27 22:01:12 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Jan 27 22:01:12 WeatherPi weewx[4043]:   ngen += 
self.generate(section[subsection], gen_ts)
Jan 27 22:01:12 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 206, in generate
Jan 27 22:01:12 WeatherPi weewx[4043]:   ngen += 
self.generate(section[subsection], gen_ts)
Jan 27 22:01:12 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 290, in generate
Jan 27 22:01:12 WeatherPi weewx[4043]:   default_binding)
Jan 27 22:01:12 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in _getSearchList
Jan 27 22:01:12 WeatherPi weewx[4043]:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Jan 27 22:01:12 WeatherPi weewx[4043]: File 
"/home/weewx/bin/user/wdSearchX3.py", line 936, in get_extension_list
Jan 27 22:01:12 WeatherPi weewx[4043]:   avwind120_vh = 
ValueHelper((avwind120_vt[0][0], avwind120_vt[1], avwind120_vt[2]), 
formatter=self.generator.formatter, converter=self.generator.converter)
Jan 27 22:01:12 WeatherPi weewx[4043]:   IndexError: list index 
out of range
Jan 27 22:01:12 WeatherPi weewx[4043]:   Generator terminated...
Jan 27 22:01:13 WeatherPi weewx[4043]: cheetahgenerator: Generated 1 files 
for report wdPWS in 1.05 seconds
Jan 27 22:01:23 WeatherPi weewx[4043]: cheetahgenerator: Generate failed 
with exception ''
Jan 27 22:01:24 WeatherPi weewx[4043]: cheetahgenerator:  Ignoring 
template /home/weewx/skins/Clientraw/clientrawhour.txt.tmpl
Jan 27 22:01:24 WeatherPi weewx[4043]: cheetahgenerator:  Reason: 
cannot find 'knot' while searching for 'knot.formatted'
Jan 27 22:01:24 WeatherPi weewx[4043]:   Traceback (most recent call 
last):
Jan 27 22:01:24 WeatherPi weewx[4043]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 300, in generate
Jan 27 22:01:24 WeatherPi weewx[4043]:   print >> _file, text
Jan 27 22:01:24 WeatherPi weewx[4043]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Jan 27 22:01:24 WeatherPi weewx[4043]:   rc = getattr(self, 
mainMethName)()
Jan 27 22:01:24 WeatherPi weewx[4043]: File 
"_home_weewx_skins_Clientraw_clientrawhour_txt_tmpl.py", line 132, in 
respond
Jan 27 22:01:24 WeatherPi weewx[4043]:   NotFound: cannot find 'knot' 
while searching for 'knot.formatted'
Jan 27 22:01:31 WeatherPi weewx[4043]: cheetahgenerator: Generated 3 files 
for report wdClientraw in 17.72 seconds
Jan 27 22:01:32 WeatherPi weewx[4043]: imageStackedWindRose: Generated 1 
images for wdStackedWindRose in 0.73 seconds
Jan 27 22:01:33 WeatherPi weewx[4043]: cheetahgenerator: Generated 1 files 
for report wdSteelGauges in 1.35 seconds
Jan 27 22:01:33 WeatherPi weewx[4043]: reportengine: copied 6 files to 
/home/weewx/public_html/ss
Jan 27 22:01:35 WeatherPi weewx[4043]: cheetahgenerator: Generated 2 files 
for report SteelSeries in 1.65 seconds
Jan 27 22:01:42 WeatherPi weewx[4043]: genimages: Generated 11 images for 
SteelSeries in 6.77 seconds
Jan 27 22:02:03 WeatherPi weewx[4043]: genimages: Generated 12 images for 
SmallImages in 20.69 seconds
Jan 27 22:02:03 WeatherPi rsyslogd-2007: action 'action 17' suspended, next 
retry is Sat Jan 27 22:03:33 2018 [try http://www.rsyslog.com/e/2007 ]
Jan 27 22:02:03 WeatherPi weewx[4043]: GaugeGenerator: outTemp has no 
reading (None)
Jan 27 22:02:04 WeatherPi weewx[4043]: GaugeGenerator: outHumidity has no 
reading (None)

Re: [weewx-user] 2 StandardReports ?

[plock yaa]

Hi Tom,

That's exactly what I was looking for. Thanks. My bad I did not see it in 
the documentation. Works great now.

Now, is it possible to use an alternative/different skin for the data to be 
published on the external web server? I added the following in weewx.conf

[[WebReport]]
skin = StandardWeb
HTML_ROOT = /var/www/html/web

and copied skins/Standard into skins/StandardWeb and started to edit 
index.html.tmpl.

Unfortunately, it looks like only Standard is being taken into account by 
the engine. Any hint, if possible, on how to use 2 different skins, one for 
local and one for the external webpage?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[mwall]

On Saturday, January 27, 2018 at 12:27:22 PM UTC-5, pgeenhuizen wrote:
>
> Matt,
> That did it.  
> I see that you changed the strip from horizontal to vertical.  I'm not 
> sure which I prefer, the vertical is easier to read, but the horizontal was 
> more compact, and doesn't require scrolling.  Could you make orientation an 
> option on the strip page?
>

take a look in forecast_strip.inc at line 116:

var default_display_settings = {

//  'orientation': '$orientation',

  'orientation': 'vertical',

  'show_temp': $show_temp,

change that to this:

var default_display_settings = {

  'orientation': '$orientation',

  'show_temp': $show_temp,

then you can set the orientation in weewx.conf, skin.conf, or inline as you 
would any of the other forecast parameters.

 

> Not sure about this one.  Right now when I look at the Weather Underground 
> iconic view it shows Sat, Sun and Mon and nothing for Wed, Thurs and Fri.  
> When I look at the Table and the strip they both show a forecast for Sat - 
> Thurs 
>
> Lastly and this might my foul up on the main page under the FORECAST 
> heading, I only see the forecast for the current day and only for Weather 
> Underground.
>

each of the forecast views has a parameter that controls how far into the 
future the forecast should display (e.g., num_periods or num_days).   if 
that is a longer timespan than the amount of forecast data in the database, 
then the display *should* show nothing for those empty days/hours.

i probably do not have the defaults for these dialed in perfectly just yet 
(as you might have noticed, there are many different forecast sources, and 
many different ways to view forecasts now.  testing all of the permutations 
is becoming a formidable challenge!)

m

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 11:18, mwall wrote:

On Saturday, January 27, 2018 at 11:05:37 AM UTC-5, pgeenhuizen wrote:


Well now I have a new error
an 27 10:48:52 host weewx[26967]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/forecast/single-strip-vertical.html.tmpl
Jan 27 10:48:52 host weewx[26967]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/forecast/iconic-horizontal.html.tmpl
Jan 27 10:48:52host weewx[26967]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/forecast/tides-graphic.html.tmpl


and now i remember why i did not publicize the forecast 3.2.18 release :)

forecast 3.2.19 has the single-strip-vertical and iconic-horizontal 
pages (3.2.18 has them, but they were not in the install.py 
configuration).


iconic works.  vertical strip still has css issues.  the graphic tide 
display is not ready yet, so i have excluded that from the 3.2.19 
release, but the generator should not fail now.


m


Matt,
That did it.
I see that you changed the strip from horizontal to vertical.  I'm not 
sure which I prefer, the vertical is easier to read, but the horizontal 
was more compact, and doesn't require scrolling.  Could you make 
orientation an option on the strip page?


Not sure about this one.  Right now when I look at the Weather 
Underground iconic view it shows Sat, Sun and Mon and nothing for Wed, 
Thurs and Fri.  When I look at the Table and the strip they both show a 
forecast for Sat - Thurs


Lastly and this might my foul up on the main page under the FORECAST 
heading, I only see the forecast for the current day and only for 
Weather Underground.


None of the above is a show stopper and are merely my observations, my 
main concern were the errors which are now fixed.


Once again thanks for your help and quick response.
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Add Service Tutorial for BME280 and DS18B20

[Andreas Otten]

Here is my instructable for 2 services with nodemcu esp8266

https://www.instructables.com/id/Extension-Sensors-Nodemcu-ESP8266-for-Weewx/

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Most reliable mini computer for weeWX?

[ponolan]

Something's wrong. Have you checked the system logs?

I've been running WeeWX on a Raspberry Pi Model B with 512Mb RAM for 3 
years with just a handful of outages, all of which were either 
power-related or the result of the notorious Fine Offset WH1080 USB port 
lock-up. I send logs to a Synology diskstation and minimise disk writes 
using ram storage. Have never had any SD card issues with it either.

The Beagle Bone is a great little board and more capable than a Pi; unless 
it's faulty it really should be good enough.

On Wednesday, January 24, 2018 at 7:38:36 PM UTC, Alec Bennett wrote:
>
> I've been running weeWX on a Beaglebone Black for about a year now, and 
> the thing has been freezing about once a month. It's running headless so is 
> hard to diagnose.
>
> I'm probably going to switch to a Pi, but thought I'd see if anyone has 
> any other suggestions for a very reliable mini computer that plays nice 
> with weeWX?
>
>  
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 09:44, mwall wrote:



On Saturday, January 27, 2018 at 9:36:55 AM UTC-5, pgeenhuizen wrote:

Speaking of updating extensions, I've often wonder what is the
best procedure/practice?
remove the existing extension and then install the new one?
Install the new extension then remove the old one?
Install the new extension and nothing more?


just install the new version.  the extension installer will snapshot 
the older version, which is nice if you want to roll back (rollback 
requires manual intervention.  pull requests to make rollback and 
revision-listing part of the wee_extension command-line options would 
be welcome!)


thank you for the 'wee_extension --list'

that is exactly what i was going for, and it makes clear what you have 
installed


m


You're welcome to the list and I'll let you know how it goes.
Thanks for your quick response and help.
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[mwall]

On Saturday, January 27, 2018 at 9:36:55 AM UTC-5, pgeenhuizen wrote:
>
> Speaking of updating extensions, I've often wonder what is the best 
> procedure/practice?
> remove the existing extension and then install the new one?
> Install the new extension then remove the old one?
> Install the new extension and nothing more?
>

just install the new version.  the extension installer will snapshot the 
older version, which is nice if you want to roll back (rollback requires 
manual intervention.  pull requests to make rollback and revision-listing 
part of the wee_extension command-line options would be welcome!)

thank you for the 'wee_extension --list'

that is exactly what i was going for, and it makes clear what you have 
installed

m

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 09:28, mwall wrote:



On Saturday, January 27, 2018 at 9:21:37 AM UTC-5, pgeenhuizen wrote:


Matt,
No apologies needed, these things happen, I'm only too happy to
get a timely response.
This is a test setup, so I'm willing to go either way, what would
you prefer that I do?
Pete


go ahead an update to the latest versions

Speaking of updating extensions, I've often wonder what is the best 
procedure/practice?

remove the existing extension and then install the new one?
Install the new extension then remove the old one?
Install the new extension and nothing more?

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[mwall]

On Saturday, January 27, 2018 at 9:21:37 AM UTC-5, pgeenhuizen wrote:
>
>
> Matt,
> No apologies needed, these things happen, I'm only too happy to get a 
> timely response.  
> This is a test setup, so I'm willing to go either way, what would you 
> prefer that I do?
> Pete
>

go ahead an update to the latest versions

 

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 09:12, mwall wrote:

pete,

i seem to have gotten undisciplined in my releases.  i did apply a fix 
for this, but it is un an unpublished release.  my apologies!


the behavior you see happens only when the *remaining* daily high and 
low are the same (often at the end of the day)


you can patch by doing this in forecast_iconic.inc:

at line 97 insert a line to change this:

#set $range_width = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


to this:

#set $range_width = 0

#set $trailing_width = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


and around line 155 insert a line to change this:

#set $range_height = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


to this:

#set $range_height = 0

#set $trailing_height = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


or you can install exfoliation 0.44 and forecast 3.2.18

(i have been battling some css quirks in the vertical orientation of 
the 'strip' forecast display, and so far i am losing that battle)


m


Matt,
No apologies needed, these things happen, I'm only too happy to get a 
timely response.
This is a test setup, so I'm willing to go either way, what would you 
prefer that I do?

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 08:51, mwall wrote:
sorry, i see that you posted the versions.  i thought this was fixed 
some time ago.  can we confirm that you are actually running 0.43 
exfoliation?

--


Is this what you need?

/usr/bin/wee_extension --list
Extension Name    Version   Description
lastrain  0.1   SLE for last rain information for weewx reports
StackedWindRose   2.1.0 Stacked windrose image generator for weeWX.
forecast  3.2.17    Generate and display weather and tide forecasts.
exfoliation   0.43  A minimalist layout with lots of data.

And this from the web page

weewx: 0 days, 15 hours, 15 minutes
server: 0 days, 21 hours, 19 minutes
weewx 3.8.0 with LaCrosse WS23xx and exfoliation 0.43

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Exfoliation errors

[mwall]

pete,

i seem to have gotten undisciplined in my releases.  i did apply a fix for 
this, but it is un an unpublished release.  my apologies!

the behavior you see happens only when the *remaining* daily high and low 
are the same (often at the end of the day)

you can patch by doing this in forecast_iconic.inc:

at line 97 insert a line to change this:

#set $range_width = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None

to this:

#set $range_width = 0

#set $trailing_width = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None

and around line 155 insert a line to change this:

#set $range_height = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None

to this:

#set $range_height = 0

#set $trailing_height = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None

or you can install exfoliation 0.44 and forecast 3.2.18

(i have been battling some css quirks in the vertical orientation of the 
'strip' forecast display, and so far i am losing that battle)

m

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Exfoliation errors

[mwall]

sorry, i see that you posted the versions.  i thought this was fixed some 
time ago.  can we confirm that you are actually running 0.43 exfoliation?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Exfoliation errors

[mwall]

On Saturday, January 27, 2018 at 7:43:39 AM UTC-5, pgeenhuizen wrote:
>
>
> So far everything is working as expected however I see these errors in 
> the log 
>
> cheetahgenerator:  Reason: cannot find 'trailing_height' 
>
> cheetahgenerator:  Reason: cannot find 'trailing_width' 
>

i thought that was fixed some time ago.  which version of exfoliation are 
you using?

m

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Exfoliation errors

[Pete Geenhuizen]

I guess that this is a question for Matt.

I am in the process of upgrading my weewx installation from

Centos 6 to Centos 7

weewx    3.6.2-1 to 3.8.0-1

forecast  3.2.13 to 3.2.17

exfoliation   0.39 to 0.43

So far everything is working as expected however I see these errors in 
the log


cheetahgenerator:  Reason: cannot find 'trailing_height'

cheetahgenerator:  Reason: cannot find 'trailing_width'

The errors tend to show up late at night around 10 pm Eastern and cease 
around 6 am.


I've attached a snippet from the log.

Any one else seeing these errors and if so what do I need to do to 
eliminate them?


Thanks

Pete


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


weewx-errs.gz
Description: application/gzip