[weewx-user] Re: Weewx stopped running after 4 days

['Andy Hudson-Smith' via weewx-user]

Thanks for the replies ref hardware and report intervals - I was running on 
a Pi A+ - turns out they halved the ram so its now been moved to a Pi3 and 
its running ok so far. I will look into a longer term upgrade but glad the 
Pi3 seems to be coping.

Andy

On Tuesday, 5 February 2019 08:34:54 UTC, Andrew Milner wrote:
>
> Gary - the point I was really trying to make was that - especially where 
> an RPi is involved - it is likely that one cannot necessarily do all that 
> one wishes - but compromising does not necessarily mean a significant loss 
> of information.  What people often forget is that midnight in particular 
> results in more load for reports as the yearly plots and pages are 
> regenerated together with the monthly, weekly, current etc also and this 
> can result in more issues when small archive intervals are being used. 
>
> I think we are really on the same page Gary, even if I may appear a 
> luddite and a pedant at times.
>
> Andrew
>
>
> On Tuesday, 5 February 2019 07:49:34 UTC+2, gjr80 wrote:
>>
>> I beg to disagree. I learnt a long time ago to not impose my views on a 
>> user's requirements; maybe the user needs to generate a report every 
>> minute, maybe they need to record the number of widgets every minute, maybe 
>> they just like lots of dots in their plots. At the end of the day it does 
>> not matter, WeeWX supports a 1 minute archive interval. Now if a user 
>> chooses to use a 1 minute archive interval that may impose some limits on 
>> the user, but that is a different matter. I know the old chestnut about 
>> wind speeds and directions gets dragged out every now and then. I think we 
>> need to keep in mind that the period over which an observation is made does 
>> not necessarily bear any relationship to how often you may wish to record 
>> the value.
>>
>> Gary
>>
>> On Tuesday, 5 February 2019 14:22:12 UTC+10, Andrew Milner wrote:
>>>
>>> I continue to find it almost impossible to conceive a situation where an 
>>> archive interval of under 5 minutes serves any useful purpose.  As long as 
>>> a gust value is recorded for the 5 minute period the average speed 
>>> value/direction over the period is more than sufficient - even for an 
>>> airfield - and the other readings are unlikely to alter over 5 minutes 
>>> anyway.  So with a Pi a 5 minute interval is more than sufficient.
>>>
>>> I found the following whilst googling wind gust which I thought useful 
>>> since the implication is that wind measurements over short periods of time 
>>> (if the rest of the world is right) are error prone anyway:
>>>
>>> "Wind gusts (which last only a few seconds) make it hard to determine 
>>> the overall wind speed of storms whose winds don't always blow at constant 
>>> speeds. This is especially the case for tropical cyclones and hurricanes. 
>>> To estimate the overall wind speed, the wind and wind gusts are measured 
>>> over some period of time (typically 1 minute) and are then averaged 
>>> together. The result is the highest average wind observed within the 
>>> weather event, also called the *maximum sustained wind speed*. 
>>>
>>> Here in the U.S., maximum sustained winds are always measured by 
>>> anemometers at a standard height of 33 feet (10 m) above ground for a 
>>> duration of 1 minute. The rest of the world averages their winds over a 
>>> period of 10 minutes. This difference is significant because measurements 
>>> averaged over just one minute are about 14% higher than those averaged over 
>>> the course of ten minutes."
>>>
>>>
>>> On Tuesday, 5 February 2019 01:29:23 UTC+2, gjr80 wrote:

 Yes the NoneType error is certainly due to the realtime clientraw 
 extension not handling a None value correctly, by the looks of it a wind 
 related field so quite possibly brought on by your battery/connectivity 
 issue. That extension was written over 2 years ago and never formally 
 released (and judging by the lack of user questions I assume not used by 
 too many). So that means it is probably not too robust. It maybe easiest 
 to 
 just disable it until I can get to have a look at it in the next 2-3 weeks 
 (as per other thread).

 Some good advice above about getting a machine to work reliably, the 
 only thing I would add is chose your archive interval carefully as that 
 also has an impact on stability when you start to add in a number of 
 extensions. A 5 minute archive period means there is 5 minutes between 
 report cycles so arguably WeeWX has around 5 minutes to get all of its 
 report processing completed, cut that down to 1 minute and WeeWX now only 
 has 1/5 the time. You don't want your reports taking longer to run than 
 your archive interval, that would be bad on many fronts. Some folks think 
 that having the shortest possible archive interval is essential, that may 
 be the case in some circumstances but there are other secondary effects 
 that need to be kept 

[weewx-user] Re: V3.9.1

[Pat]

Thanks for the hard work Tom, Matthew and Gary. It is much appreciated! 

On Wednesday, February 6, 2019 at 8:40:34 AM UTC-5, Thomas Keffer wrote:
>
> Well, that was a record short release. We found a serious bug in v3.9.0 
> that could break skins that do not have fonts defined, such as cmon.
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
> -tk
>

-- 
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: Second crash after 11 days

[Steve2Q]

Here is this mornings results. No change in the simulator, but weewx itself 
is going up. I was wondering if it would help with diagnosis if I tried 
running an older driver version.


-- 
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: V3.9.1

[G Hammer]

At last, Felsius.

-- 
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: Second crash after 11 days

[Thomas Keffer]

Well, that's pretty definitive: the problem is in the driver, or its
underlying libraries.

Can you check what version of pyserial you are using:

*python -c "import serial; print serial.VERSION"*

I get "3.4"

-tk

On Wed, Feb 6, 2019 at 6:56 AM Steve2Q  wrote:

> Here is this mornings results. No change in the simulator, but weewx
> itself is going up. I was wondering if it would help with diagnosis if I
> tried running an older driver version.
>
>
> --
> 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.
>

-- 
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: NOAA reports not available

[mwall]

On Tuesday, February 5, 2019 at 4:34:24 PM UTC-5, Glenn McKechnie wrote:
>
> With hindsight in full, a search on weewx-user returns  a couple of 
> hits, 2 of interest are... 
> https://groups.google.com/d/topic/weewx-user/k3yy2IK__Ow/discussion 
> https://groups.google.com/d/topic/weewx-user/p1AYCf0KkxI/discussion 
>
> It appears that it's cropped up before and Mathew may still want to 
> know about this? 
>

i just tested forecast 3.3.2 with the Seasons skin.  the NOAA menus work 
fine.  this is what the iconic forecast looks like embedded in the Seasons 
skin:

https://github.com/weewx/weewx/wiki/forecasting#forecast-data-in-the-seasons-skin

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] V3.9.1

[Thomas Keffer]

Well, that was a record short release. We found a serious bug in v3.9.0
that could break skins that do not have fonts defined, such as cmon.

So, we are releasing v3.9.1, found in the usual place
.

-tk

-- 
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: V3.9.1

[Andrew Milner]

Nah - it's just an American variation of a most of the world standard!!



On Wednesday, 6 February 2019 20:50:41 UTC+2, Colin Larsen wrote:
>
> Had to Google that, thought it was a typo :)
>
> On Thu, 7 Feb 2019, 03:45 G Hammer  
> wrote:
>
>> At last, Felsius.
>>
>> -- 
>> 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: V3.9.1

[vince]

On Wednesday, February 6, 2019 at 5:40:34 AM UTC-8, Thomas Keffer wrote:
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
>
>
Updated my github repos for building this in Docker or Vagrant for a 
variety of operating systems (debian, ubuntu, centos6, centos7), using the 
simulator driver.

Repos are https://github.com/vinceskahan/weewx-vagrant and 
https://github.com/vinceskahan/weewx-docker if you have interest 

-- 
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: Integrate data from separate device into weewx

[Michi Kaa]

Nevermind, found it, thx. 
http://www.weewx.com/docs/customizing.htm#Adding_2nd_source

Am Montag, 4. Februar 2019 16:05:51 UTC+1 schrieb Michi Kaa:
>
> I think I've understood the point of your posting but stll need a little 
> bit of an input, since I don't really understand what a REC event is, how 
> to configure one an how to bind it. Is this all pointed out in the 
> user/customisation guide? Where can I find further explanation?
>
> Am Montag, 4. Februar 2019 15:22:24 UTC+1 schrieb Andrew Milner:
>>
>> You could have your task create a text file and have a service that binds 
>> to a REC event, reads the text file and adds the radiation to the archive 
>> record.  Weewx would then take care of the daily stats in 
>> archive_day_radiation for you.
>> Alternatively your service could still bind to the REC, but instead of 
>> reading the text file it could retrieve via the API the current radiation 
>> value and thus do away with the cron task altogether.
>>
>>
>>
>> On Monday, 4 February 2019 13:27:27 UTC+2, Michi Kaa wrote:
>>>
>>> Hi,
>>>
>>> I run weewx on a raspberryPi with a WS28xx station. I also have a 3kW 
>>> peak solar panel on the roof of my house. The solar power inverter logs a 
>>> lot of data which can be read over a JSON API. So what I am doing right now 
>>> is running a cron job every 5min that looks into the weewx database for 
>>> archive entries without a radiation value, then asks the inverter for the 
>>> values for that particular time window and stores it into weewx database 
>>> and calculate archive_day_radiation also (is this calculation needed or is 
>>> it made automatically, when "radiation" column in "archive" table has 
>>> values?).
>>>
>>> This works. But is there an "official" way to do things like that?
>>>
>>>
>>>

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

[weewx-user] Re: weewx 3.8.0 in raspbian & WH2600

[Radek Dohnal]

Hi Tomáš.
Please, can you write correct setup how to configure weewx on RspPi for 
WH2600. My target is to get data from WH2600 to Grafana charts.

-- 
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: V3.9.1

[Phil Green]

Just installed v3.9.1 by apt-get method. Removed 3.8.2 but kept the database. 
V3.9.1 is excellent, I like the new skin!
Obviously some of the graphics haven’t updated yet on the other pages.
I like most of the common customisations being in Weewx.conf.

Have a look:- http://g0elm.dynalias.com:85/weewx/index.html

Regards
Phil





-- 
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: Beta testers for v3.9.0 needed

[Sef Konings]

Hi Matthew and Tom,

I have tried your solution to adapt the file genplot.py, that solved the 
problem adequately!
You only have to remove the  after the or statement! The cmon graphs are 
working too now! Thanks for your tips and solution!
I understand that this caused a new release of weewx... I will upgrade  to the 
new version asap
I have one more question, what is needed to enable the windrose graph in weewx, 
or is this part of the new skin?

Thanks!
Regards, Sef

-- 
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: NOAA reports not available

[mwall]

another data point:  forecast 3.3.2 works fine with the standard skin, as 
show in the attached screenshot.

i included the forecast by adding two lines to index.html.tmpl in the 
Standard skin:

  


#include "forecast_compact.inc"


  
Current Conditions
  

the NOAA menus work properly.

-- 
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: V3.9.1

[Colin Larsen]

Had to Google that, thought it was a typo :)

On Thu, 7 Feb 2019, 03:45 G Hammer  At last, Felsius.
>
> --
> 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.
>

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

[weewx-user] Re: Weewx stopped running after 4 days

[vince]

On Wednesday, February 6, 2019 at 5:51:15 AM UTC-8, Andy Hudson-Smith wrote:
>
> Thanks for the replies ref hardware and report intervals - I was running 
> on a Pi A+ - turns out they halved the ram so its now been moved to a Pi3 
> and its running ok so far. I will look into a longer term upgrade but glad 
> the Pi3 seems to be coping.
>
>
>
Andy - FWIW, I'm running weewx on a Seagate Dockstar (an original 
SheevaPlug, just with half the memory - only 128MB) and it runs literally 
years with no problems, but I 'did' run into problems previously when I 
loaded it up with things like weewx-wd and the Saratoga templates etc.   
Some of the extensions and complicated skins can really pound an 
underpowered system into the ground if you're not careful.

Moving your storage out to non-SD media will also help speed things up a 
lot.  If you get a pi3 or (better yet) a pi3b+ you can even boot off 
external SSD with 'no' SD at all on the system, assuming you have a good 
power supply so the disk gets appropriately powered.  I've had one running 
my WeatherFlow UDP based site for a number of months now.  Just plain 
works, if you power it sufficiently.

-- 
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: Second crash after 11 days

[Steve2Q]

Tom: I upgraded pyserial and have rebooted. I will run just the regular 
instance of weewx without the simulator, and will see how that goes. Weewxd 
started at 3.4% mem usage.

-- 
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: Second crash after 11 days

[Thomas Keffer]

That's the version that's included in the debian package python-serial.

Looking through the pyserial change log
, I don't see
any obvious patches for memory leaks between v3.2.1 and v3.4.

The only major difference (besides API details) I see between the Ultimeter
and the Vantage drivers, is that the former uses the method readline(),
instead of read(), but it's hard to see how that would lead to leaks.

You can try upgrading to v3.4 and see if that helps. First remove the
Debian package, then use pip:

*sudo apt remove python-serial*
*sudo pip install pyserial*

-tk


On Wed, Feb 6, 2019 at 7:19 AM Steve2Q  wrote:

> My version is 3.2.1
>
> --
> 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.
>

-- 
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: Beta testers for v3.9.0 needed

[Juan Antonio Mosquera]

I upgraded!,

first problem is units!, units default change in my weewx.conf i think... 

I changed units in group and all OK. 

I use Belchertown Skin... and today upgrade 3.9.0 to 3.9.1.

Thanks.

El martes, 22 de enero de 2019, 21:05:24 (UTC+1), Thomas Keffer escribió:
>
> It's been well over a year since the last "dot" release, but the V3.9 
> release is finally in sight!
>
> We have a beta version, and can use some help testing it out. The biggest 
> new feature is the new skin, *Seasons*, to replace the venerable 
> *Standard*, which has shipped since v1.0! Using the new skin is entirely 
> optional.
>
> There have also been some changes in how report options are chosen, the 
> net effect being that you will be able to specify a unit system to be 
> applied to *all* reports, or just to individual reports.
>
> I've been running v3.9 for 6 months on my home machine, so it appears to 
> be very stable. We can just use some help to see if there are any sharp 
> edges left.
>
> You can find the release candidate, v3.9.0b1 is the usual place: 
> http://weewx.com/downloads/development_versions/
>
> Thanks, all!
>
> -tk
>

-- 
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: Second crash after 11 days

[Steve2Q]

My version is 3.2.1

-- 
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: SDR, rtl_433, WH65B, and WH32B

[G Hammer]

Updated to 3.9.1, installed the weewx_sdr driver, edited the config file, 
started weewx, presto!
All looks good on my website and the various services I report to.

I'll monitor it for any unusual behavior, but it looks good right now.

I do see this logged each time I use the driver directly or when weewx 
starts. No harm that I notice, weewx runs and the data is captured.
Feb  6 22:22:16 weewx1 upowerd[1536]: unhandled action 'bind' on /sys/
devices/pci:00/:00:1a.7/usb1/1-5/1-5:1.0



On Wednesday, February 6, 2019 at 6:36:39 PM UTC-5, Tor rin wrote:
>
> I was happy to help, good luck with the rest of the configuration, I have 
> mine working fairly seamlessly now. 
>
> On Wed, Feb 6, 2019 at 5:23 PM G Hammer > 
> wrote:
>
>> Thanks to Matthew and Tor for the idea of getting data via an SDR and for 
>> assisting in getting the WH65B and WH25B recognized.
>> I have the data flowing now and will configure WeeWX to use it later this 
>> evening.
>> Finally, no more sniffing WiFi, which has been the bane of my existence 
>> for months what with router/PWS combo that just do not want to play well 
>> together.
>> This is MUCH simpler than hostapd and dnsmasq configuration. Personally, 
>> I'd recommend this method over sniffing for anyone who can't do a simple 
>> redirect of their data.
>>
>>
>>
>> On Saturday, February 2, 2019 at 4:30:48 PM UTC-5, tor...@torrin.org 
>> wrote:
>>>
>>> Yup, but I am seeing and error and not capturing any data from the 
>>> WH32B.  I created an issue, but no one has picked it up yet.  I will post 
>>> back if I get anywhere.
>>>
>>> On Saturday, February 2, 2019 at 3:28:34 PM UTC-6, G Hammer wrote:

 That may be just the ticket until the 32B is supported.
 So, you've done the steps to get a new device added?

 On Saturday, February 2, 2019 at 4:15:49 PM UTC-5, tor...@torrin.org 
 wrote:
>
> I have been researching this and I cannot find the WH32B either on 
> 915mhz (which it is supposed to be on) or 433mhz.  I am working with the 
> rtl_433 folks trying to figure it out.  In the mean time, I picked up a 
> WH25, which is supported in rtl_433 and is only $16 at AW.
>
 -- 
>> 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/MZFK9sJvg3s/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.
>>
>

-- 
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: SDR, rtl_433, WH65B, and WH32B

[Tor rin]

I was happy to help, good luck with the rest of the configuration, I have
mine working fairly seamlessly now.

On Wed, Feb 6, 2019 at 5:23 PM G Hammer  wrote:

> Thanks to Matthew and Tor for the idea of getting data via an SDR and for
> assisting in getting the WH65B and WH25B recognized.
> I have the data flowing now and will configure WeeWX to use it later this
> evening.
> Finally, no more sniffing WiFi, which has been the bane of my existence
> for months what with router/PWS combo that just do not want to play well
> together.
> This is MUCH simpler than hostapd and dnsmasq configuration. Personally,
> I'd recommend this method over sniffing for anyone who can't do a simple
> redirect of their data.
>
>
>
> On Saturday, February 2, 2019 at 4:30:48 PM UTC-5, tor...@torrin.org
> wrote:
>>
>> Yup, but I am seeing and error and not capturing any data from the
>> WH32B.  I created an issue, but no one has picked it up yet.  I will post
>> back if I get anywhere.
>>
>> On Saturday, February 2, 2019 at 3:28:34 PM UTC-6, G Hammer wrote:
>>>
>>> That may be just the ticket until the 32B is supported.
>>> So, you've done the steps to get a new device added?
>>>
>>> On Saturday, February 2, 2019 at 4:15:49 PM UTC-5, tor...@torrin.org
>>> wrote:

 I have been researching this and I cannot find the WH32B either on
 915mhz (which it is supposed to be on) or 433mhz.  I am working with the
 rtl_433 folks trying to figure it out.  In the mean time, I picked up a
 WH25, which is supported in rtl_433 and is only $16 at AW.

>>> --
> 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/MZFK9sJvg3s/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] weewx opensuse rpm files

[MIchael Cumbee]

 I have been using weewx  for several years and needed to move to another 
server. It is a 32 bit box running opensuse tumbleweed, which is a rolling 
release. I first installed 3.8 and the rpm failed at some point due to a 
scriplet error. when I tried to uninstall it says not there when I try to 
install it says it is already there.  The solution I chose was to grab 3.9 
and run an Upgrade. Well it gave the same error and the same problem. All 
of the basic files are there but I have the following issues:

1) opensuse has never used var for the web server directory and even on 3.6 
I had to move the files from there to the server root. SUSE uses 
/srv/www/htdocs/(your servers directory) 
2) On this version(tumbleweed) the rc files will not start but I found the 
systemd stuff on github  (thankyou)
3) I am not sure what was left undone other than the server root directory 
did not install in /var

Weewx is not running yet but I am going to try to manually repair whatever 
is stopping it as right now I dont know what else to do.

These are the messages that I got during the process


saving previous config as /etc/weewx/weewx.conf-3.8.2
merging configs into /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf-3.8.2
Saved configuration to /etc/weewx/weewx.conf
redirecting to systemctl stop weewx.service
Failed to stop weewx.service: Unit weewx.service not loaded.
redirecting to systemctl start weewx.service
Failed to start weewx.service: Unit weewx.service not found.
warning: %post(weewx-3.9.0-1.suse.noarch) scriptlet failed, exit status 5

 rpm -e  weewx-3.9.0-1.suse.noarch.rpm
error: package weewx-3.9.0-1.suse.noarch.rpm is not installed

More info: The machine is an old dell with 4gb ram. It is running opensuse 
tumbleweed  32 bit in headless mode.


Any suggestions are appreciated!!

-- 
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: V3.9.1

[Sef Konings]

Today I have upgraded my station to Weewx 3.9.1
Everything is now working without any problem, also the cmon graphs are 
available again !

Many thanks for your quick solution for my problem !

Kind regards,
Sef  Konings
Echt (NL)


Op woensdag 6 februari 2019 14:40:34 UTC+1 schreef Thomas Keffer:
>
> Well, that was a record short release. We found a serious bug in v3.9.0 
> that could break skins that do not have fonts defined, such as cmon.
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
> -tk
>

-- 
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: SDR, rtl_433, WH65B, and WH32B

[G Hammer]

Thanks to Matthew and Tor for the idea of getting data via an SDR and for 
assisting in getting the WH65B and WH25B recognized.
I have the data flowing now and will configure WeeWX to use it later this 
evening.
Finally, no more sniffing WiFi, which has been the bane of my existence for 
months what with router/PWS combo that just do not want to play well 
together.
This is MUCH simpler than hostapd and dnsmasq configuration. Personally, 
I'd recommend this method over sniffing for anyone who can't do a simple 
redirect of their data.



On Saturday, February 2, 2019 at 4:30:48 PM UTC-5, tor...@torrin.org wrote:
>
> Yup, but I am seeing and error and not capturing any data from the WH32B.  
> I created an issue, but no one has picked it up yet.  I will post back if I 
> get anywhere.
>
> On Saturday, February 2, 2019 at 3:28:34 PM UTC-6, G Hammer wrote:
>>
>> That may be just the ticket until the 32B is supported.
>> So, you've done the steps to get a new device added?
>>
>> On Saturday, February 2, 2019 at 4:15:49 PM UTC-5, tor...@torrin.org 
>> wrote:
>>>
>>> I have been researching this and I cannot find the WH32B either on 
>>> 915mhz (which it is supposed to be on) or 433mhz.  I am working with the 
>>> rtl_433 folks trying to figure it out.  In the mean time, I picked up a 
>>> WH25, which is supported in rtl_433 and is only $16 at AW.
>>>
>>

-- 
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: V3.9.1

[G Hammer]

Thank you for the nice update! Just installed and all is well for me.
Now, I'm off to install the SDR driver and get that operating, but wanted 
to get WeeWX updated first.


On Wednesday, February 6, 2019 at 8:40:34 AM UTC-5, Thomas Keffer wrote:
>
> Well, that was a record short release. We found a serious bug in v3.9.0 
> that could break skins that do not have fonts defined, such as cmon.
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
> -tk
>

-- 
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: build a multi-sensor data collector using rpi and sdr

[G Hammer]

Matthew,

I have installed this and it works a treat.
I do get this logged when I run the driver directly or when weewx starts.
I see no hram, weewx runs, data is captured, etc. Just the log entry.

Feb  6 22:22:16 weewx1 upowerd[1536]: unhandled action 'bind' on /sys/
devices/pci:00/:00:1a.7/usb1/1-5/1-5:1.0


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