[weewx-user] Re: Looking for reliable weather station -- reliably working with WeeWX

2018-05-18 Thread Craig Thom
I am also using an Acurite 5-in-1 (and eight additional sensors (including 
the lightning sensor)) connected to a Raspberry Pi.

rtl_sdr is the tuner, and rtl_433 uses rtl_sdr to receive and decode 
packets from known devices, including the Acurite ones.  Then the WeeWX SDR 
driver uses rtl_433 to read the data.

The only catch is that you lose the pressure sensor if you bypass the 
Acurite display or hub or Access, since that's where the pressure sensor 
is.  I bought a BMP280 breakout board and wrote a WeeWX service to read it 
(using i2c, because I couldn't get my SPI Python code to work, and I didn't 
want to use someone else's code).  It's possible there's a 433 MHz pressure 
sensor, which would be a lot easier.

On Wednesday, May 16, 2018 at 7:46:05 PM UTC-4, Max G wrote:
>
> :) OK, if I understand you correctly, there is a hardware interface of 
>> sort required between the weather station and the computer...
>>
> I have got a 433MHz dongle... :) what software do you use do decode the 
> signal? Where does it run on? Raspberry? 
>
>
>  
>

-- 
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: WU API ?

2018-05-18 Thread Craig Thom
The free API key is good for a maximum of 10 calls per minute and 500 per 
day.  That's not enough for commercial use, or at least commercial use that 
could justify paying for a higher tier.

On Friday, May 18, 2018 at 4:01:56 AM UTC-4, Andrew Milner wrote:
>
> I shall wait and see.  I would expect them to continue to allow use of api 
> for your own weather station, but I can understand the reasons for 
> limitations (as there always have been) on the uses which used to be part 
> of other plans.  I am sure there are many 'users' who are really commercial 
> who are ripping off WU with there requests for data and trying to get the 
> data for free when they shouldn't be.
>
> So I'm not panicking just yet
>
>
>
> On Friday, 18 May 2018 10:49:36 UTC+3, gjr80 wrote:
>>
>> Andrew,
>>
>> You need to log out of WU, for non-WU user that page was the entry into 
>> the WU API, for logged in WU users it takes you to your analytics page. The 
>> non-WU users it now gives a blurb about The Weather Company 'series of data 
>> packages'. They are light on detail and whilst the don't indicate they are 
>> paid for they certainly don't indicate they are free either.
>>
>> Other links of interest:
>>
>> The wxforum.net thread:  http://www.wxforum.net/index.php?topic=34403.0
>>
>> Thread in WU API Community forum:  
>> https://apicommunity.wunderground.com/weatherapi/topics/weather-underground-api-changes
>>
>> See there is something in the API community thread about the smallest 
>> data package being $850 per month.
>>
>>
>> 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: Realtime updates for custom display

2018-05-18 Thread Thomas Keffer
On Fri, May 18, 2018 at 9:57 AM, John Patrick Hoke  wrote:

> I have accomplished *something* similar using Meteotemplate on my website
> - WeeWX sends via Meteotemplate APIs data from every LOOP packet and Meteo
> has a plugin that would build someothing similar to what you are looking
> for, but weeWX itself (AFAIK) cannot do what you are describing directly
> from LOOP data
>
>
​WeeRT  can, although it would require
some skill to install and administer.​ Sample site
.

-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: Steel Guages and driver update question

2018-05-18 Thread Steve Meltz
Well, some of the problem may have been typos on my end. I know just enough
about Linux to be dangerous. While i have no problem with weewx and have
nothing but kudos for you, Tom, Andrew, Vince and others that spend so much
time helping, I always thought it would be nice if there was some
"cookbook" descriptions on how to do certain things. Weewx was never meant
to be plug-and-play, but sometimes a "do A, then B, then C" approach is
useful. Just MHO.

Again..thanks..i will try to implement the WU portion later. Kind of sucks
that they take our data and then turn around and ask use to pay to use it.


Steve

On Fri, May 18, 2018, 3:46 PM gjr80  wrote:

> Yes, appears to be working. Whilst upgrading the SteelSeries Gauges
> themselves threw the spanner in the works this time, upgrading the Gauges
> and rtgd should haven far easier than it was, will look at that. Re WU, if
> you have an API key  it will work, for the time being, if you don't have an
> API key it appears you can no longer get one hence no WU sourced forecast
> data. I will look at supporting other forecast sources in rtgd in the
> future.
>
> Gary
>
> --
> 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/reHbE13IoyU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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


Re: [weewx-user] Re: Steel Guages and driver update question

2018-05-18 Thread gjr80
Yes, appears to be working. Whilst upgrading the SteelSeries Gauges themselves 
threw the spanner in the works this time, upgrading the Gauges and rtgd should 
haven far easier than it was, will look at that. Re WU, if you have an API key  
it will work, for the time being, if you don't have an API key it appears you 
can no longer get one hence no WU sourced forecast data. I will look at 
supporting other forecast sources in rtgd in the future.

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: Steel Guages and driver update question

2018-05-18 Thread Steve2Q
THANK YOU!! Every thing looks great now. My next step will be to do the 
upgrade of Weewx itself (I still haven't convinced myself it I should). As 
for the banner in the Steel Gauges; I was thinking of activating the 
section to show forecasts from WU, but from reading some other posts, it 
seems like they stopped using the API. Is this correct?

Steve

On Friday, May 18, 2018 at 3:06:05 PM UTC-4, gjr80 wrote:
>
> Steve,
>
> Looking at gauges.js all I think you need do is change the 
> realTimeUrlWeewx setting so that it picks up you rtgd generated 
> gauge-data.txt in the gauges directory, perhaps setting it to 
> '../gauges/gauge-data.txt'
>
> Make sure you make the change to gauges.js in your skins/ss/scripts 
> directory on your weeWX machine them restart weeWX and it should pickup the 
> changes on the next report cycle.
>
> 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: Steel Guages and driver update question

2018-05-18 Thread gjr80
Steve,

Looking at gauges.js all I think you need do is change the realTimeUrlWeewx 
setting so that it picks up you rtgd generated gauge-data.txt in the gauges 
directory, perhaps setting it to '../gauges/gauge-data.txt'

Make sure you make the change to gauges.js in your skins/ss/scripts directory 
on your weeWX machine them restart weeWX and it should pickup the changes on 
the next report cycle.

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: Steel Guages and driver update question

2018-05-18 Thread Steve2Q
Hi Gary..I'm back! Finally got the web server back on line. All I have done 
so far was to change gauges.js to change the update internal from 15 
seconds to 2, added the wind rose, and deleted the two solar gauges. As you 
can see, there are still problems, but I am not going to touch anything 
else until you get back to me.

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.


Re: [weewx-user] Re: Cydia pomonella

2018-05-18 Thread hesfrrkr
following change

in line 548 #if rec['dd_cumulative'].raw > horizon_dd:  <<---   


for rec in result:
remarks = []
while horizon_labels:
(horizon_dd, horizon_event) = horizon_labels[ZERO]
#if rec['dd_cumulative'].raw > horizon_dd:  <<---   
cydiaA = rec['dd_cumulative'].raw
if cydiaA > horizon_dd:
remarks.append(horizon_event)
horizon_labels.pop(ZERO)
else:
break
val_t = ValueTuple('; '.join(remarks), None, None)
rec['remark'] = weewx.units.ValueHelper(val_t, 'day', 
self.formatter, self.converter)
return result


*only the "C_pomonella.html"**is not generated   *  
 



finally have a look at http://wetter.hes61.de/index1.html the y-scale is 
degree_C

Thanks!
Hartmut

-- 
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] WU API ?

2018-05-18 Thread Clay Jackson
So, perhaps we should consider not giving away our data

Sent from my iPhone
Clay Jackson


> On May 17, 2018, at 6:48 AM, Thomas Keffer  wrote:
> 
> Funny how they are only too happy to take our user-generated data for free, 
> but make you pay to get it back.
> 
>> On Thu, May 17, 2018 at 1:30 AM, gjr80  wrote:
>> I guess we are all aware of the issues that have plagued WU for some time. I 
>> have stuck with them, uploading data and downloading various pieces of data 
>> via their API, it's just kept on working for me. I noticed a post on 
>> wxforum.net re WU no longer issuing API keys, I found this on WU.
>> 
>> https://www.wunderground.com/weather/api/
>> 
>> Maybe some folks more acquainted with WU/The Weather Company/The Weather 
>> Channel might have more info. There is nothing I found to indicate the cost 
>> of whatever replaces the API, when I followed the various links I just went 
>> around in corporate double speak circles.
>> 
>> Looking like the the forecast extension might need a version 4.
>> 
>> 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.
> 
> -- 
> 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: WU API ?

2018-05-18 Thread John Patrick Hoke
https://apicommunity.wunderground.com/weatherapi/topics/weather-underground-api-changes

And in the thread they confirm that you are going to have to pay to
retrieve (via API) the data your PWS provides ... I use WU data for other
projects (Home Automation for example) so if I cannot get at the data I am
providing ... well... I will provide it elsewhere and move away from WU

Its pretty conterproductive to do this on their part, if they are
monetizing the data, why cut off (piss off) your inbound data streams for
hyperlocal info

On Fri, May 18, 2018 at 12:32 PM, vince  wrote:

> On Friday, May 18, 2018 at 2:35:22 AM UTC-7, JHoke wrote:
>>
>> Based on the below info, it looks like I will be sitting down to finally
>> write something to get the data from my local database to use for home
>> automation, irrigation, etc instead of the Wunderground API - i find it
>> rediculous to charge users to access the data they freely give but what do
>> I know ;(
>>
>> From their forum regarding a question if we will still have access to our
>> data via the API:
>>
>>
> Can you guys provide a couple links to the original announcements please
> ?  I couldn't find anything on their site.
>
> I saw some cryptic stuff saying WeatherBug was bought or something with
> references to CWOP and use of the term 'PWS', but each company overloads
> their terminology so much that it's hard to tell in layman's term what's
> going away or changing when.
>
> FWIW, I feed PWSweather/CWOP/WU using weewx, but use NWS for the forecast
> (although I have a WU API key that I used to play with in the past).
>
> --
> 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.
>



-- 
John P. Hoke
j...@hoke.org
https://hoke.org/john /
Random Non-Sequiturs & Photography

-- 
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: Realtime updates for custom display

2018-05-18 Thread John Patrick Hoke
I have accomplished *something* similar using Meteotemplate on my website -
WeeWX sends via Meteotemplate APIs data from every LOOP packet and Meteo
has a plugin that would build someothing similar to what you are looking
for, but weeWX itself (AFAIK) cannot do what you are describing directly
from LOOP data



On Fri, May 18, 2018 at 12:50 PM, Bruce Huddleston 
wrote:

> I'll try to describe what I'm wanting to do a little better. I have a
> Raspberry Pi connected to the 7" touchscreen. It displays a single webpage
> that has 6 observation values from an Airmar 150WX sensor. I added the
> RWYplotgenerator (great addon for my purposes) to the template and the
> webpage is working perfectly. It gets refreshed every 5 seconds. All I want
> to do is retrieve the observations at 5-10 second intervals and display
> them instead of the ARCHIVE rate of 60 seconds. I can adjust the LOOP
> interval of the 150WX to whatever I want. It's currently set to 3 seconds.
> I'm just trying to find a simple way to accomplish this. I don't need
> graphs or plots or anything fancy. I've looked at the realtime file
> creation extensions but they seem too complicated for my needs. I'm not a
> programmer but can get a feel for what they are doing by reading the code
> and understanding most of it. Just need a little handholding if that's
> possible.
>
> The observations I am using are:
> outTemp
> pressure
> barometer
> altimeter
> heatindex
> windDir_magn_mda
> windSpeed_mwd
> windGust
>
> Here is the webpage I am creating. It's pretty simple. I'm happy to share
> the template and config files with anyone if that would help. I'm using the
> airmar driver to interface to the sensor:
>
>
> 
>
>
> On Wednesday, May 16, 2018 at 10:03:24 AM UTC-5, Bruce Huddleston wrote:
>
>> I have an Airmar 150WX station that I finally got working with Weewx. It
>> was a challenge. The problem I have is that I need the updates to my
>> display to occur every 5-10 seconds. I can set the LOOP records to be
>> generated at any interval I want and it is set at 3 seconds currently. I
>> have tried to adjust the archive interval in weewx.conf lower than 60
>> seconds but if I do it gives a divide by zero error which I believe is a
>> known issue.
>>
>> My question is, is there a way to create an archive record every 5-10
>> seconds without resorting to using one of the realtime file creation
>> schemes like clientraw or crt? I've looked at those extensions but I can't
>> quite wrap my head around how they would generate a file that I could use
>> with my template. I would be happy to provide my config files and template
>> if someone is willing to help.
>>
> --
> 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.
>



-- 
John P. Hoke
j...@hoke.org
https://hoke.org/john /
Random Non-Sequiturs & Photography

-- 
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: Realtime updates for custom display

2018-05-18 Thread Bruce Huddleston
I'll try to describe what I'm wanting to do a little better. I have a 
Raspberry Pi connected to the 7" touchscreen. It displays a single webpage 
that has 6 observation values from an Airmar 150WX sensor. I added the 
RWYplotgenerator (great addon for my purposes) to the template and the 
webpage is working perfectly. It gets refreshed every 5 seconds. All I want 
to do is retrieve the observations at 5-10 second intervals and display 
them instead of the ARCHIVE rate of 60 seconds. I can adjust the LOOP 
interval of the 150WX to whatever I want. It's currently set to 3 seconds. 
I'm just trying to find a simple way to accomplish this. I don't need 
graphs or plots or anything fancy. I've looked at the realtime file 
creation extensions but they seem too complicated for my needs. I'm not a 
programmer but can get a feel for what they are doing by reading the code 
and understanding most of it. Just need a little handholding if that's 
possible.

The observations I am using are:
outTemp
pressure
barometer
altimeter
heatindex
windDir_magn_mda
windSpeed_mwd
windGust

Here is the webpage I am creating. It's pretty simple. I'm happy to share 
the template and config files with anyone if that would help. I'm using the 
airmar driver to interface to the sensor:




On Wednesday, May 16, 2018 at 10:03:24 AM UTC-5, Bruce Huddleston wrote:
>
> I have an Airmar 150WX station that I finally got working with Weewx. It 
> was a challenge. The problem I have is that I need the updates to my 
> display to occur every 5-10 seconds. I can set the LOOP records to be 
> generated at any interval I want and it is set at 3 seconds currently. I 
> have tried to adjust the archive interval in weewx.conf lower than 60 
> seconds but if I do it gives a divide by zero error which I believe is a 
> known issue.
>
> My question is, is there a way to create an archive record every 5-10 
> seconds without resorting to using one of the realtime file creation 
> schemes like clientraw or crt? I've looked at those extensions but I can't 
> quite wrap my head around how they would generate a file that I could use 
> with my template. I would be happy to provide my config files and template 
> if someone is willing to help.
>

-- 
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: WU API ?

2018-05-18 Thread vince
On Friday, May 18, 2018 at 2:35:22 AM UTC-7, JHoke wrote:
>
> Based on the below info, it looks like I will be sitting down to finally 
> write something to get the data from my local database to use for home 
> automation, irrigation, etc instead of the Wunderground API - i find it 
> rediculous to charge users to access the data they freely give but what do 
> I know ;(
>
> From their forum regarding a question if we will still have access to our 
> data via the API:
>
>
Can you guys provide a couple links to the original announcements please ? 
 I couldn't find anything on their site.

I saw some cryptic stuff saying WeatherBug was bought or something with 
references to CWOP and use of the term 'PWS', but each company overloads 
their terminology so much that it's hard to tell in layman's term what's 
going away or changing when.

FWIW, I feed PWSweather/CWOP/WU using weewx, but use NWS for the forecast 
(although I have a WU API key that I used to play with in the past).

-- 
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: Cydia pomonella

2018-05-18 Thread hesfrrkr

hallo,

now the 
┌<─ ...e/weewx/public_html/Cydia ─.[^]>  ┐┌<─ ...weewx/skins/Seasons/Cydia 
─.[^]>┐
│.nName  │ Größe │Modifikations ││.nName  │ Größe 
│Modifikations│
│/.. │ÜBERVZ.│18. Mai 18:22   ││/.. 
│ÜBERVZ.│18. Mai 15:18│
│ C_pomonella.png│  13869│18. Mai 16:32││ C_pomon~ml.tmpl│   2382│28. Mär 
06:23│
│ NOAA-2015.csv  │216│18. Mai 14:03 ││ NOAA-YY~sv.tmpl│705│18. Mai 
16:32│
│ NOAA-2016.csv  │ 87│18. Mai 14:03  │││   
│ │
│ NOAA-2017.csv  │  10353│18. Mai 14:03│││   
│ │
│ NOAA-2018.csv  │   6186│18. Mai 18:22

in the NOAA-2018.csv

YR,MO,DAY,TMPAVG_F,TMPMAX_F,TMPMIN_F,DEWPT_F,HDD_F,CDD_F,RAIN_IN
2018,01,01,43.3,48.9,36.4,40.0,39.0,0.0,0.05
2018,01,02,38.6,43.0,34.2,36.7,47.5,0.0,0.01
2018,01,03,40.1,45.2,37.1,38.4,44.8,0.0,0.78
2018,01,04,41.2,42.6,39.0,39.7,42.9,0.0,0.24
2018,01,05,41.3,44.3,36.5,38.9,42.6,0.0,0.03
2018,01,06,38.3,42.1,33.9,36.5,48.1,0.0,0.03
2018,01,07,31.4,35.6,26.7,27.9,60.6,0.0,0.0
2018,01,08,28.3,33.6,23.0,22.8,66.0,0.0,0.0
2018,01,09,34.9,38.5,29.3,22.0,54.2,0.0,0.0
2018,01,10,36.1,42.3,33.7,32.7,52.1,0.0,0.0
2018,01,11,32.7,35.8,29.5,31.7,58.1,0.0,0.19
...
2018,05,15,61.8,75.8,48.0,49.9,5.7,0.0,0.01
2018,05,16,63.0,74.4,51.2,54.2,3.6,0.0,0.01
2018,05,17,59.0,71.5,48.4,51.3,10.8,0.0,0.0
2018,05,18,55.6,61.3,50.3,51.8,16.9,0.0,0.0
Time NOW 18:28 UHR

-- 
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: Cydia pomonella

2018-05-18 Thread CRhode
Thanks for your interest in "cydia"  and thanks for the log.   

I'm guessing your /var/www/html/weewx/Cydia/NOAA-2018.csv file is empty or 
something.  The content should look something like this:

YR,MO,DAY,TMPAVG_F,TMPMAX_F,TMPMIN_F,DEWPT_F,HDD_F,CDD_F,RAIN_IN,WSPDAVG_MPH,WDIR_DEG
2018,01,01,-0.7,7.0,-7.4,-18.8,65.7,0.0,0.0,   7.0,   286
2018,01,02,7.9,16.8,-0.0,-13.2,57.1,0.0,0.0,   7.6,   259
2018,01,03,12.0,16.6,4.5,-3.1,53.0,0.0,0.0,   6.4,   289
.
.
.
2018,05,16,56.4,68.0,44.6,43.6,8.6,0.0,0.0,   2.6,   131
2018,05,17,51.7,64.6,46.9,42.2,13.3,0.0,0.0,   6.8,   342
2018,05,18,49.1,55.2,45.7,38.7,15.9,0.0,0.0,   3.2, 5


Please let me know.  -ccr-

-- 
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: Cydia pomonella

2018-05-18 Thread hesfrrkr
Now Log-Errors

 if erase file "/Cydia/C_pomonella.png"

May 18 16:18:26 hesba weewx-weewx[518]: reportengine: Caught unrecoverable 
> exception in generator weewx.cydiagenerator.CydiaGenerator
> May 18 16:18:26 hesba weewx-weewx[518]:   'dd_cumulative'
> May 18 16:18:26 hesba weewx-weewx[518]:   Traceback (most 
> recent call last):
> May 18 16:18:26 hesba weewx-weewx[518]: File 
> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
> May 18 16:18:26 hesba weewx-weewx[518]:   obj.start()
> May 18 16:18:26 hesba weewx-weewx[518]: File 
> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
> May 18 16:18:26 hesba weewx-weewx[518]:   self.run()
> May 18 16:18:26 hesba weewx-weewx[518]: File 
> "/home/weewx/bin/weewx/cydiagenerator.py", line 90, in run
> May 18 16:18:26 hesba weewx-weewx[518]:   
> self.cydia_report_generator.recs = self.zip_vectors()
> May 18 16:18:26 hesba weewx-weewx[518]: File 
> "/home/weewx/bin/weewx/cydiagenerator.py", line 547, in zip_vectors
> May 18 16:18:26 hesba weewx-weewx[518]:   if 
> rec['dd_cumulative'].raw > horizon_dd:
> May 18 16:18:26 hesba weewx-weewx[518]:   KeyError: 
> 'dd_cumulative'
> May 18 16:18:26 hesba weewx-weewx[518]:   Generator terminated
> May 18 16:18:26 hesba weewx-weewx[518]: copygenerator: copied 0 files to 
> /home/weewx/public_html
>


but no C_pomonella.html - file

Hartmut

-- 
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: Cydia pomonella

2018-05-18 Thread hesfrrkr
Hallo,

cydia not work.

I followed the instructions: on  http://lacusveris.com/cydia/software.shtml

only the NOAA-2018.csv files are created

the "C_pomonella.png ." and 
the "C_pomonella.html" --> no files

the "C_pomonella.png 

[image: http://hesba/weewx/Cydia/C_pomonella.png]

what am I doing wrong
No errors in the log's

Hartmut

>

-- 
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: adding last to 24 hrs to xstats

2018-05-18 Thread Andrew Milner
as far as I can see aprs.py appears to be a service which is bound to the 
generation of an archive record.  It is using data from a single archive 
record and creating the aprs data file in the required format FROM A SINGLE 
RECORD.

In order to do what you are trying to do you need to somehow have a 
database archive record field already containing the 24 hour data.

I do not believe you can do what you want to do by the method you are 
attempting.

An alternative is to use cheetah to generate the aprs file as a separate 
report, accessing the database as required and generating/accumulating the 
24 hour data, and use the tags which I gave you.

when creating a cheetah template file call the template for example 
awrs.txt.tmpl and add a new report to the daily reports in your skin called 
[awrs]

for the data from the latest archive record just use $current.outTemp and 
$current.outHumidity for example - or even $latest.outTemp and 
$latest.outHumidity which should be able to then replicate the existing 
awrs file.
for the 24 hr rain try the tags I gave you with span and delta to have 
cheetah calculate the rolling 24 hr rainfall every record

well a few ideas there anyway!!





On Friday, 18 May 2018 16:03:00 UTC+3, Lorin Tremblay wrote:
>
> OK here is the final goal
>
> I've been trying to complement the extension, APRS.py to have all the info 
> required to properly publish an APRS weather beacon.
>
> Originally it was missing the rain since midnight, but manage to fix that 
> one.
> Now i'm still missing the rain in the last 24 hrs and have been looking a 
> different approach on how to resolve issues.
> First I posted a request for help with that and got some answer and that I 
> should learn on my now which I've been trying.
> So I tried to generate the info via xstat, but with you suggestion i 
> thought that I might just be simpler to add straight into the APRS.py 
> code...
> It runs at the same time that the .html files are generated.
>  
>
> Here is the entire code that i'm trying to add rain in the last 24 hrs:
>
>
> *from* datetime *import* datetime
>
> *import* os
>
>
> *import* weeutil.weeutil
>
> *import* weewx.engine
>
> *import* weewx.units
>
>
>
> *class* APRS(weewx.engine.StdService):
>
> *def** __init__*(self, engine, config_dict):
>
> super(APRS, self).__init__(engine, config_dict)
>
> conf = config_dict[*'APRS'*]
>
> self._output_filename = conf[*'output_filename'*]
>
> self._output_filename_tmp = self._output_filename + *'.tmp'*
>
> self._include_position = int(conf.get(*'include_position'*, 0))
>
> self._symbol_table = conf.get(*'symbol_table'*, *'/'*)
>
> self._symbol_code = conf.get(*'symbol_code'*, *'_'*)
>
> self._comment = conf.get(*'comment'*, '')
>
>
> self._message_type = *'_'* * # Weather report (no position)*
>
> self._time_format = *'%m%d%H%M'*
>
> self._latitude = None
>
> self._longitude = None
>
> self._wind_direction_marker = *'c'*
>
> self._wind_speed_marker = *'s'*
>
> *if* self._include_position:
>
>* # Position with timestamp (no APRS messaging)*
>
> self._message_type = *'/'*
>
> self._time_format = *'%d%H%Mz'*
>
> self._latitude = ''.join(weeutil.weeutil.latlon_string(
>
> self.engine.stn_info.latitude_f,
>
> (*'N'*, *'S'*), *'lat'*))
>
> self._longitude = ''.join(weeutil.weeutil.latlon_string(
>
> self.engine.stn_info.longitude_f,
>
> (*'E'*, *'W'*), *'lon'*))
>
> self._wind_direction_marker = ''
>
> self._wind_speed_marker = *'/'*
>
>
> self.bind(weewx.NEW_ARCHIVE_RECORD, 
> self._handle_new_archive_record)
>
>
> *def** _handle_new_archive_record*(self, event):
>
> *"""Generate a positionless APRS weather report and write it to a 
> file"""*
>
> record = event.record
>
> data = [
>
> self._message_type,
>
> datetime.strftime(
>
> datetime.utcfromtimestamp(record[*'dateTime'*]),
>
> self._time_format),
>
> ]
>
> *if* self._include_position:
>
> data.append(self._latitude)
>
> data.append(self._symbol_table)
>
> data.append(self._longitude)
>
> data.append(self._symbol_code)
>
>
> *if* record.get(*'windDir'*) *is* *not* None:
>
>* # Wind direction (in degrees)*
>
>* # Wind from North needs to be reported as 360.*
>
>* # Wind from 0 means N/A in the APRS standard.*
>
>* # We need to make sure it does not get to 0, so do not rely 
> on*
>
>* # the format string rouding, but round to no decimals before*
>
>* # comparing with 0*
>
> wind_dir = int(round(record[*'windDir'*], 0))
>
> *if* wind_dir <= 0:
>
> wind_dir = 360

[weewx-user] Re: adding last to 24 hrs to xstats

2018-05-18 Thread Lorin Tremblay
OK here is the final goal

I've been trying to complement the extension, APRS.py to have all the info 
required to properly publish an APRS weather beacon.

Originally it was missing the rain since midnight, but manage to fix that 
one.
Now i'm still missing the rain in the last 24 hrs and have been looking a 
different approach on how to resolve issues.
First I posted a request for help with that and got some answer and that I 
should learn on my now which I've been trying.
So I tried to generate the info via xstat, but with you suggestion i 
thought that I might just be simpler to add straight into the APRS.py 
code...
It runs at the same time that the .html files are generated.
 

Here is the entire code that i'm trying to add rain in the last 24 hrs:


*from* datetime *import* datetime

*import* os


*import* weeutil.weeutil

*import* weewx.engine

*import* weewx.units



*class* APRS(weewx.engine.StdService):

*def** __init__*(self, engine, config_dict):

super(APRS, self).__init__(engine, config_dict)

conf = config_dict[*'APRS'*]

self._output_filename = conf[*'output_filename'*]

self._output_filename_tmp = self._output_filename + *'.tmp'*

self._include_position = int(conf.get(*'include_position'*, 0))

self._symbol_table = conf.get(*'symbol_table'*, *'/'*)

self._symbol_code = conf.get(*'symbol_code'*, *'_'*)

self._comment = conf.get(*'comment'*, '')


self._message_type = *'_'* * # Weather report (no position)*

self._time_format = *'%m%d%H%M'*

self._latitude = None

self._longitude = None

self._wind_direction_marker = *'c'*

self._wind_speed_marker = *'s'*

*if* self._include_position:

   * # Position with timestamp (no APRS messaging)*

self._message_type = *'/'*

self._time_format = *'%d%H%Mz'*

self._latitude = ''.join(weeutil.weeutil.latlon_string(

self.engine.stn_info.latitude_f,

(*'N'*, *'S'*), *'lat'*))

self._longitude = ''.join(weeutil.weeutil.latlon_string(

self.engine.stn_info.longitude_f,

(*'E'*, *'W'*), *'lon'*))

self._wind_direction_marker = ''

self._wind_speed_marker = *'/'*


self.bind(weewx.NEW_ARCHIVE_RECORD, self._handle_new_archive_record)


*def** _handle_new_archive_record*(self, event):

*"""Generate a positionless APRS weather report and write it to a 
file"""*

record = event.record

data = [

self._message_type,

datetime.strftime(

datetime.utcfromtimestamp(record[*'dateTime'*]),

self._time_format),

]

*if* self._include_position:

data.append(self._latitude)

data.append(self._symbol_table)

data.append(self._longitude)

data.append(self._symbol_code)


*if* record.get(*'windDir'*) *is* *not* None:

   * # Wind direction (in degrees)*

   * # Wind from North needs to be reported as 360.*

   * # Wind from 0 means N/A in the APRS standard.*

   * # We need to make sure it does not get to 0, so do not rely on*

   * # the format string rouding, but round to no decimals before*

   * # comparing with 0*

wind_dir = int(round(record[*'windDir'*], 0))

*if* wind_dir <= 0:

wind_dir = 360

data.append(*'%s%03u'* % (self._wind_direction_marker,

wind_dir))

*else*:

data.append(*'%s...'* % self._wind_direction_marker)


*if* record.get(*'windSpeed'*) *is* *not* None:

   * # Sustained one-minute wind speed (in mph)*

data.append(*'%s%03.f'* % (self._wind_speed_marker,

 record[*'windSpeed'*]))

*else*:

data.append(*'%s...'* % self._wind_speed_marker)


*if* record.get(*'windGust'*) *is* *not* None:

   * # Gust (peak wind speed in mph in the last 5 minutes)*

data.append(*'g%03.f'* % record[*'windGust'*])

*else*:

data.append(*'g...'*)


*if* record.get(*'outTemp'*) *is* *not* None:

   * # Temperature (in degrees Fahrenheit)*

data.append(*'t%03.f'* % record[*'outTemp'*])

*else*:

data.append(*'t...'*)


*if* record.get(*'rainRate'*) *is* *not* None:

   * # Rainfall (in hundredths of an inch) in the last hour*

data.append(*'r%03.f'* % (record[*'rainRate'*] * 100))


*if* record.get(*'rain'*) *is* *not* None:

   * # Rainfall (in hundredths of an inch) in the last 24hrs.*

data.append(*'p%03.f'* % (record[*'rain'*] * 100))


#*if* record.get(*'MISSSING INFO'*) *is* *not* None:

#   * # Rainfall (in hundredths of an inch) since 

[weewx-user] Re: adding last to 24 hrs to xstats

2018-05-18 Thread Andrew Milner
where is this code from? when is it being run?  

Originally you were trying to amend xstats - which effectively makes extra 
tags become available to the cheetah template engine

I gave a method of generating the required data without needing additional 
24 hour tags, by using existing tags available to the cheetah template 
engine.

You have now come up with some code which appears to be processing records 
obtained from somewhere other than directly from the weewx database and 
appending the output somewhere else.

Being in the dark somewhat my answer is "I do not know"

Sorry - cannot help more - I do not know where the code comes from, when it 
is run or how it is used, so cannot answer.  Sorry





On Friday, 18 May 2018 14:54:36 UTC+3, Lorin Tremblay wrote:
>
> So not being a coder or someone that know how to code
> How do you add it to this where the question mark are?
>
> *if* record.get(*'rainRate'*) *is* *not* None:
>
>* # Rainfall (in hundredths of an inch) in the last hour*
>
> data.append(*'r%03.f'* % (record[*'rainRate'*] * 100))
>
>
> #   *if* record.get(*'?'*) *is* *not* None:
>
> #  * # Rainfall (in hundredths of an inch) last 24hrs*
>
> #data.append(*'p%03.f'* % (record[*'?'*] * 100))
>
>
> *if* record.get(*'rain'*) *is* *not* None:
>
>* # Rainfall (in hundredths of an inch) since midnight*
>
> data.append(*'P%03.f'* % (record[*'rain'*] * 100))
>
>
> Thanks for your help andrew!
>
>
>
> On Thursday, May 17, 2018 at 9:50:38 PM UTC-4, Andrew Milner wrote:
>>
>> you could just use span with a day delta:
>>
>> eg
>> $span($day_delta=1).rain.sum for the rain total for previous 24 hours 
>> according to the customisation guide
>> or
>> $span($day_delta=1).outTemp.avg for the average temperature during 
>> previous 24 hours
>>
>>
>>
>> On Friday, 18 May 2018 01:09:48 UTC+3, Lorin Tremblay wrote:
>>>
>>> Hi!
>>>
>>> Trying to modify the xstats to add the last 24hrs to stats.
>>>
>>> here is the modification that I have made, but obviously not being a 
>>> coder there is one or more mistake, can anyone help me sort it out?
>>>
>>> "*#*
>>>
>>> *#Copyright (c) 2009-2015 Tom Keffer *
>>>
>>> *#*
>>>
>>> *#See the file LICENSE.txt for your full rights.*
>>>
>>> *#*
>>>
>>> *"""Extended stats based on the xsearch example*
>>>
>>>
>>> *This search list extension offers extra tags:*
>>>
>>>
>>> *  'alltime':All time statistics.*
>>>
>>>
>>> *  '24_hrs':  Statistics for the last 24 hours.* 
>>>
>>>
>>> *  'seven_day':  Statistics for the last seven days.* 
>>>
>>>
>>> *  'thirty_day': Statistics for the last thirty days.*
>>>
>>>
>>> *You can then use tags such as $alltime.outTemp.max for the all-time max*
>>>
>>> *temperature, or $seven_day.rain.sum for the total rainfall in the last 
>>> seven*
>>>
>>> *days, or $thirty_day.wind.max for maximum wind speed in the past thirty 
>>> days.*
>>>
>>> *"""*
>>>
>>> *import* datetime
>>>
>>> *import* time
>>>
>>>
>>> *from* weewx.cheetahgenerator *import* SearchList
>>>
>>> *from* weewx.tags *import* TimespanBinder
>>>
>>> *from* weeutil.weeutil *import* TimeSpan
>>>
>>>
>>> *class* ExtendedStatistics(SearchList):
>>>
>>> 
>>>
>>> *def** __init__*(self, generator):
>>>
>>> SearchList.__init__(self, generator)
>>>
>>>   
>>>
>>> *def** get_extension_list*(self, timespan, db_lookup):
>>>
>>> *"""Returns a search list extension with additions.*
>>>
>>>
>>> *timespan: An instance of weeutil.weeutil.TimeSpan. This holds*
>>>
>>> *  the start and stop times of the domain of valid 
>>> times.*
>>>
>>>
>>> *db_lookup: Function that returns a database manager given a*
>>>
>>> *   data binding.*
>>>
>>> *"""*
>>>
>>>
>>>* # First, create a TimespanBinder object for all time. This one 
>>> is easy*
>>>
>>>* # because the object timespan already holds all valid times to 
>>> be*
>>>
>>>* # used in the report.*
>>>
>>> all_stats = TimespanBinder(timespan,
>>>
>>>db_lookup,
>>>
>>>context=*'alltime'*,
>>>
>>>formatter=self.generator.formatter,
>>>
>>>converter=self.generator.converter)
>>>
>>> 
>>>
>>>* # Now use a similar process to get statistics for the last 24 
>>> hours.*
>>>
>>> hour_dt = datetime.date.fromtimestamp(timespan.stop) - 
>>> datetime.timedelta(hour=24)
>>>
>>> hour_ts = time.mktime(hour_dt.timetuple())
>>>
>>> 24_hours_stats = TimespanBinder(TimeSpan(hour_ts, timespan.stop),
>>>
>>>   db_lookup,
>>>
>>>   context=*'24_hrs'*,
>>>
>>>   
>>> formatter=self.generator.formatter,
>>>
>>>   
>>> 

[weewx-user] Re: adding last to 24 hrs to xstats

2018-05-18 Thread Lorin Tremblay
So not being a coder or someone that know how to code
How do you add it to this where the question mark are?

*if* record.get(*'rainRate'*) *is* *not* None:

   * # Rainfall (in hundredths of an inch) in the last hour*

data.append(*'r%03.f'* % (record[*'rainRate'*] * 100))


#   *if* record.get(*'?'*) *is* *not* None:

#  * # Rainfall (in hundredths of an inch) last 24hrs*

#data.append(*'p%03.f'* % (record[*'?'*] * 100))


*if* record.get(*'rain'*) *is* *not* None:

   * # Rainfall (in hundredths of an inch) since midnight*

data.append(*'P%03.f'* % (record[*'rain'*] * 100))


Thanks for your help andrew!



On Thursday, May 17, 2018 at 9:50:38 PM UTC-4, Andrew Milner wrote:
>
> you could just use span with a day delta:
>
> eg
> $span($day_delta=1).rain.sum for the rain total for previous 24 hours 
> according to the customisation guide
> or
> $span($day_delta=1).outTemp.avg for the average temperature during 
> previous 24 hours
>
>
>
> On Friday, 18 May 2018 01:09:48 UTC+3, Lorin Tremblay wrote:
>>
>> Hi!
>>
>> Trying to modify the xstats to add the last 24hrs to stats.
>>
>> here is the modification that I have made, but obviously not being a 
>> coder there is one or more mistake, can anyone help me sort it out?
>>
>> "*#*
>>
>> *#Copyright (c) 2009-2015 Tom Keffer *
>>
>> *#*
>>
>> *#See the file LICENSE.txt for your full rights.*
>>
>> *#*
>>
>> *"""Extended stats based on the xsearch example*
>>
>>
>> *This search list extension offers extra tags:*
>>
>>
>> *  'alltime':All time statistics.*
>>
>>
>> *  '24_hrs':  Statistics for the last 24 hours.* 
>>
>>
>> *  'seven_day':  Statistics for the last seven days.* 
>>
>>
>> *  'thirty_day': Statistics for the last thirty days.*
>>
>>
>> *You can then use tags such as $alltime.outTemp.max for the all-time max*
>>
>> *temperature, or $seven_day.rain.sum for the total rainfall in the last 
>> seven*
>>
>> *days, or $thirty_day.wind.max for maximum wind speed in the past thirty 
>> days.*
>>
>> *"""*
>>
>> *import* datetime
>>
>> *import* time
>>
>>
>> *from* weewx.cheetahgenerator *import* SearchList
>>
>> *from* weewx.tags *import* TimespanBinder
>>
>> *from* weeutil.weeutil *import* TimeSpan
>>
>>
>> *class* ExtendedStatistics(SearchList):
>>
>> 
>>
>> *def** __init__*(self, generator):
>>
>> SearchList.__init__(self, generator)
>>
>>   
>>
>> *def** get_extension_list*(self, timespan, db_lookup):
>>
>> *"""Returns a search list extension with additions.*
>>
>>
>> *timespan: An instance of weeutil.weeutil.TimeSpan. This holds*
>>
>> *  the start and stop times of the domain of valid times.*
>>
>>
>> *db_lookup: Function that returns a database manager given a*
>>
>> *   data binding.*
>>
>> *"""*
>>
>>
>>* # First, create a TimespanBinder object for all time. This one 
>> is easy*
>>
>>* # because the object timespan already holds all valid times to 
>> be*
>>
>>* # used in the report.*
>>
>> all_stats = TimespanBinder(timespan,
>>
>>db_lookup,
>>
>>context=*'alltime'*,
>>
>>formatter=self.generator.formatter,
>>
>>converter=self.generator.converter)
>>
>> 
>>
>>* # Now use a similar process to get statistics for the last 24 
>> hours.*
>>
>> hour_dt = datetime.date.fromtimestamp(timespan.stop) - 
>> datetime.timedelta(hour=24)
>>
>> hour_ts = time.mktime(hour_dt.timetuple())
>>
>> 24_hours_stats = TimespanBinder(TimeSpan(hour_ts, timespan.stop),
>>
>>   db_lookup,
>>
>>   context=*'24_hrs'*,
>>
>>   
>> formatter=self.generator.formatter,
>>
>>   
>> converter=self.generator.converter)
>>
>>
>>* # Now create a TimespanBinder for the last seven days. This one 
>> we*
>>
>>* # will have to calculate. First, calculate the time at 
>> midnight, seven*
>>
>>* # days ago. The variable week_dt will be an instance of 
>> datetime.date.*
>>
>> week_dt = datetime.date.fromtimestamp(timespan.stop) - 
>> datetime.timedelta(weeks=1)
>>
>> week_ts = time.mktime(week_dt.timetuple())
>>
>> seven_day_stats = TimespanBinder(TimeSpan(week_ts, timespan.stop),
>>
>>  db_lookup,
>>
>>  context=*'seven_day'*,
>>
>>  
>> formatter=self.generator.formatter,
>>
>>  
>> converter=self.generator.converter)
>>
>>
>>* # Now use a similar process to get statistics for the last 30 
>> days.*
>>
>> days_dt = 

[weewx-user] Re: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread gjr80
Hmm,

#for $_record in $day.records
$_record.dateTime $_record.outTemp $_record.leafWet1
#end for

seems pretty darn straightforward to me and I suspect a heck of a lot less 
convoluted than any standalone python script. Cheetah generated reports are 
very powerful and can do far more than generate a simple HTML page with basic 
aggregates. Standalone python may be faster and more efficient but I would 
argue the simplicity and flexibility of the template and speed of modern 
processors more than make up for this.

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] windBatteryStatus readout for VantageVue extra wind transmitter

2018-05-18 Thread Sef Konings
Hi weewx friends,

I am currently using a separate windspeed and direction transmitter @ about 
10 meters in my antenna tower. This transmitter powered by battery, that is 
being loaded by the power of its small solarpanel in the housing.

This transmitter is configured as an extra ISS (type 4) on the Vantage-Vue 
console.  It would be nice if there was a possibility to monitor the 
current battery status of this extra Windspeed meter transmitter 

Because it is in principle the exact same device as the main ISS 
transmitter, I think it should be possible..

I have tried to add an extra parameter (windBatteryStatus) in the loop of 
the file vantage.py :   ('txBatteryStatus','B'), ('consBatteryVoltage', 
'H'), ('windBatteryStatus',  'B'), and in 

  self.loop_data = {'txBatteryStatus': None,
  'consBatteryVoltage': None,
  'windBatteryStatus': None}  

I also  added this parameter in skin.conf, but that is not working...   I 
get this errormessage in the user.log:

  engine: Caught unrecoverable exception in engine:  ***
 *  unpack requires a string argument of length 96
   Traceback (most recent call last):
 File "/usr/share/weewx/weewx/engine.py", line 871, in main
   engine.run()
 File "/usr/share/weewx/weewx/engine.py", line 187, in run
   for packet in self.console.genLoopPackets():
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 507, in 
genLoopPackets
   for _loop_packet in self.genDavisLoopPackets(200):
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in 
genDavisLoopPackets
   loop_packet = self._unpackLoopPacket(_buffer[:95])
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1408, 
in _unpackLoopPacket
   data_tuple = loop_fmt.unpack(raw_loop_string)
   error: unpack requires a string argument of length 96
   Exiting.

(I have restored to the original vantage.py)

Has anyone an idea how to achieve this ?

Thanks!

Sef

https://sekoni.nl/weewx


  

-- 
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: WU API ?

2018-05-18 Thread JHoke
Based on the below info, it looks like I will be sitting down to finally 
write something to get the data from my local database to use for home 
automation, irrigation, etc instead of the Wunderground API - i find it 
rediculous to charge users to access the data they freely give but what do 
I know ;(

>From their forum regarding a question if we will still have access to our 
data via the API:

 Tim Roche 
, 
Official Rep

   - 274 Posts 
   -  19 Reply Likes

You will no longer have access to the PWS data through the API.  You will 
however have access to the data on your PWS page if you click the table 
view, you will see a download option.

hope this helps
tim

On Thursday, May 17, 2018 at 4:30:56 AM UTC-4, gjr80 wrote:
>
> I guess we are all aware of the issues that have plagued WU for some time. 
> I have stuck with them, uploading data and downloading various pieces of 
> data via their API, it's just kept on working for me. I noticed a post on 
> wxforum.net re WU no longer issuing API keys, I found this on WU.
>
> https://www.wunderground.com/weather/api/
>
> Maybe some folks more acquainted with WU/The Weather Company/The Weather 
> Channel might have more info. There is nothing I found to indicate the cost 
> of whatever replaces the API, when I followed the various links I just went 
> around in corporate double speak circles.
>
> Looking like the the forecast extension might need a version 4.
>
> 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: WU API ?

2018-05-18 Thread Andrew Milner
I have never used wu for forecast feed.  I do use it for previous day's 
data for my irrigation though, but could if push came to shove generate the 
water % from my own data rather than my data which I have uploaded.  But 
then again - it is using my own data which should not be affected anyway ……

for forecasting I use two other sites - meteoblue and windguru and just pop 
their forecasts into a frame on my site with no data download anyway.

avoids using wu (and their (un)availability) that way …..



On Friday, 18 May 2018 11:14:36 UTC+3, gjr80 wrote:
>
> Nobody is panicing. But when you take this with all of the other WU 
> shenanigans over the past year or two you would have to say the writing is 
> on the wall. I will be starting work on an alternate forecast feed for my 
> site. Something about failing to plan is planning to fail comes to mind.
>
> 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: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread Andrew Milner
I agree wit2h you if he only requires max, min fior the day.  If however he 
wants all readings fior the previous 24 hrs then I think weewx report is 
not the correct route.

Anyways - looping around in a template I don't think is that simple either 
and almost ends up more convoluted than a simple program!!

But it is horses for courses I guess.  I prefer cron for single daily tasks.



On Friday, 18 May 2018 10:59:16 UTC+3, gjr80 wrote:
>
> Why do it via cron, keep it simple in weeWX by using a template and the 
> report_timing option (weewx.com/docs/customizing.htm#customizing_gen_time), 
> this is exactly the use case it was intended for. Keeping it in a weeWX 
> template gives you all the power of the weeWX tag system rather than 
> forcing you to use sql to retrieve data and then having to format the 
> results.
>
> 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: WU API ?

2018-05-18 Thread gjr80
Nobody is panicing. But when you take this with all of the other WU shenanigans 
over the past year or two you would have to say the writing is on the wall. I 
will be starting work on an alternate forecast feed for my site. Something 
about failing to plan is planning to fail comes to mind.

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: WU API ?

2018-05-18 Thread Andrew Milner
I shall wait and see.  I would expect them to continue to allow use of api 
for your own weather station, but I can understand the reasons for 
limitations (as there always have been) on the uses which used to be part 
of other plans.  I am sure there are many 'users' who are really commercial 
who are ripping off WU with there requests for data and trying to get the 
data for free when they shouldn't be.

So I'm not panicking just yet



On Friday, 18 May 2018 10:49:36 UTC+3, gjr80 wrote:
>
> Andrew,
>
> You need to log out of WU, for non-WU user that page was the entry into 
> the WU API, for logged in WU users it takes you to your analytics page. The 
> non-WU users it now gives a blurb about The Weather Company 'series of data 
> packages'. They are light on detail and whilst the don't indicate they are 
> paid for they certainly don't indicate they are free either.
>
> Other links of interest:
>
> The wxforum.net thread:  http://www.wxforum.net/index.php?topic=34403.0
>
> Thread in WU API Community forum:  
> https://apicommunity.wunderground.com/weatherapi/topics/weather-underground-api-changes
>
> See there is something in the API community thread about the smallest data 
> package being $850 per month.
>
>
> 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: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread gjr80
Why do it via cron, keep it simple in weeWX by using a template and the 
report_timing option (weewx.com/docs/customizing.htm#customizing_gen_time), 
this is exactly the use case it was intended for. Keeping it in a weeWX 
template gives you all the power of the weeWX tag system rather than forcing 
you to use sql to retrieve data and then having to format the results.

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: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread Michael Aschauer
thx a lot andrew!

2018-05-18 9:50 GMT+02:00 Andrew Milner :

> you can do the cron task yourself with simple python program accessing the
> database and writing the file, triggered by cron.
>
> generating such a file only once per day is not really fitting within the
> scope of weewx and weewx reporting.  You could write a weewx 'report', but
> I do not think you would find it simple.
>
> the formula I gave you will convert all your leaf wetness values as they
> are received, so they will be stored in the database as the converted
> values.  put the change into [StdCalibrate]
>[[Corrections]]
>   formula
>
>
> On Friday, 18 May 2018 10:23:52 UTC+3, aschaue...@gmail.com wrote:
>>
>> thx andrew, unfortunately  the company that is running the algorithmus
>> takes up to 2.000 € for adapting the values and coding the output file. so
>> i want do realize this by myself. your input is highly appreciated!
>> is there even a way/function, to export given values (temp, hum, leaf,
>> rain) to a seperated file?
>>
>>
 --
> 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/F_EJ_ys98mI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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


[weewx-user] Re: WU API ?

2018-05-18 Thread gjr80
Andrew,

You need to log out of WU, for non-WU user that page was the entry into the WU 
API, for logged in WU users it takes you to your analytics page. The non-WU 
users it now gives a blurb about The Weather Company 'series of data packages'. 
They are light on detail and whilst the don't indicate they are paid for they 
certainly don't indicate they are free either.

Other links of interest:

The wxforum.net thread:  http://www.wxforum.net/index.php?topic=34403.0

Thread in WU API Community forum:  
https://apicommunity.wunderground.com/weatherapi/topics/weather-underground-api-changes

See there is something in the API community thread about the smallest data 
package being $850 per month.


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: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread Andrew Milner
you can do the cron task yourself with simple python program accessing the 
database and writing the file, triggered by cron.

generating such a file only once per day is not really fitting within the 
scope of weewx and weewx reporting.  You could write a weewx 'report', but 
I do not think you would find it simple.

the formula I gave you will convert all your leaf wetness values as they 
are received, so they will be stored in the database as the converted 
values.  put the change into [StdCalibrate]
   [[Corrections]]
  formula


On Friday, 18 May 2018 10:23:52 UTC+3, aschaue...@gmail.com wrote:
>
> thx andrew, unfortunately  the company that is running the algorithmus 
> takes up to 2.000 € for adapting the values and coding the output file. so 
> i want do realize this by myself. your input is highly appreciated!
> is there even a way/function, to export given values (temp, hum, leaf, 
> rain) to a seperated file?
>
>
>>>

-- 
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: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread aschauer . michl
thx andrew, unfortunately  the company that is running the algorithmus 
takes up to 2.000 € for adapting the values and coding the output file. so 
i want do realize this by myself. your input is highly appreciated!
is there even a way/function, to export given values (temp, hum, leaf, 
rain) to a seperated file?


>>

-- 
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: Changing LeafWetness Values & generate DataFile

2018-05-18 Thread Andrew Milner
Generating a file only once per day is better suited to a simple cron task 
rather than weewx I suspect - and the cron task could also take care of any 
conversions and formatin issues for your data file.  It IS possible with 
weewx, but weewx is really more suited to regular reporting cycles rather 
than once per day.  

The conversion could be done by 
leafwetness = 255 - (17 * leafwetness)



On Friday, 18 May 2018 09:32:43 UTC+3, aschaue...@gmail.com wrote:
>
>
> Hi,
>
> i´m running a davis vantage pro station with soil moisture and leaf 
> wetness sensors. the data of this station should be used in a pest control 
> program in my village.
>
> leaf wetness is indicated with values between 1 (dry) and 15 (wet).
>
> but the algorithmus uses other weather stations, were the wetness range is 
> 0 (wet) and 255 (dry).
>
> so first, i have to convert the standard values to the appropriate 
> algorithmus values like this:
>
> 0 255
> 1 238
> 2 221
> 3 204
> 4 187
> 5 170
> 6 153
> 7 136
> 8 119
> 9 102
> 10 85
> 11 68
> 12 51
> 13 34
> 14 17
> 15 0
>
> is this possible with weewx [stdconvert] ?
>
>
> in the evening of each day it is necessary to upload a data file according 
> to this synthax 
> 
> can a generate a datafile like this with weewx?
>
> i appreciate any tipps and tricks, thx!
>
> best greetings,
> michl
>
>
>
>
>

-- 
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] Changing LeafWetness Values & generate DataFile

2018-05-18 Thread aschauer . michl



Hi,

i´m running a davis vantage pro station with soil moisture and leaf wetness 
sensors. the data of this station should be used in a pest control program 
in my village.

leaf wetness is indicated with values between 1 (dry) and 15 (wet).

but the algorithmus uses other weather stations, were the wetness range is 
0 (wet) and 255 (dry).

so first, i have to convert the standard values to the appropriate 
algorithmus values like this:

0 255
1 238
2 221
3 204
4 187
5 170
6 153
7 136
8 119
9 102
10 85
11 68
12 51
13 34
14 17
15 0

is this possible with weewx [stdconvert] ?


in the evening of each day it is necessary to upload a data file according 
to this synthax 

can a generate a datafile like this with weewx?

i appreciate any tipps and tricks, thx!

best greetings,
michl




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