[weewx-user] New weather station

[Macha]

It’s probably not remembered, but some while ago I posted about a problem I was 
having with my (many years old) fousb station.

Basically, it was reporting ludicrously high rainfall and wind speeds. These 
"readings" happening even when the relevant sensors were unplugged.

So, I concluded that the unit’s electronics were, to use an Engineering term, 
buggered.

Being unwilling to spend money on a new station, I explored the possibility of 
making a "homebrew" station and went out and bought a BBC Micro:bit and a 
Sparkfun Weather:bit.

The Sparkfun product comes with software written in Microsoft’s Typescript. 
This actually ran too slowly for my purposes, as did Micropython, so I ended up 
using C++ with the compiler on mbed.org which loops round the monitoring tasks 
needed in about 1mS ( I wanted to avoid interrupts ).

I also wrote a (crude) driver for weewx, which pulls loop data off the 
Micro:bit, so all in all I’m feeling quite smug!

My next step is to have a go at writing code, running on the Micro:bit, which 
can read the BME280 as currently I’m doing that with the attached RPi.

I’m old enough btw to be able to say "I can write FORTRAN in any language", so 
please don’t ask to see the code!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/278917c8-36a7-4bb1-9fd0-1ea5cc6849d7%40googlegroups.com.

[weewx-user] Re: fousb strange behaviour

[Macha]

Thanks for responding.

Yes, I get spiders (and birds perching on it and ...).

However, these rain results occur even when the rain meter isn’t connected. For 
example, overnight recorded 30mm of rain when the meter was disconnected - 
furthermore, it wasn’t even raining.

I was wondering about some kind interference. Or the station just being, well, 
buggered.

I’m almost at the point of splashing out on a new station, but wouldn’t want 
the new one to act just like the current one.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d2a91952-7e81-4845-907b-24b4b60c8510%40googlegroups.com.

[weewx-user] fousb strange behaviour

[Macha]

... well at least I think it is.

I’ve had a "cheapo" wh1080 system running for a few years with an RPi and weewx.

I’ve quite a few glitches over the years - lockups and communication dropouts 
sorted with fresh batteries and/or restarts. Silly readings have been tamed 
with +/- limits.

The latest behaviour is stumping me. Over the past few weeks I’ve been getting 
rain readings when no rain has fallen. Furthermore, these rain readings are 
"sensible" in the sense of being within normal rainfall levels around here. For 
example last week it recorded around 100mm per day for 3 days, which is what 
continuous heavy rain would produce.

Except it hasn’t actually rained for several weeks.

I’ve tried the following ...

disconnecting the rain sensor (tipping bucket) - it still records rain.

moving the remote unit closer (now within 5m of the console) - no difference.

changing USB cable (no change).

using a powered USB device (no change).

Any clues (please)



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e080c81e-877a-4bd3-9801-8afdd5af2b2c%40googlegroups.com.

[weewx-user] Re: weewx, raspberry pi and sd cards - the lifetime for card

[Macha]

Hi,

In the early days with my Pi farm, I lost* a few SD cards.

I then moved on to keeping my / file system on a usb flash drive, this was 
a bit better, but I still lost* a couple of those.

I then tried putting / on my NFS server. This worked fine, except that when 
I had too many (4+) RPis using this arrangement, crashes (recoverable) 
would become annoyingly frequent.

I've also done things like stopping swap space and so on.

My current arrangement (I have around 10 RPis) is a mix. I have a few using 
/ on my NFS, a few "SD card only" and a few where frequent writes (images 
etc) are stored on the NFS as a mount point. With this, everything ticks 
along nicely and I haven't lost a card for a few years.

I also use "raspibackup" to image the SD cards once a week.

I have to say that I have a bit of an aversion to using powered USB hubs - 
it's a personal  preference!

Cheers

* "lost" means completely unreadable/unwriteable


On Monday, October 31, 2016 at 9:34:25 AM UTC+1, Jacek Skowroński wrote:
>
> Hi,
> How does Your sd card "live" in raspberry pi?
> On my example I lost 5 cards already - all of them by 3-4months long.
> Is it normal?
>
> Yust now I'm looking to get rid of sd cards and write down data somewhere 
> else.
> Any topics? Any hints?
>

-- 
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: Please can I have my bug back?

[Macha]

No I didn't. In fact I didn't play around with nice levels etc.

The "original" RPi is a Pi 2 (more by accident than intention, but it 
should have enough "welly") - it now runs just weewx and a single camera 
and its CPU utilisation is very low. 

In fact, the original "lockouts" weren't coincident with weewx's reporting 
and seemed pretty random (and infrequent). I still suspect that the whole 
issue had something to do with the fact that this "original" machine stores 
"/" on my NFS and consequently Ethernet traffic is high.

Cheers

PS: The RPi now running 3 cameras, several Adafruit sensors and audio 
streaming has had a traumatic history. It is a "Model B+ and was originally 
housed outdoors in a weatherproof clear plastic case. Unfortunately, this 
case wasn't as rugged as hoped and about 12 months ago - after it had 
crashed and following a few days of high wind and heavy rain - I found the 
RPi lying in the grass, soaking wet and covered in a kind of powdery grey 
gunk. I cleaned it up (toothbrush + alcohol + compressed air) and it then 
worked fine agin. The only lasting damage being the failure of the 
spring/clip thing that holds the SD card in place - this is now secured by 
a plastic cable tie. The original SD card was completely fried.

On Sunday, October 30, 2016 at 8:53:44 AM UTC+1, Andrew Milner wrote:
>
> when you had cams and weewx on one machine did you have turbo mode 
> enabled?  It would have needed it I expect.
>
> weewx will have failed because the camera were hogging resources - you 
> could have tried raising the priority.  weewx will trundle along at very 
> low cpu usage UNTIL it generates reports and plots - then it will need very 
> high resources.
>
>
>
> On Sunday, 30 October 2016 09:42:12 UTC+2, Macha wrote:
>
>> OK, status report on my "lockout" with weewx and my FOUSB station.
>>
>> I moved 2 webcams from the RPi running weewx onto a different machine 
>> (another RPi, I have quite a few).
>>
>> Result? No weewx lockouts for nearly 10 days. I'm not sure if this passes 
>> the "5 sigma" test, but it's certainly a record uptime.
>>
>> Still a few puzzlements - on the previous setup, it was always weewx 
>> (well Python I suppose) that "failed", the webcams (run with mjpg-streamer) 
>> were always rock-solid. On the new setup, the RPi which now has the "moved" 
>> webcams is quite busy - it runs the 2 new cameras, plus an RPi camera (all 
>> driven with mjpg-streamer) and also icecast2+darkice (monitoring bird 
>> tweets, etc.) - CPU utilisation is around 35%.  This machine never fails.
>>
>> The previous RPi is now chuffing along at <1% 
>>
>> Anyway, thanks again for the advice and comments ...
>>
>>

-- 
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: Please can I have my bug back?

[Macha]

OK, status report on my "lockout" with weewx and my FOUSB station.

I moved 2 webcams from the RPi running weewx onto a different machine (another 
RPi, I have quite a few).

Result? No weewx lockouts for nearly 10 days. I'm not sure if this passes the 
"5 sigma" test, but it's certainly a record uptime.

Still a few puzzlements - on the previous setup, it was always weewx (well 
Python I suppose) that "failed", the webcams (run with mjpg-streamer) were 
always rock-solid. On the new setup, the RPi which now has the "moved" webcams 
is quite busy - it runs the 2 new cameras, plus an RPi camera (all driven with 
mjpg-streamer) and also icecast2+darkice (monitoring bird tweets, etc.) - CPU 
utilisation is around 35%.  This machine never fails.

The previous RPi is now chuffing along at <1% 

Anyway, thanks again for the advice and comments ...

-- 
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: Please can I have my bug back?

[Macha]

Hi,

Yes, the console has batteries, recently changed, so still pretty strong. 
Rebooting the pi has no effect on the console. it just sits there and 
doesn't undergo any kind of reset/reboot/power cycle.

I had been wondering if my problem is down to the high usage of the 
USB/Ethernet channel. I have three cameras running (each using 
mjpg-streamer to grab/stream frames) plus weewx, also the ethernet data 
rate is high, because the pi's root file system is held on my network NAS 
server. On the other hand, the camera "links" are never broken, it's always 
the WX station, so maybe it's something to do with Python's USB code, or 
this console's handing of USB, or something else ...

I guess I'll go down the syslog-monitoring route suggested by Glenn 
(thanks!) as a reboot once a week-ish isn't a big deal.

Cheers

On Wednesday, October 19, 2016 at 9:57:48 PM UTC+2, mwall wrote:
>
> On Wednesday, October 19, 2016 at 3:38:55 PM UTC-4, Macha wrote:
>>
>> So, 3 Logitech webcams and a WX station. The station is a WEA22 from 
>> WeatherEye (now only £55 from Amazon!). The console is self-powered and 
>> connected directly to USB (no hub).
>>
>
> are there batteries in the weather station console?
>
> when you reboot the pi, does that power cycle the weather station console?
>  
>

-- 
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: Please can I have my bug back?

[Macha]

Hi,

Thanks for the responses! I'll answer as many questions as I can ..

The RPi (meteopi) running the weather station is part of a small "pi-stack" 
housed in a case. It's powered from a 18V switched mode supply, regulated 
down to 5V by a buck converter. I've checked the voltage on meteopi with a 
scope and it's a tad over 5V, with very little ripple and no "sag". It has 
all USB ports connected. Here's the lsusb output ...

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 

Bus 001 Device 004: ID 046d:0809 Logitech, Inc. Webcam Pro 9000

Bus 001 Device 005: ID 046d:0809 Logitech, Inc. Webcam Pro 9000

Bus 001 Device 006: ID 1941:8021 Dream Link WH1080 Weather Station / USB 
Missile Launcher

Bus 001 Device 007: ID 046d:0826 Logitech, Inc.

So, 3 Logitech webcams and a WX station. The station is a WEA22 from 
WeatherEye (now only £55 from Amazon!). The console is self-powered and 
connected directly to USB (no hub). One other point worth noting is that 
the root file system is held on my network server, not on the SD card.

The raspbian op system is ...

wheezy - 3.18.7-v7

Python version is 2.7.3 and I seem to have versions 0.1.4 and 1.0.0 of 
libusb installed - presumably the latter is used. pyusb appears to be 0.4.3.

I've attached a copy of my weewx.conf, but the relevant parts are ...

[FineOffsetUSB]

# This section is for the Fine Offset series of weather stations.



# The station model, e.g., WH1080, WS1090, WS2080, WH3081

model = WEA22



# How often to poll the station for data, in seconds

polling_interval = 60



# The driver to use:

driver = weewx.drivers.fousb


[StdArchive]



# If the station hardware supports data logging then the archive 
interval

# will be downloaded from the station. Otherwise, specify it (in 
seconds).

archive_interval = 300



# How long to wait (in seconds) before processing new archive data. Must

# be greater than zero.

archive_delay = 15



# If possible, new archive records are downloaded from the station

# hardware. If the hardware does not support this, then new archive

# records will be generated in software.

# Set the following to "software" to force software record generation.

record_generation = software



# Whether to include LOOP data in hi/low statistics

loop_hilo = True



# The data binding used to save archive records

data_binding = wx_binding

When the "lockup" occurs (perhaps a better description is "lockout"), a RPi 
reboot fixes it, there's no need to do anything to the console, and as 
previously mentioned, it happens about once/twice a week.

I hadn't even begun to think about how I'd monitor syslog, but the rsyslog 
idea is great - I wouldn't have thought of doing it that way ... 

Once again, thanks for the interest, I really appreciate it.


On Wednesday, October 19, 2016 at 10:12:19 AM UTC+2, Macha wrote:
>
> Well, not really I suppose, but ...
>
> Some time ago I commented that my setup (Raspberry Pi + W1080 clone) 
> "crashed" weewx from time to time. I found that restarting weewx didn't 
> help because it couldn't read from the Console. So, I had this cron job 
> which checked if weewx was running. If not, the RPi was rebooted and things 
> worked fine until the next time. This event happened, on average, once a 
> week.
>
> Now, after upgrading to V3.6.0, this kind-of-lockup still occurs, but 
> weewx doesn't crash and simply reports to syslog ...
>
> Caught WeeWxIOError: Cannot determine archive interval
>
>
> ... each 60 seconds.
>
>
> So I still need to "trap" this error in order to reboot the RPi (I have 
> tried many things to "reset" the USB link to the console, but haven't found 
> any solution other than a reboot). The only thing I can think of is to 
> periodically scan syslog and reboot if this message turns up.
>
>
> Is there any other way I can flag weewx errors other than syslog?
>
>
>

-- 
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 CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer <tkef...@gmail.com>
# 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 = 0

# Root directory of the weewx data file hierarchy for 

[weewx-user] Please can I have my bug back?

[Macha]

Well, not really I suppose, but ...

Some time ago I commented that my setup (Raspberry Pi + W1080 clone) 
"crashed" weewx from time to time. I found that restarting weewx didn't 
help because it couldn't read from the Console. So, I had this cron job 
which checked if weewx was running. If not, the RPi was rebooted and things 
worked fine until the next time. This event happened, on average, once a 
week.

Now, after upgrading to V3.6.0, this kind-of-lockup still occurs, but weewx 
doesn't crash and simply reports to syslog ...

Caught WeeWxIOError: Cannot determine archive interval


... each 60 seconds.


So I still need to "trap" this error in order to reboot the RPi (I have 
tried many things to "reset" the USB link to the console, but haven't found 
any solution other than a reboot). The only thing I can think of is to 
periodically scan syslog and reboot if this message turns up.


Is there any other way I can flag weewx errors other than syslog?


-- 
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: FO USB

[Macha]

You have to be a bit cautious above (my) anecdotal evidence. Before this 
WEA22, I got an identical-looking station of Amazon which packed up after a 
month, as did its replacement sender unit. I sent it all back and got this 
one.

Luck of the draw perhaps 

On Friday, September 23, 2016 at 1:35:02 PM UTC+2, pon...@gmail.com wrote:
>
> Looks identical. 
>
> And only £59.99 on Amazon! I've toyed with the idea of getting a second 
> one and streaming data for both to MySQL and then eliminating duplicate 
> records* ; wondered if it might be a simpler and more effective way of 
> guaranteeing gap-free data. Some of the suggestions here re powered USB 
> hubs don't seem entirely convincing
>
> *not very seriously -- the spouse eyeball rotation factor is a 
> consideration
>
>

-- 
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: FO USB

[Macha]

That's interesting - I've never had that, just the weewx crash.

My station is a WEA22 from Weathereye, which I believe is a W1080 type, so 
it looks like it's down to chance.

The station has been in operation for about 3 years and has performed OK - 
even surviving a mauling by a herd of Sanglier (that sort of thing happens 
around here).


On Thursday, September 22, 2016 at 9:21:56 PM UTC+2, pon...@gmail.com wrote:
>
> When it happens to me it's the WH1080 USB and not the Pi, and resetting 
> the Pi makes no difference. The only solution is to remove the batteries 
> and lose the data collected between when the problem occurred and that 
> point.
>

-- 
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: FO USB

[Macha]

Hi,

Thanks for replying.

I've had this station for about 3 years and this behaviour has been there 
from day 1.

I think I've pretty much exhausted all possibilities actually. In the early 
days I tried a powered USB hub - no joy.

I've now got this RPi in a stack with two others - fed with a bomb-proof 5V 
supply. I've looked at the supply line with both a digital VM and a 'scope 
for each RPi. Volts are dead on 5-and-a-bit after the polyfuse and ripple 
is very low.

So, I guess it's down to "life's rich tapestry" and a quirk of this 
particular station. In fact it's not too troublesome, booting a couple of 
times a week is no big deal, esp. as I store the root filesystem for this 
Rpi on my NFS, so it doesn't even stress the SD card too much 

A final thought. I would tend to suspect the RPi as the culprit and not the 
console as the problem goes away (for a while) after a reboot. I've 
sometimes wondered if it's something to do with some weird interaction 
between USB and Ethernet on the RPi as they share the same hardware and 
both are pretty busy (however, it also happened before I migrated to an NFS 
file system, so maybe not).

Cheers,

On Sunday, September 18, 2016 at 2:26:28 PM UTC+2, mwall wrote:
>
> On Sunday, September 18, 2016 at 5:24:47 AM UTC-4, Macha wrote:
>>
>> I have a W1080-type station (actually marked "WEA22") connected to a RPi 
>> V2. The station console is connected directly to the RPi's USB, together 
>> with 2 webcams.
>>
>
> this is probably your problem.
>
> use a powered usb hub for the station and see if that makes your failures 
> go away.
>
> the fine offset stations are *very* sensitive to usb power, and the rpi is 
> not very good at providing stable usb power.
>
> 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] FO USB

[Macha]

Hello,

It's me again 

I don't know if this helps in understanding FO USB lockups (just ignore if 
not ... )

I have a W1080-type station (actually marked "WEA22") connected to a RPi 
V2. The station console is connected directly to the RPi's USB, together 
with 2 webcams.

>From time to time (twice a week about) I get what could be described as a 
"lockout" where weewx can't get data from the console. It always starts 
with syslog showing ...

Sep 18 10:57:53 meteopi weewx[13587]: fousb: get_observations failed: bad 
pointer: 0x
Sep 18 10:57:53 meteopi weewx[13587]: engine: Shutting down StdReport thread
Sep 18 10:57:53 meteopi weewx[13587]: engine: Caught WeeWxIOError: Max 
retries exceeded while fetching observations
Sep 18 10:57:53 meteopi weewx[13587]:   Waiting 60 seconds then 
retrying...

I then get ...

Sep 18 10:58:53 meteopi weewx[13587]: engine: retrying...
Sep 18 10:58:53 meteopi weewx[13587]: engine: Using configuration file 
/home/weewx-3.5.0/weewx.conf
Sep 18 10:58:53 meteopi weewx[13587]: engine: Loading station type 
FineOffsetUSB (weewx.drivers.fousb)
Sep 18 10:58:53 meteopi weewx[13587]: fousb: driver version is 1.8
Sep 18 10:58:53 meteopi weewx[13587]: fousb: polling mode is PERIODIC
Sep 18 10:58:53 meteopi weewx[13587]: fousb: polling interval is 60
Sep 18 10:58:53 meteopi weewx[13587]: fousb: found station on USB bus=001 
device=006
Sep 18 10:58:53 meteopi weewx[13587]: engine: StdConvert target unit is 0x1
Sep 18 10:58:53 meteopi weewx[13587]: 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
Sep 18 10:58:53 meteopi weewx[13587]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA,maxSolarRad=RS
Sep 18 10:58:53 meteopi weewx[13587]: engine: Archive will use data binding 
wx_binding
Sep 18 10:58:53 meteopi weewx[13587]: engine: Record generation will be 
attempted in 'software'
Sep 18 10:58:53 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0x00
Sep 18 10:58:53 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0x20
Sep 18 10:58:53 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0x40
Sep 18 10:58:54 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0x60
Sep 18 10:58:54 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0x80
Sep 18 10:58:54 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0xa0
Sep 18 10:58:54 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0xc0
Sep 18 10:58:54 meteopi weewx[13587]: fousb: unstable read: blocks differ 
for ptr 0xe0
Sep 18 10:58:54 meteopi weewx[13587]: fousb: unrecognised magic number 
Sep 18 10:58:54 meteopi weewx[13587]: engine: Caught unrecoverable 
exception in engine:
Sep 18 10:58:54 meteopi weewx[13587]:   unsupported operand type(s) 
for *: 'NoneType' and 'int'
Sep 18 10:58:54 meteopi weewx[13587]:   Traceback (most recent call 
last):
Sep 18 10:58:54 meteopi weewx[13587]: File 
"/home/weewx-3.5.0/bin/weewx/engine.py", line 853, in main
Sep 18 10:58:54 meteopi weewx[13587]:   engine = 
EngineClass(config_dict)
Sep 18 10:58:54 meteopi weewx[13587]: File 
"/home/weewx-3.5.0/bin/weewx/engine.py", line 75, in __init__
Sep 18 10:58:54 meteopi weewx[13587]:  
 self.loadServices(config_dict)
Sep 18 10:58:54 meteopi weewx[13587]: File 
"/home/weewx-3.5.0/bin/weewx/engine.py", line 136, in loadServices
Sep 18 10:58:54 meteopi weewx[13587]:  
 self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
config_dict))
Sep 18 10:58:54 meteopi weewx[13587]: File 
"/home/weewx-3.5.0/bin/weewx/engine.py", line 484, in __init__
Sep 18 10:58:54 meteopi weewx[13587]:   if software_interval != 
self.engine.console.archive_interval:
Sep 18 10:58:54 meteopi weewx[13587]: File 
"/home/weewx-3.5.0/bin/weewx/drivers/fousb.py", line 993, in 
archive_interval
Sep 18 10:58:54 meteopi weewx[13587]:   return 
self._archive_interval_minutes() * 60
Sep 18 10:58:54 meteopi weewx[13587]:   TypeError: unsupported 
operand type(s) for *: 'NoneType' and 'int'
Sep 18 10:58:54 meteopi weewx[13587]:   Exiting

In a way this is fortunate, in the sense that I run a cron job to check if 
weewx is running, if not I reboot and the problem goes away until the next 
time.

I don't get the "lockup" in the way where I have to "restart" the console 
(batteries out, etc.), but I haven't found any way to get USB going again 
other than a reboot.

Not really looking for a fix, just 

[weewx-user] Re: archive interval

[Macha]

I think it's possible I've answered my own question.

I did ...

./wee_device --set-interval=5

... and it now reports each 5 minutes.

I don't understand it though. Surely the timings of records stored in the 
station console, the "rate" of saving to the database and the frequency of 
reporting are independent?


On Saturday, September 17, 2016 at 8:12:06 PM UTC+2, Macha wrote:
>
> Hello,
>
> I'm running weewx 3.5.0 on a Raspberry Pi with a WEA22 (an FO W1080 type) 
> directly from the RPi's USB.
>
> I'd like to change the reporting interval - currently each 2 minutes, so I 
> started digging around.
>
> Other than the skin/tmpl files, most things are set to installation 
> defaults. The first thing I noticed was I was getting, in syslog ...
>
> engine: The archive interval in the configuration file (300) does not 
> match the station hardware interval (120).
>
> ... I had record_generation = hardware, so I changed this to "= software"
>
> ... restarted weewx (even rebooted the RPi) but I'm still getting the 
> syslog message and reports are still generated each 2 minutes.
>
> Any ideas?
>
> 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] archive interval

[Macha]

Hello,

I'm running weewx 3.5.0 on a Raspberry Pi with a WEA22 (an FO W1080 type) 
directly from the RPi's USB.

I'd like to change the reporting interval - currently each 2 minutes, so I 
started digging around.

Other than the skin/tmpl files, most things are set to installation 
defaults. The first thing I noticed was I was getting, in syslog ...

engine: The archive interval in the configuration file (300) does not match 
the station hardware interval (120).

... I had record_generation = hardware, so I changed this to "= software"

... restarted weewx (even rebooted the RPi) but I'm still getting the 
syslog message and reports are still generated each 2 minutes.

Any ideas?

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] End of my Tether

[Macha]

You also got ...

failed to execute '/lib/udev/mtp-probe' 'mtp-probe 
/sys/devices/platform/soc/2098.usb/usb1/1-1/1-1.2 1 4': No such file or 
directory

.. what does lsusb return? Does it see the connected usb device?

You could also try ..

sudo apt-get install libmtp-runtime

... to see if it's there.

-- 
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] BASIC question regarding config file

[Macha]

I think it depends on the way you installed it. With my Pi, it shows it 
running as a python task. I always do ..

ps aux | grep wee

.. and it shows the command launching weewx, something like ...

root  4193 13.9  5.4  78352 48232 ?Sl   Sep06 398:00 python 
./bin/weewxd weewx.conf

I use it in a Cron job to reboot the Pi on the odd occasion I get a USB 
lockup and weewx bombs out. Weewx is launched from a @reboot script.




On Thursday, September 8, 2016 at 2:00:31 PM UTC+2, Jim W. wrote:
>
> This is what I get with the ps -a command. For some reason the weewx 
> process does not show up?  
>
> pi@WXraspberrypi:/ $ ps -a
>   PID TTY  TIME CMD
>   933 tty1 00:00:00 bash
>  3310 pts/200:00:00 ps
> 20632 pts/000:00:00 sudo
> 20636 pts/000:00:00 tail
>
> On Thursday, September 8, 2016 at 12:12:48 AM UTC-4, Andrew Milner wrote:
>>
>> Or you can force a .conf reload with a hup 
>> "
>>
>> You can tell a running instance of weewx to reread its configuration 
>> file by sending it the HUP signal. First run ps to find out the Process 
>> ID (PID) number of the instance, then send it the HUP signal: 
>>
>> ps -a  # Note the PID of the weewxd processkill -HUP *pid*  # Send 
>> it a HUP signal
>>
>> Note that this *only* rereads the configuration file. It will not reload 
>> any code.
>> "
>>
>>
>> On Thursday, 8 September 2016 06:16:25 UTC+3, Dave Webb wrote:
>>
>>> You need to stop and restart weewx for it to pick up the changes in 
>>> weewx.conf
>>>
>>> Dave-KB1PVH
>>>
>>> Sent from my Galaxy S7
>>>
>>> On Sep 7, 2016 11:15 PM, "Jim W."  wrote:
>>>
 Does the config file get read once during start up or is it poled 
 continuously? If I make a change in the config file do I have to stop and 
 start weewx? 
 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+...@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: Update to 3.5.0

[Macha]

Hi,

Thanks for replying.

Having (now) read the customisation guide properly (!), it's clear on how 
to add new groups, etc.

As far as the 'ghost' values appearing, the ET value which was appearing in 
LOOP has now disappeared, so for the moment I'm willing to put these things 
down to Gremlins 

Otherwise, things are running just fine (and its sunny at the moment, which 
helps ... )

... now if anyone can think of a good way of recording daily sunshine hours 
without spending ridiculous amounts of cash, I'd be pleased to hear from 
them. The best idea I've heard so far is to attach a small solar panel to 
my Pi's ADC and monitor that ... volts = sun, no volts = no sun ...

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