[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread Sam Roza
Unfortunately, it's repeatable. The data builds up, and then all at once, it is fed into weewx, and the program crashes: ~~~ Oct 8 21:29:15 raspberrypi kernel: [ 110.920747] device eth0 entered promiscuous mode Oct 8 21:29:20 raspberrypi weewx[735]: interceptor: MainThread: empty queue Oct

[weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips
Looks like it's all working now. Thanks! On Saturday, October 8, 2016 at 9:47:07 PM UTC-7, Tim Phillips wrote: > > I actually had a fun time learning by "doing," as it's the way that I > learn things the best, for better or worse. This is a good project for me > as I know what "sudo" does and

Re: [weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips
Looks like it's working now. Thanks for the help! Really had a fun time doing this today! - - - - - - - - - - *Tim Phillips* *Cell: 425-765-1631* On Sat, Oct 8, 2016 at 9:27 PM, mwall wrote: > On Sunday, October 9, 2016 at 12:18:29 AM UTC-4, Tim Phillips wrote: >>

[weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips
I actually had a fun time learning by "doing," as it's the way that I learn things the best, for better or worse. This is a good project for me as I know what "sudo" does and knew enough to be able to get leafpad (text editor) to edit the config file as an admin. I thought I was doing

[weewx-user] Re: Station not showing on Weewx stations map

2016-10-08 Thread Tim Phillips
That's a really good point. I never thought of just using the weather underground URL. I'll give that a shot and see if it works. I spent the day trying to get this to work at all am quite proud of it "just" working with WU's site. I'm super new to RPi and Linux so I appreciate the help. So

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 11:25:31 PM UTC-4, Sam Roza wrote: > > Not sure what happened there...any ideas? > i do not know what made it start working, but that is what working output looks like. the OKOKOKOK is simply multiple OK responses from the interceptor. we do not care about

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread Sam Roza
On Saturday, October 8, 2016 at 6:57:49 PM UTC-7, mwall wrote: > > btw, here it is with a better sed expression for the filter: > > ngrep -l -q -d eth0 '0004a369e0d6' | sed '/mac=/!d' | xargs -n 1 curl > http://localhost: -s -d > > m > Ah yes. That filter is a bit more efficient, isn't it?

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread mwall
btw, here it is with a better sed expression for the filter: ngrep -l -q -d eth0 '0004a369e0d6' | sed '/mac=/!d' | xargs -n 1 curl http://localhost: -s -d m -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 6:47:27 PM UTC-4, Sam Roza wrote: > > None of them seemed to ever do anything when fully put together like this. > Note that I did add '@-' to the end of the command with the xargs on it, > since I believe it is necessary when using the -d option. > i think that

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread Sam Roza
On Saturday, October 8, 2016 at 2:44:15 PM UTC-7, mwall wrote: > > > > On Saturday, October 8, 2016 at 5:23:30 PM UTC-4, Sam Roza wrote: >> >> >> >> On Saturday, October 8, 2016 at 1:53:31 PM UTC-7, mwall wrote: >>> >>> On Saturday, October 8, 2016 at 4:29:20 PM UTC-4, Sam Roza wrote:

[weewx-user] Re: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 5:23:07 PM UTC-4, Miguel Iniesta wrote: > > The log attached has been obtained with debug = 1. >> >> >> ok, lets go back a step. which versions do you have for pyusb and libusb? dpkg -l | grep libusb dpkg -l | grep python-usb then try this: cd /home/weewx sudo

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 5:23:30 PM UTC-4, Sam Roza wrote: > > > > On Saturday, October 8, 2016 at 1:53:31 PM UTC-7, mwall wrote: >> >> On Saturday, October 8, 2016 at 4:29:20 PM UTC-4, Sam Roza wrote: >>> >>> >>> With sed command, it strips the unwanted data from the output, but for >>>

[weewx-user] Re: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]

2016-10-08 Thread Miguel Iniesta
The log attached has been obtained with debug = 1. Thanks, On Saturday, October 8, 2016 at 9:49:44 PM UTC+2, mwall wrote: > > On Saturday, October 8, 2016 at 3:16:04 PM UTC-4, Miguel Iniesta wrote: >> >> Running v3.6.0 on ubuntu 16.04. Connected to a WMR300 station produces >> error

[weewx-user] Re: weewx with OS LW301 and interceptor driver

2016-10-08 Thread Sam Roza
On Saturday, October 8, 2016 at 1:53:31 PM UTC-7, mwall wrote: > > On Saturday, October 8, 2016 at 4:29:20 PM UTC-4, Sam Roza wrote: >> >> >> With sed command, it strips the unwanted data from the output, but for >> some reason, it's not working. I've tried with both curl and nc, but I >>

[weewx-user] Re: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 3:16:04 PM UTC-4, Miguel Iniesta wrote: > > Running v3.6.0 on ubuntu 16.04. Connected to a WMR300 station produces > error WeeWxIOError: [Errno 110] > Please, find log attached. > miguel, could you try again, but with debug=1 in the weewx configuration file?

[weewx-user] v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]

2016-10-08 Thread Miguel Iniesta
Hello, Running v3.6.0 on ubuntu 16.04. Connected to a WMR300 station produces error WeeWxIOError: [Errno 110] Please, find log attached. Any help please. Thank you, Miguel -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from

[weewx-user] Re: Version 3.6.0 failure

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 1:08:49 PM UTC-4, pgeenhuizen wrote: > > With that in mind is there a way to make changes like this to the 2 config > files when upgrading weewx? > oops, here is the correct syntax: wee_config --upgrade --config=old_config_file.conf

[weewx-user] Re: Retrying after MySQL has gone away, Interceptor driver unable to load.

2016-10-08 Thread Steve
That edit seems to have fixed it thanks Matthew. Here's the log snippet from starting WeeWX with the edited interceptor.py (0.11 not the 0.8 I was using earlier) then stopping MySQL, and starting MySQL after WeeWX said it would wait 2 minutes to retry. Regards, Steve. Oct 9 04:24:02 rpi3

[weewx-user] Re: Version 3.6.0 failure

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 1:08:49 PM UTC-4, pgeenhuizen wrote: > > Thanks Matt, that did it. > > I did a diff of the 2 conf files, but missed that one. > > With that in mind is there a way to make changes like this to the 2 config > files when upgrading weewx? > as a matter of fact, there

[weewx-user] Re: Version 3.6.0 failure

2016-10-08 Thread Pete Geenhuizen
Thanks Matt, that did it. I did a diff of the 2 conf files, but missed that one. With that in mind is there a way to make changes like this to the 2 config files when upgrading weewx? Pete On 10/08/16 12:53, mwall wrote: On Saturday, October 8, 2016 at 12:48:05 PM UTC-4, pgeenhuizen

[weewx-user] Re: Retrying after MySQL has gone away, Interceptor driver unable to load.

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 12:22:22 PM UTC-4, Steve wrote: > > Sorry for the confusion Matthew. > > When I was using FOSUB if MySQL went away and then came back, it would > catch up. I only mentioned it because nothing went wrong. > > The upgrading of MySQL is only related because MySQL

[weewx-user] Re: Retrying after MySQL has gone away, Interceptor driver unable to load.

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 9:11:21 AM UTC-4, Steve wrote: > > This is probably for Matthew? > > Before updating to 3.6.0 tonight I thought I'd do an apt-get update and > upgrade. MySQL got upgraded. While it was down WeeWX was unable to write to > it and was waiting another 2 minutes. (When

[weewx-user] Re: tfa nexus raspi record correlation

2016-10-08 Thread GBW
Hallo, Thanks for your tips. In fact, substituting the later drivers did not work at all. Weewx failed to read the data regardless of my efforts.The original and other windows software still worked with the station, so I concluded that I had miraculously destroyed something in the raspi

Re: [weewx-user] Wunderfixer error or my error? (Just upgraded to 3.6.0).

2016-10-08 Thread Thomas Keffer
Substitute your version of wunderfixer with this one and see if that fixes the problem. -tk On Sat, Oct 8, 2016 at 6:41 AM, Steve wrote: > I ran wunderfixer after upgrading to 3.6.0 tonight and got the

[weewx-user] Wunderfixer error or my error? (Just upgraded to 3.6.0).

2016-10-08 Thread Steve
I ran wunderfixer after upgrading to 3.6.0 tonight and got the following. (Wunderfixer is run every night just before midnight via cron and the log has always shown some missing data has been uploaded). Nothing appears in weew.log after running it now. root@rpi3:/home/weewx/bin#

[weewx-user] Retrying after MySQL has gone away, Interceptor driver unable to load.

2016-10-08 Thread Steve
This is probably for Matthew? Before updating to 3.6.0 tonight I thought I'd do an apt-get update and upgrade. MySQL got upgraded. While it was down WeeWX was unable to write to it and was waiting another 2 minutes. (When I was using a Fine-Offset WH3080 it was no hassle), but now I'm using

Re: [weewx-user] Re: Version 3.6.0 hits the streets

2016-10-08 Thread Thomas Keffer
For separating date and time, one strategy I've seen is to use a "T". Then you don't need the quotes. So, a date range would be: --date=2016/09/28T03:00-2016/10/02T12:00 But I can see another issue. wunderfixer uses a different format: --date=-mm-DD Personally, I prefer this to

Re: [weewx-user] Re: Version 3.6.0 hits the streets

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 1:46:03 AM UTC-4, gjr80 wrote: > > >> >> Oh yes - somewhere in the instructions (or help, not sure which) - the >> time in the --date command is in brackets. I presume this is because the >> time is optional - but why the brackets? An option in syntax

[weewx-user] Re: Version 3.6.0 hits the streets

2016-10-08 Thread mwall
On Saturday, October 8, 2016 at 7:05:51 AM UTC-4, Peter_F wrote: > > Thanks Tom, Matthew and Gary, > I upgraded without any issues. One thing I noticed though is that the > Weather Underground RapidFire rest posts are now logged by default. I > added 'log_success = False' to my weewx.conf to

Re: [weewx-user] Responsive Skin install

2016-10-08 Thread Amanda and Darryn Capes-Davis
Looking good. If you find the right files for Adelaide metro, it should be pretty much a turnkey operation replacing the base tags in the template. Let me know how you go. Perhaps we can work to break out the forecast page and index include files and create different files for each Aus metro

Re: [weewx-user] Re: Version 3.6.0 hits the streets

2016-10-08 Thread Andrew Milner
Just seen an 'oddity' . accessing the rpi via ssh from windows via putty when the window is small I get two lines per period ... one line for first tranche of 250 records with last timestamp date and time one line for remaining records of period with last timestamp date and time In full

Re: [weewx-user] Re: Version 3.6.0 hits the streets

2016-10-08 Thread Andrew Milner
Square brackets perhaps?? For some reason the round brackets looks as though they should be included (to sill me at least)!! This may be helpful . http://pcsupport.about.com/od/commandlinereference/a/command-syntax.htm no doubt there is a definition for python somewhere too On