[weewx-user] Re: Imperial/Metric rain data problem

[Brent Wesley]

Thanks

I found where it was going wrong in the skin.conf. The one place I didn't 
check.

On Thursday, 5 January 2017 15:27:14 UTC+10, Andrew Milner wrote:
>
> Are you saying that the database is showing the delta in the database as 
> imperial - or as metric (ie in cm)?
>
> Check that the units sections of weewx.conf and skin.conf are not changing 
> the units back to imperial
>
> You can also change the units by using the dot codes within a template eg $
> rain.day.sum.mm 
>
>
>
> On Thursday, 5 January 2017 07:01:30 UTC+2, Brent Wesley wrote:
>
>> Hi Everyone
>>
>> I have found I have an issue with the raid data coming back in to weewx. 
>> Looking at the data coming in from the interceptor driver I am using to 
>> ready from my OS LW300 system, the rain data is coming back as imperial 
>> figure which is converted to the correct rain delta in the driver (previous 
>> ready subtracted from the current). 
>>
>> I have my DB set up and metric so when displaying rain.day.sum it is 
>> showing an incorrect value.
>>
>> What is the easiest way to fix this. I am happy to drop the previous rain 
>> figures from the DB and not convert them.
>>
>> Thanks
>> Brent.
>>
>

-- 
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: Imperial/Metric rain data problem

[Andrew Milner]

Are you saying that the database is showing the delta in the database as 
imperial - or as metric (ie in cm)?

Check that the units sections of weewx.conf and skin.conf are not changing 
the units back to imperial

You can also change the units by using the dot codes within a template eg 
$rain.day.sum.mm 



On Thursday, 5 January 2017 07:01:30 UTC+2, Brent Wesley wrote:

> Hi Everyone
>
> I have found I have an issue with the raid data coming back in to weewx. 
> Looking at the data coming in from the interceptor driver I am using to 
> ready from my OS LW300 system, the rain data is coming back as imperial 
> figure which is converted to the correct rain delta in the driver (previous 
> ready subtracted from the current). 
>
> I have my DB set up and metric so when displaying rain.day.sum it is 
> showing an incorrect value.
>
> What is the easiest way to fix this. I am happy to drop the previous rain 
> figures from the DB and not convert them.
>
> Thanks
> Brent.
>

-- 
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] Imperial/Metric rain data problem

[Brent Wesley]

Hi Everyone

I have found I have an issue with the raid data coming back in to weewx. 
Looking at the data coming in from the interceptor driver I am using to 
ready from my OS LW300 system, the rain data is coming back as imperial 
figure which is converted to the correct rain delta in the driver (previous 
ready subtracted from the current). 

I have my DB set up and metric so when displaying rain.day.sum it is 
showing an incorrect value.

What is the easiest way to fix this. I am happy to drop the previous rain 
figures from the DB and not convert them.

Thanks
Brent.

-- 
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: Rain dailly total and NOAA rain total wrong value

[Andrew Milner]

If your database is metric then rain is in cm
If your database is metricwx then rain is mm

Your NOAA report is, according to the title line above the table, in mm - 
but the units are determined by the contents of the template and so can 
easily be changed to other units by changing the template appropriately.

http://weewx.com/docs/customizing.htm#units



On Thursday, 5 January 2017 00:19:57 UTC+2, lionel...@free.fr wrote:

> Hi,
>
> Le mercredi 4 janvier 2017 00:38:20 UTC+1, mwall a écrit :
>>
>> On Tuesday, January 3, 2017 at 5:47:04 PM UTC-5, lionel.sylvie wrote:
>>
>> This is the same corrections in the weewx.conf between versions.
>>> Where I can find the commits?
>>>
>>
>> the change to rain multiplier happened on 11 jun 2015:
>>
>>
>> https://github.com/weewx/weewx/commit/0bb7db1edc806caebe68357bc315ccf8674eea52
>>
>> so it has been part of the ws23xx driver for some time now.
>>
>> the divide-by-ten happens only to data from the logger, so if you are 
>> using record_generation=hardware you will definitely see a difference, but 
>> if you are using record_generation=software you will see a difference only 
>> when weewx has to do catchup.
>>
>>  I compare all the versions of the WS23xx I used since 2.7, all are 
> similar concerning the formula. The x10 in the commit above concern the 
> wind speed which is included after the 2.7 version.
>
> To come back to my original question, it's concern not the generated data 
> but the values shown in the NOAA files.
> In the file attached in this post NOAA of November, when we take the rain 
> value for the 24 November 2016, this is 24.9mm. When we take the value in 
> the database (weewx.sdb) for the same date ("1479942000" : Sat Nov 24 2016 
> 00:00:00 GMT+0100), the value is 2.486. Is it the same units?
> From a report of an official station close to mine (4-5kms), the cumul was 
> 11.2mm.
>
> http://www.infoclimat.fr/observations-meteo/archives/24/novembre/2016/saint-martin-d-heres/00014.html
>
> When I do the sum of the rain falls during this same day (data taken in 
> the archive table of weewx.sdb), I get 1.243 which is the half value form 
> the archive_day_rain. Is it normal ?
> When I sum all the rain data for November 2016 coming from the archive (= 
> 8.029) and compare to the sum of the archive_day_rain for November 
> (=16.058) and the NOAA of November (=160.6mm), I get a double value for the 
> archive_day_rain and NOAA. Is there any issue during the calculation of the 
> archive  ?
>
> rds
> Lio
> PS : After these all analysis, the archive_day_rain is in cm and the NOAA 
> is in mm. True? then I get the explanation for the x10 between values of 
> archive_day_rain and NOAA.
>
>

-- 
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 do I edit the weewx.conf file?

[Dr__Bob]

I'm not sure what exactly your question is.  If you are trying to figure 
out how to edit the file, then you need to use an editor.  "nano" is a good 
straight-forward choice:

 nano /etc/weewx/weewx.conf

However, /etc is typically a protected directory and you have to a) either 
be logged in as root (*never* a good idea!) or b) better use "sudo":

 sudo nano /etc/weewx/weewx.conf

(sudo lets you become the "superuser" (aka root) and "do" something.)

Once you've edited the file, you'll have to stop and restart weewx, of 
course.

On Wednesday, January 4, 2017 at 6:41:49 PM UTC-8, Steve Dulmes wrote:
>
> Hi, I'm new to weewx and to Python. I have an Acurite 5in1 connected to a 
> Raspberry Pi3 with USB. I have weewx installed and running and it is 
> working well. 
> I would like get it reporting to Weather Underground but I do not know how 
> to edit the config file to put my weather station info in the appropriate 
> section and save it. 
> I've tried using the open command, but it continues to say I've made a 
> syntax error. 
> Examples of my failed tries:
> open (/etc/weewx/weewx.conf)
> open('/etc/weewx/weewx.conf')
> open(/etc/weewx/weewx.conf, w) ...to write and save a new copy of the file?
> cd etc/weewx ...this worked to change the directory, but then all my tries 
> to get to the weewx.conf failed
> Probably pretty simple, but I can't figure it out.
> Any help would be appreciated.
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] exfoliation skin and interactions with the forecast skin

[Dr__Bob]

Hi All,

I'm a new weewx user and I've been playing with the exfoliation skin by 
mwall. I've brought the items below to mwall's attention over on the 
wxforum, but it probably doesn't hurt to give them more exposure on this 
list. Maybe someone else has seen them before or has some additional ideas..

1) I had to comment out the following bit of code in index.html.tmpl as it 
wasn't working.  I got the string "$day.maxSolarRad.max.format('%.0f')
?'maxSolarRad'?" on my page.

##if $varExists('day.maxSolarRad')
##  $day.maxSolarRad.max.format('%.0f')
##  $current.maxSolarRad.format('%.0f')
##end if
 
2) I had to modify forecast_strip.inc in the forecast skin to get it to 
work with another skin (ss, the Stainless Steel gauges).  Maybe I did 
something not quite correct, but I just included in the ss/index.html.tmpl 
the following in the :

  
  

and then put the following where I wanted the forecast strip:

#set global $forecast_strip_settings = dict()
#set global $forecast_strip_settings['source'] = 'NWS'
#include "../forecast/forecast_strip.inc"

That works, except for the icons.  To get the icons to work, I had to 
change every occurrence of "icons/" in  forecast_strip.inc to be 
"../forecast/icons/".  That then worked.  I don't think that html allows 
for multiple search paths for images.  (Yeah, I know enough html to do 
serious damage to any web page that I come in contact with.  I'm slowly 
picking up some css.  What can I say; I grew up on Fortran and you know 
about old dogs and new tricks...)  Anyway, if you are in the forecast 
directory, "../forecast/icons/" works just as well as "icons/".  However, 
it doesn't work if the relative directory structure changes, I'm guessing.

3) To get the forecasts to work in the exfoliation skin I had to add  
search_list_extensions = user.forecast.ForecastVariables 
to [CheetahGenerator] in the exfoliation skin.conf.  I knew to do that 
after reading the forecast wiki and getting it to work in the ss skin but I 
was kind of surprised, since forecasts were included all over the place in 
the exfoliation skin.  Maybe just a gentle reminder somewhere in the 
exfoliation skin.conf would be useful?  Would adding the following in 
weewx.conf

[StdReport]
  [[CheetahGenerator]]
 search_list_extensions = user.forecast.ForecastVariables 

work to get the variables available in all reports?

-- 
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 won't start with daemon and by itself on 1st try

[vince]

On Wednesday, January 4, 2017 at 3:39:35 PM UTC-8, Jerry Deibel wrote:
>
> Mwall,
>
> Here is the log after a shutdown and start.I started the log as soon 
> as it booted,  but how does that tell up anything.
>
> pi@raspberrypi:~ $ tail -f /var/log/syslog
>
>>
>>
try "tail -n 300 -f /var/log/syslog" to go back 300 lines

"tail -f" just shows you the lines from now forward, not stuff that 
happened before you typed the command 

-- 
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 won't start with daemon and by itself on 1st try

[Jerry Deibel]

Mwall,

Here is the log after a shutdown and start.I started the log as soon as 
it booted,  but how does that tell up anything.

pi@raspberrypi:~ $ tail -f /var/log/syslog
Jan  4 18:33:31 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[655]: 
index_parse.c:191: indx_parse(): error opening 
/media/pi/rootfs/BDMV/index.bdmv
Jan  4 18:33:31 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[655]: 
index_parse.c:191: indx_parse(): error opening 
/media/pi/rootfs/BDMV/BACKUP/index.bdmv
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 0.debian.pool.ntp.org -> 
104.156.99.226
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 1.debian.pool.ntp.org -> 
138.68.2.126
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 2.debian.pool.ntp.org -> 
199.223.248.99
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 3.debian.pool.ntp.org -> 
108.59.2.24
Jan  4 18:33:36 raspberrypi dhcpcd[412]: eth0: no IPv6 Routers available
Jan  4 18:33:54 raspberrypi systemd[1]: Time has been changed
Jan  4 18:33:54 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Wed Jan  4 18:34:24 2017 [try http://www.rsyslog.com/e/2007 ]

jerry


>
>
>

-- 
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: Acurite 01536 (Costco)

[Marcus Watkins]

I'm using a raspberry pi 2. I did hack together a USB cable power combo and
power the unit from that. Why they don't take power over USB out of the box
is beyond me...

On Jan 4, 2017 11:23 AM, "Brian Champion-Wescott" 
wrote:

> Marcus,
>
> What hardware are you using for your AcuRite 01536?  I have tried using a
> few different Linux distros on regular laptops, without any luck.  Are you
> using a Raspberry Pi?
>
> Thanks,
> Brian
>
> On Sunday, December 25, 2016 at 2:17:58 PM UTC-5, Marcus Watkins wrote:
>>
>> For Christmas today I received an Acurite 01536 5-in-1 weather station
>> with USB connection (from Costco). I set it up with weewx and was excited
>> to see it works out of the box for the most part.
>>
>> One difference from the docs is there's no 'USB Mode' switch on this
>> base, so I'm interested to see if the log fills up over time.
>>
>> The only real 'issue' is the barometer reads outside the values allowed
>> by weewx by default. I'm also seeing values vary by quite a bit, but it's
>> super windy out right now. I added an adjustment to match the display,
>> we'll see how it lines up over time.
>>
>> Does anyone know if the display reports barometer or pressure?
>>
>> All in all, seems to be working great.
>>
>> -Marcus
>>
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/_uOEWSOPBQk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

mwall,

I tried the weewx unit file and I can start it using

sudo systemctl start weewx

and that works  and I can stop it using...

sudo systemctl stop weewx

But weewx still will not start on a reboot.

I did the 
sudo systemctl enable weewx

Jerry




On Wed, Jan 4, 2017 at 2:34 PM, mwall  wrote:

> jerry,
>
> you might try using a pure systemd configuration instead of using an rc
> script.  the weewx rc script *should* work with systemd, but lately there
> have been postings to this forum that indicate that might be changing.
>
> get rid of the rc script:
>
> sudo /etc/init.d/weewx stop
> sudo update-rc.d weewx remove
> sudo rm /etc/init.d/weewx
>
> install the weewx unit file:
>
> https://github.com/weewx/weewx/wiki/systemd
>
> data are stored in the 'archive' table, which is in the file weewx.sdb if
> you are using sqlite.  the other tables in that database are for daily
> aggregates.
>
> you can use the .schema command to see all of the tables and their
> schemas.
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/4tqBDJjpKuc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: importing data from Weather Display log files

[gjr80]

Ok, two options. Option 1, copy wdConvert.py to /user/share/weewx, cd to 
/user/share/weewx then try the command you were using, ie

sudo cp ./wdConvert.py /usr/share/weewx
cd /usr/share/weewx
sudo python ./wdConvert.py

Option 2, try the following command:

sudo PYTHONPATH=/usr/share/weewx python ./wdConvert.py

assuming you are still in the same directory as where wdConvert.py is located.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: importing data from Weather Display log files

[Niklas Berglund]

Yeah, Im sure its like you say, a PYTHONPATH issue.  I don't know where to 
point the python path to where he'll find the module to include.. 

Im running a simple :  "sudo python ./wdConvert.py" command. No arguments 
added.  What sort of capture do you need me to post?

I've installed WeeWX using the DEB install. 

Thanks for taking the time with a noob :-)

Niklas



Den onsdag 4 januari 2017 kl. 20:50:00 UTC+1 skrev gjr80:
>
> Hi,
>
> Sounds like a PYTHONPATH issue. I had a quick look at the repo and did not 
> see any guidance on what should be included on the command line. Exactly 
> what command are you using to run the script? Try running it again but this 
> time capture the command you used and all the output. Post this capture. 
> Also, what type of install? setup.py, deb ?
>
> As for your first question, does this script still work, bear in mind this 
> script is from circa May 2013 when weewx v2.4.0 was the current version. 
> There has been a lot of water under the bridge since then (lots of 
> significant changes introduced in weewx v3.0.0) but since this script only 
> produces a csv file for later import you might be lucky - the amount of 
> interaction with weewx in the script appears minimal.
>
> Gary
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: importing data from Weather Display log files

[gjr80]

Hi,

Sounds like a PYTHONPATH issue. I had a quick look at the repo and did not see 
any guidance on what should be included on the command line. Exactly what 
command are you using to run the script? Try running it again but this time 
capture the command you used and all the output. Post this capture. Also, what 
type of install? setup.py, deb ?

As for your first question, does this script still work, bear in mind this 
script is from circa May 2013 when weewx v2.4.0 was the current version. There 
has been a lot of water under the bridge since then (lots of significant 
changes introduced in weewx v3.0.0) but since this script only produces a csv 
file for later import you might be lucky - the amount of interaction with weewx 
in the script appears minimal.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[mwall]

jerry,

you might try using a pure systemd configuration instead of using an rc 
script.  the weewx rc script *should* work with systemd, but lately there 
have been postings to this forum that indicate that might be changing.

get rid of the rc script:

sudo /etc/init.d/weewx stop
sudo update-rc.d weewx remove
sudo rm /etc/init.d/weewx

install the weewx unit file:

https://github.com/weewx/weewx/wiki/systemd

data are stored in the 'archive' table, which is in the file weewx.sdb if 
you are using sqlite.  the other tables in that database are for daily 
aggregates.

you can use the .schema command to see all of the tables and their schemas.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Andrew Milner]

1. Install phpliteadmin to view/amend SQLite databases

2. check user guide for how to remove 'spikes' for your incorrect rain 
reading

3. if you installed via setup.py the daemon is located at sudo 
/etc/init.d/weewx start or sudo /etc/init.d/weewx stop etc etc etc





On Wednesday, 4 January 2017 20:41:46 UTC+2, Jerry Deibel wrote:

> Hi,
> I have been running weewx with my ambient 1400 Observer for about 2 years. 
> Last year I moved the OP system to a USB stick to save wear and tear on the 
> SD card and  last week the USB had a sector error and would not load.  So 
> much for moving over from a SD card to a USB stick.
>
> I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
> so to make sure everything was ok.  I backup my archive every day so I 
> restored the archive database for the last year as well.   
> The last 2 years I ran a daemon process to run it on power up , so today I 
> did that..
>
> Now my problem is . 
> After doing the following to run it on power up
> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
> sudo chmod +x /etc/init.d/weewx
> sudo update-rc.d weewx defaults 98
>
> I then tried to startsudo /etc/init.d/weewx start : no log 
> outpur and ps aux shows not running
> It DID  not start
> I then stopped it..  sudo /etc/init.d/weewx  stop
> I then started it again.   sudo /etc/init.d/weewx start
> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx   
>  ... shows it running ok.
>
> Also, it does not start on  a power up.  
>
> Here is the log right after power up ..
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/index.bdmv
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org 
> -> 45.79.1.70
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org 
> -> 195.21.137.209
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org 
> -> 104.131.53.252
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org 
> -> 138.68.2.126
> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather 
> system...
> Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system: 
> weewx not running
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx 
> version 3.6.2
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Platform 
> Linux-4.4.34-v7+-armv7l-with-debian-8.0
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: pid file is 
> /var/run/weewx.pid
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Using configuration file 
> /home/weewx/weewx.conf
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Loading station type 
> ObserverIP (user.observerip)
> Jan  4 13:31:09 raspberrypi weewx[1616]: Starting weewx weather system: 
> weewx.
> Jan  4 13:31:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi weewx[1631]: observerip: version is 0.5mw
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: Unknown firmware 
> version: ��
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: polling interval is 
> 16.0
> Jan  4 13:31:10 raspberrypi weewx[1631]: engine: StdConvert target unit is 
> 0x1
> Jan  4 13:31:10 raspberrypi weewx[1631]: wxcalculate: The following values 
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> 

[weewx-user] Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

Hi,
I have been running weewx with my ambient 1400 Observer for about 2 years. 
Last year I moved the OP system to a USB stick to save wear and tear on the 
SD card and  last week the USB had a sector error and would not load.  So 
much for moving over from a SD card to a USB stick.

I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
so to make sure everything was ok.  I backup my archive every day so I 
restored the archive database for the last year as well.   
The last 2 years I ran a daemon process to run it on power up , so today I 
did that..

Now my problem is . 
After doing the following to run it on power up
sudo util/init.d/weewx.debian to /etc/init.d/weewx)
sudo chmod +x /etc/init.d/weewx
sudo update-rc.d weewx defaults 98

I then tried to startsudo /etc/init.d/weewx start : no log 
outpur and ps aux shows not running
It DID  not start
I then stopped it..  sudo /etc/init.d/weewx  stop
I then started it again.   sudo /etc/init.d/weewx start
AND IT STARTED    Outputting to log and ...  ps aux | grep weewx... 
shows it running ok.

Also, it does not start on  a power up.  

Here is the log right after power up ..
pi@raspberrypi:~ $ tail -f /var/log/syslog
Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
index_parse.c:191: indx_parse(): error opening 
/media/pi/rootfs/BDMV/index.bdmv
Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
index_parse.c:191: indx_parse(): error opening 
/media/pi/rootfs/BDMV/BACKUP/index.bdmv
Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org -> 
45.79.1.70
Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org -> 
195.21.137.209
Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org -> 
104.131.53.252
Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org -> 
138.68.2.126
Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 ]
Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 ]
Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...
Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system: 
weewx not running
Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx version 
3.6.2
Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9 
(default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Platform 
Linux-4.4.34-v7+-armv7l-with-debian-8.0
Jan  4 13:31:09 raspberrypi weewx[1627]: engine: pid file is 
/var/run/weewx.pid
Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Using configuration file 
/home/weewx/weewx.conf
Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Loading station type 
ObserverIP (user.observerip)
Jan  4 13:31:09 raspberrypi weewx[1616]: Starting weewx weather system: 
weewx.
Jan  4 13:31:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
Jan  4 13:31:09 raspberrypi weewx[1631]: observerip: version is 0.5mw
Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: Unknown firmware 
version: ��
Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: polling interval is 
16.0
Jan  4 13:31:10 raspberrypi weewx[1631]: engine: StdConvert target unit is 
0x1
Jan  4 13:31:10 raspberrypi weewx[1631]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jan  4 13:31:10 raspberrypi weewx[1631]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jan  4 13:31:10 raspberrypi weewx[1631]: engine: Archive will use data 
binding wx_binding
Jan  4 13:31:10 raspberrypi weewx[1631]: engine: Record generation will be 
attempted in 'hardware'
Jan  4 13:31:10 raspberrypi weewx[1631]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
Jan  4 13:31:10 raspberrypi weewx[1631]: engine: 

[weewx-user] Re: Acurite 01536 (Costco)

[Brian Champion-Wescott]

Marcus,

What hardware are you using for your AcuRite 01536?  I have tried using a 
few different Linux distros on regular laptops, without any luck.  Are you 
using a Raspberry Pi?

Thanks,
Brian

On Sunday, December 25, 2016 at 2:17:58 PM UTC-5, Marcus Watkins wrote:
>
> For Christmas today I received an Acurite 01536 5-in-1 weather station 
> with USB connection (from Costco). I set it up with weewx and was excited 
> to see it works out of the box for the most part.
>
> One difference from the docs is there's no 'USB Mode' switch on this base, 
> so I'm interested to see if the log fills up over time.
>
> The only real 'issue' is the barometer reads outside the values allowed by 
> weewx by default. I'm also seeing values vary by quite a bit, but it's 
> super windy out right now. I added an adjustment to match the display, 
> we'll see how it lines up over time.
>
> Does anyone know if the display reports barometer or pressure?
>
> All in all, seems to be working great.
>
> -Marcus
>
>
>
>

-- 
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: Interface Davis Vantage Vue <-> Raspberry Pi 3

[Devonian]

I also have an RF logger interface that uses XBEE modules to transmit the 
logs and loop packets direct from the Vantage console to my PC/Pi or 
whatever you have weewx installed on, basically making a wireless logger 
interface.
Same footprint as the USB logger plug-in module and then has XBEE to USB at 
the PC end.
Works pretty fine, but again, definitely not an off the shelf solution (the 
boards can be purchased through Belfyboy I linked to above or via 
Seedstudio where he has them published).
You will need to solder some small components to the PCB's, program the 
logger chip and configure the XBEE modules to 'talk' serial @ 19200 ;-)

-- 
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 extension version 3.2.0

[Mario Romanello]

It is correct?

weewx.conf:

# Options for extension 'forecast'

[Forecast]

data_binding = forecast_binding

[[OWM]]

api_key = INSERT_OWM_API_KEY_HERE

[[WWO]]

api_key = INSERT_WWO_API_KEY_HERE

[[WU]]

api_key = 9ed8cb535d935e48


[StdReport]


[[forecast]]

[[[Extras]]]

forecast_iconic_settings

source = WU

num_days = 7

HTML_ROOT = public_html/forecast

skin = forecast
in my html page:







 Coming 
soon...



#set global $forecast_iconic_settings = dict()

#set global $forecast_iconic_settings['source'] = 'WU'

#set global $forecast_iconic_settings['num_days'] = 7

#include "forecast_iconic.inc"





I'm sorry for my english..thanks.





Il giorno mercoledì 4 gennaio 2017 13:49:11 UTC+1, Andrew Milner ha scritto:
>
> Can you possibly be more specific?  The wiki gives lots of information as 
> to how to include forecasts on your existing pages - and also provides the 
> forecast skin to generate specific forecast page.  For all forecasts except 
> zambretti you will however need to register with the specific forecast 
> service and obtain the necessary keys/logins/etc as specified in the 
> forecast wiki prerequisites.
>
>
>
> On Wednesday, 4 January 2017 13:09:48 UTC+2, Mario Romanello wrote:
>
>> Hello and congratulations for a job well done with this extension. Could 
>> you help me? I installed the extension, but do not know how to implement it 
>> on my site, I could use a little guidance. Excuse me but I am a beginner, 
>> thank you so much!
>
>

-- 
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: importing data from Weather Display log files

[Niklas Berglund]

Hi.

I was wondering if this script is still working. I have finally made the 
switch from Weather Display to WeeWX. I have log files for a couple of 
years back that I would like to import to WeeWX. 

I've read through this and been trying to get wdConvert.py to work. My 
Python skills are not the best. 

I get the following error when trying to run wdConvert.py : 



  File "./wdConvert.py", line 23, in 
import weewx.uwxutils
ImportError: No module named weewx.uwxutils



I don't know where to find the module or how to tell python where its 
located. 

Is there anyone that would like to help me on this ?

Niklas








Den lördag 18 maj 2013 kl. 18:41:09 UTC+2 skrev William Phelps:
>
> I am making progress on this. I now have a python program that will read 
> WD log files and parse them. Most of the effort was in adding enough checks 
> to get around all the quirks in the data - there are lots!  In going over 
> my several years of data, I found places where the date/time skips ahead, 
> not too much of a surprise, but also places where it jumps backward by odd 
> amounts. I also found several occurrences of duplicate date and time, 
> sometimes with the same data, sometimes with different data.
>
> The program reads these WD log files:
>  nlg.txt - main log file
>  nvantagelog.txt - data specific to the Davis Vantage stations
>  nindoorlog.txt - indoor data
>
> The program takes start and end dates as parameters and writes a csv file, 
> to make review and editing easier.  The next step will be to import the csv 
> file into the weewx database. I tried using "sqllitebrowser" for this but 
> it crashes trying to do an import.
>
> I have a copy of Tom's convert_csv.py and it looks like it should be 
> fairly easy to modify this to work with the csv file my program writes.
>
> Right now the program works with a fixed archive interval.  I plan to also 
> add the ability to change (increase) the interval, by averaging the data, 
> since for one of my stations I changed from 60 seconds to 300 seconds.
>
> William
>

-- 
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 extension version 3.2.0

[Andrew Milner]

Can you possibly be more specific?  The wiki gives lots of information as 
to how to include forecasts on your existing pages - and also provides the 
forecast skin to generate specific forecast page.  For all forecasts except 
zambretti you will however need to register with the specific forecast 
service and obtain the necessary keys/logins/etc as specified in the 
forecast wiki prerequisites.



On Wednesday, 4 January 2017 13:09:48 UTC+2, Mario Romanello wrote:

> Hello and congratulations for a job well done with this extension. Could 
> you help me? I installed the extension, but do not know how to implement it 
> on my site, I could use a little guidance. Excuse me but I am a beginner, 
> thank you so much!

-- 
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: Interface Davis Vantage Vue <-> Raspberry Pi 3

[Alan]

I like my Si1000 radio but it is definitely not an off-the-shelf solution. 
Info is available on wxforum if you like to tinker.

I do not a have Davis base; I bought just the Vantage Vue ISS with 
intention of using a Raspbery Pi in the house.



On Tuesday, January 3, 2017 at 9:53:28 AM UTC-5, Lutz wrote:
>
> Hi,
>
> Do I need the expensive WeatherLink® USB (6510USB) to connect a Davis 
> Vantage Vue with a Raspberry Pi 3 or are there cheaper alternatives?
>
> Best regards
>

-- 
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 extension version 3.2.0

[Mario Romanello]

Hello and congratulations for a job well done with this extension. Could you 
help me? I installed the extension, but do not know how to implement it on my 
site, I could use a little guidance. Excuse me but I am a beginner, thank you 
so much!

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