Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Thanks for the time you spent on this. I'll try eliminating things until I 
find it. I may even have to reinstall weewx.  Much appreciated for the 
help.   Bob 

On Monday, February 11, 2019 at 5:59:39 PM UTC-5, mwall wrote:
>
> On Saturday, February 9, 2019 at 9:19:27 AM UTC-5, bgrattan wrote:
>>
>> Matt,
>> Here are the three files. ForecastVariables is commented out. I can 
>> change it if you need. NOAA drop down menus now work.  Thanks.  Bob
>>
>
> i cannot replicate the behavior you are seeing.  no matter what i do, the 
> NOAA menus are always generated properly.
>
> there must be something else about your environment that is causing the 
> problem, but i am at a loss as to what that might be.
>
> you could try disabling all of your other reports - leave only the 
> standard report enabled.  then enable/disable ForecastVariables to see if 
> you get the same behavior.
>
> 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: NOAA reports not available

[bgrattan]

Sorry, no date problem...  I just read the update info for 3.9.1.   Bob

On Saturday, February 9, 2019 at 11:32:04 AM UTC-5, bgra...@umw.edu wrote:
>
> Matt,
> One thing I have noticed which may or may not give you a clue is my [Time] 
> format is not being picked up correctly from skin.conf. I have set the 
> following which isn't showing--it seems to have defaulted to something else/
>
>

-- 
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: NOAA reports not available

[bgrattan]

Matt,
One thing I have noticed which may or may not give you a clue is my [Time] 
format is not being picked up correctly from skin.conf. I have set the 
following which isn't showing--it seems to have defaulted to something else/

day= %H:%M
week   = %H:%M on %A
month  = %d-%b-%Y %H:%M
year   = %d-%b-%Y %H:%M
rainyear   = %d-%b-%Y %H:%M
current= %A %B-%d-%Y %H:%M
ephem_day  = %H:%M
ephem_year = %d-%b-%Y %H:%M

It may have happened in the upgrade to 3.9.1

This may be some other problem which I won't work on until we figure out what 
is going on with the present ForecastVaribles.

Thanks.  Bob


On Saturday, February 9, 2019 at 9:19:27 AM UTC-5, bgra...@umw.edu wrote:
>
> Matt,
>
> Here are the three files. ForecastVariables is commented out. I can change 
> it if you need. NOAA drop down menus now work.  Thanks.  Bob
>
> On Friday, February 8, 2019 at 6:49:29 PM UTC-5, mwall wrote:
>>
>> On Friday, February 8, 2019 at 6:43:14 PM UTC-5, bgrattan wrote:
>>>
>>> I have removed ForecastVariables in skin.conf. All of the month/year 
>>> selections appear as they should--you can have a look. The forecast items 
>>> no longer appear.
>>>
>>
>> please post these files:
>>
>> skins/Standard/index.html.tmpl
>> skins/Standard/skin.conf
>> weewx.conf (remove all passwords first)
>>
>> 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: NOAA reports not available

[bgrattan]

Matt,

Here are the three files. ForecastVariables is commented out. I can change 
it if you need. NOAA drop down menus now work.  Thanks.  Bob

On Friday, February 8, 2019 at 6:49:29 PM UTC-5, mwall wrote:
>
> On Friday, February 8, 2019 at 6:43:14 PM UTC-5, bgrattan wrote:
>>
>> I have removed ForecastVariables in skin.conf. All of the month/year 
>> selections appear as they should--you can have a look. The forecast items 
>> no longer appear.
>>
>
> please post these files:
>
> skins/Standard/index.html.tmpl
> skins/Standard/skin.conf
> weewx.conf (remove all passwords first)
>
> 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.


n4mrv.index.html.tmpl
Description: Binary data
 ###
# STANDARD SKIN CONFIGURATION FILE#
# Copyright (c) 2010 Tom Keffer#
###

[Extras]
# Put any extra tags here that you want to be available in the templates

# Here's an example. 
# This radar image would be available as $Extras.radar_img
radar_img = http://radar.weather.gov/ridge/lite/NCR/AKQ_loop.gif
# This URL will be used as the image hyperlink:
radar_url = 
http://radar.weather.gov/ridge/radar.php?product=NCR&rid=AKQ&loop=yes

# Here's another. If you have a Google Analytics ID, uncomment and edit 
# the next line, and the analytics code will automatically be included
# in your generated HTML files:
#googleAnalyticsId = UA-12345678-1

###

[Units]
# This section is for managing the selection and formatting of units.

[[Groups]]
# For each group of measurements, this section sets what units to
# use for it.
# NB: The unit is always in the singular. I.e., 'mile_per_hour',
# NOT 'miles_per_hour'

group_altitude = foot # Options are 'foot' or 
'meter'
group_degree_day   = degree_F_day # Options are 'degree_F_day' 
or 'degree_C_day'
group_direction= degree_compass
group_moisture = centibar
group_percent  = percent
group_pressure = inHg # Options are 'inHg', 'mmHg', 
'mbar', or 'hPa'
group_radiation= watt_per_meter_squared
group_rain = inch # Options are 'inch', 'cm', 
or 'mm'
group_rainrate = inch_per_hour# Options are 
'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
group_speed= mile_per_hour# Options are 
'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
group_speed2   = mile_per_hour2   # Options are 
'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
group_temperature  = degree_F # Options are 'degree_F' or 
'degree_C'
group_uv   = uv_index
group_volt = volt

# The following are used internally and should not be changed:
group_count= count
group_interval = minute
group_time = unix_epoch
group_elapsed  = second

[[StringFormats]]
# This section sets the string formatting for each type of unit.

centibar   = %.0f
cm = %.2f
cm_per_hour= %.2f
degree_C   = %.1f
degree_F   = %.1f
degree_compass = %.0f
foot   = %.0f
hPa= %.1f
hour   = %.1f
inHg   = %.3f
inch   = %.2f
inch_per_hour  = %.2f
km_per_hour= %.0f
km_per_hour2   = %.1f
knot   = %.0f
knot2  = %.1f
mbar   = %.1f
meter  = %.0f
meter_per_second   = %.1f
meter_per_second2  = %.1f
mile_per_hour  = %.0f
mile_per_hour2 = %.1f
mm = %.1f
mmHg   = %.1f
mm_per_hour= %.1f
percent= %.0f
second = %.0f
uv_index   = %.1f
volt   = %.1f
watt_per_meter_squa

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Matt,

I have removed ForecastVariables in skin.conf. All of the month/year 
selections appear as they should--you can have a look. The forecast items 
no longer appear.

The  [[[DAILYCHARTS]]], [[[MONTHLYCHARTS]]], and [[[YEARLYCHARTS]]] are 
from trying to install the WX-HWS page which I haven't mastered yet. I can 
remove them if you think it will help.

On Friday, February 8, 2019 at 4:35:48 PM UTC-5, mwall wrote:

Thanks.
Bob 

-- 
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: NOAA reports not available

[bgrattan]

Matt,

Thanks for the quick reply. I've been trying to fix things and forgot to 
clean up some of the test code changes, sorry. However, when I make the 
corrections the drop down NOAA menus are still missing. I have attached my 
corrected index.html.tmpl file.
No errors are showing up that I see. Thanks.
Bob

On Friday, February 8, 2019 at 10:41:28 AM UTC-5, mwall wrote:
>
>
>
> On Friday, February 8, 2019 at 10:04:35 AM UTC-5, bgrattan wrote:
>>
>> Any idea what's going on here? You say its working for you but I can't 
>> seem to find the correct setting to have both the forecast and NOAA 
>> summaries. I have attached my Standard/skin.conf
>>
>
> in your index.html.tmpl you have commented out the cheetah code that 
> generates the 'select' items for the NOAA menus.
>
> this is what i see in your generated html:
>
> 
>
> -Select month-
> 
> 
> Yearly summary: 
> 
> 
> -Select year-
> 
>
> this is what is in the original index.html.tmpl:
>
> 
> #for $monthYear in $SummaryByMonth
> $monthYear
> #end for
> -Select month-
> 
> 
> Yearly summary:   
>  
> 
> #for $yr in $SummaryByYear
> $yr
> #end for
> -Select year-
> 
>
> you have removed the '#for' loops, so the menus are not generated.
>
> 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.


indexn4mrv.html.tmpl
Description: Binary data

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Matt,

I have upgraded to weewx 3.9.1 and forecast 3.3.2. I thought all was fine 
but then found that my NOAA summary drop down menus had disappeared again. 
I added the forecast_compact to the Standard skin (with your help, thanks) 
and everything seems good except the NOAA menus.  The NOAA *.txt files are 
being created properly.

Once again, if I remove the "search_list_extensions = 
user.forecast.ForecastVariables" from skin.conf under [CheetahGenerator] 
the NOAA drop downs are available but then the compact forecast is gone.

Any idea what's going on here? You say its working for you but I can't seem 
to find the correct setting to have both the forecast and NOAA summaries. I 
have attached my Standard/skin.conf

Thanks,
Bob

http://grattans.org/wx

##
On Wednesday, February 6, 2019 at 10:25:09 AM UTC-5, mwall wrote:
>
> another data point:  forecast 3.3.2 works fine with the standard skin, as 
> show in the attached screenshot.
>
> i included the forecast by adding two lines to index.html.tmpl in the 
> Standard skin:
>
>   
>
> 
> #include "forecast_compact.inc"
>
> 
>   
> Current Conditions
>   
>
> the NOAA menus work properly.
>
>

-- 
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.
 ###
# STANDARD SKIN CONFIGURATION FILE#
# Copyright (c) 2010 Tom Keffer#
###

[Extras]
# Put any extra tags here that you want to be available in the templates

# Here's an example. 
# This radar image would be available as $Extras.radar_img
radar_img = http://radar.weather.gov/ridge/lite/NCR/AKQ_loop.gif
# This URL will be used as the image hyperlink:
radar_url = 
http://radar.weather.gov/ridge/radar.php?product=NCR&rid=AKQ&loop=yes

# Here's another. If you have a Google Analytics ID, uncomment and edit 
# the next line, and the analytics code will automatically be included
# in your generated HTML files:
#googleAnalyticsId = UA-12345678-1

###

[Units]
# This section is for managing the selection and formatting of units.

[[Groups]]
# For each group of measurements, this section sets what units to
# use for it.
# NB: The unit is always in the singular. I.e., 'mile_per_hour',
# NOT 'miles_per_hour'

group_altitude = foot # Options are 'foot' or 
'meter'
group_degree_day   = degree_F_day # Options are 'degree_F_day' 
or 'degree_C_day'
group_direction= degree_compass
group_moisture = centibar
group_percent  = percent
group_pressure = inHg # Options are 'inHg', 'mmHg', 
'mbar', or 'hPa'
group_radiation= watt_per_meter_squared
group_rain = inch # Options are 'inch', 'cm', 
or 'mm'
group_rainrate = inch_per_hour# Options are 
'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
group_speed= mile_per_hour# Options are 
'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
group_speed2   = mile_per_hour2   # Options are 
'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
group_temperature  = degree_F # Options are 'degree_F' or 
'degree_C'
group_uv   = uv_index
group_volt = volt

# The following are used internally and should not be changed:
group_count= count
group_interval = minute
group_time = unix_epoch
group_elapsed  = second

[[StringFormats]]
# This section sets the string formatting for each type of unit.

centibar   = %.0f
cm = %.2f
cm_per_hour= %.2f
degree_C   = %.1f
degree_F   = %.1f
degree_compass = %.0f
foot   = %.0f
hPa= %.1f
hour   = %.1f
inHg   = %.3f
inch   = %.2f
inch_per_hour  = %.2f
km_per_hour= %.0f
km_per_hour2   = %.1f
knot   = %.0f
knot2  = %.1f
mbar   = %.1f
meter  = %.0f
meter_per_second   = %.1f
meter_per_second2  = %.1f
mile_per_hour  = %.0f
mile_per_hour2 = %.1f
  

[weewx-user] Re: Font problems with compact forecast (Standard skin)

[bgrattan]

Got it! Many thanks!  Bob

On Thursday, February 7, 2019 at 4:48:32 PM UTC-5, mwall wrote:
>
> whoops!  i see that you have included the css.  however, apparently the 
> relative path does not work - this fails:
>
> http://grattans.org/forecast/forecast_compact.css
>
> with this error from your web server:
>
> [an error occurred while processing this directive]
>
> so you can either fix your web server so that the forecast skin is in its 
> paths, or you can copy the forecast_compact.css file into the Standard skin
>
> 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] Font problems with compact forecast (Standard skin)

[bgrattan]

Hello,
I have installed the latest forecast extension and attempted to add it to 
my Standard skin. It seems to be working, however the fonts do not display 
correctly, or at least they seem to be causing the alignment of icons and 
text.
See http://grattans.org/wx

I have added the following to index.html.tmpl


  
###

#include "../forecast/forecast_compact.inc"
##

  
Current Conditions
  


Also have:

 # List of files to be copied only the first time the generator runs
copy_once = backgrounds/*, weewx.css, mobile.css, favicon.ico, 
smartphone/icons/*, smartphone/custom.js,icons/*.png


Also:

search_list_extensions = user.forecast.ForecastVariables


It seems to have the data but the formatting is off because of the font.  
Weewx 3.9.1 with setup.py install on Ubuntu.

Something stupid I've done. Any suggestions will be appreciated.  Thanks.

Bob

-- 
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: V3.9.1

[bgrattan]

Tom,

I'm not sure why I have this problem because it sounds like we have the 
same setup. My son setup a station VP2 + APRS logger + RPI in Norway and 
had the same problem. I read about the fix somewhere in the group a few 
years ago and have had to use it with each upgrade as the vantage.py is 
overwritten by a new version. It was something about the APRS logger 
sending constant data where the regular logger waits for requests for data. 
The explanation is beyond  my expertise.

Bob

On Thursday, February 7, 2019 at 1:34:42 PM UTC-5, Tom Robertson wrote:
>
> I am using the Vantage Pro 2 and CWOP with my APRS # and all is working 
> well.  I do not see any errors.  I have my Davis connected via a USB to 
> serial adapter and running on a Pi3B+ with weewx 3.9.1.
>
> https://aprs.fi/#!call=a%2FKQ5S-13&timerange=3600&tail=3600 
> 
>
> -
> Tom
>
> On Feb 7, 2019, at 11:33 AM, bgra...@umw.edu  wrote:
>
> Thanks, Tom and all who contributed, for the nice upgrade to 3.9.1.  I 
> just upgraded from 3.8.2 and all went well. Now I need to explore some of 
> the new features.
>
> Just a FIY to those with a VantagePro2 and an APRS data link: With the new 
> default vantage.py driver, I still get the Loop error "*expected to read 
> 99 chars; got 0 instead*" To fix this, I changed (as in past versions) 
> "*for_loopPacket 
> in self.genDavisLoopPacket(200):*"
> to: "*for_loopPacket in self.genDavisLoopPacket(2):*"  Not sure why but 
> this fixes it and it works fine. My APRS link is a serial version.
>
> Thanks again,
> Bob
> http://grattans.org/wx
>
> On Wednesday, February 6, 2019 at 8:40:34 AM UTC-5, Thomas Keffer wrote:
>>
>> Well, that was a record short release. We found a serious bug in v3.9.0 
>> that could break skins that do not have fonts defined, such as cmon.
>>
>> So, we are releasing v3.9.1, found in the usual place 
>> .
>>
>> -tk
>>
>
> -- 
> 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+...@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: V3.9.1

[bgrattan]

Thanks, Tom and all who contributed, for the nice upgrade to 3.9.1.  I just 
upgraded from 3.8.2 and all went well. Now I need to explore some of the 
new features.

Just a FIY to those with a VantagePro2 and an APRS data link: With the new 
default vantage.py driver, I still get the Loop error "*expected to read 99 
chars; got 0 instead*" To fix this, I changed (as in past versions) 
"*for_loopPacket 
in self.genDavisLoopPacket(200):*"
to: "*for_loopPacket in self.genDavisLoopPacket(2):*"  Not sure why but 
this fixes it and it works fine. My APRS link is a serial version.

Thanks again,
Bob
http://grattans.org/wx

On Wednesday, February 6, 2019 at 8:40:34 AM UTC-5, Thomas Keffer wrote:
>
> Well, that was a record short release. We found a serious bug in v3.9.0 
> that could break skins that do not have fonts defined, such as cmon.
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
> -tk
>

-- 
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: NOAA reports not available

[bgrattan]

Glenn,

*I've got it!!!* I checked the original skin.conf under 3.8.2 and noticed 
that "search_list_extensions = user.forecast.ForecastVariables" didn't 
exist under [CheetahGenerator]. I commented it out in mine and the 
summaries worked from drop down lists.
I'll have to go back and figure out what that was doing but, anyway, the 
problem seems to be solved for now.
Thank you again for the much appreciated help! I'm sorry for all the 
complications! I would like to treat you to a pint but don't think I could 
stand the plane ride...
Cheers,
Bob

On Monday, February 4, 2019 at 9:56:28 PM UTC-5, Glenn McKechnie wrote:
>
> No insights (to me ) from the files you provided. 
>
> What's in no.htaccess? I wouldn't have thought there could be anything 
> in there that would prevent weewx from using the contents of NOAA. 
> It's more a webserver control point  - but then...? 
>
> Ownership and permissions seem okay. root.www-data is typical for a 
> debian install, 775 is liberal. 
>
> It's nice to see someone else that uses 'tree' It's a great little 
> program  and perfect for this case! 
> it shows the files where they should be. 
>
> I guess you could move them (the ones in public_html/NOAA ) aside, 
> then restart weewx to allow weewx to regenerate them. Then see if 
> excitement or disappointment wins that coin toss. 
>
>
> If it wasn't for the fact that your tmpl and skin.conf works here... 
> flawlessly even... Phttt. 
>
>
>
>
>
> On 05/02/2019, bgra...@umw.edu   > wrote: 
> > Hi Glenn, 
> > 
> > Sorry to put you through all of this. I have attached two files. One 
> from 
> > wee_debug and one of a "tree" from /home/weewx (a bit long but may have 
> a 
> > clue). I have a symlink in /var/www/html to /home/weewx/public_html 
> which 
> > has been working ok with apache2. A "diff" on cheetahgenerator.py and 
> 382 
> > source came out equal. The same thing on 370 showed a small difference 
> so I 
> > 
> > used that file but nothing changed so I put the original back. I'll work 
> on 
> > 
> > blocking the WX-HWS code I added to see if that changes anything.  In 
> > trying to get things going earlier, I changed some ownership to 
> > root:www-data and permissions to 775. I wouldn't think this would matter 
> > with this problem (?). 
> > Thanks again. 
> > Bob 
> > 
> > On Monday, February 4, 2019 at 5:01:17 PM UTC-5, Glenn McKechnie wrote: 
> >> 
> >> Hey Bob, 
> >> 
> >> There is no change, but it confirms that 
> >> 1.) we are working on the same page (the change has propagated to 
> godaddy) 
> >> 
> >> 2.) The [[SummaryByMonth]] and [[SummaryByYear]] sections aren't being 
> >> picked up and filled. If weewx couldn't find them, it would complain 
> >> with an error - at least it does here. It's odd that they aren't being 
> >> substituted as I believe your locations are correct - see below. 
> >> 
> >> I assume you are running as root, in which case it doesn't matter what 
> >> the permissions on the NOAA directories are. FWIW The Directory is 
> >> 0744, the files are 0644 
> >> 
> >> Regarding your syslog output. I'm not familiar with public_html as the 
> >> web directory. I assume it gets remapped by apache2(?) and that's when 
> >> it becomes /weewx/ as ftpuploads refers to it. 
> >> eg:- ftpupload: Uploaded file /weewx/NOAA/NOAA-2019-02.txt 
> >> Are you using apache? Are you rewriting the Directory? 
> >> 
> >> It might pay to use wee_debug to sanitise your weewx.conf file. Double 
> >> check the output is cleaned of anything private, then post the 
> >> contents here. 
> >> http://weewx.com/docs/utilities.htm#wee_debug_utility 
> >> 
> >> Regarding weewx.conf values... 
> >> 
> >> Mine runs with 
> >> WEEWX_ROOT = / 
> >> SKIN_ROOT = /home/weewx/skins 
> >> HTML_ROOT = /var/www/html/weewx 
> >> 
> >> Yours is 
> >> WEEWX_ROOT = /home/weewx  (I assume this otherwise the following 
> >> values won't expand out) 
> >> and you supplied these previously 
> >> SKIN_ROOT = skins 
> >> HTML_ROOT = public_html 
> >> and that's pretty much a setup.py install 
> >> 
> >> Which means that your NOAA files should reside in 
> >> /home/weewx/public_html/NOAA 
> >> eg:- /home/weewx/public_html/NOAA/NOAA-2019-02.txt 
> >> 
> >> From there CheetahGenerator should be able to find them and use them 
> >> in the index template. 
> >> 
> >> Nope, I'm out of ideas. 
> >> 
> >> Regarding WX-HWS. I'm running your template with that section 
> >> basically commented out (sort of, I have stubs in place) 
> >> You could try commenting out that whole section, or at least the 
> >> HTML_ROOT = /home/weewx/public_html/hws entries for a couple of runs. 
> >> Not sure if it will make any difference but we're at that stage. 
> >> 
> >> 
> >> Replace cheetah the application or weewx/cheetahgenerator.py ? 
> >> You could try reinstalling cheetah, It shouldn't mess with anything. 
> >> You could replace the  weewx/cheetahgenerator.py file with a fresh 
> >> copy from the source package without any issue.  As an aside, I'm 
> >>

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Glenn,

Had a thought that might not mean anything but here it goes. The page is 
not finding the summaries in /NOAA because I am unable to select a month or 
year. The box fails to display a drop down list of months or years from 
which I would select. It seems that it's the actual drop down list that is 
missing here because, until I select a year/month, the software has no need 
to go to /NOAA to display a date.txt file. Maybe it's the code/mechanism 
that creates the drop down list is missing (?) or not functioning (?) The 
list of months/years is not in /NOAA so maybe there is some script that 
produces it and creates links to /NOAA...  I really don't know how these 
drop down lists function so I'm out of my element at this point.  Any 
thoughts on this idea?  Thanks.
Bob


On Monday, February 4, 2019 at 9:56:28 PM UTC-5, Glenn McKechnie wrote:
>
> No insights (to me ) from the files you provided. 
>
> What's in no.htaccess? I wouldn't have thought there could be anything 
> in there that would prevent weewx from using the contents of NOAA. 
> It's more a webserver control point  - but then...? 
>
> Ownership and permissions seem okay. root.www-data is typical for a 
> debian install, 775 is liberal. 
>
> It's nice to see someone else that uses 'tree' It's a great little 
> program  and perfect for this case! 
> it shows the files where they should be. 
>
> I guess you could move them (the ones in public_html/NOAA ) aside, 
> then restart weewx to allow weewx to regenerate them. Then see if 
> excitement or disappointment wins that coin toss. 
>
>
> If it wasn't for the fact that your tmpl and skin.conf works here... 
> flawlessly even... Phttt. 
>
>
>
>
>
> On 05/02/2019, bgra...@umw.edu   > wrote: 
> > Hi Glenn, 
> > 
> > Sorry to put you through all of this. I have attached two files. One 
> from 
> > wee_debug and one of a "tree" from /home/weewx (a bit long but may have 
> a 
> > clue). I have a symlink in /var/www/html to /home/weewx/public_html 
> which 
> > has been working ok with apache2. A "diff" on cheetahgenerator.py and 
> 382 
> > source came out equal. The same thing on 370 showed a small difference 
> so I 
> > 
> > used that file but nothing changed so I put the original back. I'll work 
> on 
> > 
> > blocking the WX-HWS code I added to see if that changes anything.  In 
> > trying to get things going earlier, I changed some ownership to 
> > root:www-data and permissions to 775. I wouldn't think this would matter 
> > with this problem (?). 
> > Thanks again. 
> > Bob 
> > 
> > On Monday, February 4, 2019 at 5:01:17 PM UTC-5, Glenn McKechnie wrote: 
> >> 
> >> Hey Bob, 
> >> 
> >> There is no change, but it confirms that 
> >> 1.) we are working on the same page (the change has propagated to 
> godaddy) 
> >> 
> >> 2.) The [[SummaryByMonth]] and [[SummaryByYear]] sections aren't being 
> >> picked up and filled. If weewx couldn't find them, it would complain 
> >> with an error - at least it does here. It's odd that they aren't being 
> >> substituted as I believe your locations are correct - see below. 
> >> 
> >> I assume you are running as root, in which case it doesn't matter what 
> >> the permissions on the NOAA directories are. FWIW The Directory is 
> >> 0744, the files are 0644 
> >> 
> >> Regarding your syslog output. I'm not familiar with public_html as the 
> >> web directory. I assume it gets remapped by apache2(?) and that's when 
> >> it becomes /weewx/ as ftpuploads refers to it. 
> >> eg:- ftpupload: Uploaded file /weewx/NOAA/NOAA-2019-02.txt 
> >> Are you using apache? Are you rewriting the Directory? 
> >> 
> >> It might pay to use wee_debug to sanitise your weewx.conf file. Double 
> >> check the output is cleaned of anything private, then post the 
> >> contents here. 
> >> http://weewx.com/docs/utilities.htm#wee_debug_utility 
> >> 
> >> Regarding weewx.conf values... 
> >> 
> >> Mine runs with 
> >> WEEWX_ROOT = / 
> >> SKIN_ROOT = /home/weewx/skins 
> >> HTML_ROOT = /var/www/html/weewx 
> >> 
> >> Yours is 
> >> WEEWX_ROOT = /home/weewx  (I assume this otherwise the following 
> >> values won't expand out) 
> >> and you supplied these previously 
> >> SKIN_ROOT = skins 
> >> HTML_ROOT = public_html 
> >> and that's pretty much a setup.py install 
> >> 
> >> Which means that your NOAA files should reside in 
> >> /home/weewx/public_html/NOAA 
> >> eg:- /home/weewx/public_html/NOAA/NOAA-2019-02.txt 
> >> 
> >> From there CheetahGenerator should be able to find them and use them 
> >> in the index template. 
> >> 
> >> Nope, I'm out of ideas. 
> >> 
> >> Regarding WX-HWS. I'm running your template with that section 
> >> basically commented out (sort of, I have stubs in place) 
> >> You could try commenting out that whole section, or at least the 
> >> HTML_ROOT = /home/weewx/public_html/hws entries for a couple of runs. 
> >> Not sure if it will make any difference but we're at that stage. 
> >> 
> >> 
> >> Replace cheetah the application or weewx/cheetahgener

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Glenn,
Your files are loaded now. Haven't seen any difference.
I upgraded from 3.7.0 to 3.8.2 several months ago. Could there be a problem 
with cheetah? Is it possible to reinstall cheetah without messing up the 
configuration?
I've also been trying to install WX-HWS, with only partial luck, as it 
can't find the wxcharts. Don't think I have changed anything that would 
affect this.  Thanks.

On Monday, February 4, 2019 at 3:52:39 AM UTC-5, Glenn McKechnie wrote:
>
> Bugger - wrong file. 
>
> Use this one. 
>
> On 04/02/2019, Glenn McKechnie > 
> wrote: 
> > Hi Bob, 
> > 
> > The simplest explanation would be that CheetahGenerator is not finding 
> > the NOAA templates to generate the html links - and that it's not 
> > throwing an error in the process. 
> > 
> > Attached is a version of your index.html.tmpl that will display the 
> > NOAA filenames it finds. If it finds any (I don't expect it will) 
> > They will be listed as comments in the page source. 
> > Give it a run and we'll see if it leads anywhere. 
> > Ignore the attached weewx.css - it just fixes a div renaming to 
> > satisfy the validator.w3.org 
> > 
> > As I say, it works for me. 
> > http://203.213.243.61/weewx/ 
> > But that doesn't really help you. :-( 
> > 
> > 
> > On 04/02/2019, Glenn McKechnie > 
> wrote: 
> >> Okay, it seems that we're back to square one. 
> >> 
> > 
> > -- 
> > 
> > 
> > Cheers 
> >  Glenn 
> > 
> > rorpi - read only raspberry pi & various weewx addons 
> > https://github.com/glennmckechnie 
> > 
>
>
> -- 
>
>
> Cheers 
>  Glenn 
>
> rorpi - read only raspberry pi & various weewx addons 
> https://github.com/glennmckechnie 
>

-- 
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: NOAA reports not available

[bgrattan]

are'
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Using archive interval of 900 
seconds (specified by hardware)
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Use LOOP data in hi/low 
calculations: 1
Feb  3 16:57:25 n4mrv weewx[4183]: manager: Daily summary version is 2.0
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Feb  3 16:57:25 n4mrv weewx[4183]: manager: Starting backfill of daily summaries
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
weewx.engine.StdArchive
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.NWSForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: NWS: forecast version 
3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: NWS: last forecast 
issued 2016-11-24 16:02:00 EST (1480021320), requested 2016-11-24 17:15:1
7 EST (1480025717)
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: NWS: interval=10800 
max_age=604800 lid=VAZ115 foid=AKQ
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.NWSForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.ZambrettiForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Zambretti: forecast 
version 3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Zambretti: last 
forecast issued 2019-02-03 15:30:00 EST (1549225800), requested 2019-02-03 1
5:30:00 EST (1549225800)
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Zambretti: 
interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
hemisphere=
NORTH lower_pressure=950.0 upper_pressure=1050.0
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.ZambrettiForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.WUForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: WU: forecast version 
3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: WU: last forecast 
issued 2019-02-03 14:00:15 EST (1549220415), requested 2019-02-03 14:00:15
 EST (1549220415)
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: WU: interval=10800 
max_age=604800 api_key=1694 location=37.7531,-77.4843 fc=hour
ly10day
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.WUForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.XTideForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: XTide: forecast 
version 3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: XTide: location 
(location) has not been specified
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: XTide: forecast will 
not be run
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.XTideForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.OWMForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: OWM: forecast version 
3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: OWM: API key (api_key) 
is not specified
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: OWM: forecast will not 
be run
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.OWMForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.UKMOForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: UKMO: forecast version 
3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: UKMO: API key 
(api_key) is not specified
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: UKMO: forecast will 
not be run
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.UKMOForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.AerisForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Aeris: forecast 
version 3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Aeris: client 
identifier (client_id) is not specified
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Aeris: client secret 
(client_secret) is not specified
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: Aeris: forecast will 
not be run
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.AerisForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
user.forecast.WWOForecast
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: WWO: forecast version 
3.2.4
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: WWO: API key (api_key) 
is not specified
Feb  3 16:57:25 n4mrv weewx[4183]: forecast: MainThread: WWO: forecast will not 
be run
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Finished loading service 
user.forecast.WWOForecast
Feb  3 16:57:25 n4mrv weewx[4183]: engine: Loading service 
weewx.restx.StdStationRegistry
Feb  3 16:57:25 n4mrv weewx[4183]: restx: StationRegistry: Station will be 
registered.
Feb  3 16:57:25 n4

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Glenn,

Something odd. My index.html.tmpl looks ok (attached) so something is 
happening when it's used to generate the page. I have also attached the 
skin.conf file in case that helps in understanding what's going on. Both 
files are local and the problem is on my local machine as well as the pages 
uploaded to my GoDaddy site.

On Saturday, February 2, 2019 at 5:24:42 PM UTC-5, Glenn McKechnie wrote:
>
> Hi Bob, 
>
> Your page at http://grattans.org/wx/ is missing some vital code, which 
> interestingly you have correct in your last post. 
> Is that from your local tmpl version? 
>
> The navbar code is missing the 6 lines that start with - in the diff 
> below. 
>
> @@ -451,17 +451,11 @@ 
>   onclick="openURL('year.html')" /> 
>  Monthly summary:  
>   
> -#for $monthYear in $SummaryByMonth 
> -$monthYear 
> -#end for 
> -Select month- 
>   
>   
>  Yearly summary:  
>   
> -#for $yr in $SummaryByYear 
> -$yr 
> -#end for 
> -Select year- 
>   
>   
>
> I have your page at http://grattans.org/wx/ correctly generating the 
> NOAA pages here  if I include that AND also fix the unicode error in 
> your http://forecast.weather.gov url. 
>
> CheetahGenerator complains about invalid code -  I see this " 
> highlight=on​ " 
> Remove evrything after the =on and it should generate correctly and 
> you'll get a fresh copy created and uploaded to your website. 
> Obviously you'll eventually need to correct the URL and replace 
> whatever we have rudely taken out. 
>
> I suspect half the problem is here, with this broken URL. It breaks 
> page generation and we/you aren't seeing your changes as the latest 
> changes aren't being uploaded. 
>
>
>
>
>
>
> On 03/02/2019, bgra...@umw.edu   > wrote: 
> > Glenn, 
> > Here's what I found, so far: 
> > 
> > two NOAA directories 
> > /home/weewx/skins/Standard/NOAA - contains 2 template files for  and 
> MM 
> > 
> > summaries 
> > /home/weewx/pub_html/NOAA - contains all the summary files *.txt from 
> > 2007-present day 
> > 
> > I substituted the original index.html.tmpl and an older weewx.conf file 
> and 
> > 
> > got the same results, no pull down  or MM summaries. 
> > 
> > The files seem to be being built but not accessible from index.html 
> > Standard skin. 
> > 
> > From my index.html.tmpl: 
> > 
> >   
> >  > onclick="openURL('index.html')" /> 
> >  > onclick="openURL('week.html')" /> 
> >  > onclick="openURL('month.html')" /> 
> >  > onclick="openURL('year.html')" /> 
> > Monthly summary:  
> >  
> > #for $monthYear in $SummaryByMonth 
> > $monthYear 
> > #end for 
> > -Select month- 
> >  
> >  
> > Yearly summary:  
> >  
> > #for $yr in $SummaryByYear 
> > $yr 
> > #end for 
> > -Select year- 
> >  
> >  
> >
> >  
> > 
> > Thanks for your continued help.  Hope the above tells you something. 
> Sorry 
> > I'm not much 
> > of a programmer. 
> > 
> > Bob 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
>
>
> -- 
>
>
> Cheers 
>  Glenn 
>
> rorpi - read only raspberry pi & various weewx addons 
> https://github.com/glennmckechnie 
>

-- 
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.


Standard_skin_conf
Description: Binary data


index_html_tmpl
Description: Binary data

Re: [weewx-user] Re: NOAA reports not available

[bgrattan]

Glenn,
Thanks! I’ll try the fix tomorrow. Not sure how or when this got messed up. As 
I haven’t used the summary feature for a while then I haven’t missed it.
Much appreciated!  Just curious where you are located?
Will keep you posted.

Bob

-- 
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: NOAA reports not available

[bgrattan]

Glenn,
Here's what I found, so far:

two NOAA directories 
/home/weewx/skins/Standard/NOAA - contains 2 template files for  and MM 
summaries
/home/weewx/pub_html/NOAA - contains all the summary files *.txt from 
2007-present day

I substituted the original index.html.tmpl and an older weewx.conf file and 
got the same results, no pull down  or MM summaries.

The files seem to be being built but not accessible from index.html 
Standard skin.

>From my index.html.tmpl:

 




Monthly summary: 

#for $monthYear in $SummaryByMonth
$monthYear
#end for
-Select month-


Yearly summary: 

#for $yr in $SummaryByYear
$yr
#end for
-Select year-


  


Thanks for your continued help.  Hope the above tells you something. Sorry 
I'm not much
of a programmer.

Bob

-- 
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: NOAA reports not available

[bgrattan]

Glenn,

Still missing the NOAA reports. I moved datepicker.js and it didn't seem to 
change anything. I have wxobs running fine and removing datepicker.js 
didn't seem to affect it, or anything else.

On Thursday, January 31, 2019 at 7:04:50 PM UTC-5, Glenn McKechnie wrote:
>
> I've had this happen before and its been a javascript problem , 
> clashing with similarly named code or a missing script. 
>
>
> wxobs (https://github.com/glennmckechnie/weewx-wxobs ) uses either one 
> of 2 files, standard.js or seasons.js skins for the generation of the 
> NOAA templates - but only for itself. 
> It shouldn't be influencing any other pages, especially the standard 
> skin as that has the NOAA script hard coded into the index.html page. 
>
> Version 0.6.5 of wxobs, which is installed there, doesn't install 
> either of those files so accidental overwrites won't be an issue. It 
> does install a file named datepicker.js but that shouldn't be 
> interfering with anything either. If you wanted to be certain then 
> rename, or move that one away and see if the NOAAs regenerate. 
>
> As an aside. If it's next on your list and you want help to get wxobs 
> up and running, contact me directly and we'll try and work around the 
> problem you appear to be having. I assume it's on a hosted server? 
>
> On 01/02/2019, Pat > wrote: 
> > It might be missing the NOAA tmpl files. Maybe reinstall the skin and 
> then 
> > restart weewx and see if they are back after an interval period 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
>
>
> -- 
>
>
> Cheers 
>  Glenn 
>
> rorpi - read only raspberry pi & various weewx addons 
> https://github.com/glennmckechnie 
>

-- 
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: NOAA reports not available

[bgrattan]

Thanks, Glenn, I’ll check on that tomorrow. Much appreciated for the help.
Bob

-- 
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: NOAA reports not available

[bgrattan]

It seems that HTMLPages is coming from the Bootstrap skin so I'll look into 
that.

On Thursday, January 31, 2019 at 5:12:45 PM UTC-5, Pat wrote:
>
> It looks like you're using 2 skins called "wxobs" and "HTMLPages"? If so, 
> you might need to check with the developer of those skins to see why. 
>
> If that's not true then you haven't pasted enough of the logs.
>
>
> On Thursday, January 31, 2019 at 5:07:14 PM UTC-5, bgra...@umw.edu wrote:
>>
>> Hello,
>>
>> I haven't used my monthly/yearly reports for a while and, after trying, 
>> found that the month and year dropdown tabs are empty. The NOAA templates 
>> are in place.
>> My latest log (debug=1) is attached. I haven't noticed any errors lately 
>> and everything else has been working. Ian S. has been helping me with the 
>> new weather34
>> template files (still a work in progress). Not really sure what I should 
>> be looking for here.  Thanks in advance for any advice you can offer.
>>
>> Bob
>> grattans.org/wx
>>
>>
>>

-- 
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: NOAA reports not available

[bgrattan]

Thanks for the quick reply, Pat. Yes I am using the extension "wxobs" plus 
the Standard skin but am not sure what "HTMLPages" is connected to. 
Bob

-- 
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] NOAA reports not available

[bgrattan]

al=600 max_age=604800 winddir_period=1800 pressure_period=10800 
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.ZambrettiForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
user.forecast.WUForecast
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: WU: forecast version 
3.2.4
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: WU: last forecast 
issued 2019-01-31 16:15:15 EST (1548969315), requested 2019-01-31 16:15:15 EST 
(1548969315)
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: WU: interval=10800 
max_age=604800 api_key=1694 location=37.7531,-77.4843 fc=hourly10day
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.WUForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
user.forecast.XTideForecast
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: XTide: forecast 
version 3.2.4
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: XTide: location 
(location) has not been specified
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: XTide: forecast will 
not be run
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.XTideForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
user.forecast.OWMForecast
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: OWM: forecast version 
3.2.4
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: OWM: API key 
(api_key) is not specified
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: OWM: forecast will 
not be run
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.OWMForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
user.forecast.UKMOForecast
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: UKMO: forecast 
version 3.2.4
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: UKMO: API key 
(api_key) is not specified
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: UKMO: forecast will 
not be run
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.UKMOForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
user.forecast.AerisForecast
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: Aeris: forecast 
version 3.2.4
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: Aeris: client 
identifier (client_id) is not specified
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: Aeris: client secret 
(client_secret) is not specified
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: Aeris: forecast will 
not be run
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.AerisForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
user.forecast.WWOForecast
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: WWO: forecast version 
3.2.4
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: WWO: API key 
(api_key) is not specified
Jan 31 16:48:18 n4mrv weewx[13080]: forecast: MainThread: WWO: forecast will 
not be run
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
user.forecast.WWOForecast
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
weewx.restx.StdStationRegistry
Jan 31 16:48:18 n4mrv weewx[13080]: restx: StationRegistry: Station will be 
registered.
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
weewx.restx.StdWunderground
Jan 31 16:48:18 n4mrv weewx[13080]: restx: Wunderground-PWS: Data for station 
KVAASHLA4 will be posted
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
weewx.restx.StdWunderground
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
weewx.restx.StdPWSweather
Jan 31 16:48:18 n4mrv weewx[13080]: restx: PWSWeather: Data for station N4MRV 
will be posted
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
weewx.restx.StdPWSweather
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service weewx.restx.StdCWOP
Jan 31 16:48:18 n4mrv weewx[13080]: restx: CWOP: Data for station N4MRV-1 will 
be posted
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
weewx.restx.StdCWOP
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service weewx.restx.StdWOW
Jan 31 16:48:18 n4mrv weewx[13080]: restx: WOW: Data for station 964806001 will 
be posted
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
weewx.restx.StdWOW
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service 
weewx.restx.StdAWEKAS
Jan 31 16:48:18 n4mrv weewx[13080]: restx: AWEKAS: Data will be uploaded for 
user bgrattan
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Finished loading service 
weewx.restx.StdAWEKAS
Jan 31 16:48:18 n4mrv weewx[13080]: engine: Loading service user.emoncms.EmonCMS
Jan 31 16:48:18 

[weewx-user] Re: Bootstrap gauge scales - how to change?

[bgrattan]

Ok, I've found the guage section of skin.conf (Bootstrap) and am playing 
with values. Thanks to the post by Buzz Z.
Bob

-- 
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] Bootstrap gauge scales - how to change?

[bgrattan]

Hello,
I think I have my Bootstrap skin working but see a problem with the gauge 
scales which are displayed. I am showing US unit values but the scales are 
showing
Metric. Could someone tell me how to make the scales show US? Probably simple 
but I can’t find it. Thanks in advance. See site below.

http://grattans.org/wx/Bootstrap/

Bob
http://grattans.org/wx

-- 
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] Serial to USB pl-2303

[bgrattan]

It may be that your /dev/ttyS0 (or whatever you use) has changed to another 
ttyS?. I think there are instructions in the wiki that tell how to lock in a 
certain device after a reboot. Just a thought. Good luck
BG

-- 
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: Colors for dewpoint level in index.html

[bgrattan]

Thanks and much appreciated Tom and mwall. I had used the .raw earlier but 
have tried so many syntax changes that it was probably in the wrong place 
to begin with. Also, I will definitely clean up the code with the suggested 
changes, once I'm sure things are working. For now it looks good.
Now, if I could find a way to reduce the current dewpoint everyone in 
Ashland, VA would be happy...
Bob

-- 
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: Quick rebuild of index.html

[bgrattan]

Thanks. That's just what I need. Bob

 
>

-- 
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] Colors for dewpoint level in index.html

[bgrattan]

Hello,

I have been trying, with no luck, to add colors do various levels of the 
current dewpoint which post in the table on index.html. It works fine for 
UV but not for dewpoint. Steve helped me with the html code for UV but when 
I try the same thing for dewpoint it doesn't work. It gives the correct 
data but shows the color violet rather than red which it should display for 
the range  71 to 80. It's probably something simple but  I've tried 
everything I can think of at this point. Could someone help on this?
My  is for odd/even shading on the display.  Thanks.
Bob

My attempt at coloring dewpoint (from index.html.tmpl)

   #if $current.dewpoint.has_data

Dewpoint
  #if $current.dewpoint <= 55
$current.dewpoint 
  #else if $current.dewpoint >= 56 and $current.dewpoint <= 
64
$current.dewpoint 
  #else if $current.dewpoint >= 65 and $current.dewpoint <= 
70
$current.dewpoint 
  #else if $current.dewpoint >= 71 and $current.dewpoint <= 
80
$current.dewpoint 
  #else if $current.dewpoint >= 81
$current.dewpoint
  #end if


Code for UV color level which works fine:

   #if $day.UV.has_data

UV Index
  #if $current.UV.raw <= 2.4
$current.UV
  #else if $current.UV.raw >= 2.5 and $current.UV.raw <= 5.4
$current.UV
  #else if $current.UV.raw >= 5.5 and $current.UV.raw <= 7.4
$current.UV
  #else if $current.UV.raw >= 7.5 and $current.UV.raw <= 
10.4
$current.UV
  #else if $current.UV.raw > 10.5
$current.UV
  #end if

#end if

My site: *grattans.org/wx*

-- 
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] Quick rebuild of index.html

[bgrattan]

Hello,

As a not-so-good programmer, I frequently have to make changes to 
index.html.tmpl and observe whether my changes have fixed a problem. Since 
my archive period is 15 minutes (a carry over from wview) I then have to 
wait for the archive period to complete in order to view the results.  This 
takes up quite a bit of time.

Is there a command I could run to rebuild the index.html file using the 
last archived data? This would at least show me quickly if my syntax and 
code are displaying correctly in advance of the next archive data. A simple 
restart of weewx doesn't do what I need.

Thanks in advance.

Bob

grattans.org/wx

-- 
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: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb

[bgrattan]

>
> Pat,
>>>
>>
This is the board I have: 
 
https://shop.switchdoc.com/collections/grove/products/the-thunder-board-i2c-lightning-detector-grove-connectors

It looks as if the weewx extension Matt suggests would be the best but I 
would prefer to run it in an RPI and not my main weewx server, if possible. 
The AS3935 board I have is not the one he references but it seems to have 
the same connections using Grove connectors.

I'm going to play around with the software from SwitchDocs Lab and see what 
I come up with. If I can eliminate the PubNub host and produce a web page 
on my own server then that might work. However, since weewx already has a 
data display and graph built-in then that looks promising also. Sort of 
mixed up as to what to do at this point... Thanks.
Bob

-- 
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: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb

[bgrattan]

Thanks, Pat, there may be hope for me after all if you have the time to 
help.  I also have the SwitchDocs board for the RPI detector because I 
thought it might be easier to work with the Python than the Arduino IDE. I 
also have an extra RPI that could be used. Let me look at the software and 
get back to you. It would be nice to have  the AS3935 send data to weewx as 
that would simplify things. I think Matt wrote the extension for weewx but 
I haven't looked at it closely.
Again, much appreciated and I'll get back to you after I read some more.
Bob

>

-- 
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: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb

[bgrattan]

Thanks to everyone for the comments. With my limited experience I will probably 
not attemp to add this to weewx since it’s running so well at present.
I’ll probably try to setup my own web server to receive the AS3935 data using 
MQTT if I can figure out how not to send to pubnub.com whch seems to be 
programmed in the arduino sketch somewhere.

-- 
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: How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb

[bgrattan]

Thanks, Steve, very nice displays. I do hope someone can offer me some ideas. 
Bob

-- 
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] How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb

[bgrattan]

Hello,

I am using an Arduino with the SwitchDoc Labs Thunder Board - AS3935 for 
lightning detection and would like to incorporate the data in my weewx 
station (weewx.tgz, ubuntu 16.04, VP2+).
Not being much of a programmer, I wonder if anyone has tried this setup?
Since I'm running ubuntu on a linux machine (Intel NUC), I wonder if I need 
to setup a separate Rpi to send the data to the weewx machine (I have an 
extra if this is easier). The Thunder Board is presently configured to send 
data via MQTT to pubsub.com which I don't want to do but am not sure how to 
modify the Arduino code.
Any help on this would be greatly appreciated. Thanks.

Bob
http://grattans.org/wx

-- 
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] Some possible helps for anyone running an old Davis Vantage Pro2 console

[bgrattan]

Doug,
I too have an old and new console and have asked Davis about 3.80. Please let 
me know if you hear from them. Thanks.
Bob

-- 
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: forecast (3.2.4) from NWS using AFM format

[bgrattan]

Thanks, Matt, I was afraid that was the problem. I would be glad to help but 
it's way beyond my level of python. Will be glad to help test if that would 
help at a later point when you have time to work on it. Much appreciated ! And 
thanks for all your weewx work!

Bob

-- 
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: forecast (3.2.4) from NWS using AFM format

[bgrattan]

Follow up from log:

forecast: NWSThread: NWS: downloading forecast from 
'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=AKQ'

forecast: NWSThread: NWS: no PFM found for VAZ115 in forecast from AKQ

Maybe "NWS_DEFAULT_PFM_URL" doesn't work for AFM? Seems to be the same text 
format.


-- 
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] forecast (3.2.4) from NWS using AFM format

[bgrattan]

Hello,

I am trying to get an NWS forecast for my area (Ashland, VA) which is in 
the AFM format for VAZ115. There does not seem to be one for Ashland in the 
PFM format.
I have added the following to forecast.py:

NWS_DEFAULT_PFM_URL = 
'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt' 

The lid VAZ115 and foid AKQ are in place.

Not sure this is going to work.  Is this all I need to modify?  Weewx is a 
manual install on latest ubuntu and is working fine,

see: http://grattans.org/wx/forecast/multiple-tables.html

Thanks in advance.

Bob

-- 
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: weewx doesn't start automatically after reboot

[bgrattan]

I have an rs232-->USB adapter which creates ttyUSB0 at startup. Should this be 
a rule in rules.d? Something I hadn't thought about.
I'll remove the modemmanager. Thanks.
Bob

-- 
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: weewx doesn't start automatically after reboot

[bgrattan]

Matt,

I added the " loop_on_init=true" to weewx.conf and that seemed to do it. I 
wasn't sure how to add the delay to weewx.service. I'll keep watch on it to 
be sure it restarts correctly. Thanks so much for the help, also Susan and 
Tom.
Bob

Last log:

Mar 23 11:35:00 nuc weewx[853]: engine: Initializing weewx version 3.7.0
Mar 23 11:35:00 nuc weewx[853]: engine: Using Python 2.7.12 (default, Nov 
19 2016, 06:48:10) #012[GCC 5.4.0 20160609]
Mar 23 11:35:00 nuc weewx[853]: engine: Platform 
Linux-4.8.0-41-generic-x86_64-with-Ubuntu-16.04-xenial
Mar 23 11:35:00 nuc weewx[853]: engine: Locale is 'en_US.UTF-8'
Mar 23 11:35:00 nuc weewx[853]: engine: pid file is /var/run/weewx.pid
Mar 23 11:35:00 nuc weewx[1105]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 23 11:35:00 nuc weewx[1105]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 23 11:35:00 nuc weewx[1105]: engine: Unable to load driver: [Errno 2] 
could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
'/dev/ttyUSB0'
Mar 23 11:36:00 nuc weewx[1105]: engine: *retrying...*
Mar 23 11:36:00 nuc weewx[1105]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 23 11:36:00 nuc weewx[1105]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 23 11:36:00 nuc weewx[1105]: engine: StdConvert target unit is 0x1
Mar 23 11:36:00 nuc weewx[1105]: engine: Archive will use data binding 
wx_binding
Mar 23 11:36:00 nuc weewx[1105]: engine: Record generation will be 
attempted in 'hardware'
Mar 23 11:36:00 nuc weewx[1105]: engine: Using archive interval of 900 
seconds (specified by hardware)
Mar 23 11:36:00 nuc weewx[1105]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Mar 23 11:36:00 nuc weewx[1105]: engine: Starting up weewx version 3.7.0
Mar 23 11:36:00 nuc weewx[1105]: engine: Clock error is -1.61 seconds 
(positive is fast)
Mar 23 11:36:00 nuc weewx[1105]: engine: Starting main packet loop.


>

-- 
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 doesn't start automatically after reboot

[bgrattan]

Andrew,

I rebooted with debug on weewx and nothing showed up in syslog or 
weewx.log. I searched around for the "(/etc/systemd/system/*weewx.service; 
disabled*; vendor preset: enabled)" message and tried the command "*systemctl 
enable weewx*." The result after reboot was this:

root@nuc:~# service weewx status
? weewx.service - weewx weather system
   Loaded: loaded (/etc/systemd/system*/weewx.service; enabled*; vendor 
preset: enabled)
   Active: inactive (dead) since Wed 2017-03-22 15:29:33 EDT; 38s ago
  Process: 810 ExecStart=/home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited, 
status=0/SUCCESS)
 Main PID: 810 (code=exited, status=0/SUCCESS)

Mar 22 15:29:33 nuc weewxd[810]: Traceback (most recent call last):
Mar 22 15:29:33 nuc weewxd[810]:   File "/home/weewx/bin/weewxd", line 64, 
in 
Mar 22 15:29:33 nuc weewxd[810]: weewx.engine.main(options, args)
Mar 22 15:29:33 nuc weewxd[810]:   File "/home/weewx/bin/weewx/engine.py", 
line 833, in main
Mar 22 15:29:33 nuc weewxd[810]: 
daemon.daemonize(pidfile=options.pidfile)
Mar 22 15:29:33 nuc weewxd[810]:   File "/home/weewx/bin/daemon.py", line 
79, in daemonize
Mar 22 15:29:33 nuc weewxd[810]: os.dup2(si.fileno(), 
sys.stdin.fileno())
Mar 22 15:29:33 nuc weewxd[810]:   File "/home/weewx/bin/weewx/engine.py", 
line 803, in sigTERMhandler
Mar 22 15:29:33 nuc weewxd[810]: raise Terminate
Mar 22 15:29:33 nuc weewxd[810]: weewx.engine.Terminate

It started fine manually:

root@nuc:~# service weewx restart
root@nuc:~# service weewx status
? weewx.service - weewx weather system
   Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2017-03-22 15:31:08 EDT; 3s ago
 Main PID: 2519 (weewxd)
   CGroup: /system.slice/weewx.service
   mq2519 /usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

There must be some conflict between in the systemctl startup process. I 
moved the "weewx.service" (no modifications) according to directions in 
startup.
I'm now wise enough in the ways of linux to figure this one out.

Thanks for the quick reply.

Bob
++
On Wednesday, March 22, 2017 at 11:55:30 AM UTC-4, Andrew Milner wrote:
>
> what does the weewx log say??  is weewx waiting for the time to be set 
> correctly, or a network to be available perhaps??  The key should lie in 
> the weewx log (or/and system startup log - syslog)
>
>
>
> On Wednesday, 22 March 2017 16:44:50 UTC+2, bgra...@umw.edu wrote:
>
>> Hello,
>>
>> I've about finished moving weewx to a new computer and from debian to 
>> Ubuntu. Everything seems to be working correctly except the auto restart 
>> after reboot. I can stop/start/restart from the service or init.d commands 
>> and all works correctly. There is something incorrect with my configuration 
>> for startup. Here are some log messages:
>>
>> *After computer reboot weewx fails to start:*
>> root@nuc:~# service weewx status
>> ? weewx.service - weewx weather system
>>Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor 
>> preset: enabled)
>>Active: inactive (dead)
>> +++
>> *Manual restart of weewx service:*
>> root@nuc:~# service weewx restart
>> root@nuc:~# service weewx status
>> ? weewx.service - weewx weather system
>>Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor 
>> preset: enabled)
>>Active: active (running) since Wed 2017-03-22 10:11:05 EDT; 7s ago
>>  Main PID: 2398 (weewxd)
>>CGroup: /system.slice/weewx.service
>>mq2398 /usr/bin/python /home/weewx/bin/weewxd --daemon 
>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf
>> +++
>> *Manual stop/start from init.d:*
>> root@nuc:/etc/init.d# ./weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> root@nuc:/etc/init.d# ./weewx start
>> [ ok ] Starting weewx (via systemctl): weewx.service.
>> root@nuc:/etc/init.d# ./weewx status
>> ? weewx.service - weewx weather system
>>Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor 
>> preset: enabled)
>>Active: active (running) since Wed 2017-03-22 10:13:08 EDT; 13s ago
>>  Main PID: 2491 (weewxd)
>>CGroup: /system.slice/weewx.service
>>mq2491 /usr/bin/python /home/weewx/bin/weewxd --daemon 
>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf
>>
>> Any suggestions will be appreciated.  Thanks in advance.
>>
>> Bob
>>
>>
>>
>>

-- 
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 doesn't start automatically after reboot

[bgrattan]

Hello,

I've about finished moving weewx to a new computer and from debian to 
Ubuntu. Everything seems to be working correctly except the auto restart 
after reboot. I can stop/start/restart from the service or init.d commands 
and all works correctly. There is something incorrect with my configuration 
for startup. Here are some log messages:

*After computer reboot weewx fails to start:*
root@nuc:~# service weewx status
? weewx.service - weewx weather system
   Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor 
preset: enabled)
   Active: inactive (dead)
+++
*Manual restart of weewx service:*
root@nuc:~# service weewx restart
root@nuc:~# service weewx status
? weewx.service - weewx weather system
   Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2017-03-22 10:11:05 EDT; 7s ago
 Main PID: 2398 (weewxd)
   CGroup: /system.slice/weewx.service
   mq2398 /usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf
+++
*Manual stop/start from init.d:*
root@nuc:/etc/init.d# ./weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
root@nuc:/etc/init.d# ./weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
root@nuc:/etc/init.d# ./weewx status
? weewx.service - weewx weather system
   Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2017-03-22 10:13:08 EDT; 13s ago
 Main PID: 2491 (weewxd)
   CGroup: /system.slice/weewx.service
   mq2491 /usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

Any suggestions will be appreciated.  Thanks in advance.

Bob



-- 
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] use weewx db in wview

[bgrattan]

The db move from weewx to wview worked fine, no problems. I used sqlite3 .dump 
rather than just copy as I was going from 64-bit to 32. Done just in time as my 
weewx server crashed an hour later...  thanks again

Bob

-- 
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] use weewx db in wview

[bgrattan]

Thanks, Tom, I'll let you know. May wait a while until this storm is gone for 
good.
Bob

-- 
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] use weewx db in wview

[bgrattan]

Hello,

I used wview with good luck for about seven years and moved to weewx a 
couple of years ago [Much appreciated to Tom, Matt and all those who do 
excellent work and support]. I have kept an instance of wview running in 
the background because it was always running well. Not being much of a 
programmer, I feel that weewx is easier to configure and keep up for what I 
need.

A disk crash the other day caused me to completely reinstall weewx 
(setup.py) which is now running 3.7.0 very well.  I would like to also 
reinstall wview but need some db records (sqlite3) from weewx to bring 
wview up to date.

To get to my question, can I dump/read the weewx db back into wview? It 
seemed to be easy in the other direction.

My station is a VP2+ on Debian jessie: grattans.org/wx

Thanks in advance.

Bob

-- 
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: Selection of USB/RS232 device to RPI. To control WMR 928

[bgrattan]

An rs232 -> usb which uses an FTDI chip works the best as it usually contains a 
serial number which is useful in setting up a udev rule. Mwall has posted a 
good guide to creating a rule for this purpose. I had been using a converter 
with pl2303 chip but started having problems with it switching ttyUSB on me.
Bob

-- 
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: NWS Alerts

[bgrattan]

Ok, I think I understand now... The warnings.html file should have been in 
/home/weewx/public_html where the templates have created the files to be 
displayed. I got it to appear in index.html (although in the wrong place 
for now). Need to work on the placement.

Many thanks and much appreciated for getting me straight.

Bob

>


-- 
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: NWS Alerts

[bgrattan]

Monachus,

Thanks for the reply. I have tried adding your line below in several places 
but nothing shows up on the skin. warnings.html is in 
/home/weewx/skins/Standard as well as index.html.tmpl. When I view the 
created page source, the line appears but it does not display the contents 
of warnings.html.  The file contents look like this:

Current Watches, Warnings and Advisories for Western Hanover (VAZ511) 
Virginia Issued by the National Weather Service
There are no active watches, warnings or advisories

Permissions on warnings.html are fully open.

I must be missing some other element but my html knowledge is very low and 
I don't know what to look for.  Thanks for any suggestions.

Bob

On Wednesday, December 7, 2016 at 1:36:00 PM UTC-5, Monachus wrote:

> Just add the line below to your template somewhere.  The template would 
> normally be here: /etc/weewx/skins/Standard/index.html.tmpl
>
>  data="warnings.html">
>
> You can customize the height and width and where you put it.
>
>
> On Wednesday, December 7, 2016 at 12:23:13 PM UTC-6, bgra...@umw.edu 
> wrote:
>>
>> Hi Monachus,
>>
>> Could you give me some help adding your script to the Standard skin?  I 
>> have got the curl setup which creates the file 
>> /home/weewx/skins/Standard/warnings.html but don't know what I'm doing when 
>> it comes to adding the alert file text to my main page. I prefer adding the 
>> alert info and not the dark sky graphic forecast. Thanks in advance.
>>
>> Bob
>>
>> http://grattans.org/wx
>>
>>

-- 
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: NWS Alerts

[bgrattan]

Hi Monachus,

Could you give me some help adding your script to the Standard skin?  I have 
got the curl setup which creates the file 
/home/weewx/skins/Standard/warnings.html but don't know what I'm doing when it 
comes to adding the alert file text to my main page. I prefer adding the alert 
info and not the dark sky graphic forecast. Thanks in advance.

Bob

http://grattans.org/wx

-- 
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] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

rv weewx[2347]: restx: StationRegistry: Station will be 
registered.
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service 
weewx.restx.StdWunderground
Nov 17 11:37:51 n4mrv weewx[2347]: restx: Wunderground-PWS: Data for station 
KVAASHLA4 will be posted
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.restx.StdWunderground
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service 
weewx.restx.StdPWSweather
Nov 17 11:37:51 n4mrv weewx[2347]: restx: PWSWeather: Data for station N4MRV 
will be posted
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.restx.StdPWSweather
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service weewx.restx.StdCWOP
Nov 17 11:37:51 n4mrv weewx[2347]: restx: CWOP: Data for station N4MRV-1 will 
be posted
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.restx.StdCWOP
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service weewx.restx.StdWOW
Nov 17 11:37:51 n4mrv weewx[2347]: restx: WOW: Data for station 964806001 will 
be posted
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.restx.StdWOW
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service weewx.restx.StdAWEKAS
Nov 17 11:37:51 n4mrv weewx[2347]: restx: AWEKAS: Data will be uploaded for 
user bgrattan
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.restx.StdAWEKAS
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service weewx.engine.StdPrint
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.engine.StdPrint
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Loading service 
weewx.engine.StdReport
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Finished loading service 
weewx.engine.StdReport
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Starting up weewx version 3.6.2
Nov 17 11:37:51 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Clock error is -0.90 seconds 
(positive is fast)
Nov 17 11:37:51 n4mrv weewx[2347]: vantage: Getting archive packets since 
2016-11-17 11:30:00 EST (1479400200)
Nov 17 11:37:51 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:37:51 n4mrv weewx[2347]: vantage: Retrieving 0 page(s); starting 
index= 0
Nov 17 11:37:51 n4mrv weewx[2347]: engine: Starting main packet loop.
Nov 17 11:37:52 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:37:52 n4mrv weewx[2347]: vantage: Requesting 200 LOOP packets.
Nov 17 11:37:52 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:38:00 n4mrv weewx[2347]: vantage: LOOP try #1; error: Expected to 
read 99 chars; got 0 instead
Nov 17 11:38:00 n4mrv weewx[2347]: vantage: Requesting 200 LOOP packets.
Nov 17 11:38:00 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:38:10 n4mrv weewx[2347]: vantage: LOOP try #2; error: Expected to 
read 99 chars; got 0 instead
Nov 17 11:38:10 n4mrv weewx[2347]: vantage: Requesting 200 LOOP packets.
Nov 17 11:38:10 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:38:20 n4mrv weewx[2347]: vantage: LOOP try #3; error: Expected to 
read 99 chars; got 0 instead
Nov 17 11:38:20 n4mrv weewx[2347]: vantage: Requesting 200 LOOP packets.
Nov 17 11:38:20 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:38:30 n4mrv weewx[2347]: vantage: LOOP try #4; error: Expected to 
read 99 chars; got 0 instead
Nov 17 11:38:30 n4mrv weewx[2347]: vantage: LOOP max tries (4) exceeded.
Nov 17 11:38:30 n4mrv weewx[2347]: engine: Main loop exiting. Shutting engine 
down.
Nov 17 11:38:30 n4mrv weewx[2347]: restx: Shut down AWEKAS thread.
Nov 17 11:38:30 n4mrv weewx[2347]: restx: Shut down WOW thread.
Nov 17 11:38:30 n4mrv weewx[2347]: restx: Shut down CWOP thread.
Nov 17 11:38:30 n4mrv weewx[2347]: restx: Shut down PWSWeather thread.
Nov 17 11:38:30 n4mrv weewx[2347]: restx: Shut down Wunderground-PWS thread.
Nov 17 11:38:30 n4mrv weewx[2347]: restx: Shut down StationRegistry thread.
Nov 17 11:38:30 n4mrv weewx[2347]: engine: Caught WeeWxIOError: Max tries 
exceeded while getting LOOP data.
Nov 17 11:38:30 n4mrv weewx[2347]:   Waiting 60 seconds then retrying...
Nov 17 11:39:30 n4mrv weewx[2347]: engine: retrying...
Nov 17 11:39:30 n4mrv weewx[2347]: engine: Using configuration file 
/home/weewx/weewx.conf
Nov 17 11:39:30 n4mrv weewx[2347]: engine: Initializing engine
Nov 17 11:39:30 n4mrv weewx[2347]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Nov 17 11:39:30 n4mrv weewx[2347]: vantage: driver version is 3.0.9
Nov 17 11:39:30 n4mrv weewx[2347]: vantage: Opened up serial port /dev/ttyUSB0; 
baud 19200; timeout 5.00
Nov 17 11:39:30 n4mrv weewx[2347]: vantage: gentle wake up of console successful
Nov 17 11:39:30 n4mrv weewx[2347]: vantage: _setup; hardware type is 16
Nov 17 11:39:30 n4mr

Re: [weewx-user] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

Tom,

I'm using the Davis streaming data logger (6450) with serial output to a 
serial-->usb converter (PL2303) on ttyUSB0. This worked well with wview for 
about seven years until I moved to weewx almost two years ago. With weewx I saw 
the loop problem and found the solution suggested by someone on the web who was 
feeding weewx data to a ham radio setup with APRS. Davis makes another logger 
(non streaming, I think) which may not have this problem.
I'll run the debug log for you sometime this weekend. Thanks.

Bob

-- 
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] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

SOLVED!

Thanks for the quick reply, Tom. My own stupid mistake. In rechecking 
everything, I found that my edit of vantage.py didn't take. Once the 200 
was actually changed to 2 then all worked well.
Much appreciated for the great software and all who contribute!

Bob

http://grattans.org/wx


-- 
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] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

Hello,

After running 3.5.0 with no problems (VP2+{serial} on Debian Jessie), I am 
getting the following loop error:

root@n4mrv:/home/weewx# service weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (running) since Wed 2016-11-16 11:54:58 EST; 3min 12s ago
  Process: 4553 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 4611 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─4624 /usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

Nov 16 11:56:38 n4mrv weewx[4624]: engine: Starting up weewx version 3.6.2
Nov 16 11:56:38 n4mrv weewx[4624]: engine: Clock error is -0.62 seconds 
(positive is fast)
Nov 16 11:56:38 n4mrv weewx[4624]: engine: Starting main packet loop.
Nov 16 11:56:48 n4mrv weewx[4624]: vantage: LOOP try #1; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:56:58 n4mrv weewx[4624]: vantage: LOOP try #2; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:57:08 n4mrv weewx[4624]: vantage: LOOP try #3; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:57:18 n4mrv weewx[4624]: vantage: LOOP try #4; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:57:18 n4mrv weewx[4624]: vantage: LOOP max tries (4) exceeded.
Nov 16 11:57:18 n4mrv weewx[4624]: engine: Caught WeeWxIOError: Max tries 
exceeded while getting LOOP data.
Nov 16 11:57:18 n4mrv weewx[4624]:   Waiting 60 seconds then retrying...

I remember having this before and adjusting "for_loopPacket in 
self.genDavisLoopPackets(200)" from 200 to 2. I can't find this again 
except in vantage.py and it doesn't seem to help. All hardware is exactly 
the same and was working fine with 3.5.0.

Can anyone help with this? I'm down until I can fix it.  Thanks in advance.

Bob

-- 
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: Current ET data not showing on main index page

[bgrattan]

Thanks, Tom, I see now that my rain is showing in place of ET. I'll correct it. 
Bob

-- 
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: Current ET data not showing on main index page

[bgrattan]

OK, now I have some data in the table display but nothing in the graph.  
Here is how I setup the graph in the skin and index:

[[[dayET]]]
# Make sure the y-axis increment is at least 0.02 for the ET 
plot
yscale = None, None, 0.02
plot_type = bar

rain
aggregate_type = sum
aggregate_interval = 3600
label = ET (hourly total)
--

 #if $day.ET.has_data
  
  #end if










>

-- 
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] Current ET data not showing on main index page

[bgrattan]

Hello,

One of my weather page fans has requested that I chart ET data and I have 
attempted to add this to the main page of the Standard skin. The blank 
chart is there with no data and there is no data (0.0) in my ET table data. 
I checked the db in the archive and there is some data displayed in the ET 
column--not every 15 minutes (interval) but once or twice an hour. My ET 
since midnight does show the high. I think I'm missing a step here 
somewhere but I'm not sure where. My wview is still running on the same 
computer and it seems to be showing ET data.

I am running Jessie debian with the latest weewx in /home/weewx. Station is 
a VP2+

Thanks in advance for any suggestions.

Bob
http://grattans.org/wx (weewx)
http://grattans.org/wx.bak (wview)

-- 
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.