Re: [weewx-user] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[Andrew Milner]

generating an archive record every minute seems way over the top, and may 
create other issues if the reports cannot be generated within a 1 minute 
window - especially the reports generated once a day at midnight - as the 
database grows bigger and bigger (which will be very quickly at 1 minute 
archive intervals)



On Sunday, 30 September 2018 09:31:48 UTC+3, Glenn F wrote:
>
> Thanks Gary.   Website is back to running as it was. Though i used
> "wee_device 
> --set-interval=1" I need that immediacy. Happy.. Though I still have that 
> fecking 15000mm/h  rain rate  ??   Clues../?
>
>
> On Sun, Sep 30, 2018 at 5:58 PM gjr80 > 
> wrote:
>
>> Ok, it looks like when you did the wee_device --clear you reset the 
>> archive interval on your station to the default 30 minutes. When WeeWX 
>> starts the archive interval is read from weewx.conf and the station (if 
>> it supports this), if there is a discrepancy then the station archive 
>> interval is used. In your case the answer is in the log (sorry did not read 
>> this far when you first posted, that was a lot of log!):
>>
>> Sep 29 19:15:29 Weather-Station weewx[2068]: engine: The archive 
>> interval in the configuration file (300) does not match the station 
>> hardware interval (1800).
>> Sep 29 19:15:29 Weather-Station weewx[2068]: engine: Using archive 
>> interval of 1800 seconds (specified by hardware)=
>>
>> This will explain the dotty plots as well, there is only one data point 
>> being saved every 30 minutes. I suspect you want to change to a 5 minute 
>> archive interval, to do this you will need to use wee_device again but 
>> this time with the --set-interval action, something like:
>>
>> $ wee_device --set-interval=5
>>
>> Note the interval is in minutes and also not you need to stop WeeWX 
>> before doing this and then start again once set. Depending on your 
>> privileges you may need to use sudo 
>>
>> Gary
>>
>> On Sunday, 30 September 2018 14:25:05 UTC+10, Glenn F wrote:
>>>
>>> using the " sudo /etc/init.d/weewx start/stop "  command. I had this set 
>>> perfectly bugger it until I tried to remove the bad data :( which is still 
>>> there and now my webpage is only logging updates every half hr even with 
>>> the same weewx.conf file, before it would give me the exact time update 
>>> with a page refresh per minute , and also the plots are dots rather than 
>>> the line graph it was before..  Almost feel like giving up on this years 
>>> data , only had it since JAN, and just starting over.. Would be hair 
>>> pulling if I had some :P 
>>>
>>> On Sat, Sep 29, 2018 at 8:34 PM gjr80  wrote:
>>>
 Exactly what command have you used to start/restart WeeWX?

 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/JWXQzbrLbms/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 a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/JWXQzbrLbms/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] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[gjr80]

Yep, what we need to do is find out where the bad data is. It will either 
be in the archive or in the daily summaries or both, judging by your site 
my guess is it's definitely in the daily summaries and maybe the archive. 
Tom gave you a command to run at post #4 above, that will check the 
archive. Try running it again, note you will need to stop WeeWX and make 
another copy of your database to /var/tmp (you can start WeeWX again as 
soon as you have made the copy):

$ echo "SELECT dateTime, datetime(dateTime,'unixepoch','localtime'), 
rainRate from archive where rainRate > 100;" | sqlite3 /var/tmp/weewx.sdb

What does it come up with, if that shows the bad data then we need to fix 
that. If it doesn't show the bad data then the issue is confined to the 
daily summaries. Let us know how you go.

Gary

On Sunday, 30 September 2018 16:31:48 UTC+10, Glenn F wrote:
>
> Thanks Gary.   Website is back to running as it was. Though i used
> "wee_device 
> --set-interval=1" I need that immediacy. Happy.. Though I still have that 
> fecking 15000mm/h  rain rate  ??   Clues../?
>
>
> On Sun, Sep 30, 2018 at 5:58 PM gjr80 > 
> wrote:
>
>> Ok, it looks like when you did the wee_device --clear you reset the 
>> archive interval on your station to the default 30 minutes. When WeeWX 
>> starts the archive interval is read from weewx.conf and the station (if 
>> it supports this), if there is a discrepancy then the station archive 
>> interval is used. In your case the answer is in the log (sorry did not read 
>> this far when you first posted, that was a lot of log!):
>>
>> Sep 29 19:15:29 Weather-Station weewx[2068]: engine: The archive 
>> interval in the configuration file (300) does not match the station 
>> hardware interval (1800).
>> Sep 29 19:15:29 Weather-Station weewx[2068]: engine: Using archive 
>> interval of 1800 seconds (specified by hardware)=
>>
>> This will explain the dotty plots as well, there is only one data point 
>> being saved every 30 minutes. I suspect you want to change to a 5 minute 
>> archive interval, to do this you will need to use wee_device again but 
>> this time with the --set-interval action, something like:
>>
>> $ wee_device --set-interval=5
>>
>> Note the interval is in minutes and also not you need to stop WeeWX 
>> before doing this and then start again once set. Depending on your 
>> privileges you may need to use sudo 
>>
>> Gary
>>
>> On Sunday, 30 September 2018 14:25:05 UTC+10, Glenn F wrote:
>>>
>>> using the " sudo /etc/init.d/weewx start/stop "  command. I had this set 
>>> perfectly bugger it until I tried to remove the bad data :( which is still 
>>> there and now my webpage is only logging updates every half hr even with 
>>> the same weewx.conf file, before it would give me the exact time update 
>>> with a page refresh per minute , and also the plots are dots rather than 
>>> the line graph it was before..  Almost feel like giving up on this years 
>>> data , only had it since JAN, and just starting over.. Would be hair 
>>> pulling if I had some :P 
>>>
>>> On Sat, Sep 29, 2018 at 8:34 PM gjr80  wrote:
>>>
 Exactly what command have you used to start/restart WeeWX?

 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/JWXQzbrLbms/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 a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/JWXQzbrLbms/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] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[Glenn F]

Thanks Gary.   Website is back to running as it was. Though i used
"wee_device
--set-interval=1" I need that immediacy. Happy.. Though I still have that
fecking 15000mm/h  rain rate  ??   Clues../?


On Sun, Sep 30, 2018 at 5:58 PM gjr80  wrote:

> Ok, it looks like when you did the wee_device --clear you reset the
> archive interval on your station to the default 30 minutes. When WeeWX
> starts the archive interval is read from weewx.conf and the station (if
> it supports this), if there is a discrepancy then the station archive
> interval is used. In your case the answer is in the log (sorry did not read
> this far when you first posted, that was a lot of log!):
>
> Sep 29 19:15:29 Weather-Station weewx[2068]: engine: The archive interval
> in the configuration file (300) does not match the station hardware
> interval (1800).
> Sep 29 19:15:29 Weather-Station weewx[2068]: engine: Using archive
> interval of 1800 seconds (specified by hardware)=
>
> This will explain the dotty plots as well, there is only one data point
> being saved every 30 minutes. I suspect you want to change to a 5 minute
> archive interval, to do this you will need to use wee_device again but
> this time with the --set-interval action, something like:
>
> $ wee_device --set-interval=5
>
> Note the interval is in minutes and also not you need to stop WeeWX before
> doing this and then start again once set. Depending on your privileges you
> may need to use sudo
>
> Gary
>
> On Sunday, 30 September 2018 14:25:05 UTC+10, Glenn F wrote:
>>
>> using the " sudo /etc/init.d/weewx start/stop "  command. I had this set
>> perfectly bugger it until I tried to remove the bad data :( which is still
>> there and now my webpage is only logging updates every half hr even with
>> the same weewx.conf file, before it would give me the exact time update
>> with a page refresh per minute , and also the plots are dots rather than
>> the line graph it was before..  Almost feel like giving up on this years
>> data , only had it since JAN, and just starting over.. Would be hair
>> pulling if I had some :P
>>
>> On Sat, Sep 29, 2018 at 8:34 PM gjr80  wrote:
>>
>>> Exactly what command have you used to start/restart WeeWX?
>>>
>>> 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/JWXQzbrLbms/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 a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/JWXQzbrLbms/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] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[gjr80]

Ok, it looks like when you did the wee_device --clear you reset the archive 
interval on your station to the default 30 minutes. When WeeWX starts the 
archive interval is read from weewx.conf and the station (if it supports 
this), if there is a discrepancy then the station archive interval is used. 
In your case the answer is in the log (sorry did not read this far when you 
first posted, that was a lot of log!):

Sep 29 19:15:29 Weather-Station weewx[2068]: engine: The archive interval in 
the configuration file (300) does not match the station hardware interval (
1800).
Sep 29 19:15:29 Weather-Station weewx[2068]: engine: Using archive interval 
of 1800 seconds (specified by hardware)=

This will explain the dotty plots as well, there is only one data point 
being saved every 30 minutes. I suspect you want to change to a 5 minute 
archive interval, to do this you will need to use wee_device again but this 
time with the --set-interval action, something like:

$ wee_device --set-interval=5

Note the interval is in minutes and also not you need to stop WeeWX before 
doing this and then start again once set. Depending on your privileges you 
may need to use sudo 

Gary

On Sunday, 30 September 2018 14:25:05 UTC+10, Glenn F wrote:
>
> using the " sudo /etc/init.d/weewx start/stop "  command. I had this set 
> perfectly bugger it until I tried to remove the bad data :( which is still 
> there and now my webpage is only logging updates every half hr even with 
> the same weewx.conf file, before it would give me the exact time update 
> with a page refresh per minute , and also the plots are dots rather than 
> the line graph it was before..  Almost feel like giving up on this years 
> data , only had it since JAN, and just starting over.. Would be hair 
> pulling if I had some :P 
>
> On Sat, Sep 29, 2018 at 8:34 PM gjr80 > 
> wrote:
>
>> Exactly what command have you used to start/restart WeeWX?
>>
>> 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/JWXQzbrLbms/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] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[Glenn F]

using the " sudo /etc/init.d/weewx start/stop "  command. I had this set
perfectly bugger it until I tried to remove the bad data :( which is still
there and now my webpage is only logging updates every half hr even with
the same weewx.conf file, before it would give me the exact time update
with a page refresh per minute , and also the plots are dots rather than
the line graph it was before..  Almost feel like giving up on this years
data , only had it since JAN, and just starting over.. Would be hair
pulling if I had some :P

On Sat, Sep 29, 2018 at 8:34 PM gjr80  wrote:

> Exactly what command have you used to start/restart WeeWX?
>
> 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/JWXQzbrLbms/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: wind speed and gusts discrete values?

[Thomas Keffer]

Gusts are a peak value. They are not an average. So, they retain the
precision of the original measurement.

-tk

On Sat, Sep 29, 2018 at 9:30 AM Paolo Benvenuto 
wrote:

> ok, now it's clera.
>
> However, wind speed shows continous values, while gusts do not. Is there a
> reason for this behaviour?
>
> don Paolo Benvenuto
>
>
> Il giorno sab 29 set 2018 alle ore 17:24 Andrew Milner <
> andrew.s.r.mil...@gmail.com> ha scritto:
>
>> if record generation is hardware you will get 16 discrete wind direction
>> values and windspeed to the nearest 1 mph (1.6 kph).
>>
>> If record generation is software you will get a weewx average of the loop
>> wind directions (sum of direction / number of readings) which could be any
>> value, and will not be discrete to the nearest 1 mph and the direction will
>> be sum of directions / number of readings in interval which will be a
>> greater number of values.
>>
>>
>>
>> On Saturday, 29 September 2018 16:36:53 UTC+3, Paolo Benvenuto wrote:
>>>
>>> Il giorno venerdì 28 settembre 2018 14:50:23 UTC+2, gjr80 ha scritto:

 You are using software record generation which causes windSpeed and
 windDir (and others) to be the weeWX calculated averages of the loop values
 in an archive period. On the other hand hardware record generation uses the
 archive record generated by your station. For Davis stations the windSpeed
 has a resolution of 1mph and the archive record wind directions are one of
 16 discrete directions so hence you see wind speeds that at multiples of
 1mph and discrete wind directions when you use hardware record generation.

 To change back to hardware record generation, edit weewx.conf, under
 [StdArchive] set record_generation = hardware, save weewx.conf and restart
 WeeWX.

>>>
>>> let me try with
>>>
>>> record_generation = hardware
>>>
>>> but I still cannot understand why with this setting I'm going to get
>>> continous values
>>>
>>>
 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/AjWkRbf6a6Q/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.
>

-- 
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: Belchertown Skin MQTT Updates Pressure Reading

[Pat]

Maybe. I'm not quite sure how to handle this one. 

Your MQTT published message may have both barometer_inHg as well as 
altimeter_inHg 
- or even other pressure values.

For example my station it's the altimeter_inHg that matches my console. 

I almost wonder if this needs to be a variable on which one to show?

On Monday, September 24, 2018 at 9:15:51 AM UTC-4, matt...@gmail.com wrote:
>
> Hi I changed this in the index.html template file. should this be included 
> in the next release?  Should fix the metric code also.
>
> if ( data.hasOwnProperty("altimeter_inHg") ) { 
> jQuery(".wx-barometer-value").text( parseFloat( data["barometer_inHg"] 
> ).toFixed(2) + " $unit.label.pressure" );
> // Barometer US 
>
>
> On Monday, September 24, 2018 at 7:23:13 AM UTC-4, matt...@gmail.com 
> wrote:
>>
>> Hi All,
>>
>> I have installed the Belchertown skin and have the real time updates 
>> working but I have notices the pressure reading on the static page is the 
>> barometer_inHg and the MQTT uses the altimeter_inHg.  When the pages loads 
>> I see the altitude adjusted pressure then it drops to the altimeter 
>> pressure when the real time updates start coming in.  My station, an old 
>> WM-918, send both pressures to weewx and I want to keep the barometer_in 
>> displayed.
>>
>> I see in the web page source code that the MQTT updates are coded for the 
>> altimeter pressure.  I am also running mosquito on my own PC and can 
>> subscribes to the feed and see it posting both altimeter and barometer.
>>
>> My page is on my internal network at the moment and cannot be accessed 
>> outside my house.
>>
>> How can this be fixed?
>>
>> Matt
>>
>

-- 
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] Date error on some historic data graphs using Belchertown skin

[Pat]

Hi everyone, I think this has been resolved in a latest commit. In 0.6 I 
was using timespan but also highcharts was packaged as 1 skin. The 
timespans were giving me some problems, so I reverted to time.time and that 
was causing the problems you see. Thanks Gary for taking the time to check 
my code! 

I've pushed an updated commit here 
and
 
you can view the new file in full here 
.
 
Those here are welcome to try it. If I don't hear back it'll be rolled into 
my 0.8 update when I release that. 


On Tuesday, September 25, 2018 at 9:48:21 PM UTC-4, Philip Kutzenco wrote:
>
> Yes, same for me. The week.json datafile has the last point for each 
> measurement associated with the beginning of the 60 minute period following 
> the current time. So, it is the same cause. As you say, it's likely related 
> to the timestamp Pat chose to use.
>
> Phil
>
> On Tuesday, September 25, 2018 at 7:12:57 PM UTC-4, Colin Larsen wrote:
>>
>> I've just noticed that the end of the Week chart is an hour ahead of my 
>> current time - probably all related
>>
>> On Wed, Sep 26, 2018 at 7:40 AM Colin Larsen  wrote:
>>
>>> Thanks Gary and Phil for finding and sorting this :)
>>>
>>> On Wed, 26 Sep 2018, 04:19 Philip Kutzenco,  wrote:
>>>
 Gary,

 Excellent. Thanks for sussing this out! I'll look forward to Pat's next 
 release.

 Phil

 On Tuesday, September 25, 2018 at 10:04:07 AM UTC-4, gjr80 wrote:
>
> OK, I think I have handle on what is happening here. The cause is as 
> Phil has noted, the last timestamp in each data series in month.json 
> is midnight at the end of the current local day. A commit by Pat on 4 
> September changed that timestamp from being the last timestamp in the 
> archive to being the midnight timestamp. Looking at the releases that Pat 
> has made I think 0.7 will exhibit this behaviour but 0.6 does not. I will 
> drop Pat a line with the details.
>
> Gary
>
> On Tuesday, 25 September 2018 22:14:20 UTC+10, Philip Kutzenco wrote:
>>
>> So, looking at the data in the json file, the last epoch date in the 
>> series is 153793440 and translates to September 26 at 4:00 AM UTC. 
>> So 
>> that is midnight on September 26 EDT (my time zone). So it sounds like 
>> the 
>> aggregated temperature data displayed is for the period prior to that 
>> date/time. But it definitely makes the plot seem inaccurate, especially 
>> when you look at past dates. You'd expect that the aggregated data point 
>> to 
>> correspond to the data gathered from the start of the date to midnight 
>> just 
>> before the next date starts. I hope that is clear (and that I'm not 
>> confused). 
>>
>> Phil
>>
>>
>>
>> On Tuesday, September 25, 2018 at 7:59:03 AM UTC-4, Philip Kutzenco 
>> wrote:
>>>
>>> Gary,
>>>
>>> I think this is the file you want me to post. It is timestamped 
>>> September 25, 2108 at 7:46 AM. I am in the US Eastern Time Zone 
>>> currently 
>>> observing Daylight Saving Time. So my time zone is EDT. I checked the 
>>> date 
>>> and time with the date command on my Raspberry Pi running running weewx 
>>> and 
>>> it is correct.
>>>
>>> Let me know if you wanted a different file.
>>>
>>> Thanks. I appreciate the help.
>>>
>>> Phil
>>>
>>> On Monday, September 24, 2018 at 11:33:58 PM UTC-4, gjr80 wrote:

 I suspect the issue will be related to how highcharts is 
 interpreting timestamps in the plot data rather then the wrong data 
 being 
 in the plot data files. I have seen something like this before but it 
 was 
 related to the timezone of the client computer viewing the plots, 
 would 
 seem that is not the issue here though. I am rather pushed for time at 
 the 
 moment but will have a look when I can, though it's been a while 
 though 
 since I have delved into highcharts.

 Phil, can you post one of the generated  highcharts data files that 
 is displaying the issue. Would help to know your timezone and at  what 
 time 
 the file was generated as well.

 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+...@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 unsubscri

Re: [weewx-user] Re: wind speed and gusts discrete values?

[gjr80]

windSpeed and windGust should both be using the same discrete 1mph (or 
equivalent km/h or m/s) values if you are using hardware record generation. 
Did you complete the last step in the instructions I gave you, you need to 
restart WeeWX for any changes in weewx.conf to take effect. When I look at 
your site just now you do indeed have continuous windSpeed values, but your 
site says WeeWX has been running for 2 days 6 hours, that indicates to me 
you have not restarted WeeWX.

Gary

On Sunday, 30 September 2018 02:30:22 UTC+10, Paolo Benvenuto wrote:
>
> ok, now it's clera.
>
> However, wind speed shows continous values, while gusts do not. Is there a 
> reason for this behaviour?
>
> don Paolo Benvenuto
>
>
> Il giorno sab 29 set 2018 alle ore 17:24 Andrew Milner <
> andrew.s...@gmail.com > ha scritto:
>
>> if record generation is hardware you will get 16 discrete wind direction 
>> values and windspeed to the nearest 1 mph (1.6 kph).
>>
>> If record generation is software you will get a weewx average of the loop 
>> wind directions (sum of direction / number of readings) which could be any 
>> value, and will not be discrete to the nearest 1 mph and the direction will 
>> be sum of directions / number of readings in interval which will be a 
>> greater number of values.
>>
>>
>>
>> On Saturday, 29 September 2018 16:36:53 UTC+3, Paolo Benvenuto wrote:
>>>
>>> Il giorno venerdì 28 settembre 2018 14:50:23 UTC+2, gjr80 ha scritto:

 You are using software record generation which causes windSpeed and 
 windDir (and others) to be the weeWX calculated averages of the loop 
 values 
 in an archive period. On the other hand hardware record generation uses 
 the 
 archive record generated by your station. For Davis stations the windSpeed 
 has a resolution of 1mph and the archive record wind directions are one of 
 16 discrete directions so hence you see wind speeds that at multiples of 
 1mph and discrete wind directions when you use hardware record generation.

 To change back to hardware record generation, edit weewx.conf, under 
 [StdArchive] set record_generation = hardware, save weewx.conf and restart 
 WeeWX.

>>>
>>> let me try with
>>>
>>> record_generation = hardware
>>>
>>> but I still cannot understand why with this setting I'm going to get 
>>> continous values
>>>  
>>>
 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/AjWkRbf6a6Q/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.

[weewx-user] Re: Belchertown skin for weewx now available!

[dhindley]

Thanks.  I did that and managed to get the skin installed. Looking great.  
Thanks for your work in creating the skin. Much appreciated.

On Saturday, 29 September 2018 12:13:06 UTC+1, Pat wrote:
>
> You can download the zip to your computer by using the http link in the 
> wget command, then copy the zip to your Pi using FTP, SFTP or USB file 
> copy. Whatever's easiest. 
>
> On Saturday, September 29, 2018 at 4:05:10 AM UTC-4, dhin...@djhindley.com 
> wrote:
>
> I like the look of this skin, but am failing at the first hurdle. When I 
> try to download ver 0.7 tar file using wget, I get the following error:
>
> GnuTLS:A TLS fatal alert has been received.
> Unable to establish SSL connection.
>
> I am probably doing something dumb; any ideas on how to solve this would 
> be much appreciated.  I am downloading it to my Raspberry pi.
>
> Thanks.
>
> On Tuesday, 21 August 2018 19:45:13 UTC+1, Pat wrote:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an i
>
> ...

-- 
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] Where are variables filled with data?

[Bent Jensen]

Finally I found it. 

The variable is indeed formed in the skin.conf file. Now I've got it 
working.

Thank you for your inputs. :-)

Cheers
Bent

-- 
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 using Wunderground as a source

[Charles Ross]

Interested to see if you can do this.   My wax station is 15 years old and not 
sure it’s gonna make another winter.  Looked into the Atlas but won’t consider 
until I know I can keep weewx.

Thanks for getting this started.

-- 
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] Where are variables filled with data?

[Bent Jensen]

Oh but I have. But this particular problem is not described in the 
custumizing guide.

And as far as I can see this particular variable is not constructed in the 
skin template.

I have been searching for the word "on" in the templates, and found out 
that the word "on" is in really many words. :-)

Almost everything but "on" is translated into danish.

Bent

-- 
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: wind speed and gusts discrete values?

[Paolo Benvenuto]

ok, now it's clera.

However, wind speed shows continous values, while gusts do not. Is there a
reason for this behaviour?

don Paolo Benvenuto


Il giorno sab 29 set 2018 alle ore 17:24 Andrew Milner <
andrew.s.r.mil...@gmail.com> ha scritto:

> if record generation is hardware you will get 16 discrete wind direction
> values and windspeed to the nearest 1 mph (1.6 kph).
>
> If record generation is software you will get a weewx average of the loop
> wind directions (sum of direction / number of readings) which could be any
> value, and will not be discrete to the nearest 1 mph and the direction will
> be sum of directions / number of readings in interval which will be a
> greater number of values.
>
>
>
> On Saturday, 29 September 2018 16:36:53 UTC+3, Paolo Benvenuto wrote:
>>
>> Il giorno venerdì 28 settembre 2018 14:50:23 UTC+2, gjr80 ha scritto:
>>>
>>> You are using software record generation which causes windSpeed and
>>> windDir (and others) to be the weeWX calculated averages of the loop values
>>> in an archive period. On the other hand hardware record generation uses the
>>> archive record generated by your station. For Davis stations the windSpeed
>>> has a resolution of 1mph and the archive record wind directions are one of
>>> 16 discrete directions so hence you see wind speeds that at multiples of
>>> 1mph and discrete wind directions when you use hardware record generation.
>>>
>>> To change back to hardware record generation, edit weewx.conf, under
>>> [StdArchive] set record_generation = hardware, save weewx.conf and restart
>>> WeeWX.
>>>
>>
>> let me try with
>>
>> record_generation = hardware
>>
>> but I still cannot understand why with this setting I'm going to get
>> continous values
>>
>>
>>> 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/AjWkRbf6a6Q/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: wind speed and gusts discrete values?

[Andrew Milner]

if record generation is hardware you will get 16 discrete wind direction 
values and windspeed to the nearest 1 mph (1.6 kph).

If record generation is software you will get a weewx average of the loop 
wind directions (sum of direction / number of readings) which could be any 
value, and will not be discrete to the nearest 1 mph and the direction will 
be sum of directions / number of readings in interval which will be a 
greater number of values.



On Saturday, 29 September 2018 16:36:53 UTC+3, Paolo Benvenuto wrote:
>
> Il giorno venerdì 28 settembre 2018 14:50:23 UTC+2, gjr80 ha scritto:
>>
>> You are using software record generation which causes windSpeed and 
>> windDir (and others) to be the weeWX calculated averages of the loop values 
>> in an archive period. On the other hand hardware record generation uses the 
>> archive record generated by your station. For Davis stations the windSpeed 
>> has a resolution of 1mph and the archive record wind directions are one of 
>> 16 discrete directions so hence you see wind speeds that at multiples of 
>> 1mph and discrete wind directions when you use hardware record generation.
>>
>> To change back to hardware record generation, edit weewx.conf, under 
>> [StdArchive] set record_generation = hardware, save weewx.conf and restart 
>> WeeWX.
>>
>
> let me try with
>
> record_generation = hardware
>
> but I still cannot understand why with this setting I'm going to get 
> continous values
>  
>
>> 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: wind speed and gusts discrete values?

[Paolo Benvenuto]

Il giorno venerdì 28 settembre 2018 14:50:23 UTC+2, gjr80 ha scritto:
>
> You are using software record generation which causes windSpeed and 
> windDir (and others) to be the weeWX calculated averages of the loop values 
> in an archive period. On the other hand hardware record generation uses the 
> archive record generated by your station. For Davis stations the windSpeed 
> has a resolution of 1mph and the archive record wind directions are one of 
> 16 discrete directions so hence you see wind speeds that at multiples of 
> 1mph and discrete wind directions when you use hardware record generation.
>
> To change back to hardware record generation, edit weewx.conf, under 
> [StdArchive] set record_generation = hardware, save weewx.conf and restart 
> WeeWX.
>

let me try with

record_generation = hardware

but I still cannot understand why with this setting I'm going to get 
continous values
 

> 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: Belchertown skin for weewx now available!

[Pat]

You can download the zip to your computer by using the http link in the 
wget command, then copy the zip to your Pi using FTP, SFTP or USB file 
copy. Whatever's easiest. 

On Saturday, September 29, 2018 at 4:05:10 AM UTC-4, dhin...@djhindley.com 
wrote:
>
> I like the look of this skin, but am failing at the first hurdle. When I 
> try to download ver 0.7 tar file using wget, I get the following error:
>
> GnuTLS:A TLS fatal alert has been received.
> Unable to establish SSL connection.
>
> I am probably doing something dumb; any ideas on how to solve this would 
> be much appreciated.  I am downloading it to my Raspberry pi.
>
> Thanks.
>
> On Tuesday, 21 August 2018 19:45:13 UTC+1, Pat wrote:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.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] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[gjr80]

Exactly what command have you used to start/restart WeeWX?

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: Belchertown skin for weewx now available!

[dhindley]

I like the look of this skin, but am failing at the first hurdle. When I 
try to download ver 0.7 tar file using wget, I get the following error:

GnuTLS:A TLS fatal alert has been received.
Unable to establish SSL connection.

I am probably doing something dumb; any ideas on how to solve this would be 
much appreciated.  I am downloading it to my Raspberry pi.

Thanks.

On Tuesday, 21 August 2018 19:45:13 UTC+1, Pat wrote:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick install:
>
> wget https://
> github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> sudo wee_extension --install weewx-belchertown-0.1.tar.gz
>
> Configure weewx.conf with your options
>
> Restart weewx
>
> Out of the box, it is a very basic theme. Make sure to check out the readme 
> for all options available !
>
>
> This is my first skin, and I've done all I could to test it out in various 
> environments to iron out any initial bugs. If you do find something that's 
> a little off, or room for improvement, please let me know!
>
>

-- 
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] Rain Rate record 15358.8 mm/hr on 14 May 05:48

[Glenn F]

OK   It would appear I have somehow mucked it up..  Station hadnt updated 
in 4 days so did a wee_device --clear which regenerated a current time and 
values but still does not update anymore and the offending record is still 
there.. At a loss.

On Thursday, 27 September 2018 22:59:26 UTC+12, Glenn F wrote:
>
>
> Ok that line of code was far better to establish the error, thanking you. 
> ,,  I have performed the guide from " Clean Up Old Bad Data" and finger 
> crossed that when it recycles the update it will be repaired,,  Toes 
> crossed too 
>
>
> On Tuesday, 25 September 2018 23:30:11 UTC+12, Thomas Keffer wrote:
>>
>> It's hard to read, but that's probably right. You can confirm my just 
>> selecting the most relevant columns. Try this for your SELECT statement:
>>
>> echo "SELECT dateTime, datetime(dateTime,'unixepoch','localtime'), 
>> rainRate from archive where rainRate > 100;" | sqlite3 
>> /var/tmp/datbasebu/weewx.sdb
>>
>> This print out just timestamps, the local time, and rain rates. Easier to 
>> read.
>>
>> -tk
>>
>> On Tue, Sep 25, 2018 at 3:12 AM Glenn F  wrote:
>>
>>>
>>>1. Cheers Thomas,  if you have time to view the attched imge and 
>>>see if I'm in the right direction,..  I got swamped in numbers,, love a 
>>>little clarification... 
>>>
>>>
>>> On Monday, 24 September 2018 23:30:50 UTC+12, Thomas Keffer wrote:

 Hello, Glenn

 See the Wiki entry Clean up old "bad" data 
  and 
 see if that doesn't answer your question. If not, come back and we'll dig 
 in deeper.

 -tk

 On Mon, Sep 24, 2018 at 12:38 AM Glenn F  wrote:

> It has probably been asked, and if so point me in the direction 
> please.I'd love to delete this record, I never built an ark nor got 
> flooded out, so would love this to show the actual , real, value.. 
>
> Running a FineOffsetUSB system .  
>
> Glenn.. 
>
> -- 
> 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+...@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.