Re: [weewx-user] Re: Change archive interval for single report

[gjr80]

Installing both has complicated matters a little; you now have two 
instances of gauge-data.txt being generated, one by the SteelSeries Gauges 
skin and one by the Realtime gauge-data.txt extension. The upshot of this 
is you/we need to pay careful attention to paths or you will get the two 
confused and we will end up chasing our tail. No matter lets work through 
each and see what is going on. Firstly, in terms of the syslog extract, I 
am going to ignore everything before Feb 14 16:47:06, there is just so many 
loop packet errors, config errors and ftpupload errors that make it 
impossible to decipher. I trust Feb 14 16:47:06 was the last time you 
stopped/started weeWX after installing both the skin and the extension.

Let's look at the SteelSeries Gauges skin (aka 'the skin'). If installed 
correctly it should have created a directory /home/weewx/public_html/ss on 
your weeWX machine and it should have written a number of files to that 
directory, one should be gauge-data.txt and it should be being updated 
every 1 minute given that your archive interval is 1 minute. Is 
/home/weewx/public_html/ss/gauge-data.txt being updated every minute? If so 
that suggests the skin is working correctly. Related to the skin but not 
part of it is the FTP report that is uploading files to your web 
server/host via FTP. If the /home/weewx/public_html/ss directory exists and 
gauge-data.txt is in this directory then the directory and gauge-data.txt 
should be being uploaded to you web host every 1 minute. Right now (12:08am 
15 February your time) I can see your site 
 and it appears to be 
updating fine. If I goto your SteelSeries Gauges page 
 I can see your 
gauges but they are not displaying any data (no matter, will fix that 
later). This tells me the ss directory has been created on your web server. 
I should be able to view the gauge-data.txt that was generated by the skin 
at http://www.ajburnettonline.com/weather/ss/gauge-data.txt but when I look 
at this file it is dated 23:47 13 February 2018, so either gauge-data.txt 
is not being uploaded by FTP or it is not being generated by the skin.

When I look at your log extract throughout it I see various FTP errors, 
mostly timeouts but a number of permission errors as well. I don't know 
whether this is the cause, you appear to have had successful FTP uploads 
since 23:47 13 February 2018.

I said we would come back to the SteelSeries Gauges not displaying data. In 
ss/scripts/gauges.js there is a setting realTimeUrlWeewx (normally line 74) 
that tells the SteelSeries Gauges where on your web server (not necessarily 
weeWX server) to find gauge-data.txt. You presently have it set to 
/home/weewx/public_html/gauge-data.txt which is the location on your weeWX 
server and almost certainly not the location on you web server. Using 
relative paths is usually best, in this case the path is relative to the 
ss/index.html so just setting it to 'gauge-data.txt' should work. Now to 
make the change don't edit ss/gauges.js on your web server, it will be 
overwritten next time you start weeWX, but rather make the change on your 
weeWX server in the skins directory. Edit 
/home/weewx/skins/ss/scripts/gauges.js and make the change. Save the file 
then stop then start weeWX. The next FTP upload should see the updated 
gauges.js copied to your web server (monitor you log file to see that the 
FTP upload worked).

Now the Realtime gauge-data extension. There are no errors in the log so I 
would assume the extension is producing gauge-data.txt, to confirm have a 
look in the /home/weewx/public_html directory. Is there a gauge-data.txt 
there and is it being updated every loop period (should be roughly every 
2.5 seconds for a Vantage station). If it is there and being updated have a 
look at the contents, does it appear correct (it will be somewhat cryptic 
but you should be able to make sense of it). If the file is not there we 
will need to have a look at a debug log to see what is going on. To get a 
debug log edit weewx.conf, set debug = 2, save weewx.conf then stop then 
start weeWX. Let weeWX run for a few minutes then take a log extract from 
when you just started weeWX until the few minutes were up and post the log 
extract. That should tell us what is or is not going on. Once we know that 
part of the extension is working we will worry about getting the data to 
your web server.

Gary

On Thursday, 15 February 2018 08:09:24 UTC+10, A.J. Burnett wrote:
>
> OK...I've installed both the SteelGauge skin and the Realtime gauge-data 
> extension, but now, my "gauge-data.txt" file is not being updated. I'm 
> attaching my weewx.conf, log, and gauges.js files...maybe you'll spot 
> something I missed?
>
>
>
>

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

[weewx-user] Re: fixing rain totals only for a specified period

[gjr80]

Vince,

My thoughts below.

Gary

On Thursday, 15 February 2018 06:05:58 UTC+10, vince wrote:
>
> My VP2 has recently been in a state where it was missing most rain tips 
> due to the mounting bracket getting out of level due to mounting pole 
> issues I've recently fixed.  Today's first rain in a week verifies the 
> Davis is ok, it's tipping again and matching my CoCoRaHS manual gauge 
> exactly again.   So I'd like to update things so my daily totals of rain 
> for the last 90 days or so match my daily manual readings.
>
> I know one option is edit and do a full --drop-daily, but I'd like to 
> avoid a full rebuild as I have well over 1,000,000 archive records here.   
> But I see the nice --rebuild-daily option makes that perhaps unnecessary 
> now.  Cool.
>

Yep, one of the things I would cringe at when forced to do a rebuild/(nee 
backfill) was the loss of all that loop data granularity. When wee_database 
got a touch up under v3.7.0 we were able to implement --to and --from to 
limit the the rebuild in time, but unfortunately limiting it to certain obs 
only was a bridge too far. FWIW I have come to live with the occassional 
loss of some granularity in the daily summaries.
 

>
> Couple questions:
>
>- For rebuilding the subset of dailies, I'm guessing it would be 
> "wee_database 
>--rebuild-daily --from=2017-10-01 --to=2018-02-14"
>
> Spot on. The --date option can also be used to rebuild a single date 
only. You will notice the Utilities Guide includes the sentence *'In most 
cases it is not necessary to drop the daily summaries tables using the 
action --drop-daily before rebuilding them*' under --rebuild-daily. I can't 
remember the exact circumstances (and I have seen a couple of cases where 
it was required, but I think they were cases where the daily summaries were 
somehow corrupted - not sure) that do require a --drop-daily before the 
rebuild. Obviously, if have to do a --drop-daily then you have lost all 
that granularity from loop data and you will have to rebuild the lot.

>
>- If I just edit one 'rain' element per day in the archive table and 
>leave 'rainRate' at 0.0 would that get me the updated daily totals 
>effect I'm looking for ?
>
> It should. Of course any aggregates based on a period less than 1 day will 
be nonsense for the period concerned  (eg hourly rainfall totals) but most 
folks don't use those sorts of aggregates, and if they do most use 'the 
last hour' or similar (ie here and now not months ago)

>
>- and I'm guessing I'd have to delete the NOAA files for the 
>months/years I mess with, and weewx will regenerate them as always, 
> correct 
>?
>
> Almost right, you will need to delete the lot and let weeWX regenerate 
them all. Normally, only the current month and year NOAA  format reports 
are regenerated each report cycle. For example, if you have reports from 
September 2017 to February 2018 and delete October 2017 through to February 
2018 then only February 2018 is regenerated. To force October 2017 to 
January 2018 to be regenerated you need to delete September 2017 as well. 
The only penalty paid in deleting them all is that first report cycle might 
take a while to complete.

Again, I'd like the NOAA files to show updated values matching reality as 
> measured by my manual gauge while the VP2 wasn't measuring correctly.   
> Bonus points if the rainYear totals as reported by weewx and (ideally) the 
> VP2 console catch up to reality too.
>

Well you can manually set the day, month and year rain totals on the 
console (VP2/VP2 Plus Console User Manual 
,
 
page 27). Once you have weeWX all fixed see what it reports for current 
day, month and year rainfall and then just edit the day, month and year 
totals on your console to be the same as weeWX. Now it matches :) 

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

[Craig Thom]

A few days later I'll also endorse the Raspberry Pi 3.  I've been running 
WeeWX on it for a year and haven't had any outages that weren't my own 
fault.

I should probably back up the micro SD card, since it's been in use for a 
year.

This thing has not stopped working.  No outages.  Uptime runs from whenever 
I do an apt-get update to the next time (I always reboot after doing an 
upgrade because that's one of the times weewx crapped out, when I updated 
some system stuff).

I have no experience with other systems.  

On Wednesday, January 24, 2018 at 2:38:36 PM UTC-5, 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] Modified schema for my sqlite database

[Tryphon Cosinus]

I used DB browser for SQlite under Ubuntu to copy the data into the new 
database.

I gave the new database to this command:

../bin/wee_database ../weewx.conf --rebuild-daily

and it failed during the process because this command :

../bin/wee_database --check-strings

told that the database has null strings in some records (12 null strings 
were found).

Hence, I used ../bin/wee_database --fix-strings to avoid the null strings.

With the repaired database, the command ../bin/wee_database ../weewx.conf 
--rebuild-daily is working fine.

Now I have a new and clean database with the new fields I wanted.

I don't know how I got these null strings, probably there in my old 
database running since 3 years.

Thank you for the brainstorming.

-- 
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 and icons

[vigilancewx]

cp -rp skins/forecast/icons skins/Standard

Then include the icons in the list of files that should be copied by the 
CopyGenerator. Append the icons directory to the copy_once parameter in the 
CopyGenerator configuration in skins/Standard/skin.conf:

[CopyGenerator]
copy_once = ..., icons/*.png


added the above and all is working



On Wednesday, February 14, 2018 at 10:49:02 PM UTC, vigilancewx wrote:
>
> Hi
>
>
> on a new 3.8 installation
>
>
> I have installed the forecast extension and it works fine in its default 
> installation folder
>
>
> I have changed my skin.conf to no generatre the single-strip.html file in 
> my public_html folder
>
>
> the file it is generating has all the temps etc also the colours and 
> correct fonts but no icons
>
>
> where do I create a link so the single-strip.html file has link to the 
> icons when it is generated into the public_html folder
>
>
> I did try to create a button with a link to the default forecast folder to 
> get around the problem but apache seems to prevent the link from opening
>
>
> the only folder apache will allow access to is my public_html hence the 
> reason I am trying to get the file generated
>
> in the public folder
>
>
> thanks for any advice
>
>
>

-- 
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 and icons

[vigilancewx]

I have found this on an older post

cp -rp skins/forecast/icons skins/Standard

i had already tried to copy the icons to an icons sub folder of Standard
 as that is where the icons  reside in an older version of weewx

i only use the cp command i will try with the above txt see what happens




On Wednesday, February 14, 2018 at 10:49:02 PM UTC, vigilancewx wrote:
>
> Hi
>
>
> on a new 3.8 installation
>
>
> I have installed the forecast extension and it works fine in its default 
> installation folder
>
>
> I have changed my skin.conf to no generatre the single-strip.html file in 
> my public_html folder
>
>
> the file it is generating has all the temps etc also the colours and 
> correct fonts but no icons
>
>
> where do I create a link so the single-strip.html file has link to the 
> icons when it is generated into the public_html folder
>
>
> I did try to create a button with a link to the default forecast folder to 
> get around the problem but apache seems to prevent the link from opening
>
>
> the only folder apache will allow access to is my public_html hence the 
> reason I am trying to get the file generated
>
> in the public folder
>
>
> thanks for any advice
>
>
>

-- 
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 and icons

[vigilancewx]

 

Hi


on a new 3.8 installation


I have installed the forecast extension and it works fine in its default 
installation folder


I have changed my skin.conf to no generatre the single-strip.html file in 
my public_html folder


the file it is generating has all the temps etc also the colours and 
correct fonts but no icons


where do I create a link so the single-strip.html file has link to the 
icons when it is generated into the public_html folder


I did try to create a button with a link to the default forecast folder to 
get around the problem but apache seems to prevent the link from opening


the only folder apache will allow access to is my public_html hence the 
reason I am trying to get the file generated

in the public folder


thanks for any advice


-- 
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] fixing rain totals only for a specified period

[vince]

My VP2 has recently been in a state where it was missing most rain tips due 
to the mounting bracket getting out of level due to mounting pole issues 
I've recently fixed.  Today's first rain in a week verifies the Davis is 
ok, it's tipping again and matching my CoCoRaHS manual gauge exactly again. 
  So I'd like to update things so my daily totals of rain for the last 90 
days or so match my daily manual readings.

I know one option is edit and do a full --drop-daily, but I'd like to avoid 
a full rebuild as I have well over 1,000,000 archive records here.   But I 
see the nice --rebuild-daily option makes that perhaps unnecessary now. 
 Cool.

Couple questions:

   - For rebuilding the subset of dailies, I'm guessing it would be 
"wee_database 
   --rebuild-daily --from=2017-10-01 --to=2018-02-14"
   - If I just edit one 'rain' element per day in the archive table and 
   leave 'rainRate' at 0.0 would that get me the updated daily totals 
   effect I'm looking for ?
   - and I'm guessing I'd have to delete the NOAA files for the 
   months/years I mess with, and weewx will regenerate them as always, correct 
   ?

Again, I'd like the NOAA files to show updated values matching reality as 
measured by my manual gauge while the VP2 wasn't measuring correctly.   
Bonus points if the rainYear totals as reported by weewx and (ideally) the 
VP2 console catch up to reality too.

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