[weewx-user] Re: Out of memory Error - Raspberry Pi

[Francisco Puig]

@mwall,

Thanks a lot for your analysis. I'm running an RPi B = 512 MB of RAM, if 
the issue show up again I can swap it for a RPi 3 that has 1GB of RAM and 
better CPU, maybe is overkill but I really like how weewx works. I will do 
some tests to see what happen.


On Monday, February 27, 2017 at 6:01:46 PM UTC-5, mwall wrote:
>
> On Monday, February 27, 2017 at 1:33:20 PM UTC-5, Francisco Puig wrote:
>>
>> I just sent the logs from the last 24hrs before and after the crash. 
>>
>
> francisco,
>
> how much memory is in the pi?
>
> you are generating only the Standard report.  your reports take 20 to 80 
> seconds to run.  this is slow, but fairly normal for a rpi, and not a 
> problem since your archive interval is 300 seconds.
>
> you are publishing to PWSWeather, WeatherCloud, WeatherBug, WOW, and 
> AWEKAS.
>
> you are using a sqlite database, not mysql.
>
> the memory use of weewx was 149066/90779 VSZ/RSS just before it was killed.
>
> the system has no swap.
>
> so all of this is normal.
>
> the system probably decided to kill weewx because weewx has the biggest 
> total_vm (VSZ), even though weewx is not doing anything unusual.
>
> at 06:33:06 the kernel started having problems.  just before that, apache 
> was reloaded and failed.
>
> at 06:45:26 the kernel killed weewx (pid 472)
>
> after the kernel killed weewx, systemd started apache again.  this time it 
> was successful.
>
> my guess is that apache was eating up memory, the system tried to restart 
> it, that failed, then the system killed weewx.
>
> try disabling apache and use nginx or lighttpd instead.  or, if this is a 
> 512M or 256M pi, get rid of the display and disable all video/graphics, and 
> connect using ssh.
>
> 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: New release V3.5.0

[Joan Pau]

El dimarts, 15 març de 2016 3:06:52 UTC+1, mwall va escriure:
>
> hi george,
>
> as of 3.5.0, when you install weewx and choose fousb driver, 
> record_generation will be set to software.  this will also happen if you do 
> a 'wee_config --reconfigure' and choose fousb.
>
> there are two reasons for this change:
>
> 1) the factory default archive interval for fine offset stations is 30 
> minutes.  so when record_generation=hardware, noobs are confused when their 
> station reports data only every 30 minutes.
>
> 2) when record_generation=hardware, the fousb driver must sync with the 
> station to read just the latest record.  each sync is a chance for usb 
> lockup.  when the archive interval is large-ish (e.g., 30 minutes) this is 
> less of a problem than when it is small-ish (e.g., 5 minutes).
>

Thanks Matthew,

Can you please elaborate on point 2? I read the documentation several times 
but it still confuses me.
If doing record_generation by software, does not weewx need to read the 
LOOP packets (either adaptively every 48s or according the configured 
period), thus increasing the chance for USB lockup?
I thought that record_generation = hardware, would require only one read of 
a RECORD packet per archive_interval, and hence it would generate less USB 
traffic, but I am obviously wrong.
What does that sync() operation do, which is more expensive than reading 
the LOOP packets in terms of USB usage?

And a related question regarding different values archive interval in a FO 
station and in weewx.conf.
>From the documentation, I guess that when using hardware record generation, 
if the values differ, the one from the station is used.
But what happens when using software record generation? Does weewx honor 
the value from the station or from the configuration file?
A possible scenario:
  Using software record generation, use a short archive interval in 
weewx.conf to get updated reports quite often.
  At the same time, have a longer archive interval in the station, so that 
in case of power failure, the console can keep on storing records for a 
longer period of time (at expenses of time resoultion of course).
  
A last question arises from this: at startup, does weewx catch up all the 
missing records stored in the station even when record generation is set to 
software?


-- 
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: parsing from csv file

[Frank Johnson]

thanks Mathew your the best, and sorry guys i can't spell either... lol 
  the datetime is just there to make sure its getting updated each cycle...
thanks again
frank

On Monday, February 27, 2017 at 6:02:24 PM UTC-5, Frank Johnson wrote:
>
> hi all:
>
>   hope someone can point me in the right direction i have crated a csv 
> file in raspberry pi reading data from the hat so im using the
> pond.py example but having problem reading multiple items my file just 
> contains the data...
> ie 
> 32.65,44.5,1015.6,2017-02-27 17:54:38.827595
> so i need to read that in as 
> inTemp (value)
> inHumidity (value)
> barameter (value)
> datetime (value)
>
> im adding this in to argument the SDR info to complete the site is this 
> even the right approach ??
>
> frank KF4CQ
> python newbe
>
>
>

-- 
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: WMR200: Help me to find "low batt."-bits in the d9-packet

[mwall]

On Monday, February 27, 2017 at 3:11:31 PM UTC-5, Per Edström wrote:
>
> This is what I get with debug-mode when I change channel on a sensor with 
> low battery (current temp.sensors with good battery are Ch.1+2+3+5) :
>

sorry i'm so thick, but i cannot make sense of your table.

could you simplify the test?

try this:

1) remove all t/h sensors

2) add a single t/h sensor at channel 1 with known good battery

3) add a single t/h sensor at channel 2 with known low battery

4) move the t/h sensor from channel 2 to channel 3

5) move the t/h sensor from channel 3 to channel 4

...

11) move the t/h sensor from channel 9 to channel 10

at each step, record one or more status packets.

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: WMR200: Help me to find "low batt."-bits in the d9-packet

[mwall]

On Monday, February 27, 2017 at 3:11:31 PM UTC-5, Per Edström wrote:
>
> On my WMR88 (WMR100-driver) I managed to get the battery status from the 
> data packages read from the console.
>

how did you do this?

is packet[0] & 0x40 the battery status for sensors on channels 2-7, as it 
is for channels 0-1?

 

> But on the WMR200 it is not that obvious. I have tried with two 
> temp.sensors going low on battery but I can't figure out what WMR200 is 
> doing with that information. Maybe someone here have an idea?
>

set debug_packet_status to get more info about each status packet:

debug = 1
...
[WMR200]
...
debug_packet_status = 1

but i would also look at the temperature packets (type 0xd7).

also, it looks like the wmr200 driver has the battery status inverted.  a 
value of 0 should indicate ok, a value of 1 should indicate 'battery low'.

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: parsing from csv file

[mwall]

On Monday, February 27, 2017 at 6:02:24 PM UTC-5, Frank Johnson wrote:
>
> hi all:
>
>   hope someone can point me in the right direction i have crated a csv 
> file in raspberry pi reading data from the hat so im using the
> pond.py example but having problem reading multiple items my file just 
> contains the data...
> ie 
> 32.65,44.5,1015.6,2017-02-27 17:54:38.827595
> so i need to read that in as 
> inTemp (value)
> inHumidity (value)
> barameter (value)
> datetime (value)
>
> im adding this in to argument the SDR info to complete the site is this 
> even the right approach ??
>

you're spot on!

one way to parse comma-separated values looks something like this:

with open(filename) as f:
line = f.readline()
values = line.split(',')
record['inTemp'] = line[0]
record['inHumidity'] = line[1]
record['barometer'] = line[2]

you do not need the datetime field, since you are augmenting a packet that 
already has one.

also, be sure to convert units if necessary.  check the usUnits field to 
see what unit system you should convert to.

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] parsing from csv file

[gjr80]

and dateTime in lieu of datetime

-- 
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] parsing from csv file

[gjr80]

Hi,

Not familiar with fileparse at all and maybe you made a typo in your post but 
if barameter features in your config perhaps barometer would work better?

Gary

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

[weewx-user] Re: "not reporting" after power outage

[Craig Thom]

Did you check syslog to see if weewx is giving you any errors?

$tail -f /var/log/syslog

You can stop and restart weewx in another SSH terminal window so you don't 
miss anything in the tail window.

A couple of times, after I've rebooted, weewx has been unable to 
communicate with my 1035 display.  What fixed it was unplugging the USB 
cable and plugging it back in.  syslog was clearly showing the 
communications error.

On Monday, February 27, 2017 at 4:57:53 PM UTC-5, Steve Dulmes wrote:
>
> Hello, 
> My Acurite station has been reporting flawlessly to the Weather 
> Underground for quite a while. Last Friday we had a short power outage in 
> the middle of the night and now it won't connect anymore. I'm using a 
> raspberry pi 3. 
> I stopped and started weewx to hopefully reset the connection. No go.
> I checked the weewx.conf file, and it's same as it should be. Did another 
> stop and start. Still won't work.
> Any ideas are appreciated.
> Thanks very much for your time.
> Steve

-- 
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: Out of memory Error - Raspberry Pi

[mwall]

On Monday, February 27, 2017 at 6:01:46 PM UTC-5, mwall wrote:
>
> the memory use of weewx was 149066/90779 VSZ/RSS just before it was killed.
>

btw, typical memory use for weewx is 12000-5 for RSS and 12-25 
for VSZ

so your 90779 is a bit high (probably due to the 5 uploaders?), but not 
crazy high.

m

sorry for the reply to my own post

-- 
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: sqlite to mySql problem

[Craig Thom]

I ran into the same issue last week when I was installing weewx for the 
first time (on my first RPi).  It went smoothly after that.  I have MySQL 
Workbench installed on my main Windows PC, so I'm able to connect it and 
confirm it is racking up the rows (after creating a user for myself with 
remote access).

I also have MySQL installed on my desktop PC, so I set up MASTER SLAVE 
replication.  That wasn't nearly as easy, and it took a lot of Googling and 
many missteps, but now I've got a duplicate of the weewx database/schema on 
my Windows PC, where it gets backed up automatically to my backup server 
and to Carbonite.  After the PC has been off, when I turn it on MySQL 
catches up on the data it missed.  

I'm a little let down that, after a few days of receiving and installing 
the weather station, setting up a Raspberry Pi, installing weewx, getting 
mySQL running smoothly, and registering a domain name for the Web pages 
generated by weewx, I'm done.  Everything is working perfectly; there's 
nothing else for me to do, and I was having so much fun.

On Monday, February 27, 2017 at 5:33:12 PM UTC-5, Eric Gammeter wrote:
>
> I will need some time to see how it runs now that python-mysqldb has been 
> added.  Thanks much! 
>
> On Monday, February 27, 2017 at 4:13:28 PM UTC-5, Eric Gammeter wrote:
>>
>> Getting .py errors when I attempt to switch from sqlite to mySql 
>> database.  I do not know where to look next.  Any comments/suggestions 
>> would be appreciated.  Thanks /E
>>
>

-- 
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] parsing from csv file

[Frank Johnson]

hi all:

  hope someone can point me in the right direction i have crated a csv file 
in raspberry pi reading data from the hat so im using the
pond.py example but having problem reading multiple items my file just 
contains the data...
ie 
32.65,44.5,1015.6,2017-02-27 17:54:38.827595
so i need to read that in as 
inTemp (value)
inHumidity (value)
barameter (value)
datetime (value)

im adding this in to argument the SDR info to complete the site is this 
even the right approach ??

frank KF4CQ
python newbe


-- 
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: Out of memory Error - Raspberry Pi

[mwall]

On Monday, February 27, 2017 at 1:33:20 PM UTC-5, Francisco Puig wrote:
>
> I just sent the logs from the last 24hrs before and after the crash. 
>

francisco,

how much memory is in the pi?

you are generating only the Standard report.  your reports take 20 to 80 
seconds to run.  this is slow, but fairly normal for a rpi, and not a 
problem since your archive interval is 300 seconds.

you are publishing to PWSWeather, WeatherCloud, WeatherBug, WOW, and AWEKAS.

you are using a sqlite database, not mysql.

the memory use of weewx was 149066/90779 VSZ/RSS just before it was killed.

the system has no swap.

so all of this is normal.

the system probably decided to kill weewx because weewx has the biggest 
total_vm (VSZ), even though weewx is not doing anything unusual.

at 06:33:06 the kernel started having problems.  just before that, apache 
was reloaded and failed.

at 06:45:26 the kernel killed weewx (pid 472)

after the kernel killed weewx, systemd started apache again.  this time it 
was successful.

my guess is that apache was eating up memory, the system tried to restart 
it, that failed, then the system killed weewx.

try disabling apache and use nginx or lighttpd instead.  or, if this is a 
512M or 256M pi, get rid of the display and disable all video/graphics, and 
connect using ssh.

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: sqlite to mySql problem

[Eric Gammeter]

I will need some time to see how it runs now that python-mysqldb has been 
added.  Thanks much! 

On Monday, February 27, 2017 at 4:13:28 PM UTC-5, Eric Gammeter wrote:
>
> Getting .py errors when I attempt to switch from sqlite to mySql 
> database.  I do not know where to look next.  Any comments/suggestions 
> would be appreciated.  Thanks /E
>

-- 
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: sqlite to mySql problem

[Eric Gammeter]

Preparing to unpack .../python-mysqldb_1.2.3-2.1_amd64.deb ...
Unpacking python-mysqldb (1.2.3-2.1) ...
Setting up python-mysqldb (1.2.3-2.1) ...

Ok-  they were not installed...now they are.  Cool.



On Monday, February 27, 2017 at 4:13:28 PM UTC-5, Eric Gammeter wrote:
>
> Getting .py errors when I attempt to switch from sqlite to mySql 
> database.  I do not know where to look next.  Any comments/suggestions 
> would be appreciated.  Thanks /E
>

-- 
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: sqlite to mySql problem

[gjr80]

Ok, well let's check. What response do you get if you enter the following at 
the command line:

sudo apt-get install python-mysqldb

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] "not reporting" after power outage

[Steve Dulmes]

Hello, 
My Acurite station has been reporting flawlessly to the Weather Underground for 
quite a while. Last Friday we had a short power outage in the middle of the 
night and now it won't connect anymore. I'm using a raspberry pi 3. 
I stopped and started weewx to hopefully reset the connection. No go.
I checked the weewx.conf file, and it's same as it should be. Did another stop 
and start. Still won't work.
Any ideas are appreciated.
Thanks very much for your time.
Steve

-- 
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: sqlite to mySql problem

[Eric Gammeter]

Yes-  I definitely believe I followed all the pre-req's.  

On Monday, February 27, 2017 at 4:13:28 PM UTC-5, Eric Gammeter wrote:
>
> Getting .py errors when I attempt to switch from sqlite to mySql 
> database.  I do not know where to look next.  Any comments/suggestions 
> would be appreciated.  Thanks /E
>

-- 
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: sqlite to mySql problem

[gjr80]

Hi, 

Did you install python-mysqldb as per the pre-requisites? 

http://weewx.com/docs/setup.htm

Gary

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

Re: [weewx-user] Re: WMR300: windchill/heatindex

[mwall]

On Monday, February 27, 2017 at 2:52:08 PM UTC-5, Ruben Navarro Huedo wrote:
>
> Using this version:
>
> Feb 27 20:31:06 raspberrypi weewx[3370]: engine: Caught unrecoverable 
> exception in engine:
> Feb 27 20:31:06 raspberrypi weewx[3370]:   _extract_signed() takes 
> exactly 3 arguments (2 given)
> Feb 27 20:31:06 raspberrypi weewx[3370]:   Traceback (most recent 
> call last):
> Feb 27 20:31:06 raspberrypi weewx[3370]: File 
> "/usr/share/weewx/weewx/engine.py", line 847, in main
> Feb 27 20:31:06 raspberrypi weewx[3370]:   engine.run()
> Feb 27 20:31:06 raspberrypi weewx[3370]: File 
> "/usr/share/weewx/weewx/engine.py", line 186, in run
> Feb 27 20:31:06 raspberrypi weewx[3370]:   for packet in 
> self.console.genLoopPackets():
> Feb 27 20:31:06 raspberrypi weewx[3370]: File 
> "/usr/share/weewx/weewx/drivers/wmr300.py", line 887, in genLoopPackets
> Feb 27 20:31:06 raspberrypi weewx[3370]:   pkt = 
> Station.decode(buf)
> Feb 27 20:31:06 raspberrypi weewx[3370]: File 
> "/usr/share/weewx/weewx/drivers/wmr300.py", line 1290, in decode
> Feb 27 20:31:06 raspberrypi weewx[3370]:   pkt = 
> getattr(Station, '_decode_%02x' % buf[0])(buf)
> Feb 27 20:31:06 raspberrypi weewx[3370]: File 
> "/usr/share/weewx/weewx/drivers/wmr300.py", line 1383, in _decode_d4
> Feb 27 20:31:06 raspberrypi weewx[3370]:   pkt['windchill'] = 
> Station._extract_signed(buf[18:20], 0.1) # C
> Feb 27 20:31:06 raspberrypi weewx[3370]:   TypeError: 
> _extract_signed() takes exactly 3 arguments (2 given)
> Feb 27 20:31:06 raspberrypi weewx[3370]:   Exiting.
>>
>>
sorry.  try downloading again.  now at 0.18rc7

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: sqlite to mySql problem

[Eric Gammeter]

It is a Debian pc, and was installed via dpkg / apt-get (not .py).  

On Monday, February 27, 2017 at 4:13:28 PM UTC-5, Eric Gammeter wrote:
>
> Getting .py errors when I attempt to switch from sqlite to mySql 
> database.  I do not know where to look next.  Any comments/suggestions 
> would be appreciated.  Thanks /E
>

-- 
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] sqlite to mySql problem

[Eric Gammeter]

Getting .py errors when I attempt to switch from sqlite to mySql database.  
I do not know where to look next.  Any comments/suggestions would be 
appreciated.  Thanks /E

-- 
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.
root@debian:/# service weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (exited) since Mon 2017-02-27 15:35:30 EST; 12min ago
  Process: 1744 ExecStop=/etc/init.d/weewx stop (code=exited, status=0/SUCCESS)
  Process: 1755 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

Feb 27 15:35:30 debian weewx[1769]: File 
"/usr/share/weewx/weewx/manager.py", line 973, in open_manager
Feb 27 15:35:30 debian weewx[1769]:   manager_dict['schema'])
Feb 27 15:35:30 debian weewx[1769]: File 
"/usr/share/weewx/weewx/manager.py", line 125, in open_with_create
Feb 27 15:35:30 debian weewx[1769]:   connection = 
weedb.connect(database_dict)
Feb 27 15:35:30 debian weewx[1769]: File 
"/usr/share/weewx/weedb/__init__.py", line 60, in connect
Feb 27 15:35:30 debian weewx[1769]:   __import__(db_dict['driver'])
Feb 27 15:35:30 debian weewx[1769]: File 
"/usr/share/weewx/weedb/mysql.py", line 10, in 
Feb 27 15:35:30 debian weewx[1769]:   import MySQLdb
Feb 27 15:35:30 debian weewx[1769]:   ImportError: No module named MySQLdb
Feb 27 15:35:30 debian weewx[1769]:   Exiting.
root@debian:/# 

root@debian:/var/log# tail -f syslog
Feb 27 15:35:30 debian weewx[1769]: File 
"/usr/share/weewx/weedb/__init__.py", line 60, in connect
Feb 27 15:35:30 debian weewx[1769]:   __import__(db_dict['driver'])
Feb 27 15:35:30 debian weewx[1769]: File 
"/usr/share/weewx/weedb/mysql.py", line 10, in 
Feb 27 15:35:30 debian weewx[1769]:   import MySQLdb
Feb 27 15:35:30 debian weewx[1769]:   ImportError: No module named 
MySQLdb
Feb 27 15:35:30 debian weewx[1769]:   Exiting.
Feb 27 15:37:50 debian systemd[1030]: Time has been changed


eric@debian:/etc/weewx$ cat weewx.conf
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.6.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Oak Orchard"

# Latitude and longitude in decimal degrees
latitude = 39.492
longitude = -77.172

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 540, foot

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = Vantage

# If you have a website, you may specify an URL
station_url = http://www.n8aay.net

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet 
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP)
   type = serial

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
   port = /dev/ttyUSB0

# If the connection type is ethernet, an IP Address/hostname is required:
host = 1.2.3.4

##
# The rest of this section rarely needs any attention. 
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

[weewx-user] WMR200: Help me to find "low batt."-bits in the d9-packet

[Per Edström]

On my WMR88 (WMR100-driver) I managed to get the battery status from the 
data packages read from the console. But on the WMR200 it is not that 
obvious. I have tried with two temp.sensors going low on battery but I 
can't figure out what WMR200 is doing with that information. Maybe someone 
here have an idea?

The protocol-information is here: http://www.bashewa.com/wmr200-protocol.php

This is what I get with debug-mode when I change channel on a sensor with 
low battery (current temp.sensors with good battery are Ch.1+2+3+5) :

: *(Added Ch.4)*
Feb 27 16:46:07 eBox3350 weewx[28036]: wmr200: MainThread: D Packet raw:d9 
08 50 10 84 00 c5 01
Feb 27 16:48:07 eBox3350 weewx[28036]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 00 c5 01
: *(Added Ch.6)*
Feb 27 19:25:05 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 00 c5 01
Feb 27 19:26:04 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 00 c5 01
: *(Changed Ch.6 => Ch.10)*
Feb 27 19:54:04 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 00 c5 01
Feb 27 19:55:03 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 08 cd 01
*: (No change, did the system note that ch.6 is missing** when scan-period 
is over? So this is Ch.4+6+10 on low batt?)*
Feb 27 20:09:04 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 08 cd 01
Feb 27 20:09:28 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 08 cd 01
: *(Changed Ch.10 => Ch.7)*
Feb 27 20:13:04 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 08 cd 01
Feb 27 20:13:38 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 09 ce 01

*: (No change, did the system note that ch.10 is missing when scan-period 
is over? So this is Ch.4+7+10 on low batt?)*Feb 27 20:28:03 eBox3350 
weewx[32260]: wmr200: MainThread: D Packet raw:d9 08 40 10 94 09 ce 01
Feb 27 20:28:49 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 18 94 01 ce 01
*: (Changed Ch.7 => Ch.6)*
Feb 27 20:43:03 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 18 94 01 ce 01
Feb 27 20:44:03 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 00 18 d4 01 ce 01

*: (No change, did the system note that ch.10 is missing when scan-period 
is over? So this is Ch.4+6+7 on low batt?)*Feb 27 20:57:02 eBox3350 
weewx[32260]: wmr200: MainThread: D Packet raw:d9 08 00 18 d4 01 ce 01
Feb 27 20:57:42 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 00 19 d4 00 ce 01
*: (Note that this SHOULD be as above i.e.  *

*MainThread: D Packet raw:d9 08 00 10 d4 00 c5 01  when running Ch4+6 with 
low batt, but it is not!)*Now, does anyone see any pattern here?

















































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































-- 
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: WMR300: windchill/heatindex

[Ruben Navarro Huedo]

Using this version:

Feb 27 20:31:06 raspberrypi weewx[3370]: engine: Caught unrecoverable 
exception in engine:
Feb 27 20:31:06 raspberrypi weewx[3370]:   _extract_signed() takes 
exactly 3 arguments (2 given)
Feb 27 20:31:06 raspberrypi weewx[3370]:   Traceback (most recent 
call last):
Feb 27 20:31:06 raspberrypi weewx[3370]: File 
"/usr/share/weewx/weewx/engine.py", line 847, in main
Feb 27 20:31:06 raspberrypi weewx[3370]:   engine.run()
Feb 27 20:31:06 raspberrypi weewx[3370]: File 
"/usr/share/weewx/weewx/engine.py", line 186, in run
Feb 27 20:31:06 raspberrypi weewx[3370]:   for packet in 
self.console.genLoopPackets():
Feb 27 20:31:06 raspberrypi weewx[3370]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 887, in genLoopPackets
Feb 27 20:31:06 raspberrypi weewx[3370]:   pkt = 
Station.decode(buf)
Feb 27 20:31:06 raspberrypi weewx[3370]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1290, in decode
Feb 27 20:31:06 raspberrypi weewx[3370]:   pkt = 
getattr(Station, '_decode_%02x' % buf[0])(buf)
Feb 27 20:31:06 raspberrypi weewx[3370]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1383, in _decode_d4
Feb 27 20:31:06 raspberrypi weewx[3370]:   pkt['windchill'] = 
Station._extract_signed(buf[18:20], 0.1) # C
Feb 27 20:31:06 raspberrypi weewx[3370]:   TypeError: 
_extract_signed() takes exactly 3 arguments (2 given)
Feb 27 20:31:06 raspberrypi weewx[3370]:   Exiting.


El lunes, 27 de febrero de 2017, 20:22:36 (UTC+1), Torbjørn Aasen escribió:
>
> Supports this also Norwegian as I have
>
>
> 2017-02-27 18:48 GMT+01:00 mwall  >:
>
>> On Monday, February 27, 2017 at 12:24:11 PM UTC-5, Miguel Iniesta wrote:
>>>
>>> Have you reload weewx.conf or restarted weewx after updating weewx.conf?
>>> I will have to wait al least a couple of weeks before being able to try 
>>> the solution
>>>
>>
>> miguel and torbjørn,
>>
>> i found another bug in the wmr300 driver.  the hardware reports both 
>> heatindex and windchill in history packets, so you should see heatindex and 
>> windchill for data read from the logger.  the hardware reports current 
>> windchill in *wind* packets, and the driver was not decoding these bytes.  
>> also, it looks like the hardware reports current heat index in bytes 13 and 
>> 14 of D3 packets, and the driver was not decoding these bytes.
>>
>> this is fixed in 0.18rc6 at commit baea414.
>>
>>
>> https://raw.githubusercontent.com/weewx/weewx/development/bin/weewx/drivers/wmr300.py
>>
>> 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/CMhCjyOZdRk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
>  
>
>  
>
>  
>
>  
>
> Med vennlig hilsen
>
> Torbjørn Aasen
>
> Mob: 92092037
>
>  
>
> Carpe Diem
>

-- 
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: WMR300: windchill/heatindex

[Torbjørn Aasen]

Supports this also Norwegian as I have


2017-02-27 18:48 GMT+01:00 mwall :

> On Monday, February 27, 2017 at 12:24:11 PM UTC-5, Miguel Iniesta wrote:
>>
>> Have you reload weewx.conf or restarted weewx after updating weewx.conf?
>> I will have to wait al least a couple of weeks before being able to try
>> the solution
>>
>
> miguel and torbjørn,
>
> i found another bug in the wmr300 driver.  the hardware reports both
> heatindex and windchill in history packets, so you should see heatindex and
> windchill for data read from the logger.  the hardware reports current
> windchill in *wind* packets, and the driver was not decoding these bytes.
> also, it looks like the hardware reports current heat index in bytes 13 and
> 14 of D3 packets, and the driver was not decoding these bytes.
>
> this is fixed in 0.18rc6 at commit baea414.
>
> https://raw.githubusercontent.com/weewx/weewx/development/
> bin/weewx/drivers/wmr300.py
>
> 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/CMhCjyOZdRk/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.
>



-- 









Med vennlig hilsen

Torbjørn Aasen

Mob: 92092037



Carpe Diem

-- 
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: Out of memory Error - Raspberry Pi

[Francisco Puig]

I just sent the logs from the last 24hrs before and after the crash. 

Thanks in advance for the help.


On Monday, February 27, 2017 at 1:20:32 PM UTC-5, mwall wrote:
>
> On Monday, February 27, 2017 at 1:02:30 PM UTC-5, Francisco Puig wrote:
>>
>> @mwall , here is the logs. The last log is the Before and after 
>> the memory crash issue. I hope to find the reason, could be a memory leak 
>> in some place. I manually restarted the service at Feb 27 11:07:43.
>>
>>
> francesco,
>
> i need to see more of the weewx log output - from the time it starts until 
> after two or three archive records have been saved to database.
>
> 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: Out of memory Error - Raspberry Pi

[mwall]

On Monday, February 27, 2017 at 1:02:30 PM UTC-5, Francisco Puig wrote:
>
> @mwall , here is the logs. The last log is the Before and after the memory 
> crash issue. I hope to find the reason, could be a memory leak in some 
> place. I manually restarted the service at Feb 27 11:07:43.
>
>
francesco,

i need to see more of the weewx log output - from the time it starts until 
after two or three archive records have been saved to database.

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: Out of memory Error - Raspberry Pi

[Francisco Puig]

@mwall , here is the logs. The last log is the Before and after the memory 
crash issue. I hope to find the reason, could be a memory leak in some 
place. I manually restarted the service at Feb 27 11:07:43.


*root@weather_bridge:~# sudo grep oom /var/log/**

grep: /var/log/apache2: Is a directory

grep: /var/log/apt: Is a directory

/var/log/auth.log:Feb 27 12:51:09 weather_bridge sudo: root : TTY=pts/0 
; PWD=/root ; USER=root ; COMMAND=/bin/grep oom /var/log/alternatives.log 
/var/log/apache2 /var/log/apt /var/log/auth.log /var/log/auth.log.1 
/var/log/auth.log.2.gz /var/log/auth.log.3.gz /var/log/auth.log.4.gz 
/var/log/boot.log /var/log/bootstrap.log /var/log/btmp /var/log/daemon.log 
/var/log/daemon.log.1 /var/log/daemon.log.2.gz /var/log/daemon.log.3.gz 
/var/log/daemon.log.4.gz /var/log/debug /var/log/debug.1 
/var/log/debug.2.gz /var/log/dmesg /var/log/dpkg.log /var/log/faillog 
/var/log/fsck /var/log/kern.log /var/log/kern.log.1 /var/log/kern.log.2.gz 
/var/log/kern.log.3.gz /var/log/kern.log.4.gz /var/log/lastlog 
/var/log/messages /var/log/messages.1 /var/log/messages.2.gz 
/var/log/messages.3.gz /var/log/messages.4.gz /var/log/ntpstats 
/var/log/samba /var/log/syslog /var/log/syslog.1 /var/log/syslog.2.gz 
/var/log/syslog.3.gz /var/log/syslog.4.gz /var/log/syslog.5.gz 
/var/log/syslog.6.gz /var/log/syslog.7.gz /var/log/user.lo

grep: /var/log/fsck: Is a directory

/var/log/kern.log:Feb 27 06:45:25 weather_bridge kernel: [1878102.857984] 
mandb invoked oom-killer: gfp_mask=0x26084c0, order=0, oom_score_adj=0

/var/log/kern.log:Feb 27 06:45:25 weather_bridge kernel: [1878102.858428] 
[] (dump_header) from [] (oom_kill_process+0x2b8/0x408)

/var/log/kern.log:Feb 27 06:45:25 weather_bridge kernel: [1878102.858460] 
[] (oom_kill_process) from [] 
(out_of_memory+0x2cc/0x324)

/var/log/kern.log:Feb 27 06:45:26 weather_bridge kernel: [1878102.859209] [ 
pid ]   uid  tgid total_vm  rss nr_ptes nr_pmds swapents oom_score_adj 
name

/var/log/messages:Feb 27 06:45:25 weather_bridge kernel: [1878102.857984] 
mandb invoked oom-killer: gfp_mask=0x26084c0, order=0, oom_score_adj=0

/var/log/messages:Feb 27 06:45:25 weather_bridge kernel: [1878102.858428] 
[] (dump_header) from [] (oom_kill_process+0x2b8/0x408)

/var/log/messages:Feb 27 06:45:25 weather_bridge kernel: [1878102.858460] 
[] (oom_kill_process) from [] 
(out_of_memory+0x2cc/0x324)

/var/log/messages:Feb 27 06:45:26 weather_bridge kernel: [1878102.859209] [ 
pid ]   uid  tgid total_vm  rss nr_ptes nr_pmds swapents oom_score_adj 
name

grep: /var/log/ntpstats: Is a directory

grep: /var/log/samba: Is a directory

/var/log/syslog:Feb 27 06:45:25 weather_bridge kernel: [1878102.857984] 
mandb invoked oom-killer: gfp_mask=0x26084c0, order=0, oom_score_adj=0

/var/log/syslog:Feb 27 06:45:25 weather_bridge kernel: [1878102.858428] 
[] (dump_header) from [] (oom_kill_process+0x2b8/0x408)

/var/log/syslog:Feb 27 06:45:25 weather_bridge kernel: [1878102.858460] 
[] (oom_kill_process) from [] 
(out_of_memory+0x2cc/0x324)

/var/log/syslog:Feb 27 06:45:26 weather_bridge kernel: [1878102.859209] [ 
pid ]   uid  tgid total_vm  rss nr_ptes nr_pmds swapents oom_score_adj 
name

root@weather_bridge:~# 


*root@weather_bridge:~# sudo grep total_vm /var/log/**

grep: /var/log/apache2: Is a directory

grep: /var/log/apt: Is a directory

/var/log/auth.log:Feb 27 12:52:09 weather_bridge sudo: root : TTY=pts/0 
; PWD=/root ; USER=root ; COMMAND=/bin/grep total_vm 
/var/log/alternatives.log /var/log/apache2 /var/log/apt /var/log/auth.log 
/var/log/auth.log.1 /var/log/auth.log.2.gz /var/log/auth.log.3.gz 
/var/log/auth.log.4.gz /var/log/boot.log /var/log/bootstrap.log 
/var/log/btmp /var/log/daemon.log /var/log/daemon.log.1 
/var/log/daemon.log.2.gz /var/log/daemon.log.3.gz /var/log/daemon.log.4.gz 
/var/log/debug /var/log/debug.1 /var/log/debug.2.gz /var/log/dmesg 
/var/log/dpkg.log /var/log/faillog /var/log/fsck /var/log/kern.log 
/var/log/kern.log.1 /var/log/kern.log.2.gz /var/log/kern.log.3.gz 
/var/log/kern.log.4.gz /var/log/lastlog /var/log/messages 
/var/log/messages.1 /var/log/messages.2.gz /var/log/messages.3.gz 
/var/log/messages.4.gz /var/log/ntpstats /var/log/samba /var/log/syslog 
/var/log/syslog.1 /var/log/syslog.2.gz /var/log/syslog.3.gz 
/var/log/syslog.4.gz /var/log/syslog.5.gz /var/log/syslog.6.gz 
/var/log/syslog.7.gz

/var/log/auth.log:Feb 27 12:52:15 weather_bridge sudo: root : TTY=pts/0 
; PWD=/root ; USER=root ; COMMAND=/bin/grep total_vm 
/var/log/alternatives.log /var/log/apache2 /var/log/apt /var/log/auth.log 
/var/log/auth.log.1 /var/log/auth.log.2.gz /var/log/auth.log.3.gz 
/var/log/auth.log.4.gz /var/log/boot.log /var/log/bootstrap.log 
/var/log/btmp /var/log/daemon.log /var/log/daemon.log.1 
/var/log/daemon.log.2.gz /var/log/daemon.log.3.gz /var/log/daemon.log.4.gz 
/var/log/debug /var/log/debug.1 /var/log/debug.2.gz /var/log/dmesg 
/var/log/dpkg.log /var/log/faillog /var/log/fsck /var/log/kern.log 
/var/log/kern.log

[weewx-user] Re: WMR300: windchill/heatindex

[mwall]

On Monday, February 27, 2017 at 12:24:11 PM UTC-5, Miguel Iniesta wrote:
>
> Have you reload weewx.conf or restarted weewx after updating weewx.conf?
> I will have to wait al least a couple of weeks before being able to try 
> the solution
>

miguel and torbjørn,

i found another bug in the wmr300 driver.  the hardware reports both 
heatindex and windchill in history packets, so you should see heatindex and 
windchill for data read from the logger.  the hardware reports current 
windchill in *wind* packets, and the driver was not decoding these bytes.  
also, it looks like the hardware reports current heat index in bytes 13 and 
14 of D3 packets, and the driver was not decoding these bytes.

this is fixed in 0.18rc6 at commit baea414.

https://raw.githubusercontent.com/weewx/weewx/development/bin/weewx/drivers/wmr300.py

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: WMR300: windchill/heatindex

[Miguel Iniesta]

Hello Matthew,

Yes, the pattern is really interesting, but it is still quite unknown to 
me. 
There is not any other station in this high part of the valley and further 
down the wind does not behave like this. 
Being a mountain area, I think orographic conditions might play an 
important role.

Thank you.


miguel,
>
> that is a fascinating wind pattern - the winds shift pretty decisively at 
> day/night boundaries!
>
> is that a mountain/valley weather pattern?
>
> 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: WMR300: windchill/heatindex

[Miguel Iniesta]

Have you reload weewx.conf or restarted weewx after updating weewx.conf?
I will have to wait al least a couple of weeks before being able to try the 
solution 

Cheers.

On Monday, February 27, 2017 at 5:27:10 PM UTC+1, Torbjørn Aasen wrote:
>
> This is how mine is set up and does not work
>
>
> 
>
>
> [StdWXCalculate]
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible 
> values $
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
>
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = prefer_hardware
> windchill = hardware
> heatindex = hardware
> dewpoint = hardware
> inDewpoint = prefer_hardware
> rainRate = hardware
> [[Calculatios]]
>
>
>
>  
 

-- 
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: Out of memory Error - Raspberry Pi

[mwall]

francesco,

it would also help if you could post more context about why the 
out-of-memory killer was activated.  see the answer to this posting:

http://unix.stackexchange.com/questions/128642/debug-out-of-memory-with-var-log-messages

and post any oom/total_vm results you find:

sudo grep oom /var/log/*
sudo grep total_vm /var/log/*

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: Out of memory Error - Raspberry Pi

[mwall]

On Monday, February 27, 2017 at 11:18:00 AM UTC-5, Francisco Puig wrote:
>
> After 45 days running in a raspberry pi my weewx suddenly stopped. I 
> found on the logs a *"**Out of memory: Kill process 472 (python) score 
> 814 or sacrifice child"* error. I restarted the weewx service and 
> everything came back. Anyone has an idea whats triggered the out of memory? 
> I'm attaching the logs for reference.
>

hello francisco,

it is not normal for weewx to consume large amounts of memory.

please post the log from just before weewx starts up until after two or 
three archive intervals.

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: WMR300: windchill/heatindex

[Torbjørn Aasen]

mandag 27. februar 2017 14.34.59 UTC+1 skrev mwall følgende:
>
> On Monday, February 27, 2017 at 5:49:30 AM UTC-5, Miguel Iniesta wrote:
>>
>> You can have a look: www.navarredondilla.info
>>
>
> miguel,
>
> that is a fascinating wind pattern - the winds shift pretty decisively at 
> day/night boundaries!
>
> is that a mountain/valley weather pattern?
>
> 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: WMR300: windchill/heatindex

[Torbjørn Aasen]

This is how mine is set up and does not work




[StdWXCalculate]

[[Calculations]]
# Derived quantities are calculated by this service. Possible 
values $
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = prefer_hardware
windchill = hardware
heatindex = hardware
dewpoint = hardware
inDewpoint = prefer_hardware
rainRate = hardware
[[Calculatios]]


mandag 27. februar 2017 14.31.55 UTC+1 skrev mwall følgende:
>
>
>
> On Sunday, February 26, 2017 at 3:01:41 PM UTC-5, Miguel Iniesta wrote:
>>
>> Station: WMR300
>> weewx v3.6.2
>>
>> Since updated to v3.6.2, I have realised that windchill/heatindex data 
>> are not available in my system.
>> In weewx.conf the default option for these data is prefer_harware so I 
>> understand that even a station problem would not prevent these data to be 
>> recorded. 
>> I do not have remote access to my system right now but I do not remember 
>> having modified the value of these parameters.
>>
>> Some help would be much appreciated.
>>
>
> miguel,
>
> there was a typo in the wmr300 ConfEditor.  it used 'Calculation' instead 
> of 'Calculations'.  as a result, the values in StdWXCalculate were not 
> set properly.
>
> to fix it, modify your weewx.conf to look like this:
>
> [StdWXCalculate]
> [[Calculations]]
> rainRate = hardware
> windchill = hardware
> heatindex = hardware
> dewpoint = hardware
>
> the wmr300 emits partial packets.  so if you tell weewx to calculate these 
> derived values, it never will.  the hardware provides these values, so use 
> the hardware.
>
> the bug was fixed at commit 7d26b4f.
>
> 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] Out of memory Error - Raspberry Pi

[Francisco Puig]

After 45 days running in a raspberry pi my weewx suddenly stopped. I found 
on the logs a *"**Out of memory: Kill process 472 (python) score 814 or 
sacrifice child"* error. I restarted the weewx service and everything came 
back. Anyone has an idea whats triggered the out of memory? I'm attaching 
the logs for reference.

root@weather_bridge:~# sudo tail -f /var/log/syslog

Feb 27 06:45:26 weather_bridge kernel: [1878102.860076] [26269] 0 
26269  475   18   5   00 0 man-db

Feb 27 06:45:26 weather_bridge kernel: [1878102.860100] [26272] 6 26272 
3606 2582  10   00 0 mandb

Feb 27 06:45:26 weather_bridge kernel: [1878102.860119] Out of memory: Kill 
process 472 (python) score 814 or sacrifice child

Feb 27 06:45:26 weather_bridge kernel: [1878102.860239] Killed process 472 
(python) total-vm:556264kB, anon-rss:363116kB, file-rss:0kB

Feb 27 06:45:27 weather_bridge apache2[26194]: Reloading web server: 
apache2.

Feb 27 06:45:27 weather_bridge CRON[26096]: (CRON) info (No MTA installed, 
discarding output)

Feb 27 07:17:01 weather_bridge CRON[26350]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)

Feb 27 08:17:01 weather_bridge CRON[26366]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)

Feb 27 09:17:01 weather_bridge CRON[26382]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)

Feb 27 10:17:01 weather_bridge CRON[26398]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)


root@weather_bridge:~# sudo /etc/init.d/weewx stop

[ ok ] Stopping weewx (via systemctl): weewx.service.


root@weather_bridge:~# sudo /etc/init.d/weewx start

[ ok ] Starting weewx (via systemctl): weewx.service.


root@weather_bridge:~# df

Filesystem 1K-blocksUsed Available Use% Mounted on

/dev/root   14859920 1038008  13188412   8% /

devtmpfs  218256   0218256   0% /dev

tmpfs 222544   0222544   0% /dev/shm

tmpfs 222544   24948197596  12% /run

tmpfs   5120   4  5116   1% /run/lock

tmpfs 222544   0222544   0% /sys/fs/cgroup

/dev/mmcblk0p1 63503   20593 42910  33% /boot

root@weather_bridge:~# 

-- 
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: Cant find file:///var/www/html/weewx/index.html

[Torbjørn Aasen]

It goes really well.
I thank you for all the help you have given an old man who loves to do this.
Thanks again for your help.
I'll read on your link.
Going to try and not nag more on you but can not promise anything.
Have 3 WMR928 I would also set up this way

Have a great day.


2017-02-27 14:38 GMT+01:00 mwall :

> On Monday, February 27, 2017 at 1:59:57 AM UTC-5, Torbjørn Aasen wrote:
>>
>> I do not get up Wind Cill and Heat index from WMR300 yet?
>> See picture below
>>
>
> hello torbjørn,
>
> please try the solution mentioned here:
>
> https://groups.google.com/forum/#!topic/weewx-user/CMhCjyOZdRk
>
> thank you for being patient in this process - sometimes the path meanders
> a bit, but we get there eventually.
>
> 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/6-NAVeNuNME/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.
>



-- 









Med vennlig hilsen

Torbjørn Aasen

Mob: 92092037



Carpe Diem

-- 
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: Cant find file:///var/www/html/weewx/index.html

[mwall]

On Monday, February 27, 2017 at 1:59:57 AM UTC-5, Torbjørn Aasen wrote:
>
> I do not get up Wind Cill and Heat index from WMR300 yet?
> See picture below
>

hello torbjørn,

please try the solution mentioned here:

https://groups.google.com/forum/#!topic/weewx-user/CMhCjyOZdRk

thank you for being patient in this process - sometimes the path meanders a 
bit, but we get there eventually.

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: WMR300: windchill/heatindex

[mwall]

On Monday, February 27, 2017 at 5:49:30 AM UTC-5, Miguel Iniesta wrote:
>
> You can have a look: www.navarredondilla.info
>

miguel,

that is a fascinating wind pattern - the winds shift pretty decisively at 
day/night boundaries!

is that a mountain/valley weather pattern?

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: WMR300: windchill/heatindex

[mwall]

On Sunday, February 26, 2017 at 3:01:41 PM UTC-5, Miguel Iniesta wrote:
>
> Station: WMR300
> weewx v3.6.2
>
> Since updated to v3.6.2, I have realised that windchill/heatindex data are 
> not available in my system.
> In weewx.conf the default option for these data is prefer_harware so I 
> understand that even a station problem would not prevent these data to be 
> recorded. 
> I do not have remote access to my system right now but I do not remember 
> having modified the value of these parameters.
>
> Some help would be much appreciated.
>

miguel,

there was a typo in the wmr300 ConfEditor.  it used 'Calculation' instead 
of 'Calculations'.  as a result, the values in StdWXCalculate were not set 
properly.

to fix it, modify your weewx.conf to look like this:

[StdWXCalculate]
[[Calculations]]
rainRate = hardware
windchill = hardware
heatindex = hardware
dewpoint = hardware

the wmr300 emits partial packets.  so if you tell weewx to calculate these 
derived values, it never will.  the hardware provides these values, so use 
the hardware.

the bug was fixed at commit 7d26b4f.

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: WMR300: windchill/heatindex

[Andrew Milner]

It is of course quite right and proper that there is not always a heat 
index or windchill value - and in fact you can never have both 
available!



On Monday, 27 February 2017 14:10:30 UTC+2, Andrew Milner wrote:

> If you have said windchill and/or heat index are hardware generated then:
> a) According to WMR300 manual the wmr300 only calculates (and so only 
> provides) heat index when temp is > 80F and humidity > 40%
> b) I do not know how/when windchill is calculated by wmr300  - manual says 
> it is based on wind speed and temperature, and then goes on to say it is 
> based on channel 1 temperature and humidity.  This leaves me confused 
>
> If it does not calculate heatindex or windchill then I assume the output 
> from the station is Null (none or n/a)
>
> If you have said weewx should calculate windchill (software preferred) 
> then weewx will calculate values when temp > 80, humidity > 40 or temp<50, 
> wind > 5 - or will just set to outdoor temperature
>
> If you have said hardware preferred then what you see will depend on what 
> the hardware outputs, and weewx will not necessarily perform a calculation 
> if the hardware provides a value of some sort.
>
> Why not set windchill and heatindex to software or software preferred, and 
> see what happens - do you then get meaningful values??
>
>
>
>
> On Monday, 27 February 2017 12:49:30 UTC+2, Miguel Iniesta wrote:
>
>>
>> Hello Andrew,
>>
>> I don’t have access to the station right now but weewx does not even 
>> default to outdoor temp.
>>
>> You can have a look: www.navarredondilla.info
>>
>> 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] Re: WMR300: windchill/heatindex

[Andrew Milner]

If you have said windchill and/or heat index are hardware generated then:
a) According to WMR300 manual the wmr300 only calculates (and so only 
provides) heat index when temp is > 80F and humidity > 40%
b) I do not know how/when windchill is calculated by wmr300  - manual says 
it is based on wind speed and temperature, and then goes on to say it is 
based on channel 1 temperature and humidity.  This leaves me confused 

If it does not calculate heatindex or windchill then I assume the output 
from the station is Null (none or n/a)

If you have said weewx should calculate windchill (software preferred) then 
weewx will calculate values when temp > 80, humidity > 40 or temp<50, wind 
> 5 - or will just set to outdoor temperature

If you have said hardware preferred then what you see will depend on what 
the hardware outputs, and weewx will not necessarily perform a calculation 
if the hardware provides a value of some sort.

Why not set windchill and heatindex to software or software preferred, and 
see what happens - do you then get meaningful values??




On Monday, 27 February 2017 12:49:30 UTC+2, Miguel Iniesta wrote:

>
> Hello Andrew,
>
> I don’t have access to the station right now but weewx does not even 
> default to outdoor temp.
>
> You can have a look: www.navarredondilla.info
>
> 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] Re: WMR300: windchill/heatindex

[Miguel Iniesta]

Hello Andrew,

I don’t have access to the station right now but weewx does not even 
default to outdoor temp.

You can have a look: www.navarredondilla.info

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.

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Andrew Milner]

Does the wm300 show values for windchill and heat index?  weewx software 
generated values require temp < 50F and wind > 5mph for windchill and >80F 
and humidity > 40% for heatindex otherwise will default to the same 
as outdoor temperature.



On Monday, 27 February 2017 08:59:57 UTC+2, Torbjørn Aasen wrote:
>
> Hi
>
> Yes it seems to work now.
> Got that it to send out to Wunderground too :-)
>
> I do not get up Wind Cill and Heat index from WMR300 yet?
> See picture below
>
> The next step is to get it to send out to my homepage with ftp.
>
> It's a little more fun now that something seems to work
>
>
> [image: Innebygd bilde 1]
> [image: Innebygd bilde 2]
>
> 2017-02-26 17:54 GMT+01:00 Andrew Milner  >:
>
>> so it is working fine again 
>>
>>
>>
>> On Sunday, 26 February 2017 18:33:43 UTC+2, Torbjørn Aasen wrote:
>>
>>> traHeatindex3': None, 'extraHeatindex2': None, 'extraHeatindex1': None, 
>>> 'extraHeatindex7': None, 'extraHeatindex6': None, 'extraHeatindex5': None, 
>>> 'extraHeatindex4': None, 'interval': 900.0, 'dateTime': 1488108360.0, 
>>> 'windDir': 153.0, 'outTemp': 0.6001, 'windSpeed': 1.3, 
>>> 'inHumidity': 28.0, 'windGust': 1.4001}
>>> Feb 26 17:20:58 RPi_hjemme weewx[7353]: manager: added record 2017-02-26 
>>> 12:26:00 CET (1488108360) to database 'weewx.sdb'
>>> Feb 26 17:20:58 RPi_hjemme weewx[7353]: manager: added record 2017-02-26 
>>> 12:26:00 CET (1488108360) to daily summary in 'weewx.sdb'
>>> Feb 26 17:20:59 RPi_hjemme weewx[7353]: wmr300: rain=0.254 
>>> rain_total=5.08 last_rain=4.826
>>> Feb 26 17:20:59 RPi_hjemme weewx[7353]: wmr300: historical record: 
>>> {'outHumidity': 88.0, 'barometer': 980.1, 'extraDewpoint7': None, 
>>> 'dewpoint': None, 'extraTemp2': None, 'heatindex': None, 'inTemp': 
>>> 22.402, 'windGustDir': 152.0, 'extraDewpoint2': None, 
>>> 'extraDewpoint3': None, 'extraDewpoint1': None, 'extraDewpoint6': None, 
>>> 'windchill': None, 'extraDewpoint4': None, 'extraDewpoint5': None, 'rain': 
>>> 0.25356, 'extraHumid6': None, 'extraHumid7': None, 
>>> 'extraHumid4': None, 'extraHumid5': None, 'extraHumid2': None, 
>>> 'extraHumid3': None, 'extraHumid1': None, 'extraTemp6': None, 'extraTemp7': 
>>> None, 'extraTemp4': None, 'extraTemp5': None, 'rainRate': 0.0, 
>>> 'extraTemp3': None, 'usUnits': 17, 'extraTemp1': None, 'extraHeatindex3': 
>>> None, 'extraHeatindex2': None, 'extraHeatindex1': None, 'extraHeatindex7': 
>>> None, 'extraHeatindex6': None, 'extraHeatindex5': None, 'extraHeatindex4': 
>>> None, 'interval': 900.0, 'dateTime': 1488109260.0, 'windDir': 193.0, 
>>> 'outTemp': 0.9, 'windSpeed': 1.3, 'inHumidity': 28.0, 'windGust': 0.8}
>>> Feb 26 17:20:59 RPi_hjemme weewx[7353]: manager: added record 2017-02-26 
>>> 12:41:00 CET (1488109260) to database 'weewx.sdb'
>>> Feb 26 17:20:59 RPi_hjemme weewx[7353]: manager: added record 2017-02-26 
>>> 12:41:00 CET (1488109260) to daily summary in 'weewx.sdb'
>>> Feb 26 17:21:00 RPi_hjemme weewx[7353]: wmr300: rain=0.254 
>>> rain_total=5.334 last_rain=5.08
>>> Feb 26 17:21:00 RPi_hjemme weewx[7353]: wmr300: historical record: 
>>> {'outHumidity': 86.0, 'barometer': 980.0, 'extraDewpoint7': None, 
>>> 'dewpoint': None, 'extraTemp2': None, 'heatindex': None, 'inTemp': 
>>> 22.402, 'windGustDir': 216.0, 'extraDewpoint2': None, 
>>> 'extraDewpoint3': None, 'extraDewpoint1': None, 'extraDewpoint6': None, 
>>> 'windchill': None, 'extraDewpoint4': None, 'extraDewpoint5': None, 'rain': 
>>> 0.25356, 'extraHumid6': None, 'extraHumid7': None, 
>>> 'extraHumid4': None, 'extraHumid5': None, 'extraHumid2': None, 
>>> 'extraHumid3': None, 'extraHumid1': None, 'extraTemp6': None, 'extraTemp7': 
>>> None, 'extraTemp4': None, 'extraTemp5': None, 'rainRate': 1.016, 
>>> 'extraTemp3': None, 'usUnits': 17, 'extraTemp1': None, 'extraHeatindex3': 
>>> None, 'extraHeatindex2': None, 'extraHeatindex1': None, 'extraHeatindex7': 
>>> None, 'extraHeatindex6': None, 'extraHeatindex5': None, 'extraHeatindex4': 
>>> None, 'interval': 900.0, 'dateTime': 1488110160.0, 'windDir': 164.0, 
>>> 'outTemp': 1.2002, 'windSpeed': 0.8, 'inHumidity': 28.0, 
>>> 'windGust': 1.4001}
>>> Feb 26 17:21:00 RPi_hjemme weewx[7353]: manager: added record 2017-02-26 
>>> 12:56:00 CET (1488110160) to database 'weewx.sdb'
>>> Feb 26 17:21:00 RPi_hjemme weewx[7353]: manager: added record 2017-02-26 
>>> 12:56:00 CET (1488110160) to daily summary in 'weewx.sdb'
>>> Feb 26 17:21:00 RPi_hjemme weewx[7353]: wmr300: rain=0.254 
>>> rain_total=5.588 last_rain=5.334
>>> Feb 26 17:21:00 RPi_hjemme weewx[7353]: wmr300: historical record: 
>>> {'outHumidity': 86.0, 'barometer': 980.1, 'extraDewpoint7': None, 
>>> 'dewpoint': None, 'extraTemp2': None, 'heatindex': None, 'inTemp': 22.3, 
>>> 'windGustDir': 148.0, 'extraDewpoint2': None, 'extraDewpoint3': None, 
>>> 'extraDewpoint1': None, 'extraDewpoint6': None, 'windchill': None, 
>>> 'extraDewpoint4': None, 'extraDewpoint5'

[weewx-user] Re: WMR300: windchill/heatindex

[Andrew Milner]

Does the wm300 show values for windchill and heat index?  weewx software 
generated values require temp < 50F and wind > 5mph for windchill and >80F 
and humidity > 40% for heatindex otherwise will default to the same 
as outdoor temperature.



On Sunday, 26 February 2017 22:01:41 UTC+2, Miguel Iniesta wrote:

> Station: WMR300
> weewx v3.6.2
>
> Since updated to v3.6.2, I have realised that windchill/heatindex data are 
> not available in my system.
> In weewx.conf the default option for these data is prefer_harware so I 
> understand that even a station problem would not prevent these data to be 
> recorded. 
> I do not have remote access to my system right now but I do not remember 
> having modified the value of these parameters.
>
> Some help would be much appreciated.
> Thank you.
>

-- 
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] Adding a top margin to images?

[gjr80]

Hi,

I think you will find it is hard coded as a proportion of the font size being 
used. Line 81 looks like a good place to start:

self.tmargin = int(1.5 * self.top_label_font_size + 0.5)

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] Adding a top margin to images?

[Alec Bennett]

My generated images are much bigger than default:

http://sinkingsensation.com/dropbox/daywind.png

Everything looks great except the top margin. I'd like to extend the grey
area in the header. Is that possible in the skin config? If not, any tips
on doing it with genplot.py?

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