Re: [weewx-user] How to pronounce "WeeWX"

[V. Kelly Bellis]

[image: no-so-wee-wx.png]


On Monday, August 12, 2019 at 10:25:07 AM UTC-4, Thomas Keffer wrote:
>
> "WX" is a common abbreviation for "weather."
>
> The "wee" part refers to my intention to make it a small, simple utility 
> (as opposed to its predecessor, wview). Unfortunately, it has since grown 
> into nearly as big a monster, albeit with a simpler, more modular 
> architecture.
>
> -tk
>
> On Mon, Aug 12, 2019 at 7:22 AM Michi Kaa  > wrote:
>
>> Well then, I will pronounce it that way. And I don't care what people 
>> around may think when they hear me talking about it without knowing wat it 
>> is :)
>> And what doest it mean/stand for? My guess is that at least one of the 
>> "W" is related to the noun "weather".
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1cb74dbf-f074-41f6-bcee-d0dc6346dd3a%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/17ed6301-b9c7-481a-b220-bf294b047746%40googlegroups.com.

[weewx-user] Re: On this date

[V. Kelly Bellis]

Thanks for doing this Gary. I'm too new to all of this stuff to have 
anything to look back on, but it's very cool to see what can be done with 
weewx.
- Kelly

On Tuesday, May 14, 2019 at 8:37:55 PM UTC-4, gjr80 wrote:
>
> I should have given this a little more thought before publishing. I have 
> since made a slight change to the tag name to make it a little more logical 
> and consistent with the other iterative tags that WeeWX supports (and to 
> remove a 'this'). The tag now uses .periods in lieu of .this; for 
> example, you would now use the $this_span tag as follows:
>
> #for $day in this_span.periods
> $day.outTemp.max at $day.outTemp.maxtime
> #end for
>
> Any existing template code will work fine with the current version with 
> just the need to change '.this' to '.periods'.
>
> I have also created a page 
>  
> in the wiki of the repo containing the this search list extension code 
> that explains the installation and usage of the this search list extension. 
> Hopefully this is a little more user friendly and easier to read than 
> comments in the code.
>
> Gary
>
> On Monday, 13 May 2019 17:40:37 UTC+10, gjr80 wrote:
>>
>> I've put together a search list extension that should do what you want. 
>> You will find the code here 
>> .
>>  
>> The SLE is based on the existing WeeWX tag machinery that enables 
>> iteration  over 
>> periods. So with the SLE installed you can do something like:
>>
>> #for $day in this_span.this
>> $day.outTemp.max at $day.outTemp.maxtime
>> #end for
>>
>> to display the maximum daily temperature and the time it occurred on this 
>> day in all years in the archive. The output would be something like:
>>
>> 24.5°C at 11 May 2017 12:51:00
>> 26.7°C at 11 May 2018 13:31:00
>> 23.4°C at 11 May 2019 13:15:00
>>
>> There are various parameters that can be set against $this_span to limit 
>> the period covered (the default is all records but you can limit it to the 
>> last x years, months etc as with the existing $span tag). There are 
>> various parameters that can be applied to .this to set the day to be 
>> used, for example, .this($period='week') and .this($period='month') will 
>> provide stats for this week and this month respectively over all years. 
>> There are many variations and permutations, I have tried to capture a 
>> variety of use cases in the up front comment in this.py 
>> 
>> .
>>
>> To install/use:
>>
>> 1. Download the file this.py to the WeeWX machine and save to the 
>> $BIN_ROOT/user directory:
>>
>> for a setup.py install:
>> 
>> $ wget -P /home/weewx/bin/user https://
>> raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py
>>
>> otherwise:
>>
>> $ wget -P /usr/share/weewx/user https://
>> raw.githubusercontent.com/gjr80/weewx_utilities/master/search%20list%20extensions/this/bin/user/this.py
>>
>> 2.  Add the following line to the skin config file [CheetahGenerator] 
>> stanza for the skin in which the SLE is to be used:
>> 
>> search_list_extensions = user.this.ThisSLE
>>
>> if the search_list_extensions config option already exists add 
>> user.this.ThisSLE to the end of the option using a comma as a separator, 
>> eg:
>> 
>> search_list_extensions = user,another.SLE, user.this.ThisSLE
>>
>> 3.  Add the required $this_span.this code to the template concerned.
>>
>> 4.  After the next report cycle is complete confirm there are no errors 
>> in the log and the report has been generated as expected.
>>
>> Gary
>>
>> On Saturday, 11 May 2019 23:30:47 UTC+10, Robin wrote:
>>>
>>> I apologise if this has been asked before or if there is a simple and 
>>> obvious way to do this, but I can't see it.
>>>
>>> I want to display the temperature (min,max) for today's date for each 
>>> year since we started keeping records.
>>>
>>> Can somebody point me in the right direction?
>>>
>>> Thanks people.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bcdade04-dfe7-428d-8739-d6e9d3cd3823%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Barometric pressure correction the right way

[V. Kelly Bellis]

@Louis De Lange, thanks for mentioning this. By any chance, do you recall 
where you read that FineOffset was using indoortemp for pressure 
calculations?

On Sunday, January 14, 2018 at 2:35:33 PM UTC-5, Louis De Lange wrote:
>
> As a previous owner of a Fine Offset station I can confirm that I noticed 
> this same behavior.  Living in Canada where our homes are heated, I could 
> clearly see the altimeter reading (my station did not support barometer 
> correction to sea level) seesaw with the furnace operating and shutting 
> down.  
>
> *Reading up on the issue it appeared that the Fine Offset hardware was 
> doing a temperature correction internal to the indoor unit*, but that 
> quick changes to the indoor temperature threw the reading off.  There is no 
> way that you can correct for that with calibration - it is a flaw in the 
> hardware.  
>

-- 
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: Seasons' Current Conditions Baro (Parenthetical) - Meaning?

[V. Kelly Bellis]

Got it!
https://github.com/weewx/weewx/blob/master/bin/weewx/uwxutils.py

Thanks for your help Andrew!

On Tuesday, April 30, 2019 at 10:17:31 AM UTC-4, V. Kelly Bellis wrote:
>
> Maybe here?
> https://github.com/weewx/weewx/blob/master/bin/weewx/wxformulas.py
>

-- 
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: Seasons' Current Conditions Baro (Parenthetical) - Meaning?

[V. Kelly Bellis]

Maybe here?
https://github.com/weewx/weewx/blob/master/bin/weewx/wxformulas.py

-- 
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: Seasons' Current Conditions Baro (Parenthetical) - Meaning?

[V. Kelly Bellis]

Thank you for the reply Andrew. Followup questions below

On Tuesday, April 30, 2019 at 9:35:13 AM UTC-4, Andrew Milner wrote:
>
> 1. It is the change in pressure over, I think, the last 3 hours.  Check 
> the template and see what delta is actually being used to populate the 
> field if you want a definitive answer
>

Is this where and what you were referring to?
/etc/weewx/skins/Seasons/statistics.inc
...

  $obs.label.barometer
  $unit.label.barometer
  #for $archive in $archive_data
  $archive.barometer.max.format(add_label=False)
$archive.barometer.maxtime
$archive.barometer.min.format(add_label=False)
$archive.barometer.mintime
  
  #end for


I'm guessing this is probably the wrong answer.
 

>
> 3.  You say you have an Ambient station rather than Fine Offset - so what 
> applies to one may not apply to the other.  Only read things pertaining to 
> your specific station.  The formula used for barometer and altimeter 
> derivations are well documented - either search the forum for this specific 
> answer or check the comments in the code.
>

Ambient is rebranded FineOffset hardware.

Might you know in which file and where exactly that code is contained?
 

> 4.  All weewx calculations are done using floating point with REAL types 
> and no restriction on number of places.  If you use MySQL instead of 
> sqlite3 it is possible to specify in the database fields the number of 
> digits to the right - but as far as I know this is not possible in sqlite3.
>

I embarrassed to admit, I know next to nothing about SQL no matter what 
database engine is in play; however, I trying to learn on my own. Next year 
when I turn 65, I plan to enroll in University of Maine classes as that's 
when tuition fees are waived.

-- 
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] Seasons' Current Conditions Baro (Parenthetical) - Meaning?

[V. Kelly Bellis]

[image: Seasons' Current Conditions (Parenthetical).PNG]
Under Current Conditions in the Seasons skin, the Barometer value is 
appended with a parenthetical value; e.g., 1024.3 hPa(-0.1)

1) What is the meaning of the appended parenthetical value? In all 
truthfulness, I've only now have just taken note of it as I prepare to make 
a calibration adjustment on the display console (Ambient Weather WS-2000), 
my first such adjustment since enlisting weewx. My guess is that it shows 
the change in pressure when compared to the previous report; e.g., 5 
minutes ago.

2) The related question to this pertains to the first value; e.g., 1024.3 
hPa, should it be exactly identical with the value shown on the display 
console when the pressure is steady through multiple update intervals?

I've read  that 
weewx receives 'pressure' from FineOffset hardware and then calculates 
'barometer' values. This brings up two more questions.

3) What is the formula that is being used and to how many places to the 
right of the decimal is this formula applied?

4) Loop packets suggest that 'pressure' is being reported by the hardware 
in units of inHg to 2 significant digits, is this a false assumption? and 
how might it be proven? 

pi@raspberrypi:/etc/weewx $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@raspberrypi:/etc/weewx $ sudo weewxd weewx.conf
LOOP:   2019-04-28 10:51:20 EDT (1556463080) altimeter: 29.8717169546, appTemp: 
42.072810622, barometer: 29.8843336142, cloudbase: 3250.42822233, dateTime: 
1556463080, dewpoint: 33.8944955053, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.4872761332, inHumidity: 39, inTemp: 67.3, maxSolarRad: 
815.85703395, outHumidity: 59, outTemp: 47.5, pressure: 29.71, radiation: 
881.07, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 46.1399181728, 
windDir: 290, windGust: 4.5, windSpeed: 3.8
LOOP:   2019-04-28 10:51:36 EDT (1556463096) altimeter: 29.8717169546, appTemp: 
42.2517904021, barometer: 29.8843336142, cloudbase: 3154.86029954, dateTime: 
1556463096, dewpoint: 34.3149943656, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.4872761332, inHumidity: 39, inTemp: 67.3, maxSolarRad: 
816.299633379, outHumidity: 60, outTemp: 47.5, pressure: 29.71, radiation: 
878.37, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 46.3046187182, 
windDir: 307, windGust: 4.5, windSpeed: 3.6
LOOP:   2019-04-28 10:51:52 EDT (1556463112) altimeter: 29.8717169546, appTemp: 
41.6321945021, barometer: 29.8843336142, cloudbase: 3154.86029954, dateTime: 
1556463112, dewpoint: 34.3149943656, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.4872761332, inHumidity: 39, inTemp: 67.3, maxSolarRad: 
816.741118563, outHumidity: 60, outTemp: 47.5, pressure: 29.71, radiation: 
877.51, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 45.478419953, 
windDir: 312, windGust: 5.8, windSpeed: 4.7
LOOP:   2019-04-28 10:52:08 EDT (1556463128) altimeter: 29.8717169546, appTemp: 
42.6460787021, barometer: 29.8843336142, cloudbase: 3154.86029954, dateTime: 
1556463128, dewpoint: 34.3149943656, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.4872761332, inHumidity: 39, inTemp: 67.3, maxSolarRad: 
817.181491045, outHumidity: 60, outTemp: 47.5, pressure: 29.71, radiation: 
874.46, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 47.5, windDir: 
291, windGust: 4.5, windSpeed: 2.9
LOOP:   2019-04-28 10:52:24 EDT (1556463144) altimeter: 29.8717169546, appTemp: 
40.9662707821, barometer: 29.8843336142, cloudbase: 3060.68950083, dateTime: 
1556463144, dewpoint: 34.7293458799, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.4872761332, inHumidity: 39, inTemp: 67.3, maxSolarRad: 
817.620605418, outHumidity: 61, outTemp: 47.5, pressure: 29.71, radiation: 
874.46, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 44.6901761734, 
windDir: 310, windGust: 9.2, windSpeed: 6.0
LOOP:   2019-04-28 10:52:40 EDT (1556463160) altimeter: 29.8717169546, appTemp: 
39.4917723021, barometer: 29.8843336142, cloudbase: 3154.86029954, dateTime: 
1556463160, dewpoint: 34.3149943656, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.4872761332, inHumidity: 39, inTemp: 67.3, maxSolarRad: 
818.058803625, outHumidity: 60, outTemp: 47.5, pressure: 29.71, radiation: 
874.46, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 43.5112234785, 
windDir: 308, windGust: 11.4, windSpeed: 8.5
LOOP:   2019-04-28 10:52:56 EDT (1556463176) altimeter: 29.8817634304, appTemp: 
40.8999448021, barometer: 29.8943922927, cloudbase: 3154.86029954, dateTime: 
1556463176, dewpoint: 34.3149943656, heatindex: 47.5, humidex: 47.5, 
inDewpoint: 41.665600342, inHumidity: 39, inTemp: 67.5, maxSolarRad: 
818.495940296, outHumidity: 60, outTemp: 47.5, pressure: 29.72, radiation: 
874.09, rain: 0.0, rainRate: 0, usUnits: 1, UV: 8, windchill: 44.6901761734, 
windDir: 257, windGust: 6.9, windSpeed: 6.0


Thank you very much for any reply.

Kind regards,

Kelly


-- 
You 

[weewx-user] Re: connect station without a console to Raspberrypi??

[V. Kelly Bellis]

Hi Ramesh,

That USB SDR link is for a TV receiver. Depending on your PWS outdoor 
array's transmission frequency; e.g., 433 MHz, you'll want to make certain 
that the SDR device is able to receive that frequency. A good thread to 
study regarding this stuff, including weewx driver discussions and links, 
is Stephen Rose's 
"Software Defined Radio with the WS-2902A 
". While 
I understand that you don't have the WS-2902A, I think that you will still 
benefit from this relevant topic.

Kind regards,

Kelly


On Saturday, April 27, 2019 at 12:36:43 PM UTC-4, Ramesh Rasappan wrote:
>
> Currently, my WS-2310 (Fine Offset type) is connected to a console 
> (WH2310) which in-turn plugged to a Raspberrypi. This setup works well.
>
> Now, I want to connect my PWS (WS-2310) to Raspberrypi without a console. 
> I did hear that we could use any USB SDR device. My question is, what is 
> the simplest way to connect my PWS to Raspberrypi? can I wire the station 
> to Raspberrypi? in that case what are the hardware components that I'll 
> need. Thanks
>
> found this USB SDR device on Aliexpress, link here 
> 
>
>

-- 
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: get WU forecast not working any more...?

[V. Kelly Bellis]

Correct, you will need to locate the folder where forecast.py resides on 
your system; for example,
/usr/share/weewx/user/forecast.py

And then manually replace it with the new version.

Kind regards,

Kelly


On Friday, April 19, 2019 at 1:09:43 PM UTC-4, Christian Peters wrote:

> Thanks for clarifying. 
> So I have to update I think...
>
> The link points to a.py file I can't install via 'wee_extension --install 
>  ' as it looks for a .tgz?!
> I think I should do it in that way as I think some major things changed 
> since 3.4.0 in the weewx.conf and the installer would add the right default 
> entries.?
>
> Regards,
>
> Christian 
>
> Am Freitag, 19. April 2019 14:29:45 UTC+2 schrieb V. Kelly Bellis:
>>
>> Please use forecast.py version 3.4.0rc2 until Matt is able to incorporate 
>> the Weather Underground API changes.
>>
>> https://groups.google.com/group/weewx-user/attach/639775dd1c899/forecast-3.4.0rc2.py
>>
>> Yes, you figured correctly; WU changed their services, dropping 
>> <https://apicommunity.wunderground.com/weatherapi/topics/end-of-service-for-the-weather-underground-api>
>>  
>> one - announced last November or so - in favor of another that only 
>> recently became live. More on the new stuff here: 
>> https://www.wunderground.com/weather/api/d/docs
>>
>> Open Weather Map works fine for me following the outlined procedures here:
>> https://github.com/weewx/weewx/wiki/forecasting
>>
>> And don't forget to:
>>
>> sudo /etc/init.d/weewx stop
>> sudo /etc/init.d/weewx start
>>
>>
>> Also noteworthy, the National Weather Forecast is phasing out an old 
>> product in favor of their point-n-click gridded forecasts for more 
>> localized forecasts. When Matt's day job eases up, I'm hopeful that the old 
>> NWS method codified into his forecast.py will be dropped in favor of NWS's 
>> current gridded method. It and a lot more here: 
>> https://www.weather.gov/mdl/digitalforecastservices_home
>>
>> [image: OWM Cities.PNG]
>>
>> Above, a map of all OWM cities I made from their database.
>>
>> For Germany, check out 
>> https://openweathermap.org/weathermap?basemap=map=true=temperature=30=-20=5
>>
>>
>>
>> On Friday, April 19, 2019 at 7:15:18 AM UTC-4, Christian Peters wrote:
>>>
>>> Hi all,
>>>
>>> my forecast disappears from my standard screen. As I figured out here 
>>> there was an API change of WU service. I obtain the new (longer) key but as 
>>> there seems to be even a change of the format, it doesn't work. 
>>> I run forecast 3.0.4. I see there is a much more recent version but I 
>>> see there was a lot of changes. Is it a big deal to update to the latest 
>>> forecast form 3.0.4? 
>>> Is there an option to stay on 3.0.4? But I need the forcast for 
>>> Germany...? I tried in 3.0.4 to add OWM...but I think it's not implemented 
>>> in this (old) version?
>>>
>>> Regards,
>>>
>>> Christian 
>>>
>>

-- 
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: Manual entry for precipitation?

[V. Kelly Bellis]

That would be an example name; i.e., Status.db, which I would create in 
LibreOffice Base. 

On Friday, April 19, 2019 at 10:51:39 AM UTC-4, p q wrote:
>
> I did five minutes of googling and I can't find a clear reference to 
> stratus db. Is it a SQL database or an application?
>
> If you're using SQLite with Weewx, it's pretty easy to manually edit data 
> using a tool like DB Browser. The only thing that's at all tough is it 
> shows the datetime as epoch and you'll need to translate that to your local 
> time to find the records you want to edit. I use it to clean up spurious 
> wind records that sometimes show up in my archive.
>
> On Fri, Apr 19, 2019 at 7:21 AM vince > 
> wrote:
>
>> On Friday, April 19, 2019 at 6:51:44 AM UTC-7, V. Kelly Bellis wrote:
>>
>> Is this still the case, now some nearly five years later, that weewx 
>>> doesn't provide an avenue for data entry from humans?
>>>
>>
>> If nobody 'volunteered' their time to write it and release it, then of 
>> course yes it's still the case. 
>>
>>
>>  
>>
>>> might be the best method to keep track of the numbers from both the 
>>> tipping bucket and the Stratus rain gauge.
>>>
>>>
>> You'd have to write something to write to a database.   Now that we're 
>> weewx v3 you can have alternate db with whatever schema you want, and 
>> basically any way you want to populate the data into it
>>
>> -- 
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Peter Quinn
> (415)794-2264
>

-- 
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: Manual entry for precipitation?

[V. Kelly Bellis]

Thank you Vince; do you have a link to instructions on how to use an 
alternate db in weewx?


On Friday, April 19, 2019 at 10:21:29 AM UTC-4, vince wrote:
>
> On Friday, April 19, 2019 at 6:51:44 AM UTC-7, V. Kelly Bellis wrote:
>
> Is this still the case, now some nearly five years later, that weewx 
>> doesn't provide an avenue for data entry from humans?
>>
>
> If nobody 'volunteered' their time to write it and release it, then of 
> course yes it's still the case. 
>
>
>  
>
>> might be the best method to keep track of the numbers from both the 
>> tipping bucket and the Stratus rain gauge.
>>
>>
> You'd have to write something to write to a database.   Now that we're 
> weewx v3 you can have alternate db with whatever schema you want, and 
> basically any way you want to populate the data into it
>
>

-- 
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: Manual entry for precipitation?

[V. Kelly Bellis]

[image: bottom of meniscus 241ish at 20190419 0724 EDT.jpg]


Hello Andrew, et al,

Is this still the case, now some nearly five years later, that weewx 
doesn't provide an avenue for data entry from humans? I fully expect this 
is still the case, and am just curious as I ponder what might be the best 
method to keep track of the numbers from both the tipping bucket and the 
Stratus rain gauge.

I've only started using LibreOffice Base in the past few days, and having 
never fully appreciated the distinctions of databases compared to 
spreadsheets. I'm wondering if it might be possible to create a new Stratus 
database, and then link it (somehow?) to weewx's database table for forms 
and queries in the Stratus db. Does that sound plausible?

Kind regards,

Kelly

On Saturday, May 24, 2014 at 2:01:35 AM UTC-4, Andrew Milner wrote:
>
> I think you will have to create your own service or software for this - 
> and I doubt that it will be quite as simple as you possibly expect!!  To be 
> considered are such things as spreading out the daily total over the 
> archive records which correspond to the daily total, updating the stats 
> database correctly, handling missing text file, wrongly formed text file, 
> etc  and then uploading the updated archive records to wherever you are 
> trying to send them - replacing possibly already uploaded archive 
> records submitted before the daily melt total was available. and so on 
> .
>
>
> On Friday, 23 May 2014 22:11:22 UTC+3, Nate Bargmann wrote:
>>
>> I've not found this in the documentation. 
>>
>> Has there been consideration of some method of entering daily 
>> precipitation amounts that could be read and parsed by weewx, archived 
>> and also posted to the various upload services that would accept that 
>> data? 
>>
>> I am thinking of being able to enter a daily rainnfall/snowfall total 
>> (yes, the automatic rain gauge is nice, but it doesn't always work out) 
>> that could include a time range, data range, or date/time range and 
>> total precip amount that could be designated as snowfall and snow melt. 
>> As there is no GUI in weewx (and I am not asking for one!), I am 
>> thinking of being able to write a string in a file that weewx could read 
>> periodically. 
>>
>> - Nate 
>>
>> -- 
>>
>> "The optimist proclaims that we live in the best of all 
>> possible worlds.  The pessimist fears this is true." 
>>
>> Ham radio, Linux, bikes, and more: http://www.n0nb.us 
>>
>

-- 
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: get WU forecast not working any more...?

[V. Kelly Bellis]

Christian, try this link instead. Unsure how I messed the first one up 
https://openweathermap.org/weathermap?basemap=map=true=temperature=51.5=10.5=7

On Friday, April 19, 2019 at 8:29:45 AM UTC-4, V. Kelly Bellis wrote:
>
>
> For Germany, check out 
> https://openweathermap.org/weathermap?basemap=map=true=temperature=30=-20=5
>
>

-- 
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: Forecast XTide error

[V. Kelly Bellis]

Thanks Matt for all of your donated labors for the weewx community; it is 
very much appreciated!

When you've time, one other forecast request; i.e. 

[Forecast] 
  [[*needed_fixes*]]

   - WU new API keys and commands - already mentioned
   - *NWS new Point-n-Click product*
   
The old NWS 3-letter forecast office identifier (foid, also referred to as 
HADS) and 6-character location identifier (lid) are being phased out; this 
is the NWS so-called PFM product. It has been replaced with the 
Point-n-Click product (quasi-official product name) allowing for more 
localized forecasts from a gridded database. More on that here: 
https://www.weather.gov/mdl/ndfd_home

Thanks again for fixing the XTide v2.15.2 issue!

Kind regards,

Kelly



On Sunday, April 14, 2019 at 6:44:39 PM UTC-4, mwall wrote:
>
> 'real work' is sucking up a lot of my time at the moment, but i'm trying 
> to get the new WU forecasts, UK met fixes, and possibly one or two 
> additional forecast sources into the 3.4.0 release of forecast extension.  
> until then, please use rc2.
>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

*YAY MATT!! Success at long last :) THANK YOU MATT!!!*

[image: success at long last.PNG]

My notes along the way to success:
10:07 AM   Sunday, April 7, 2019  (VKB)

Matt says:

for weewx installed via apt, you want:

PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/forecast.py 
--action=parse --method=xtide --filename=/var/tmp/ellsworth.txt --debug

Results:
pi@raspberrypi:~ $ PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/forecast.py --action=parse --method=xtide 
--filename=/var/tmp/ellsworth.txt --debug
[{'event_ts': 1554590640, 'dateTime': 1554646140, 'location': None, 'hilo': 
'L', 'offset': '0.64', 'issued_ts': 1554646140, 'method': 'XTide', 
'usUnits': 1}, {'event_ts': 1554612480, 'dateTime': 1554646140, 'location': 
None, 'hilo': 'H', 'offset': '11.10', 'issued_ts': 1554646140, 'method': 
'XTide', 'usUnits': 1}, {'event_ts': 1554635100, 'dateTime': 1554646140, 
'location': None, 'hilo': 'L', 'offset': '0.14', 'issued_ts': 1554646140, 
'method': 'XTide', 'usUnits': 1}, {'event_ts': 1554657000, 'dateTime': 
1554646140, 'location': None, 'hilo': 'H', 'offset': '10.76', 'issued_ts': 
1554646140, 'method': 'XTide', 'usUnits': 1}, {'event_ts': 1554679020, 
'dateTime': 1554646140, 'location': None, 'hilo': 'L', 'offset': '0.64', 
'issued_ts': 1554646140, 'method': 'XTide', 'usUnits': 1}, {'event_ts': 
1554700740, 'dateTime': 1554646140, 'location': None, 'hilo': 'H', 
'offset': '11.33', 'issued_ts': 1554646140, 'method': 'XTide', 'usUnits': 
1}, {'event_ts': 1554723720, 'dateTime': 1554646140, 'location': None, 
'hilo': 'L', 'offset': '-0.03', 'issued_ts': 1554646140, 'method': 'XTide', 
'usUnits': 1}, {'event_ts': 1554745500, 'dateTime': 1554646140, 'location': 
None, 'hilo': 'H', 'offset': '10.73', 'issued_ts': 1554646140, 'method': 
'XTide', 'usUnits': 1}, {'event_ts': 1554767640, 'dateTime': 1554646140, 
'location': None, 'hilo': 'L', 'offset': '0.70', 'issued_ts': 1554646140, 
'method': 'XTide', 'usUnits': 1}, {'event_ts': 1554789300, 'dateTime': 
1554646140, 'location': None, 'hilo': 'H', 'offset': '11.48', 'issued_ts': 
1554646140, 'method': 'XTide', 'usUnits': 1}, {'event_ts': 1554812640, 
'dateTime': 1554646140, 'location': None, 'hilo': 'L', 'offset': '-0.10', 
'issued_ts': 1554646140, 'method': 'XTide', 'usUnits': 1}, {'event_ts': 
1554834360, 'dateTime': 1554646140, 'location': None, 'hilo': 'H', 
'offset': '10.62', 'issued_ts': 1554646140, 'method': 'XTide', 'usUnits': 
1}, {'event_ts': 1554856560, 'dateTime': 1554646140, 'location': None, 
'hilo': 'L', 'offset': '0.83', 'issued_ts': 1554646140, 'method': 'XTide', 
'usUnits': 1}, {'event_ts': 1554878280, 'dateTime': 1554646140, 'location': 
None, 'hilo': 'H', 'offset': '11.52', 'issued_ts': 1554646140, 'method': 
'XTide', 'usUnits': 1}, {'event_ts': 1554901860, 'dateTime': 1554646140, 
'location': None, 'hilo': 'L', 'offset': '-0.08', 'issued_ts': 1554646140, 
'method': 'XTide', 'usUnits': 1}]
pi@raspberrypi:~ $

==

Matt says:

you should probably put tide.sh in /usr/share/weewx/user/tide.sh

Then:
pi@raspberrypi:/opt/weewx/bin/user $ sudo mv tide.sh 
/usr/share/weewx/user/tide.sh
=

Matt says:

then adjust paths in weewx.conf appropriately

Then in /etc/weewx/weewx.conf

Looking @ line 639, et als 
#

# Options for extension 'forecast'
[Forecast]
data_binding = forecast_binding
[[NWS]]
lid = MEZ029
foid = CAR
...
[[XTide]]
prog = /usr/share/weewx/user/tide.sh
location = Ellsworth


Success at long last! YAY Matt!
10:32 AM   Sunday, April 7, 2019  (VKB)



On Saturday, April 6, 2019 at 8:17:13 PM UTC-4, mwall wrote:

>
>
> On Saturday, April 6, 2019 at 2:21:39 PM UTC-4, V. Kelly Bellis wrote:
>>
>> Trying next:
>> PYTHONPATH=bin python /usr/share/weewx/user/forecast.py --action=parse 
>> --method=xtide --filename=/var/tmp/ellsworth.txt --debug
>>
>> Which then reults:
>> pi@raspberrypi:/ $ PYTHONPATH=bin python 
>> /usr/share/weewx/user/forecast.py --action=parse --method=xtide 
>> --filename=/var/tmp/ellsworth.txt --debug
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/user/forecast.py", line 566, in 
>> import weewx
>> ImportError: No module named weewx
>>
>
> for weewx installed via apt, you want:
>
> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/forecast.py 
> --action=parse --method=xtide --filename=/var/tmp/ellsworth.txt --debug
>
> you should probably put tide.sh in /usr/share/weewx/user/tide.sh
>
> or maybe create a directory /opt/tide and fill it with:
>
> /opt/tide/tide.sh
> /opt/tide/harmonics-dwf-20181227-free.tcd
>
> then adjust paths in tide.sh and weewx.conf appropriately
>
> i put it in /opt/weewx/bin/user/tide.sh because my weewx is installed at 
> /opt/weewx
>
> m
>

[weewx-user] Re: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

*Notes on my way to nowhere*

11:41 AM   Saturday, April 6, 2019  (VKB)

Matt says:
then i installed the harmonics file:

sudo mkdir /opt/harmonics
cd /opt/harmonics
tar xvf ~/Downloads/harmonics-dwf-20181227-free.tar.bz2

=
1)
Just checking, should permissions be addressed?, i.e.:
sudo mkdir /opt/harmonics
sudo chmod 755 /opt/harmonics

or are they okay by default?

2)
cd /opt/harmonics
tar xvf ~/Downloads/harmonics-dwf-20181227-free.tar.bz2

This results in failure.
pi@raspberrypi:~ $ sudo mkdir /opt/harmonics
pi@raspberrypi:~ $ cd /opt/harmonics
pi@raspberrypi:/opt/harmonics $ tar xvf 
~/Downloads/harmonics-dwf-20181227-free.tar.bz2
harmonics-dwf-20181227/
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
harmonics-dwf-20181227/harmonics-dwf-20181227-free.tcd
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
tar: harmonics-dwf-20181227/harmonics-dwf-20181227-free.tcd: Cannot open: 
No such file or directory
harmonics-dwf-20181227/README
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
tar: harmonics-dwf-20181227/README: Cannot create symlink to ‘COPYING’: No 
such file or directory
harmonics-dwf-20181227/Disclaimers
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
tar: harmonics-dwf-20181227/Disclaimers: Cannot create symlink to 
‘COPYING’: No such file or directory
harmonics-dwf-20181227/ChangeLog
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
tar: harmonics-dwf-20181227/ChangeLog: Cannot open: No such file or 
directory
harmonics-dwf-20181227/COPYING
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
tar: harmonics-dwf-20181227/COPYING: Cannot open: No such file or directory
harmonics-dwf-20181227/AUTHORS
tar: harmonics-dwf-20181227: Cannot mkdir: Permission denied
tar: harmonics-dwf-20181227/AUTHORS: Cannot create symlink to ‘COPYING’: No 
such file or directory
tar: Exiting with failure status due to previous errors

3)
pi@raspberrypi:/opt/harmonics $ sudo tar xvf 
~/Downloads/harmonics-dwf-20181227-free.tar.bz2

sudo is required because we're making a sub-directory during extraction; 
i.e., 
/opt/harmonics/harmonics-dwf-20181227

4)
Just checking, should permissions be addressed?, i.e.:
pi@raspberrypi:$ sudo chmod 644 
/opt/harmonics/harmonics-dwf-20181227/harmonics-dwf-20181227-free.tcd

or are they okay by default?

5)
Why bury/ nest the harmonics file below /opt/harmonics/
Why not have /opt/harmonics/harmonics-dwf-20181227-free.tcd


Matt says:
this is my tide wrapper at /opt/weewx/bin/user/tide.sh (there are only 2 
lines in the file):

#!/bin/sh
HFILE_PATH=/opt/harmonics/harmonics-dwf-20181227/harmonics-dwf-20181227-free.tcd
 
LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/tide "$@"

=

6)
No such folders exist.

pi@raspberrypi:/ $ sudo mkdir /opt/weewx
pi@raspberrypi:/ $ sudo mkdir /opt/weewx/bin
pi@raspberrypi:/ $ sudo mkdir /opt/weewx/bin/user

Created tide.sh, then
sudo cp /home/pi/weewx/extensions/forecast/tide.sh 
/opt/weewx/bin/user/tide.sh

Here again, just checking, should permissions be addressed?


Matt says:

i generated tide output for testing like this:

/opt/weewx/bin/user/tide.sh -l ellsworth -fc -df'%Y.%m.%d' -tf'%H:%M' > 
/var/tmp/ellsworth.txt



7)
Permission denied.

pi@raspberrypi:/opt/weewx/bin/user $ /opt/weewx/bin/user/tide.sh -l 
ellsworth -fc -df'%Y.%m.%d' -tf'%H:%M' > /var/tmp/ellsworth.txt
bash: /opt/weewx/bin/user/tide.sh: Permission denied

pi@raspberrypi:/opt/weewx/bin/user $ sudo /opt/weewx/bin/user/tide.sh -l 
ellsworth -fc -df'%Y.%m.%d' -tf'%H:%M' > /var/tmp/ellsworth.txt
sudo: /opt/weewx/bin/user/tide.sh: command not found

pi@raspberrypi:/ $ cd  /opt/weewx/bin/user/
pi@raspberrypi:/opt/weewx/bin/user $ ls
tide.sh
pi@raspberrypi:/opt/weewx/bin/user $ 


8)
Has Matt directed to wrong location or is it only an issue of permissions 
to be considered in any of what he outlined?

First, let's try it with permissions set:
sudo chmod 755 /opt/weewx/bin/user/tide.sh

Then once again:
pi@raspberrypi:/ $ /opt/weewx/bin/user/tide.sh -l ellsworth -fc 
-df'%Y.%m.%d' -tf'%H:%M' > /var/tmp/ellsworth.txt
bash: /opt/weewx/bin/user/tide.sh: /bin/sh^M: bad interpreter: No such file 
or directory
pi@raspberrypi:/ $

Issue created by initial creating tide.sh in TextPad on PC, specifically, 
new line in PC mode. Edited again in TextPad and saved as UNIX.

And again:
pi@raspberrypi:~/weewx/extensions/forecast $ /opt/weewx/bin/user/tide.sh -l 
ellsworth -fc -df'%Y.%m.%d' -tf'%H:%M' > /var/tmp/ellsworth.txt
Indexing 
/opt/harmonics/harmonics-dwf-20181227/harmonics-dwf-20181227-free.tcd...

Success! /var/tmp/ellsworth.txt was created YAY!


Matt says:

then i verified the tide parsing like this:

PYTHONPATH=bin python bin/user/forecast.py --action=parse --method=xtide 
--filename=/var/tmp/ellsworth.txt --debug

==

9)
pi@raspberrypi:~/weewx/extensions/forecast $ PYTHONPATH=bin python 
bin/user/forecast.py 

[weewx-user] Re: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

This is wonderful Matt, thank you so very much!! I will study this and try 
implementing this weekend.

FWIW, I followed the procedure as outlined in the section entitled 
"*Installation 
Guide For New Users of XTide*" that I wrote when I created XTide v2.15.2 
Help (b20190309) 
. 
Although it was written with Ubuntu in play, installation on the RPi was 
nearly identical.

Kind regards,

Kelly


On Friday, April 5, 2019 at 5:24:39 PM UTC-4, mwall wrote:

> please try the attached forecast 3.4.0rc2.py.  i did an install of tide 
> 2.15.2 on a raspberry pi, with no other tide installation, and it works 
> with forecast 3.4.0rc2.py
>
> this is how i compiled libtcd:
>
> ./configure
> make
> sudo make install
>
> this is how i compiled tide:
>
> ./configure
> make
> sudo make install
>
> then i installed the harmonics file:
>
> sudo mkdir /opt/harmonics
> cd /opt/harmonics
> tar xvf ~/Downloads/harmonics-dwf-20181227-free.tar.bz2
>
> this is my tide wrapper at /opt/weewx/bin/user/tide.sh (there are only 2 
> lines in the file):
>
> #!/bin/sh
> HFILE_PATH=/opt/harmonics/harmonics-dwf-20181227/harmonics-dwf-20181227-free.tcd
>  
> LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/tide "$@"
>
> i generated tide output for testing like this:
>
> /opt/weewx/bin/user/tide.sh -l ellsworth -fc -df'%Y.%m.%d' -tf'%H:%M' > 
> /var/tmp/ellsworth.txt
>
> then i verified the tide parsing like this:
>
> PYTHONPATH=bin python bin/user/forecast.py --action=parse --method=xtide 
> --filename=/var/tmp/ellsworth.txt --debug
>
> and that resulted in parsed records:
>
> [{'event_ts': 1554502500, 'dateTime': 1554493866, 'location': None, 
> 'hilo': 'L', 'offset': '0.67', 'issued_ts': 1554493866, 'method': 'XTide', 
> 'usUnits': 1}, ...]
>
> finally, when i run weewx with a configuration that contains tide 
> forecasting, this is what it looks like in the weewx log (with debug 
> enabled):
>
> Apr  5 16:35:52 7up weewx[16424]: engine: Loading service 
> user.forecast.XTideForecast
> Apr  5 16:35:52 7up weewx[16424]: forecast: MainThread: XTide: forecast 
> version 3.4.0rc2
> Apr  5 16:35:52 7up weewx[16424]: manager: Created and initialized table 
> 'archive' in database 'forecast.sdb'
> Apr  5 16:35:52 7up weewx[16424]: forecast: MainThread: XTide: 
> interval=1209600 max_age=2419200 location='Ellsworth' duration=2419200
> Apr  5 16:35:52 7up weewx[16424]: engine: Finished loading service 
> user.forecast.XTideForecast
> ...
> Apr  5 16:35:52 7up weewx[16424]: engine: Starting main packet loop.
> Apr  5 16:40:14 7up weewx[16424]: forecast: MainThread: XTide: starting 
> thread
> Apr  5 16:40:14 7up weewx[16424]: forecast: XTideThread: XTide: generating 
> tides from 2019-04-05 00:00:00 EDT (1554436800) to 2019-05-03 00:00:00 EDT 
> (1556856000)
> Apr  5 16:40:14 7up weewx[16424]: forecast: XTideThread: XTide: running 
> command '/opt/weewx/bin/user/tide.sh -fc -df'%Y.%m.%d' -tf'%H:%M' 
> -l'Ellsworth' -b'2019-04-05 00:00' -e'2019-05-03 00:00''
> ...
> Apr  5 16:40:14 7up weewx[16424]: manager: Added record 2019-04-05 
> 16:40:00 EDT (1554496800) to database 'weewx.sdb'
> Apr  5 16:40:15 7up weewx[16424]: manager: Added record 2019-04-05 
> 16:40:00 EDT (1554496800) to daily summary in 'weewx.sdb'
> Apr  5 16:40:15 7up weewx[16424]: reportengine: Running reports for latest 
> time in the database.
> Apr  5 16:40:15 7up weewx[16424]: reportengine: Running report 
> 'SeasonsReport'
> Apr  5 16:40:15 7up weewx[16424]: reportengine: Found configuration file 
> /opt/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'
> Apr  5 16:40:15 7up weewx[16424]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.forecast.ForecastVariables']
> Apr  5 16:40:15 7up weewx[16424]: forecast: XTideThread: XTide: got 222 
> lines of output
> Apr  5 16:40:15 7up weewx[16424]: forecast: XTideThread: XTide: location 
> mismatch: 'Ellsworth' != 'Ellsworth, Union River, Blue Hill Bay, Maine'
> Apr  5 16:40:15 7up weewx[16424]: forecast: XTideThread: XTide: tide 
> matrix: [{'event_ts': 1554458400, 'dateTime': 1554496815, 'location': 
> 'Ellsworth', 'hilo': 'L', 'offset': '0.64', 'issued_ts': 1554496815, 
> 'method': 'XTide', 'usUnits': 1}, ...]
> Apr  5 16:40:15 7up weewx[16424]: forecast: XTideThread: XTide: saving 108 
> forecast records
> Apr  5 16:40:15 7up weewx[16424]: manager: Added record 2019-04-05 
> 16:40:15 EDT (1554496815) to database 'forecast.sdb'
> ...
> Apr  5 16:40:16 7up weewx[16424]: manager: Added record 2019-04-05 
> 16:40:15 EDT (1554496815) to database 'forecast.sdb'
> Apr  5 16:40:16 7up weewx[16424]: forecast: XTideThread: XTide: saved 108 
> forecast records
> Apr  5 16:40:16 7up weewx[16424]: forecast: XTideThread: XTide: deleting 
> forecasts prior to 

[weewx-user] What does restx indicate insofar as forecast is concerned?

[V. Kelly Bellis]

After examining the syslog, looking for clues as to why XTide v2.15.2 
(alone and without the deprecated v2.13 on system) isn't working with 
forecast v3.4.0rc1, I keep seeing something like this:

restx: StationRegistry: wait interval (229800 < 604800) has not passed for 
record 2019-04-04 07:45:00 EDT (1554378300)

It typically appears (but not always) immediately following the XTide: 
running command, but wondered if that was due to thread sequencing rather 
than a broken record dictionary or something else.

I'm trying to understand if the bits related to restx might interfere or 
interact with the forecast extension; forecast.py

>From what little I understand, restx has its primary chores relating to 
publishing data to other sites; e.g. AWEKAS, WU, etc.

forecast.py v3.4.0rc1 - beginning at line 4026
# look for comma-delimited output.  we expect lines like this:
#   location,-MM-DD,HH:MM xM xxx,offset,description
# xtide replaces commas in the location with |
out = []
for line in p.stdout:
if line.count(',') == 4:
out.append(line)
else:
logdbg("%s: ignoring line: %s" % (XT_KEY, line))
if out:
logdbg("%s: got %d lines of output" % (XT_KEY, len(out)))
fields = out[0].split(',')
loc = fields[0].replace('|', ',')
loc = loc.replace(' - READ flaterco.com/pol.html', '')
if loc != location:
loginf("%s: location mismatch: '%s' != '%s'" %
   (XT_KEY, location, loc))
return out
loginf("%s: got no stinkin tidal events" % XT_KEY)

This leads to the the syslog line:
Apr  4 08:20:23 raspberrypi weewx[26067]: forecast: XTideThread: XTide: got 
no stinkin tidal events


Then the following bits from forecast.py v3.4.0rc1 - beginning at line 4047:

# we got no recognizable output, so try to make sense of any 
errors
err = []
preamble = True
for line in p.stderr:
if line.startswith('Indexing'):
preamble = False
if not line.startswith('Indexing') and not preamble:
line = line.rstrip()
err.append(line)
errmsg = ' '.join(err)
idx = errmsg.find('XTide Error:')
if idx >= 0:
errmsg = errmsg[idx:]
idx = errmsg.find('XTide Fatal Error:')
if idx >= 0:
errmsg = errmsg[idx:]
if len(errmsg):
logerr('%s: generate forecast failed: %s' % (XT_KEY, errmsg
))

return None
except OSError as e:
logerr('%s: generate forecast failed: %s' % (XT_KEY, e))
return None


The only XTide-related message in syslog subsequent to 'forecast: 
XTideThread: XTide: got no stinkin tidal events' is:
Apr  4 08:20:23 raspberrypi weewx[26067]: forecast: XTideThread: XTide: 
terminating thread


The python parts dealing with location may allow for all of the old 
unmaintained data that newer versions of XTide hasn't supported for many 
years. The reference in forecast.py is to the 15-year old Legal Notice for 
UK tide predictions (https://flaterco.com/pol.html).

As Dave Flater writes , "*Many data 
were purged after a legal threat from the U.K. Hydrographic Office (UKHO) 
in January 2001.  I ended maintenance of the non-U.S. data that replaced 
them for different reasons in early 2012.*"

The lengthy explanation by Mr. Flater that follows in his discussion is 
informative as to why for many years, only U.S. data is maintained by him, 
and that the scarcity of non-U.S. data is artificial. Still I wonder if 
this issue is possibly linked with forecast and XTide v2.15.2 got no 
stinkin tidal events on my RPi

-- 
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: lancet server downtime

[V. Kelly Bellis]

My condolences for your loss. Long live the server!

On Tuesday, April 2, 2019 at 10:20:58 AM UTC-4, mwall wrote:
>
> folks,
>
> you might have noticed that the server i use for many extensions (lancet) 
> has been down.  new hardware just went in today, and i hope to have 
> everything back up and running today or maybe tomorrow.
>
> we had scheduled the maintenance to happen over the weekend, and the night 
> before we did it there was a power failure that ran longer than the battery 
> backups.  when things powered back on, one of the disks failed.  so not 
> only are we doing a hardware upgrade, we are also restoring data from 
> backups.
>
> apologies for the downtime.  
>
> m
>
>

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

[weewx-user] Re: Has WU changed its API Key length

[V. Kelly Bellis]

Hi Paul,

Thank you for starting this thread. I was holding off saying anything as I 
too discovered that the new longer WU API key and forecast.py (v3.4.0rc1) 
didn't work. The primary reason in holding off in mentioning the WU issue 
was another problem I've been having with getting XTide to work with the 
forecast extension (which is what prompted Matt to create forecast.py 
v3.4.0rc1). 

The other tangential item I've held off in broaching - perhaps the topic of 
another future thread - has to do with how forecast and NWS play together 
as the old NWS 3-letter forecast office identifier (foid, also referred to 
as HADS) and 6-character location identifier (lid)are being phased out; 
this is the NWS so-called PFM product. It has been replaced with the 
Point-n-Click product (quasi-official product name) allowing for more 
localized forecasts from a gridded database. More on that here: 
https://www.weather.gov/mdl/ndfd_home

[Forecast] 
  [[*needed_fixes*]]

   - WU new API keys and commands
   - NWS new Point-n-Click product
   - new tide v.2.15.2


On Monday, April 1, 2019 at 6:43:14 PM UTC-4, Paul Oversmith wrote:
>
> Have been using Weather Underground to download forecasts for several 
> years. 
> Stopped working with a key error end of March, 2019.  So I  got a new API 
> key, but now getting the following messages:
> Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
> download forecast from '
> http://api.wunderground.com/api/cbc1/hourly10day/q/34231.json
> '
>
> Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
> error in response: keynotfound: this key does not exist
>
> Seeing that the last 4 characters are outside the block out text, I was 
> wondering if they increased the key length and that is what is preventing 
> getting the forecast. Or perhaps I need to delete some of the API key. my 
> key is: d7xcbc1
>
> Uploads to WU work.
>
> Tried to download a current version of the forecasting code, but the site 
> seems to be down.
>
> Any suggestions on how to fix?
>
>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

/usr/share/weewx/user/forecast.py
@ line 25 "A single table stores all forecast information."

Not sure if I've found the correct database @
/var/lib/weewx/forecast.sdb

If this is the correct file, there aren't any tide forecasts; only NWS, 
OWM, and Zambretti

Is this why the syslog includes:
"Mar 31 16:00:28 raspberrypi weewx[20798]: forecast: XTideThread: XTide: *got 
no tidal events*"
?

-- 
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: No Moon rise & set on Seasons skin even with pyephem installed

[V. Kelly Bellis]

Yes, thank you for that link, and Tom's related earlier post in the same 
thread indicated that he hadn't ruled it out. For a Rpi, Skyfield does seem 
a bit taxing and more trouble for weewx users than it's worth, not to 
mention the burden for our beloved developers!

On Sunday, March 31, 2019 at 3:18:07 PM UTC-4, Lloyd Brown wrote:
>
> Based on my Google search while trying to figure my pyephem problem -  
> Skyfield was discussed by Thomas Keefer and he did not want to transition 
> to it because of the dependencies.  See 
> https://groups.google.com/forum/#!searchin/weewx-user/skyfield%7Csort:date/weewx-user/w8_v-ClMcPE/mGyF9dG8AQAJ
>
> On Sunday, March 31, 2019 at 10:57:25 AM UTC-6, V. Kelly Bellis wrote:
>>
>> Hi Lloyd,
>>
>> Glad you started this thread and that you're up and running the 
>> (deprecated) pyephem extension, v3.7.3.0 for python. Thanks to you, I also 
>> am running it!
>>
>> One tangential thing that I wondered about: Is weewx also able to utilize 
>> Brandon Rhodes' later work '*Skyfield* <https://rhodesmill.org/skyfield/>' 
>> ?
>>
>>
>>
>>>>

-- 
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: No Moon rise & set on Seasons skin even with pyephem installed

[V. Kelly Bellis]

Hi Lloyd,

Glad you started this thread and that you're up and running the 
(deprecated) pyephem extension, v3.7.3.0 for python. Thanks to you, I also 
am running it!

One tangential thing that I wondered about: Is weewx also able to utilize 
Brandon Rhodes' later work '*Skyfield* ' ?


On Saturday, March 30, 2019 at 12:10:31 PM UTC-4, Lloyd Brown wrote:
>
> Fixed
> I must have done pip install pyephem without the sudo because the ephem 
> got put in the my home directory.  Did the sudo pip install pyephem and 
> stopped and started WeeWX and I have Moon rise and set.
>
>
>
>>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Hi Matt,

Within the entirety of the forecast extension, is forecast.py the only file 
that contains the path to tide? Are there compiled versions of forecast 
files that may still hold vestiges to tide?

Thank you for any reply.

Kind regards,

Kelly


On Friday, March 22, 2019 at 1:08:39 PM UTC-4, mwall wrote:
>
> please try the attached forecast code to see if that will shed any more 
> light.  it has some additional generate/parse debug output, as well as 
> python3-readiness (not that that will help you, but since i'm in the code, 
> we may as well take care of everything and test tom's python3 changes.  it 
> has been running fine for me.)
>
> after you download forecast-3.4.0rc1.py to the Downloads folder on the 
> pi, the process looks something like this:
>
> sudo mv /usr/share/weewx/user/forecast.py /usr/share/weewx/user/
> forecast-3.2.2.py
> sudo cp ~/Downloads/forecast-3.4.0rc1.py /usr/share/weewx/user/forecast.py
> sudo /etc/init.d/weewx stop
> sudo /etc/init.d/weewx start
>
> m
>

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

Re: [weewx-user] Re: How to Read dateTime Field in weewx.sdb?

[V. Kelly Bellis]

Thank you for the helpful suggestions, but neither approach worked. 

This is only a minor nuisance, with the larger item of the cause for the 75 
minutes worth of missing data remaining unknown. As far as I have observed 
thus far using the Atmocom device, + the RPi 3B+, the weewx driver and 
weewx, this was the first gap in the data that has occurred over the past 
several weeks.

I have written to Relko Vazic: 

Has there been any firmware updates for the Atmocom device (Firmware 
Updates Over the Air)? and by any chance, was there one between (unixepoch) 
1553838600 & 1553843100 (as recorded in /var/lib/weewx/weewx.sdb); or as 
~/atmocom/wxdb/wx201903.db has recorded in it between 20190329 01:42:41 & 
03:05:50 UTC-4? This gap in data can also be seen on WU for KMEELLSW50 
.


This was not caused by a local electrical outage as my other unit 
(WS-2902A) has been uploading to WU KMEELLSW49 
 without issue. 
Other than that, I'm unsure what else to rule out.


On Friday, March 29, 2019 at 11:47:41 AM UTC-4, Thomas Keffer wrote:
>
> It does seem like there is a bug that prevents you from editing the 
> display format. Try using the dropdown list, and selecting "Unix epoch to 
> date." It will show the time in UTC.
>
> The other alternative is to use the tool "sqlite3". For example,
>
> sqlite3 weewx.sdb
> sqlite> SELECT datetime(dateTime,'unixepoch','localtime'), barometer FROM 
> archive LIMIT 5;
>
> This is what I use.
>
> -tk
>
>
>

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

[weewx-user] Re: How to Read dateTime Field in weewx.sdb?

[V. Kelly Bellis]

Thanks for the link. 

Before seeing your kind reply, I was dividing the whole mess by 60, then 
60, then 24, then 365.2422 and figured we were looking at 19700101 
00:00:00; however, I still don't understand the deliberate obfuscation for 
any human reading the weewx.sdb


On Friday, March 29, 2019 at 9:44:35 AM UTC-4, peterq...@gmail.com wrote:
>
> Google for Unix Epoch. It's the number of seconds since Jan 1 1970. You 
> can find online converters like this one:https://www.epochconverter.com/
>
> On Friday, March 29, 2019 at 6:32:18 AM UTC-7, V. Kelly Bellis wrote:
>>
>> Something happened with my RPi-weewx-Atmocom experiment running in the 
>> wee hours of the morning and I'm trying decipher the times of when these 
>> happenings occurred, but cannot makes much sense out of the dateTime 
>> field in the /var/lib/weewx/weewx.sdb which apparently are some measure of 
>> seconds. 
>>
>> What have I missed? I was unable to find a global Search mechanism 
>> covering the whole of http://weewx.com/docs/ = does such a feature yet 
>> exist?
>>
>> How difficult would it be to add another column to the weewx.sdb allowing 
>> YYMMDD 
>> HH:MM:SS.SS to be more easily understood?
>>
>> I just want to know what time things went off the rails... and when the 
>> ship righted itself.
>>
>> [image: I-just-want-to-know-what-time-things-went-off-the-rails.png]
>>
>>
>>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Wow - the ice is totally gone out of the Charles? Bet the water is still 
pretty chilly... though I suppose it wouldn't matter all that much on the 
right size boat :)

Whenever you're able to get to it will be just fine; no rush. Maybe me and 
my blind man's cane will wander into the reeds.

<http://sailing.mit.edu/future/fj1.jpg>


On Tuesday, March 26, 2019 at 5:08:21 PM UTC-4, mwall wrote:
>
> On Monday, March 25, 2019 at 11:22:28 AM UTC-4, V. Kelly Bellis wrote:
>>
>> One thought that keeps coming up, are any of your tests being done on a 
>> system where the only xtide installation is v2.15.2?
>>
>
> i have been testing on a raspberry pi and an x64 box, both running some 
> version of debian.  both have old and new xtide on them.
>
> i'll try removing the debian xtide from the pi so see if that gives me 
> results like yours (but it won't be for a few days - boats going in the 
> water now, so lots of bottom painting and logistics to take care of)
>  
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Matt - How's it going?

One thought that keeps coming up, are any of your tests being done on a 
system where the only xtide installation is v2.15.2?


On Friday, March 22, 2019 at 1:08:39 PM UTC-4, mwall wrote:
>
>
> yay!  i see exactly the same output when i run tide with those options, 
> whether i use tide 2.11 or tide 2.15.2
>
> but your weewx-forecast still gets nothing.  on the other hand, my 
> weewx-forecast *does* see the output and happily parses it.
>
> so the obvious difference is still not so obvious.
>
> please try the attached forecast code to see if that will shed any more 
> light.  it has some additional generate/parse debug output, as well as 
> python3-readiness (not that that will help you, but since i'm in the code, 
> we may as well take care of everything and test tom's python3 changes.  it 
> has been running fine for me.)
>
> after you download forecast-3.4.0rc1.py to the Downloads folder on the 
> pi, the process looks something like this:
>
> sudo mv /usr/share/weewx/user/forecast.py /usr/share/weewx/user/
> forecast-3.2.2.py
> sudo cp ~/Downloads/forecast-3.4.0rc1.py /usr/share/weewx/user/forecast.py
> sudo /etc/init.d/weewx stop
> sudo /etc/init.d/weewx start
>
> m
>

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

[weewx-user] Re: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Thank you Matt for the help, but still no cigar, unfortunately.

Mar 22 13:40:22 raspberrypi weewx[3297]: manager: Added record 2019-03-22 
13:40:00 EDT (1553276400) to database 'weewx.sdb'
Mar 22 13:40:22 raspberrypi weewx[3297]: manager: Added record 2019-03-22 
13:40:00 EDT (1553276400) to daily summary in 'weewx.sdb'
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: MainThread: Zambretti: 
starting thread
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: MainThread: NWS: not yet 
time to do the forecast
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: MainThread: OWM: not yet 
time to do the forecast
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: MainThread: XTide: 
starting thread
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: generating forecast for 2019-03-22 09:00:00 EDT (1553259600)
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: XTideThread: XTide: 
generating tides from 2019-03-22 00:00:00 EDT (1553227200) to 2019-04-19 
00:00:00 EDT (1555646400)
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: using winddir from 2019-03-22 08:30:00 EDT (1553257800) to 
2019-03-22 09:00:00 EDT (1553259600)
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: XTideThread: XTide: 
running command '/usr/share/weewx/tide.sh -fc -df'%Y.%m.%d' -tf'%H:%M' 
-l'Ellsworth' -b'2019-03-22 00:00' -e'2019-04-19 00:00''
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: using pressure from 2019-03-22 06:00:00 EDT (1553248800) to 
2019-03-22 09:00:00 EDT (1553259600)
Mar 22 13:40:22 raspberrypi weewx[3297]: atmocomudp: MainThread: Listening 
for UDP broadcasts to IP address  on port 12000, with timeout 90 
and share_socket True...
Mar 22 13:40:22 raspberrypi weewx[3297]: reportengine: Running reports for 
latest time in the database.
Mar 22 13:40:22 raspberrypi weewx[3297]: reportengine: Running report 
'SeasonsReport'
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: XTideThread: XTide: got 
no tidal events
Mar 22 13:40:22 raspberrypi weewx[3297]: manager: Daily summary version is 
2.0
Mar 22 13:40:22 raspberrypi weewx[3297]: forecast: XTideThread: XTide: 
terminating thread
Mar 22 13:40:22 raspberrypi weewx[3297]: reportengine: Found configuration 
file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'
Mar 22 13:40:23 raspberrypi weewx[3297]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.forecast.ForecastVariables']
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: units=1 winddir=22.8282497722 pressure=29.669207315 
first_p=29.7504201375 last_p=29.547317715
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: pressure=1004.71452333 month=2 winddir=1 trend=-2.29261212944 
north=True
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: code is O
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: generated 1 forecast record
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: saving 1 forecast records
Mar 22 13:40:23 raspberrypi weewx[3297]: manager: Added record 2019-03-22 
13:40:00 EDT (1553276400) to database 'forecast.sdb'
Mar 22 13:40:23 raspberrypi weewx[3297]: manager: Daily summary version is 
2.0
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: saved 1 forecast records
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: deleting forecasts prior to 1552671623
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: deleted forecasts prior to 1552671623
Mar 22 13:40:23 raspberrypi weewx[3297]: forecast: ZambrettiThread: 
Zambretti: terminating thread
Mar 22 13:40:28 raspberrypi weewx[3297]: cheetahgenerator: Generated 8 
files for report SeasonsReport in 5.59 seconds
Mar 22 13:40:28 raspberrypi weewx[3297]: manager: Daily summary version is 
2.0
Mar 22 13:40:29 raspberrypi weewx[3297]: imagegenerator: Generated 14 
images for SeasonsReport in 1.05 seconds
Mar 22 13:40:29 raspberrypi weewx[3297]: copygenerator: copied 87 files to 
/var/www/html/weewx
Mar 22 13:40:29 raspberrypi weewx[3297]: reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Mar 22 13:40:29 raspberrypi weewx[3297]: reportengine: Report 
'MobileReport' not enabled. Skipping.
Mar 22 13:40:29 raspberrypi weewx[3297]: reportengine: Report 
'StandardReport' not enabled. Skipping.
Mar 22 13:40:29 raspberrypi weewx[3297]: reportengine: Running report 
'forecast'
Mar 22 13:40:29 raspberrypi weewx[3297]: reportengine: Found configuration 
file /etc/weewx/skins/forecast/skin.conf for report 'forecast'
Mar 22 13:40:29 raspberrypi weewx[3297]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 

[weewx-user] Re: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Exactly! And was why I questioned that the period isn't matching the 
forecast number of days; e.g., 7 days;
-b'2019-03-22 00:00' -e'2019-03-30 00:00'

[image: 7-day example.PNG]


On Friday, March 22, 2019 at 11:52:44 AM UTC-4, Andrew Milner wrote:
>
> in the command you issued you requested tide information for the 4 weeks 
> from 22 march thru 19 april - so that is why 4 weeks of data was returned.
>
>
>
>
>
> On Friday, 22 March 2019 17:36:09 UTC+2, V. Kelly Bellis wrote:
>>
>> It works and produces 4-weeks worth of tide tables  - why 4 weeks and not 
>> the same number of forecast days?
>>
>> [image: tide output to tty.PNG]
>>
>>
>> On Friday, March 22, 2019 at 11:04:16 AM UTC-4, mwall wrote:
>>>
>>>
>>> and what happens when you execute the command directly?  try it:
>>>
>>> /usr/share/weewx/tide.sh -fc -df'%Y.%m.%d' -tf'%H:%M' -l'Ellsworth' 
>>> -b'2019-03-22 00:00' -e'2019-04-19 00:00'
>>>  
>>>
>>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

[image: line 3906 in forecast_dot_py.PNG]



Does the weewx.conf call of:
prog = /usr/share/weewx/tide.sh
take precedence over the call at line 3906 in forecast.py?


On Thursday, March 21, 2019 at 9:56:56 AM UTC-4, mwall wrote:
>
>
> the default installation assumes that tide is located at /usr/bin/tide
>
> this can be changed with the `prog` option.
>
> as long as the thing referred to by `prog` produces output in the format 
> produced by the 'tide' program (which is unchanged since 1999 or so), then 
> everything works.
>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

So far I haven't gotten forecast to run the latest version of tide, but I 
understand that you as a developer might want to support tide users of 
legacy versions, and I find that refreshing - thank you for helping them! - 
and for helping me in trying to get tide to work in forecast.

On Thursday, March 21, 2019 at 9:56:56 AM UTC-4, mwall wrote:
>
> when someone asks "does forecast work with the latest version of xtide?" 
> it is rather handy to have 2 (or 5 or 10) different versions of xtide or 
> its harmonics installed at once so that i can answer accurately.
>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

If the forecast interval has been set to n days, should the tide interval; 
i.e., -b -e, do likewise?

What does restx accomplish and is it a forecast term, linux, xtide, etc., 
and why is it set to be (71400 < 604800) - whatever that means??

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Will sudo apt-get purge xtide purge only the old deprecated xtide stuff or 
will frig with all things xtide system-wide?


On Wednesday, March 20, 2019 at 9:48:08 AM UTC-4, mwall wrote:
>
> you might want to purge the debian installation of tide
>
> sudo apt-get purge xtide
>
>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

The .sh has no luck, but regular tide -l location works. 


[image: got nojoy.PNG]




On Wednesday, March 20, 2019 at 9:41:44 AM UTC-4, V. Kelly Bellis wrote:
>
> pi@raspberrypi:~ $ /usr/local/share/xtide/harmonics-dwf-20181227-free.tcd 
> tide -l Ellsworth
> bash: /usr/local/share/xtide/harmonics-dwf-20181227-free.tcd: Permission 
> denied
>
>
>
> On Wednesday, March 20, 2019 at 9:38:25 AM UTC-4, mwall wrote:
>>
>>
>>
>> On Wednesday, March 20, 2019 at 9:26:06 AM UTC-4, V. Kelly Bellis wrote:
>>>
>>>
>>> apparently the environment in which you run weewx is not the same as the 
>>>> environment in which you run tide directly, so when the forecast extension 
>>>> invokes /usr/local/bin/tide, tide cannot find the harmonics.  the tide.sh 
>>>> script ensures that you use the right harmonics by explicitly telling tide 
>>>> which harmonics file to use.  you do not need tide.sh if you fix your 
>>>> environment issues.
>>>>
>>>
>>> What does this syslog message suggest:
>>> Mar 20 08:25:31 raspberrypi weewx[16792]: forecast: XTideThread: XTide: 
>>> got no tidal events
>>>
>>> 'got no tidal events' is still present after every attempt to remediate 
>>> forecast not showing tide predictions; e.g.,
>>>
>>
>> this message indicates that the forecast extension is not getting any 
>> data from the tide program.
>>
>> what happens when you use the tide.sh approach?  what output do you get 
>> when you invoke tide.sh directly?
>>  
>>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

pi@raspberrypi:~ $ /usr/local/share/xtide/harmonics-dwf-20181227-free.tcd 
tide -l Ellsworth
bash: /usr/local/share/xtide/harmonics-dwf-20181227-free.tcd: Permission 
denied



On Wednesday, March 20, 2019 at 9:38:25 AM UTC-4, mwall wrote:
>
>
>
> On Wednesday, March 20, 2019 at 9:26:06 AM UTC-4, V. Kelly Bellis wrote:
>>
>>
>> apparently the environment in which you run weewx is not the same as the 
>>> environment in which you run tide directly, so when the forecast extension 
>>> invokes /usr/local/bin/tide, tide cannot find the harmonics.  the tide.sh 
>>> script ensures that you use the right harmonics by explicitly telling tide 
>>> which harmonics file to use.  you do not need tide.sh if you fix your 
>>> environment issues.
>>>
>>
>> What does this syslog message suggest:
>> Mar 20 08:25:31 raspberrypi weewx[16792]: forecast: XTideThread: XTide: 
>> got no tidal events
>>
>> 'got no tidal events' is still present after every attempt to remediate 
>> forecast not showing tide predictions; e.g.,
>>
>
> this message indicates that the forecast extension is not getting any data 
> from the tide program.
>
> what happens when you use the tide.sh approach?  what output do you get 
> when you invoke tide.sh directly?
>  
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

> apparently the environment in which you run weewx is not the same as the 
> environment in which you run tide directly, so when the forecast extension 
> invokes /usr/local/bin/tide, tide cannot find the harmonics.  the tide.sh 
> script ensures that you use the right harmonics by explicitly telling tide 
> which harmonics file to use.  you do not need tide.sh if you fix your 
> environment issues.
>

What does this syslog message suggest:
Mar 20 08:25:31 raspberrypi weewx[16792]: forecast: XTideThread: XTide: got 
no tidal events

'got no tidal events' is still present after every attempt to remediate 
forecast not showing tide predictions; e.g.,

[image: still nojoy.PNG]


-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Hello Matt,

Thank you for your reply.

I'm still not understanding why in /etc/weewx/weewx.conf under 

[Forecast]
 ...
   [[XTide]]
  prog = /usr/local/bin/tide

What's wrong with this?

And why the need for the tide.sh?

[Forecast]
 ...
   [[XTide]]
  prog =  /usr/share/weewx/tide.sh



RE: Updating XTide
The need to update xtide would be predicated on which old version of xtide 
you are using with the latest harmonics, and you're particular need to have 
accurate tide information. In your example listed from the forecast 
extension page <https://github.com/weewx/weewx/wiki/forecasting>, 
http://sailing.mit.edu/weather/forecast.html, I was unable to reach the 
site (it keeps timing out) to see it working. 

https://flaterco.com/xtide/changelog.html might be worth consulting in 
making the decision to update xtide as there have been several changes made 
since 2.13 (deprecated apt-get package linked on your forecast extension 
page <https://github.com/weewx/weewx/wiki/forecasting>); and of course, 
comparing your xtide results with 
https://tidesandcurrents.noaa.gov/stationhome.html is advised.

You might want to consider adding a note on your forecast extension page 
<https://github.com/weewx/weewx/wiki/forecasting> that harmonics data 
outside of the U.S. has been discontinued and hasn't been maintained since 
early 2012.


On Tuesday, March 19, 2019 at 10:22:09 AM UTC-4, mwall wrote:
>
> On Tuesday, March 19, 2019 at 9:32:20 AM UTC-4, V. Kelly Bellis wrote:
>>
>>
>> Have you tried to install XTide v2.15.2 and do you have it working with 
>> weewx and the forecast extension?
>>
>
> yes.  but there is no need to install the latest xtide - older versions 
> work just fine with the latest harmonics.
>
>  
>
>> And did I understand you correctly? - see previous post.
>>
>
> yes
>  
>  
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Hello Matt,

Hope you are well. It's been a few days and I haven't heard back from you 
yet.

Have you tried to install XTide v2.15.2 and do you have it working with 
weewx and the forecast extension?
And did I understand you correctly? - see previous post.

Kind regards,

Kelly


On Thursday, March 14, 2019 at 3:19:03 PM UTC-4, V. Kelly Bellis wrote:
>
> Hello Matt,
>
> Thank you for your reply, though I don't fully understand it. 
>
> Have you tried to install XTide v2.15.2 and do you have it working with 
> weewx and the forecast extension?
>
> *RE: The environment*
> /usr/local/bin/tide already knows where to find harmonics as directed by
> /etc/environment wherein is contained:
> HFILE_PATH=/usr/local/share/xtide
> WVS_DIR=/home/pi/XTide/wvs
>
>
> XTide was installed from source files and into the associated directories 
> following the David Flater's excellent, though sometimes terse, 
> instructions.  Weewx got installed automatically through the apt-get 
> process.
>
> /usr/share/weewx/weewxd 
>
> In /etc/weewx/weewx.conf under 
> [Forecast]
>  ...
>[[XTide]]
>   prog = /usr/local/bin/tide
>
>
> *IF* I understand you, 
> 1) I should create /usr/share/weewx/tide.sh wherein is contained
> #!/bin/sh
> HFILE_PATH=/usr/local/share/harmonics-dwf-20181227-free.tcd tide "$@"
>
> 2) and then, you're saying I should
> In /etc/weewx/weewx.conf under 
> [Forecast]
>  ...
>[[XTide]]
>   prog =  /usr/share/weewx/tide.sh
>  
> *Is this understanding correct?*
>
>
> FWIW - Found more deprecated droppings from the old deb-package that 
> weren't properly removed by sudo apt-get remove xtide-data; i.e., 
> /usr/share/xtide/harmonics-initial.tcd - manually removed by
> pi@raspberrypi:~ $ sudo rm -r /usr/share/xtide
>
>
>
>
> On Tuesday, March 12, 2019 at 5:04:16 PM UTC-4, V. Kelly Bellis wrote:
>>
>> RE: Forecasting Extension, RPi, Raspbian, weewx v3.9.1, XTide v2.15.2
>> https://github.com/weewx/weewx/wiki/forecasting
>>
>> The xtide package (sudo apt-get install xtide) is an old, neglected, and 
>> abandoned Debian package. How old? It and its related data: xtide 
>> v2.13.2-1+b1 and data circa 20100529. The net result is as you would 
>> expect, tide heights and times have drifted enough away from current NOAA 
>> predictions to be noticeable or worse.
>>
>> Building XTide from source files on the RPi (including a path statement 
>> in /etc/environment, to the harmonics file; i.e., 
>> /usr/local/share/xtide/harmonics-dwf-20181227-free.tcd) has xtide working 
>> properly by itself; however, when viewing /var/log/syslog I'm seeing 
>> STATION_NOT_FOUND.
>>
>> I was wondering if there might be any documentation written for 
>> non-programmers in how weewx and XTide have been integrated? 
>>
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Hello Matt,

Thank you for your reply, though I don't fully understand it. 

Have you tried to install XTide v2.15.2 and do you have it working with 
weewx and the forecast extension?

*RE: The environment*
/usr/local/bin/tide already knows where to find harmonics as directed by
/etc/environment wherein is contained:
HFILE_PATH=/usr/local/share/xtide
WVS_DIR=/home/pi/XTide/wvs


XTide was installed from source files and into the associated directories 
following the David Flater's excellent, though sometimes terse, 
instructions.  Weewx got installed automatically through the apt-get 
process.

/usr/share/weewx/weewxd 

In /etc/weewx/weewx.conf under 
[Forecast]
 ...
   [[XTide]]
  prog = /usr/local/bin/tide


*IF* I understand you, 
1) I should create /usr/share/weewx/tide.sh wherein is contained
#!/bin/sh
HFILE_PATH=/usr/local/share/harmonics-dwf-20181227-free.tcd tide "$@"

2) and then, you're saying I should
In /etc/weewx/weewx.conf under 
[Forecast]
 ...
   [[XTide]]
  prog =  /usr/share/weewx/tide.sh
 
*Is this understanding correct?*


FWIW - Found more deprecated droppings from the old deb-package that 
weren't properly removed by sudo apt-get remove xtide-data; i.e., 
/usr/share/xtide/harmonics-initial.tcd - manually removed by
pi@raspberrypi:~ $ sudo rm -r /usr/share/xtide




On Tuesday, March 12, 2019 at 5:04:16 PM UTC-4, V. Kelly Bellis wrote:
>
> RE: Forecasting Extension, RPi, Raspbian, weewx v3.9.1, XTide v2.15.2
> https://github.com/weewx/weewx/wiki/forecasting
>
> The xtide package (sudo apt-get install xtide) is an old, neglected, and 
> abandoned Debian package. How old? It and its related data: xtide 
> v2.13.2-1+b1 and data circa 20100529. The net result is as you would 
> expect, tide heights and times have drifted enough away from current NOAA 
> predictions to be noticeable or worse.
>
> Building XTide from source files on the RPi (including a path statement in 
> /etc/environment, to the harmonics file; i.e., 
> /usr/local/share/xtide/harmonics-dwf-20181227-free.tcd) has xtide working 
> properly by itself; however, when viewing /var/log/syslog I'm seeing 
> STATION_NOT_FOUND.
>
> I was wondering if there might be any documentation written for 
> non-programmers in how weewx and XTide have been integrated? 
>

-- 
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: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Matt - Thanks for the reply.

I'm guessing from your response that there is no documentation on xtide 
integration. 
XTide is running perfectly on the RPi, but the syslog is still indicating 
that there is an issue with weewx: forecast: XTide
even after implementing your suggested path update and location in 
(presumably) /etc/weewx/weewx.conf

*Details*
RE: weewx_forecasting-extension_xtide
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l 
GNU/Linux

*Sequence of Events*
20190221 Installed forecasting extension, sudo apt-get xtide, and sudo 
apt-get xtide-data
20190222 Realized deprecated deb package and data, sudo apt-get remove 
xtide, and sudo apt-get remove xtide-data
20190222 Built XTide v2.15.1 from source files
20190224 XTide v2.15.2 available
20190226 Built XTide v2.15.2 from source files

(time off to work on 
https://flaterco.com/files/xtide/XTide%20v2.15.2%20Help%20b20190309.chm)

20190312 Examined /var/log/syslog and discovered xtide STATION_NOT_FOUND 
errors
20190313 Examined /usr/bin/ and discovered tide v2.13.2 was not removed(!) 
- manually removed - and left wondering what other lingering bits could 
there be from the original installation on 20190221 of the deprecated 
stuff, this despite the overt sudo apt-get remove efforts.

9:13 AM   Wednesday, March 13, 2019  (VKB)
pi@raspberrypi:~ $ sudo rm /usr/bin/tide

pi@raspberrypi:~ $ sudo leafpad /etc/weewx/weewx.conf
@ line number 652 [[XTide]], inserted and edited the following lines 
 prog = /usr/local/bin/tide
 location = Boston

pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@raspberrypi:~ $ sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.


 And again from /var/log/syslog
Mar 13 10:30:16 raspberrypi weewx[2614]: manager: Added record 2019-03-13 
10:30:00 EDT (1552487400) to database 'weewx.sdb'
Mar 13 10:30:16 raspberrypi weewx[2614]: manager: Added record 2019-03-13 
10:30:00 EDT (1552487400) to daily summary in 'weewx.sdb'
Mar 13 10:30:16 raspberrypi weewx[2614]: forecast: XTideThread: XTide: 
generating tides from 2019-03-13 00:00:00 EDT (1552449600) to 2019-04-10 
00:00:00 EDT (1554868800)
Mar 13 10:30:16 raspberrypi weewx[2614]: atmocomudp: MainThread: Listening 
for UDP broadcasts to IP address  on port 12000, with timeout 90 
and share_socket True...
Mar 13 10:30:17 raspberrypi weewx[2614]: forecast: XTideThread: XTide: got 
no tidal events
Mar 13 10:30:17 raspberrypi weewx[2614]: forecast: XTideThread: XTide: 
generate forecast failed: XTide Error:  STATION_NOT_FOUND The specified 
station was not found in any harmonics file.  Error details: Could not 
find: Boston

FY(and your students)I & FWIW - https://flaterco.com/xtide/harmonics.html

Kind regards,

Kelly



On Tuesday, March 12, 2019 at 5:49:32 PM UTC-4, mwall wrote:
>
> On Tuesday, March 12, 2019 at 5:04:16 PM UTC-4, V. Kelly Bellis wrote:
>>
>> I was wondering if there might be any documentation written for 
>> non-programmers in how weewx and XTide have been integrated? 
>>
>
> the forecast extension invokes xtide, parses the output, then stores the 
> result in the forecast database.  the results can then be combined with 
> other forecast data when generating reports.
>
> by default, the forecast extension will invoke /usr/bin/tide
>
> if your 'tide' program is located somewhere else, you can tell the 
> extension to find it like this:
>
> [Forecast]
> [[XTide]]
> prog = /path/to/tide
> location = Boston
>
> as for the tide location, you must test that directly with tide.  once you 
> have a string that works, use that string as the 'location' parameter for 
> the forecast extension.  if the location has commas or spaces then put it 
> in quotes.
>
> btw, this spring i'm hoping to have some students put together a guide for 
> how to create your own harmonics from your own data.  we have been using 
> maxbotix ultrasonic sensors on raspberry pi running weewx to collect tide 
> data from a couple of islands in maine.  apparently you can create your own 
> harmonics with 6-9 months of data (the data we have so far tracks the xtide 
> predictions for tenants harbor and camden pretty well, but there are 
> offsets in magnitude and phase).  its been a bit of a struggle - power 
> outages, snow on solar panels, critters chewing through cables, 
> seawater/corrosion.  but we'll get there...
>
> m 
>

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

Re: [weewx-user] Cleaning up old 'bad' data

[V. Kelly Bellis]

The bad data has been purged. All reports; i.e., day, week, month & year, 
are showing no rain information - bad or otherwise. Thanks again for all of 
your encouragement which in and by itself is much appreciated.

In answer to your question, the WU data doesn't come from weewx; instead, 
the Ambient Weather WS-2000 console sends it directly to WU (KMEELLSW50 
).
 


Weewx gets its data using Arthur Emerson's atmocomUDP 
 driver which he has 
been most generously working on for the past several weeks. 

[image: Atmocom R1_180424_5D37672.jpg]


Relko Vazic's *Atmocom*  device (pictured) is still 
in beta, but has had solid performance since arriving here from Spain on 
20190114; first in sending captured data to a non-weewx related SQLite3 
database; and second in working with weewx thanks to Arthur's driver, which 
in Version 1.20, now is correctly accommodating rainRate and rain values. 
The next version of the Atmocom device is smaller than the one I 
photographed that's shown above.

-- 
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] Cleaning up old 'bad' data

[V. Kelly Bellis]

 "*If data you removed is still there then you have operationally done 
something wrong*."

Thanks Andrew for mentioning this, that's likely what has happened - I 
screwed something up and only thought I had removed the bogus data. 

In answer to your other questions, I tried to follow verbatim what Tom has 
outlined in his article, but most likely I didn't. 

I just now browsed /var/lib/weewx/weewx.sdb and the data I thought that I 
had deleted is still there . I'll have another go at it in a moment, 
but am also wondering: is it practicable to delete the entirety of 
/var/lib/weewx/weewx.sdb and then import 
 
my Weather Underground data? There's a little more than a month's worth for 
KMEELLSW50 


-- 
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] Cleaning up old 'bad' data

[V. Kelly Bellis]

Hi Andrew,

Earlier in this thread, rainRate and rain values were nullified in 
accordance with 
https://github.com/weewx/weewx/wiki/Cleaning-up-old-%27bad%27-data#cleaning-archive-data

On Monday, February 25, 2019 at 11:27:47 AM UTC-5, Andrew Milner wrote:
>
> I am having difficulty understanding exactly what you mean.  What DATA in 
> the database did you update, how did you update it, and how is it not being 
> shown in the .png graphs??
>
>

-- 
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] Cleaning up old 'bad' data

[V. Kelly Bellis]

Hi Andrew,
Yes, in accordance with 
https://github.com/weewx/weewx/wiki/Cleaning-up-old-%27bad%27-data#daily-summaries

On Monday, February 25, 2019 at 9:29:28 AM UTC-5, Andrew Milner wrote:
>
> did you delete the bad data from the archive AND the daily summary tables 
> ???  To remove from daily summary tables you either need to massage them 
> manually or drop the summary tables and then rebuild them.
>
>

-- 
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] Cleaning up old 'bad' data

[V. Kelly Bellis]

Hello Andrew,

Thank you for the reply. Sorry didn't see it until after my reply to Tom. 
I've tried as you suggested deleting all html and png files:

[image: remove em all.PNG]


And the results were the same, the updated and bad data purged from 
weewx.sdb isn't reflected in the freshened reports.

On Monday, February 25, 2019 at 9:18:59 AM UTC-5, Andrew Milner wrote:
>
> The simplest way is to delete ALL .png's *.png, and ALL HTML files *.html 
> to force ALL pages and pngs to be recreated
>
>

-- 
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] Cleaning up old 'bad' data

[V. Kelly Bellis]

Yes! But the curious part: the newly generated .pngs are not reflecting the 
purged bad data.

On Monday, February 25, 2019 at 9:15:33 AM UTC-5, Thomas Keffer wrote:
>
> If you're running weewxd, they will be regenerated at the end of the next 
> archive interval.
>
> Or, you can use wee_reports 
> <http://www.weewx.com/docs/utilities.htm#wee_reports_utility>.
>
> -tk
>
> On Mon, Feb 25, 2019 at 6:10 AM V. Kelly Bellis  > wrote:
>
>> Thank you for the reply Tom.
>>
>> I've deleted weekrain.html, weekrain.png, monthrain.html, monthrain.png, 
>> yearrain.html, and yearrain.png and presume there's no way to compel 
>> regeneration from what you've stated - is that correct?
>>
>> Kind regards,
>>
>> Kelly
>>
>> On Monday, February 25, 2019 at 8:12:28 AM UTC-5, Thomas Keffer wrote:
>>>
>>> Unfortunately, with the present image generator, it's not possible to 
>>> use dynamic captions. They have to be static. So, the inclusive dates 
>>> cannot be included in them. 
>>>
>>> As for how long... the images get regenerated as often as their 
>>> aggregation period. So, if you have a daily total, it will get updated 
>>> daily. If that's too long to wait, just delete them all --- they will get 
>>> regenerated at the next archive interval.
>>>
>>> -tk
>>>
>>> On Mon, Feb 25, 2019 at 5:02 AM V. Kelly Bellis  
>>> wrote:
>>>
>>>> RE: 
>>>> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data#regenerate-web-pages
>>>>
>>>> Under the section heading *Regenerate web pages*, "Most old web pages 
>>>> and plots will be automatically regenerated, *but it may take a while.*"  
>>>> Consider expanding on what *a while* is predicated on in the article; 
>>>> e.g., frequency of report generation once a year, once a month, etc. Also, 
>>>> how might these old web pages otherwise be expunged?
>>>>
>>>>
>>>> [image: History.PNG]
>>>>
>>>> [image: yearly not OK.PNG]
>>>> Here we see History with Year highlighted, though the graph is 
>>>> captioned with the word weekly and without the word year.
>>>> Consider rewording caption: "Rain for the year  MM DD -  MM DD 
>>>> from weekly totals"
>>>>
>>>>
>>>> [image: monthly not OK.PNG]
>>>> Similarly, we see History with Month highlighted, though the graph is 
>>>> captioned with the word daily and without the word month.Consider 
>>>> rewording 
>>>> caption: "Rain for the month  MM DD -  MM DD from daily totals"
>>>>
>>>>
>>>> [image: weekly not OK.PNG]
>>>> Lastly, we see History with Week highlighted, though the graph is 
>>>> captioned with the word daily and without the word week.Consider rewording 
>>>> caption: "Rain for the week  MM DD -  MM DD from daily totals"
>>>>
>>>> N.B. in the three graphs above, all of the erroneous rain data has been 
>>>> nullified, including any fictitious rain from the Simulator. 
>>>>
>>>> *How long will these bogus values linger in the graphs, and what are 
>>>> the alternatives for their culling? *
>>>>
>>>> -- 
>>>> 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.

Re: [weewx-user] Cleaning up old 'bad' data

[V. Kelly Bellis]

Thank you for the reply Tom.

I've deleted weekrain.html, weekrain.png, monthrain.html, monthrain.png, 
yearrain.html, and yearrain.png and presume there's no way to compel 
regeneration from what you've stated - is that correct?

Kind regards,

Kelly

On Monday, February 25, 2019 at 8:12:28 AM UTC-5, Thomas Keffer wrote:
>
> Unfortunately, with the present image generator, it's not possible to use 
> dynamic captions. They have to be static. So, the inclusive dates cannot be 
> included in them. 
>
> As for how long... the images get regenerated as often as their 
> aggregation period. So, if you have a daily total, it will get updated 
> daily. If that's too long to wait, just delete them all --- they will get 
> regenerated at the next archive interval.
>
> -tk
>
> On Mon, Feb 25, 2019 at 5:02 AM V. Kelly Bellis  > wrote:
>
>> RE: 
>> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data#regenerate-web-pages
>>
>> Under the section heading *Regenerate web pages*, "Most old web pages 
>> and plots will be automatically regenerated, *but it may take a while.*"  
>> Consider expanding on what *a while* is predicated on in the article; 
>> e.g., frequency of report generation once a year, once a month, etc. Also, 
>> how might these old web pages otherwise be expunged?
>>
>>
>> [image: History.PNG]
>>
>> [image: yearly not OK.PNG]
>> Here we see History with Year highlighted, though the graph is captioned 
>> with the word weekly and without the word year.
>> Consider rewording caption: "Rain for the year  MM DD -  MM DD 
>> from weekly totals"
>>
>>
>> [image: monthly not OK.PNG]
>> Similarly, we see History with Month highlighted, though the graph is 
>> captioned with the word daily and without the word month.Consider rewording 
>> caption: "Rain for the month  MM DD -  MM DD from daily totals"
>>
>>
>> [image: weekly not OK.PNG]
>> Lastly, we see History with Week highlighted, though the graph is 
>> captioned with the word daily and without the word week.Consider rewording 
>> caption: "Rain for the week  MM DD -  MM DD from daily totals"
>>
>> N.B. in the three graphs above, all of the erroneous rain data has been 
>> nullified, including any fictitious rain from the Simulator. 
>>
>> *How long will these bogus values linger in the graphs, and what are the 
>> alternatives for their culling? *
>>
>> -- 
>> 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.

Re: [weewx-user] Cleaning up old 'bad' data

[V. Kelly Bellis]

RE: 
https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data#regenerate-web-pages

Under the section heading *Regenerate web pages*, "Most old web pages and 
plots will be automatically regenerated, *but it may take a while.*"  
Consider expanding on what *a while* is predicated on in the article; e.g., 
frequency of report generation once a year, once a month, etc. Also, how 
might these old web pages otherwise be expunged?


[image: History.PNG]

[image: yearly not OK.PNG]
Here we see History with Year highlighted, though the graph is captioned 
with the word weekly and without the word year.
Consider rewording caption: "Rain for the year  MM DD -  MM DD from 
weekly totals"


[image: monthly not OK.PNG]
Similarly, we see History with Month highlighted, though the graph is 
captioned with the word daily and without the word month.Consider rewording 
caption: "Rain for the month  MM DD -  MM DD from daily totals"


[image: weekly not OK.PNG]
Lastly, we see History with Week highlighted, though the graph is captioned 
with the word daily and without the word week.Consider rewording caption: 
"Rain for the week  MM DD -  MM DD from daily totals"

N.B. in the three graphs above, all of the erroneous rain data has been 
nullified, including any fictitious rain from the Simulator. 

*How long will these bogus values linger in the graphs, and what are the 
alternatives for their culling? *

-- 
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] Cleaning up old 'bad' data

[V. Kelly Bellis]

Good to know - thanks again! Inadvertently, I entered an Escher drawing :) 

On Sunday, February 24, 2019 at 4:19:38 PM UTC-5, Thomas Keffer wrote:
>
> Actually, what you're doing there is creating *another* shell, which is 
> running inside your sudo shell, which is running inside your original user 
> shell.
>
> A simple "exit", or Ctrl-D, will get you out of sudo -i mode (or, for 
> that matter, any other shell).
>
> -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] Cleaning up old 'bad' data

[V. Kelly Bellis]

*Thanks Tom - that did the trick!* 

Thank you for the advice; and also, thank you very much for writing the 
original article. It was quite timely as the precipitation event is upon us 
and I continue testing Arthur Emerson's new and improved atmocomUDP v1.20 
<https://github.com/captain-coredump/weewx-atmocom-udp> driver which fixed 
an earlier weewx rain-related issue.

[image: pi2root2pi.png]

FYI & FWIW for other new users who happen upon this thread; user *root*, 
invoked with 
sudo -i

can be changed back to normal user with su - username; e.g., 
su - pi



On Sunday, February 24, 2019 at 2:13:53 PM UTC-5, Thomas Keffer wrote:
>
> The "sudo" only applies to the first command (echo), not the second 
> (sqlite3). Try running interactively:
>
> *sudo -i*
> *echo "UPDATE archive SET rain=NULL WHERE (rain >0);" | sqlite3 backup.sdb*
>
>
>
> On Sun, Feb 24, 2019 at 10:39 AM V. Kelly Bellis  > wrote:
>
>> Hello,
>>
>> Closely following the outlined procedures at 
>> Cleaning up old 'bad' data 
>> <https://github.com/weewx/weewx/wiki/Cleaning-up-old-%27bad%27-data>
>>
>> After first stopping weewx, making a copy of the weewx.sdb, I'm trying to 
>> clean out all rainRate and rain values greater than 0 on my RPi 3B+ 
>> running Raspbian Linux 9 (stretch) [4.14.98-v7+], but have run into a wee 
>> snag:
>>
>> [image: read only db.PNG]
>>
>>
>> Any advice will be much appreciated.
>>
>> Kind regards,
>>
>> Kelly
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

[weewx-user] Cleaning up old 'bad' data

[V. Kelly Bellis]

Hello,

Closely following the outlined procedures at 
Cleaning up old 'bad' data 


After first stopping weewx, making a copy of the weewx.sdb, I'm trying to 
clean out all rainRate and rain values greater than 0 on my RPi 3B+ running 
Raspbian Linux 9 (stretch) [4.14.98-v7+], but have run into a wee snag:

[image: read only db.PNG]


Any advice will be much appreciated.

Kind regards,

Kelly

-- 
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: forecast extension InstallError

[V. Kelly Bellis]

Hi Gary and Matt,

Thank you very much for the kind assistance. That did the trick!

[image: forecast installed.PNG]


Kelly


On Saturday, February 23, 2019 at 5:50:02 PM UTC-5, gjr80 wrote:
>
> Hi,
>
> Have a look at the install command you used, you need to change 
> weewx-forecast-x.y.tgz to weewx-forecast-3.3.2.tgz
>
> 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] forecast extension InstallError

[V. Kelly Bellis]

RE: https://github.com/weewx/weewx/wiki/forecasting

Hello,

Following the installation instructions,

[image: forecast installation instructions.PNG]


I've tried to install the *forecast* extension for weewx running on my RPi 
3B+ running Raspbian Linux 9 (stretch) [4.14.98-v7+], but have run into a 
wee snag:


[image: forecast extension InstallError.PNG] 


Thank you for any reply.

Kind regards,

Kelly

-- 
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] Is there a list of available extensions for weewx?

[V. Kelly Bellis]

That's great, Glenn - THANK YOU !!!

On Wednesday, February 20, 2019 at 4:55:32 PM UTC-5, Glenn McKechnie wrote:
>
> Hi Kelly, 
>
> There is a list at the wiki. 
> https://github.com/weewx/weewx/wiki 
>
> half way down the page ... 
> https://github.com/weewx/weewx/wiki#extensions-to-weewx 
>
> On 21/02/2019, V. Kelly Bellis > 
> wrote: 
> > *Is there a single collective reference page that describes available 
> > extensions for weewx?* 
> > 
> > FWIW - I wasn't able to find a good definition of what exactly the term 
> > 'weewx extension' means in http://weewx.com/docs/usersguide.htm; 
> however, 
> > after a circuitous route via google, 
> > https://github.com/weewx/weewx/wiki/extensions, and then eventually 
> back to 
> > 
> > it's replica at http://weewx.com/docs/customizing.htm#extensions I 
> > understand that it means a package to extend the functionality of weewx. 
> > The MSDOS old school meaning of an extension; i.e., as in 
> eight_dot_three 
> > isn't immediately applicable, though maybe so in the abstract. Anyway, 
> all 
> > this leads to suggest: consider adding the weewx definition for 
> extension 
> > in the User's Guide, possibly under 
> > http://weewx.com/docs/usersguide.htm#Overview 
> > 
> > Kind regards, 
> > 
> > Kelly 
> > 
> > -- 
> > 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. 
> > 
>
>
> -- 
>
>
> Cheers 
>  Glenn 
>
> rorpi - read only raspberry pi & various weewx addons 
> https://github.com/glennmckechnie 
>

-- 
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] Is there a list of available extensions for weewx?

[V. Kelly Bellis]

*Is there a single collective reference page that describes available 
extensions for weewx?*

FWIW - I wasn't able to find a good definition of what exactly the term 
'weewx extension' means in http://weewx.com/docs/usersguide.htm; however, 
after a circuitous route via google, 
https://github.com/weewx/weewx/wiki/extensions, and then eventually back to 
it's replica at http://weewx.com/docs/customizing.htm#extensions I 
understand that it means a package to extend the functionality of weewx. 
The MSDOS old school meaning of an extension; i.e., as in eight_dot_three 
isn't immediately applicable, though maybe so in the abstract. Anyway, all 
this leads to suggest: consider adding the weewx definition for extension 
in the User's Guide, possibly under 
http://weewx.com/docs/usersguide.htm#Overview

Kind regards,

Kelly

-- 
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: Atmocom interceptor UDP station driver v1.00 now available!

[V. Kelly Bellis]

Hello Arthur!

Many thanks for all of the great work that you've done on your weewx driver 
for Relko Vazic's ATMOCOM <https://atmocom.com/> device (currently in 
beta). Your driver has been running steadily since earlier this week!

[image: weewx up 4d13h.PNG]


The Atmocom device is still in beta, and as far as I'm aware of, a single 
device is not intended for multiple weather stations; just one weather 
station per one Atmocom device.


KMEELLSW50 
<https://www.wunderground.com/personal-weather-station/dashboard?ID=KMEELLSW50>

I've been testing the device since its arrival last month from Spain with 
the Ambient Weather WS-2000. The WS-2000 has been sending data to Weather 
Underground since 2019015 starting around 17:00 UTC-5. The WS-2000 has 
received three firmware updates for its Display Tablet; i.e., 1.2.1 -> 
1.3.5 on 20190115 when it arrived; 1.3.5 -> 1.3.7 on 20190116; and 1.3.7 -> 
1.3.8 on 20190124. That update process requires a power cycle before SD 
card insertion, and after SD card insertion. The WS-2000 has also received 
three firmware updates for its WiFi; 4.0.2 -> 4.0.9 on 20190116; 4.0.9 -> 
4.1.0 on 20190121; and 4.1.0 -> 4.1.1 on 20190124. That update process 
requires the devices (phone running awnet app and the console) to be on the 
same subnet, and I would power cycle the Atmocom device afterwards. Note 
that it's a painstaking method each time switching back and forth between 
SSIDs as the WS-2000 has a clunky way to enter alpha-numeric strings, and 
no facility of saving SSID and their associated passwords. Needless to say, 
there have been data flow interruptions caused by these updates to the 
WS-2000 and is important to keep in mind when subsequently combing through 
its data.


Kind regards,

Kelly
-- 
V. Kelly Bellis, PLS
17 Union Street
Ellsworth, ME 04605




On Saturday, February 16, 2019 at 5:42:47 PM UTC-5, Arthur Emerson wrote:
>
> I have forked v1.03 of my WeatherFlow UDP station driver, and used it as 
> the base for a new Atmocom interceptor UDP driver that I just committed as 
> v1.00 to GitHub:
>
> https://github.com/captain-coredump/weewx-atmocom-udp/
>
>
> I made one huge improvement with this new driver: "wee_config 
> --reconfigure" is fully supported...with a complete dialog for setting 
> every option...and even builds a simple sensor_map for decoding Weather 
> Underground packets!  (I promise to back-port this feature to the WF driver 
> in the near future.)
>
>
> The README file contains simple installation instructions, and also 
> explains the sensor_map feature and configuration.  *Without a proper 
> sensor_map in weewx.conf, this driver will not log ANY data!*  The 
> sensor_map concept was borrowed from Matthew Wall’s weewx-SDR driver.  I 
> enjoyed the hours that I spent writing the README file to explain 
> everything, and hope that you enjoy reading it just as much when setting up 
> this driver on your own system.
>
>
> Before you curse me out for the added complexity of the sensor_map 
> feature, let me explain the rationale.  I believe that the Atmocom 
> interceptor device can re-broadcast observations from multiple stations, 
> and want to provide the end user with the ability to mix-and-match 
> measurements from multiple units if they have them.  Plus, stations can 
> send data to multiple web services, and having the sensor_map being 
> configurable will let someone do something like log outdoor measurements 
> from Weather Underground updates but indoor measurements from Ambient 
> Weather updates.
>
>
> I do not own an Atmocom interceptor device or station that could even use 
> it, so most of my personal testing was done on self-generated UDP packets.  
> The WeatherFlow UDP driver on which this is based has been running for 
> almost a year now at multiple locations around the world with no 
> reliability issues, so I do not anticipate any huge problems.
>
>
> Note that I have not tested against live hardware for rain accumulation 
> correctness.  If anyone finds a problem, please submit an issue in GitHub.
>
>
> If deemed worthy, can someone please add it to the wiki and wherever 
> third-party drivers are listed?
>
>
> My usual disclaimer applies.  I am not a programmer by trade, and did not 
> sleep in a Holiday Inn Express last night.  Please let me know via GitHub 
> if you find any bugs.  Enjoy.
>
>

-- 
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] Is There A Preferred WeeWX Server for RPi 3B+

[V. Kelly Bellis]

Apache, Nginx, Lighttpd, Other - Is there a preferred web server for WeeWX 
running on the same Raspberry Pi 3B+ (Raspbian OS installed using NOOBS)?

Thank you for any replies.

Kind regards,

Kelly



-- 
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: timesync vs NTP on Raspberry Pi 3B+

[V. Kelly Bellis]

Many thanks Vince and Scott. 

On Sunday, February 10, 2019 at 7:24:12 PM UTC-5, Scott Grayban wrote:
>
> If you look 
> at 
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
>
> # don't run timesyncd if we have another NTP daemon installed
> *ConditionFileIsExecutable=!/usr/sbin/ntpd*
> ConditionFileIsExecutable=!/usr/sbin/openntpd
> ConditionFileIsExecutable=!/usr/sbin/chronyd
> ConditionFileIsExecutable=!/usr/sbin/VBoxService
>
> So it's completely disabled with NTP
>
> On Sunday, February 10, 2019 at 11:05:40 AM UTC-8, vince wrote:
>>
>> On Sunday, February 10, 2019 at 10:44:48 AM UTC-8, V. Kelly Bellis wrote:
>>>
>>> http://weewx.com/docs/usersguide.htm states that I should run a NTP 
>>> <http://www.ntp.org/> daemon, but doesn't address an existing/ running 
>>> pre-installed timesync service; e.g., installed with Raspbian via NOOBS
>>>
>>> Elsewhere <http://raspberrypi.tomasgreno.cz/ntp-client-and-server.html>, 
>>> we read that timesync and NTP should not be run at the same time - "*but 
>>> you can not have running both of them at the same time*"
>>>
>>> Is the pre-installed timesync sufficient for weewx? Either way, could 
>>> the users guide include some mention of timesync's shortcomings or 
>>> sufficiency insofar as weewx is concerned?
>>>
>>>
>>>
>> The users guide can't/shouldn't try to cover all the nuances of every 
>> operating system nor the sheer unfettered joy that is systemd (ha - beat 
>> Matthew to it!)
>>
>> What happens is if you run NTP, systemd gets out of the way and doesn't 
>> enable its ntp hack/feature/whatever.
>>
>> So, FWIW, I always run NTP because I have decades of positive experience 
>> with that software.   It's a well-understood thing.   Much easier to debug 
>> when that's needed.
>>
>> (and any time I can disable systemd 'helping' me, I tend to do so.  That 
>> thing is much harder to debug when it goes whacko.)
>>  
>>
>

-- 
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: timesync vs NTP on Raspberry Pi 3B+

[V. Kelly Bellis]

Hi Vince,
Thank you for the reply.
Are you saying that there's no issue installing (as super user?) the ntp 
package with /lib/systemd-/systemdtimesyncd running?


On Sunday, February 10, 2019 at 2:05:40 PM UTC-5, vince wrote:
>
> On Sunday, February 10, 2019 at 10:44:48 AM UTC-8, V. Kelly Bellis wrote:
>>
>> http://weewx.com/docs/usersguide.htm states that I should run a NTP 
>> <http://www.ntp.org/> daemon, but doesn't address an existing/ running 
>> pre-installed timesync service; e.g., installed with Raspbian via NOOBS
>>
>> Elsewhere <http://raspberrypi.tomasgreno.cz/ntp-client-and-server.html>, 
>> we read that timesync and NTP should not be run at the same time - "*but 
>> you can not have running both of them at the same time*"
>>
>> Is the pre-installed timesync sufficient for weewx? Either way, could the 
>> users guide include some mention of timesync's shortcomings or sufficiency 
>> insofar as weewx is concerned?
>>
>>
>>
> The users guide can't/shouldn't try to cover all the nuances of every 
> operating system nor the sheer unfettered joy that is systemd (ha - beat 
> Matthew to it!)
>
> What happens is if you run NTP, systemd gets out of the way and doesn't 
> enable its ntp hack/feature/whatever.
>
> So, FWIW, I always run NTP because I have decades of positive experience 
> with that software.   It's a well-understood thing.   Much easier to debug 
> when that's needed.
>
> (and any time I can disable systemd 'helping' me, I tend to do so.  That 
> thing is much harder to debug when it goes whacko.)
>  
>

-- 
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] timesync vs NTP on Raspberry Pi 3B+

[V. Kelly Bellis]

http://weewx.com/docs/usersguide.htm states that I should run a NTP 
 daemon, but doesn't address an existing/ running 
pre-installed timesync service; e.g., installed with Raspbian via NOOBS

Elsewhere , we 
read that timesync and NTP should not be run at the same time - "*but you 
can not have running both of them at the same time*"

Is the pre-installed timesync sufficient for weewx? Either way, could the 
users guide include some mention of timesync's shortcomings or sufficiency 
insofar as weewx is concerned?

Kind regards,

Kelly

-- 
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: Can weeWX link with an SQLite3 Database?

[V. Kelly Bellis]

Thank you Vince for the reply. 
I'll install weewx and give it, and the WeatherFlow UDP driver, a test 
drive!
BTW - Are you a/k/a vreihen on wxforum.net ?
Kind regards,
Kelly
V. Kelly Bellis, PLS 
17 Union Street 
Ellsworth, ME 04605 
Check this out, it was fun making: */Determing True North 
<https://www.youtube.com/watch?v=zMwDkzl43n8> 
<https://www.youtube.com/watch?v=zMwDkzl43n8>/* 


On Thursday, January 17, 2019 at 3:02:12 PM UTC-5, vince wrote:
>
> On Thursday, January 17, 2019 at 10:09:27 AM UTC-8, V. Kelly Bellis wrote:
>
>> Atmocom's UDP broadcast listener and parser will capture broadcast 
>> packets (currently only in WU data format) containing weather data sent 
>> from the Ambient Weather WS-2000 (in my test example), gets passed along by 
>> ATMOCOM to WU (again, in this beta scenario) and then logs each record in a 
>> monthly SQLite database, which in in my first experiments are on the RPi 
>> running the aforecited atmoudp36.bin. 
>>
>>
>>
> The WeatherFlow driver for weewx listens for that station's hub UDP 
> broadcasts and saves it to the normal weewx database (with some mapping of 
> message contents to weewx schema done in weewx.conf).  You might want to 
> take a look at that to see if you can borrow from how it does that what 
> tweaks you might need to do in order to take a similar approach.  Should be 
> very doable if you want to just run weewx with that station only.
>
> If you want to run that as a secondary data source, it would be a little 
> more work to get it to write to a secondary weewx db, but that should 
> (untested) be a data binding thing to add.   Should probably work in both 
> cases.
>
> Anyway - look at the WeatherFlow UDP driver.  Works really well.
>
>

-- 
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: Can weeWX link with an SQLite3 Database?

[V. Kelly Bellis]

Thank you for the reply, Tom. 

Atmocom's UDP broadcast listener and parser will capture broadcast packets 
(currently only in WU data format) containing weather data sent from the 
Ambient Weather WS-2000 (in my test example), gets passed along by ATMOCOM 
to WU (again, in this beta scenario) and then logs each record in a monthly 
SQLite database, which in in my first experiments are on the RPi running 
the aforecited atmoudp36.bin. 

If interested, more on that here: 
https://github.com/atmocom/python3-udp#installing-and-running-atmoudp36bin-standalone-executable-for-raspberry-pi

Kind regards,

Kelly

On Thursday, January 17, 2019 at 12:07:37 PM UTC-5, V. Kelly Bellis wrote:
>
> Hello,
>
> New to all of this weather data business; please excuse my stupid 
> questions.
>
> I'm currently beta testing Atmocom, a device best described as a special 
> purpose wireless router. It connects your WiFi enabled weather station to 
> your regular home or business network wireless router and the Internet. Any 
> network traffic that passes through will be forwarded to its original 
> destination while also being replicated and forwarded (using UDP) to a user 
> configurable alternate destination. In my current case, that's a RPi 3B+ 
> running Raspbian: /home/pi/atmocom/wxdb 
>
> The database is in the SQLite3 format produced by atmoudp36.bin which is 
> a standalone executable for Raspberry PI using Python 3. I've begun 
> browsing the http://weewx.com/docs/usersguide.htm and see that Python 3 
> will not work as an environment for weeWX, but wondered if the database in 
> SQLite3 might still be of any use in weeWX?
>
> Thanks!
>
> Kind regards,
>
> Kelly
>

-- 
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] Can weeWX link with an SQLite3 Database?

[V. Kelly Bellis]

Hello,

New to all of this weather data business; please excuse my stupid questions.

I'm currently beta testing Atmocom, a device best described as a special 
purpose wireless router. It connects your WiFi enabled weather station to 
your regular home or business network wireless router and the Internet. Any 
network traffic that passes through will be forwarded to its original 
destination while also being replicated and forwarded (using UDP) to a user 
configurable alternate destination. In my current case, that's a RPi 3B+ 
running Raspbian: /home/pi/atmocom/wxdb 

The database is in the SQLite3 format produced by atmoudp36.bin which is a 
standalone executable for Raspberry PI using Python 3. I've begun browsing 
the http://weewx.com/docs/usersguide.htm and see that Python 3 will not 
work as an environment for weeWX, but wondered if the database in SQLite3 
might still be of any use in weeWX?

Thanks!

Kind regards,

Kelly

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