date:20210104

OK, found 4.0.0b9, yes indeed altimeter was before pressure. Plus when you 
look back at the initial log extract provided you can see the evidence:

Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
weewx version 4.0.0b9
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
Linux-4.19.75-v7l+-armv7l-with-debian-10.1
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
'en_US.UTF-8'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
configuration file /home/weewx/weewx.conf
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
target unit is 0x1
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following values will be calculated: altimeter=prefer_hardware, 
appTemp=prefer_hardware, barometer=prefer_hardware, 
beaufort=prefer_hardware, cloudbase=prefer_hardware, 
dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
humidex=prefer_hardware, inDewpoint=prefer_hardware, 
maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following algorithms will be used for calculations: altimeter=aaASOS, 
maxSolarRad=RS
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will 
use data binding wx_binding

b10 was the same but b11 onwards was fixed and as I said later releases 
have changed in this area significantly.

Sure this was an issue for 4.0.0b9 but I don't believe it is an issue for 
4.0.0b11 and any subsequent releases. Easiest solution is to upgrade.

Gary

On Tuesday, 5 January 2021 at 15:24:51 UTC+10 gjr80 wrote:

> Ah, didn't notice that. the other thing is you appear to be running a late 
> beta of a version about four versions ago. Plus there has been quite a few 
> changes to StdWXCalculate over the last few releases. You may find that the 
> issue has been resolved (deliberately or unintentionally) in one of those 
> releases.
>
> I don't have access to 4.0.0b9 but I will take a browse through some of 
> his close friends and see if I can't spot a problem.
>
> Gary
>
> On Tuesday, 5 January 2021 at 14:34:24 UTC+10 brent...@gmail.com wrote:
>
>> The issue is that it's looping over the calculations in that order in the 
>> wxservices.py source code, and not the order from the weewx.conf.
>>
>> I had to edit the order in the wxservices.py code in order to get things 
>> to work right.
>>
>> I did add it as an issue in the github repository.
>>
>> On Monday, January 4, 2021 at 8:12:07 PM UTC-8 gjr80 wrote:
>>
>>> Yes, pressure needs to be listed before the other pressures, order 
>>> matters in this case. I thought of that but the wee_debug output you 
>>> provided in the other thread showed pressure was first so I did not 
>>> bother. No matter, I guess it's fixed now.
>>>
>>> Gary
>>>
>>> On Tuesday, 5 January 2021 at 13:38:15 UTC+10 brent...@gmail.com wrote:
>>>
 Think I figured it out.

 Calculating the altimeter depends on pressure being calculated, but the 
 list of calculations had pressure in alphabetical order.
 I moved pressure in the calculations section before altimeter and my 
 problem appears to be solved.


 wxservices.py line 46

[[Calculations]]
 pressure = prefer_hardware
 altimeter = prefer_hardware
 appTemp = prefer_hardware
 barometer = prefer_hardware
 beaufort = prefer_hardware
 cloudbase = prefer_hardware
 dewpoint = prefer_hardware
 ET = prefer_hardware
 heatindex = prefer_hardware
 humidex = prefer_hardware
 inDewpoint = prefer_hardware
 maxSolarRad = prefer_hardware
 rainRate = prefer_hardware
 windchill = prefer_hardware
 windrun = prefer_hardware

 On Mon, Jan 4, 2021 at 4:45 PM Tom Keffer  wrote:

> Everything looks normal to me. The log shows a post to CW8738:
>
> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
> Published record 2021-01-04 13:50:00 PST (1609797000)
>
> After that, you did a keyboard interrupt, but the log stops before the 
> next reporting cycle.
>
> Taking a look at findu, your packets are also showing up regularly: 
> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>
> What are you seeing that causes concern?
>
> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  
> wrote:
>
>> A couple months ago I moved my weather station to run on a Raspberry 
>> pi, and things have been running smoothly  with the ex

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

> Once I sort this possible discrepancy, I'd like to pick your brain on adding 
> the Station Volts.

I added it at head.  Station volts will now show up as supplyVoltage.

> On Jan 4, 2021, at 7:44 PM, John Kline  wrote:
> 
> 
> The IP100 resets the day’s rain total at midnight (according to it’s clock).  
> It doesn’t really matter to the driver when that happens.  The driver is 
> simply looking for a positive increment in day_rain_total.  On a negative 
> increment (e.g., reset), the driver just saves the last value and reports 0.0 
> for rain.
> 
>>> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
>>> 
>> 
>> Thanks for the guidance John!   I was anticipating to simply have a day with 
>> a clean run, starting at midnight.  I should have this info tomorrow.
>> 
>> I assume the loop will recognize my local timezone to reset to zero at 
>> midnight, recognizing the db is being recorded on GMT?
>> 
>> Once I sort this possible discrepancy, I'd like to pick your brain on adding 
>> the Station Volts.
>> 
>> Regards,
>> 
>>> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:
>>> You don’t to delete records.  There isn’t really much to the rain 
>>> calculation.  For all rain that occurred while WeeWX is up and running, the 
>>> day_rain_total will increment, the driver will calculate the delta and add 
>>> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 inches 
>>> would have had to happen while WeeWX wasn’t running.
>>> 
>>> Let’s try a day where WeeWX has been running, uninterrupted, since midnight.
>>> 
> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
> 
 
>>> 
 Thanks for the quick response John!
 
 I am running your version of the IP100 for weewx 4 - version 0.5
 
 I did restart the weewx today -- had some network issues, compliments of 
 Comcast.   However, I've witnessed discrepancies between the IP100 Console 
 and weewx for several days -- just finally had a chance to get some data 
 captures.   I may need to capture data again tomorrow (knowing it will be 
 raining buckets again).
 
 At this point in time:
 
   IP100
 weewx
 Rainfall  0.06 
   0.15
 Rain Rate  0.00   
 0.00
 
 Can I truncate (delete all records) from the weewx.sdb (after backing up 
 of course) to start fresh, so that we have a solid baseline to evaluate?
 
> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com wrote:
> Station volts is not in the default map.  It wouldn’t be hard to add.
> 
> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped 
> the version to 0.5 in my fork).  I’m presuming you are running it.
> 
> Although I’m not currently running the driver, I did run it for almost 
> two years and rain values ALWAYS agreed with my WeeWX instances running 
> the CC3000 driver and talking to the same RainWise weather station.
> 
> day_rain_total is used to calculate rain.  It is not, in itself saved to 
> the database.
> 
> I have not downloaded your files.  You’ll have to tell me if the ip100 
> console does not agree with the console for today’s rain and, if not, 
> what two values you are seeing.  Please list them.
> 
> If you do have a discrepancy for today’s rain, please state if you 
> restarted weewx today (or if it restarted on its own today).  That would 
> be a way to lose rainfall.
> 
> 
>>> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
>>> 
>> 
> 
>> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the 
>> IP-100 v0.5 extension.  It appears the IP-100 Console data does not 
>> match the data presented via weewx (using the out-of-box index.html, 
>> which is using the SeasonsSkin) -- particularly, the Rain and Rain Rate. 
>>   I've shared screen shots of both the IP-100 Console and the weewx html
>> 
>> Based on some investigation, the log file (attached) indicates the data 
>> which is showing on the IP-100 Console is being captured correctly,   
>> However, looking at the archive table (attached) in the weewx.sdb, it 
>> does not appear the data elements are being posted to the archive table 
>> correctly - specifically day_rain_total (log) vs rain (archive table) 
>> and rain (log) vs rainRate (archive table).
>> 
>> Additionally, the station_volts (log file) are not being posted to the 
>> archive table.
>> 
>> I'm new to this world, but do have some technical bones -- any guidance 
>> on what actions need to be taken to address the discrepancy would be 
>> appreciated.
>> 
>> Thanks in advance!
>> 
>> Archive Table
>> 
>> Syslog

Re: [weewx-user] Barometer data missing for CWOP

Ah, didn't notice that. the other thing is you appear to be running a late 
beta of a version about four versions ago. Plus there has been quite a few 
changes to StdWXCalculate over the last few releases. You may find that the 
issue has been resolved (deliberately or unintentionally) in one of those 
releases.

I don't have access to 4.0.0b9 but I will take a browse through some of his 
close friends and see if I can't spot a problem.

Gary

On Tuesday, 5 January 2021 at 14:34:24 UTC+10 brent...@gmail.com wrote:

> The issue is that it's looping over the calculations in that order in the 
> wxservices.py source code, and not the order from the weewx.conf.
>
> I had to edit the order in the wxservices.py code in order to get things 
> to work right.
>
> I did add it as an issue in the github repository.
>
> On Monday, January 4, 2021 at 8:12:07 PM UTC-8 gjr80 wrote:
>
>> Yes, pressure needs to be listed before the other pressures, order 
>> matters in this case. I thought of that but the wee_debug output you 
>> provided in the other thread showed pressure was first so I did not 
>> bother. No matter, I guess it's fixed now.
>>
>> Gary
>>
>> On Tuesday, 5 January 2021 at 13:38:15 UTC+10 brent...@gmail.com wrote:
>>
>>> Think I figured it out.
>>>
>>> Calculating the altimeter depends on pressure being calculated, but the 
>>> list of calculations had pressure in alphabetical order.
>>> I moved pressure in the calculations section before altimeter and my 
>>> problem appears to be solved.
>>>
>>>
>>> wxservices.py line 46
>>>
>>>[[Calculations]]
>>> pressure = prefer_hardware
>>> altimeter = prefer_hardware
>>> appTemp = prefer_hardware
>>> barometer = prefer_hardware
>>> beaufort = prefer_hardware
>>> cloudbase = prefer_hardware
>>> dewpoint = prefer_hardware
>>> ET = prefer_hardware
>>> heatindex = prefer_hardware
>>> humidex = prefer_hardware
>>> inDewpoint = prefer_hardware
>>> maxSolarRad = prefer_hardware
>>> rainRate = prefer_hardware
>>> windchill = prefer_hardware
>>> windrun = prefer_hardware
>>>
>>> On Mon, Jan 4, 2021 at 4:45 PM Tom Keffer  wrote:
>>>
 Everything looks normal to me. The log shows a post to CW8738:

 Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
 Published record 2021-01-04 13:50:00 PST (1609797000)

 After that, you did a keyboard interrupt, but the log stops before the 
 next reporting cycle.

 Taking a look at findu, your packets are also showing up regularly: 
 http://www.findu.com/cgi-bin/raw.cgi?call=CW8738

 What are you seeing that causes concern?

 On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:

> A couple months ago I moved my weather station to run on a Raspberry 
> pi, and things have been running smoothly  with the exception of the data 
> that gets uploaded to CWOP.
>
> I upload data to cwop, wunderground, pwsweather, and my own weather 
> site.  The only one missing the data is cwop.
>
> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a 
> vantage vue weather station.
>
> I've attached below the cwop data, loop data, and syslog.
>
> Thanks in advance for any help.
>
>
>
> My raw data for cwop has a  b.  for the barometric data. 
>
> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>   
>
> Loop Data looks like:
> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 
> 0.01, 
> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 
> 0, 
> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, 
> rainRate: 
> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
> 28.0, yearET: 0.0, yearRain: 0.4
>
> Here's my syslog from the startup with debug = 1
>
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: 
> Initializing weewx version 4.0.0b9
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
> Python 2.

[weewx-user] Re: Version 4.3.0 released

2021-01-04 Thread Greg from Oz

Updated and working OK so far.

Thanks
https://weather.ubeaut.work/


On Tuesday, 5 January 2021 at 10:28:30 UTC+11 tke...@gmail.com wrote:

> This release fixes a bug in V4.2 that caused average values to be calculated 
> incorrectly if the archive interval changes.
>
>
> 4.3.0 01/04/2020
>
> Version 4.2.0 had a bug, which caused the sums in the daily summary to be
> incorrectly calculated. This version includes a patch to fix the problem. It
> runs once at startup. Fixes issue #623.
>
> The WMR200 driver is no longer supported. An unsupported version can be found
> at https://github.com/weewx/weewx-wmr200. Support for LaCrosse WS23xx and
> Oregon WMR300 will continue.
>
> Service weewx.wxxtypes.StdDelta was inadvertently left out of the list of
> services to be run. Fortunately, it is not used. Yet. Added it back in.
>
> Added the "old" NWS algorithm as an option for calculating heat index.
>
> Changed how various undocumented parameters in [StdWXCalculate] are specified.
> The only one people are likely to have used is 'ignore_zero_wind'. Its name 
> has
> changed to 'force_null', and it has been moved. See the Upgrading Guide.
>
> Documented the various [StdWXCalculate] options.
>
> Fixed corner case for windDir when using software record generation,
> ignore_zero_wind=True, and windSpeed=0 for entire record interval. Now emits
> last windDir value.
>
> Fixed problem when looking up stars with more than one word in their name.
> Fixes issue #620.
>
> Fixed problem where wind gust direction is not available when using software
> record generation.
>
> Added --no-prompt action to wee_import allowing wee_import to be run 
> unattended.
>
> Fixed problem that prevented option `observations` from being used in the
> simulator. Thanks to user Graham!
>
> Fixed problem where wind chill was calculated incorrectly for METRICWX
> databases. PR #627. Thanks to user edi-x!
>
> Allow wind vectors to be converted to unit of beaufort. Fixes issue #629.
>
> Option log_failure under [StdReport] is set to True by the upgrade process.
> See the Upgrading Guide.
>
>

-- 
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/340984fe-95b4-4532-b9b5-d2f2a1c869f5n%40googlegroups.com.

Re: [weewx-user] Barometer data missing for CWOP

The issue is that it's looping over the calculations in that order in the 
wxservices.py source code, and not the order from the weewx.conf.

I had to edit the order in the wxservices.py code in order to get things to 
work right.

I did add it as an issue in the github repository.

On Monday, January 4, 2021 at 8:12:07 PM UTC-8 gjr80 wrote:

> Yes, pressure needs to be listed before the other pressures, order 
> matters in this case. I thought of that but the wee_debug output you 
> provided in the other thread showed pressure was first so I did not 
> bother. No matter, I guess it's fixed now.
>
> Gary
>
> On Tuesday, 5 January 2021 at 13:38:15 UTC+10 brent...@gmail.com wrote:
>
>> Think I figured it out.
>>
>> Calculating the altimeter depends on pressure being calculated, but the 
>> list of calculations had pressure in alphabetical order.
>> I moved pressure in the calculations section before altimeter and my 
>> problem appears to be solved.
>>
>>
>> wxservices.py line 46
>>
>>[[Calculations]]
>> pressure = prefer_hardware
>> altimeter = prefer_hardware
>> appTemp = prefer_hardware
>> barometer = prefer_hardware
>> beaufort = prefer_hardware
>> cloudbase = prefer_hardware
>> dewpoint = prefer_hardware
>> ET = prefer_hardware
>> heatindex = prefer_hardware
>> humidex = prefer_hardware
>> inDewpoint = prefer_hardware
>> maxSolarRad = prefer_hardware
>> rainRate = prefer_hardware
>> windchill = prefer_hardware
>> windrun = prefer_hardware
>>
>> On Mon, Jan 4, 2021 at 4:45 PM Tom Keffer  wrote:
>>
>>> Everything looks normal to me. The log shows a post to CW8738:
>>>
>>> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
>>> Published record 2021-01-04 13:50:00 PST (1609797000)
>>>
>>> After that, you did a keyboard interrupt, but the log stops before the 
>>> next reporting cycle.
>>>
>>> Taking a look at findu, your packets are also showing up regularly: 
>>> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>>>
>>> What are you seeing that causes concern?
>>>
>>> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:
>>>
 A couple months ago I moved my weather station to run on a Raspberry 
 pi, and things have been running smoothly  with the exception of the data 
 that gets uploaded to CWOP.

 I upload data to cwop, wunderground, pwsweather, and my own weather 
 site.  The only one missing the data is cwop.

 I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a 
 vantage vue weather station.

 I've attached below the cwop data, loop data, and syslog.

 Thanks in advance for any help.



 My raw data for cwop has a  b.  for the barometric data. 

 CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
   

 Loop Data looks like:
 LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
 barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
 consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
 dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
 extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
 extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
 humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
 inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
 monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
 outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, 
 rainRate: 
 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
 soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
 28.0, yearET: 0.0, yearRain: 0.4

 Here's my syslog from the startup with debug = 1

 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: 
 Initializing weewx version 4.0.0b9
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
 Python 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
 Linux-4.19.75-v7l+-armv7l-with-debian-10.1
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
 'en_US.UTF-8'
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
 configuration file /home/weewx/weewx.conf
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
 target unit is 0x1
 Jan  4 13:48:41 raspberrypi

Re: [weewx-user] Barometer data missing for CWOP

Yes, pressure needs to be listed before the other pressures, order matters 
in this case. I thought of that but the wee_debug output you provided in 
the other thread showed pressure was first so I did not bother. No matter, 
I guess it's fixed now.

Gary

On Tuesday, 5 January 2021 at 13:38:15 UTC+10 brent...@gmail.com wrote:

> Think I figured it out.
>
> Calculating the altimeter depends on pressure being calculated, but the 
> list of calculations had pressure in alphabetical order.
> I moved pressure in the calculations section before altimeter and my 
> problem appears to be solved.
>
>
> wxservices.py line 46
>
>[[Calculations]]
> pressure = prefer_hardware
> altimeter = prefer_hardware
> appTemp = prefer_hardware
> barometer = prefer_hardware
> beaufort = prefer_hardware
> cloudbase = prefer_hardware
> dewpoint = prefer_hardware
> ET = prefer_hardware
> heatindex = prefer_hardware
> humidex = prefer_hardware
> inDewpoint = prefer_hardware
> maxSolarRad = prefer_hardware
> rainRate = prefer_hardware
> windchill = prefer_hardware
> windrun = prefer_hardware
>
> On Mon, Jan 4, 2021 at 4:45 PM Tom Keffer  wrote:
>
>> Everything looks normal to me. The log shows a post to CW8738:
>>
>> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
>> Published record 2021-01-04 13:50:00 PST (1609797000)
>>
>> After that, you did a keyboard interrupt, but the log stops before the 
>> next reporting cycle.
>>
>> Taking a look at findu, your packets are also showing up regularly: 
>> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>>
>> What are you seeing that causes concern?
>>
>> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:
>>
>>> A couple months ago I moved my weather station to run on a Raspberry pi, 
>>> and things have been running smoothly  with the exception of the data that 
>>> gets uploaded to CWOP.
>>>
>>> I upload data to cwop, wunderground, pwsweather, and my own weather 
>>> site.  The only one missing the data is cwop.
>>>
>>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
>>> vue weather station.
>>>
>>> I've attached below the cwop data, loop data, and syslog.
>>>
>>> Thanks in advance for any help.
>>>
>>>
>>>
>>> My raw data for cwop has a  b.  for the barometric data. 
>>>
>>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>>   
>>>
>>> Loop Data looks like:
>>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
>>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
>>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
>>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>>> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
>>> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
>>> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
>>> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
>>> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
>>> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
>>> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
>>> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
>>> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
>>> 28.0, yearET: 0.0, yearRain: 0.4
>>>
>>> Here's my syslog from the startup with debug = 1
>>>
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
>>> weewx version 4.0.0b9
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
>>> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
>>> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
>>> 'en_US.UTF-8'
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
>>> configuration file /home/weewx/weewx.conf
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
>>> station type Vantage (weewx.drivers.vantage)
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
>>> target unit is 0x1
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>>> following values will be calculated: altimeter=prefer_hardware, 
>>> appTemp=prefer_hardware, barometer=prefer_hardware, 
>>> beaufort=prefer_hardware, cloudbase=prefer_hardware, 
>>> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
>>> humidex=prefer_hardware, inDewpoint=prefer_hardware, 
>>> maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
>>> rainRate=prefer_hardware, windchill=pref

[weewx-user] Re: diffrent upload time to ss

OK, so there you go, you should find gauge-data.txt appearing in 
/var/www/html/weewx/realtime.

Jan  5 01:01:44 metfm weewx[31863] DEBUG weewx.engine: Loading service 
> user.rtgd.RealtimeGaugeData
> Jan  5 01:01:44 metfm weewx[31863] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  5 01:01:44 metfm weewx[31863] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  5 01:01:44 metfm weewx[31863] INFO user.rtgd: Unknown block specified 
> for scroller_text
> Jan  5 01:01:44 metfm weewx[31863] INFO user.rtgd: 
> '/var/www/html/weewx/realtime/gauge-data.txt' wil be generated. 
> min_interval is None
> Jan  5 01:01:44 metfm weewx[31863] DEBUG weewx.engine: Finished loading 
> service user.rtgd.RealtimeGaugeData
>
 

> Jan  5 01:02:58 metfm weewx[31863] DEBUG user.rtgd: gauge-data.txt 
> (1609801379) generated in 0.01757 seconds
>
 

> Jan  5 01:03:58 metfm weewx[31863] DEBUG user.rtgd: gauge-data.txt 
> (1609801439) generated in 0.01018 seconds
>

Jan  5 01:04:59 metfm weewx[31863] DEBUG user.rtgd: gauge-data.txt 
> (1609801499) generated in 0.01187 seconds
>

I'm guessing that since you are using ftp to upload your files the issue is 
that gauge-data.txt is only uploaded every time the ftp 'report' is run 
which is every archive interval, in your case every five minutes. If you 
want to upload gauge-data.txt to your web server more often than every five 
minutes you have a couple of options. The rtgd extension can be configured 
to upload to a remote server via HTTP POST. To do this the remote server 
must have php installed. Setting up HTTP POST is covered here 

 
in the rtgd wiki. The rtgd extension can also use rsync to transfer 
gauge-data.txt to a remote server, the setup is covered in the comments in 
rtgd.py from about line 213 to line 265. I have not used the rsync 
capability in rtgd.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ca009662-054f-45ec-abf3-de95519d7079n%40googlegroups.com.

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

The IP100 resets the day’s rain total at midnight (according to it’s clock).  
It doesn’t really matter to the driver when that happens.  The driver is simply 
looking for a positive increment in day_rain_total.  On a negative increment 
(e.g., reset), the driver just saves the last value and reports 0.0 for rain.

> On Jan 4, 2021, at 7:40 PM, tim lambert  wrote:
> 
> 
> Thanks for the guidance John!   I was anticipating to simply have a day with 
> a clean run, starting at midnight.  I should have this info tomorrow.
> 
> I assume the loop will recognize my local timezone to reset to zero at 
> midnight, recognizing the db is being recorded on GMT?
> 
> Once I sort this possible discrepancy, I'd like to pick your brain on adding 
> the Station Volts.
> 
> Regards,
> 
>> On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:
>> You don’t to delete records.  There isn’t really much to the rain 
>> calculation.  For all rain that occurred while WeeWX is up and running, the 
>> day_rain_total will increment, the driver will calculate the delta and add 
>> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 inches 
>> would have had to happen while WeeWX wasn’t running.
>> 
>> Let’s try a day where WeeWX has been running, uninterrupted, since midnight.
>> 
 On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
 
>>> 
>> 
>>> Thanks for the quick response John!
>>> 
>>> I am running your version of the IP100 for weewx 4 - version 0.5
>>> 
>>> I did restart the weewx today -- had some network issues, compliments of 
>>> Comcast.   However, I've witnessed discrepancies between the IP100 Console 
>>> and weewx for several days -- just finally had a chance to get some data 
>>> captures.   I may need to capture data again tomorrow (knowing it will be 
>>> raining buckets again).
>>> 
>>> At this point in time:
>>> 
>>>   IP100 
>>>weewx
>>> Rainfall  0.06  
>>>  0.15
>>> Rain Rate  0.00   
>>> 0.00
>>> 
>>> Can I truncate (delete all records) from the weewx.sdb (after backing up of 
>>> course) to start fresh, so that we have a solid baseline to evaluate?
>>> 
 On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com wrote:
 Station volts is not in the default map.  It wouldn’t be hard to add.
 
 I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped 
 the version to 0.5 in my fork).  I’m presuming you are running it.
 
 Although I’m not currently running the driver, I did run it for almost two 
 years and rain values ALWAYS agreed with my WeeWX instances running the 
 CC3000 driver and talking to the same RainWise weather station.
 
 day_rain_total is used to calculate rain.  It is not, in itself saved to 
 the database.
 
 I have not downloaded your files.  You’ll have to tell me if the ip100 
 console does not agree with the console for today’s rain and, if not, what 
 two values you are seeing.  Please list them.
 
 If you do have a discrepancy for today’s rain, please state if you 
 restarted weewx today (or if it restarted on its own today).  That would 
 be a way to lose rainfall.
 
 
>> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
>> 
> 
 
> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the IP-100 
> v0.5 extension.  It appears the IP-100 Console data does not match the 
> data presented via weewx (using the out-of-box index.html, which is using 
> the SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've shared 
> screen shots of both the IP-100 Console and the weewx html
> 
> Based on some investigation, the log file (attached) indicates the data 
> which is showing on the IP-100 Console is being captured correctly,   
> However, looking at the archive table (attached) in the weewx.sdb, it 
> does not appear the data elements are being posted to the archive table 
> correctly - specifically day_rain_total (log) vs rain (archive table) and 
> rain (log) vs rainRate (archive table).
> 
> Additionally, the station_volts (log file) are not being posted to the 
> archive table.
> 
> I'm new to this world, but do have some technical bones -- any guidance 
> on what actions need to be taken to address the discrepancy would be 
> appreciated.
> 
> Thanks in advance!
> 
> Archive Table
> 
> Syslog
> 
> IP-100 Console
> 
> weewx html page
 
> -- 
> 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.
> To view this discussion on t

Re: [weewx-user] Just want to verify the location of the Pressure Sensor in the Accurite 02032C

2021-01-04 Thread p q

I'm fairly sure that's correct as it still reports the pressure when the
battery to the outdoor sensor runs down.

On Mon, Jan 4, 2021 at 6:33 PM  wrote:

> I want to make sure the pressure sensor for the Accurite 02032C is in the
> indoor console and not in the 5-1 sensor that is placed on a pole outdoors.
>
> Thanks,
>
> Chris Maness
>
> --
> 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/86943363-98eb-25db-d133-92828a837d0d%40gmail.com
> 
> .
>


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM2245HaFZOMKL5MbfnbMHKTx565xBJGNLH9Dki0qAouSYg%40mail.gmail.com.

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

2021-01-04 Thread tim lambert

Thanks for the guidance John!   I was anticipating to simply have a day 
with a clean run, starting at midnight.  I should have this info tomorrow.

I assume the loop will recognize my local timezone to reset to zero at 
midnight, recognizing the db is being recorded on GMT?

Once I sort this possible discrepancy, I'd like to pick your brain on 
adding the Station Volts.

Regards,

On Monday, January 4, 2021 at 7:34:48 PM UTC-8 jo...@johnkline.com wrote:

> You don’t to delete records.  There isn’t really much to the rain 
> calculation.  For all rain that occurred while WeeWX is up and running, the 
> day_rain_total will increment, the driver will calculate the delta and add 
> it to the loop record as ‘rain’.  For the discrepancy to occur, 0.09 inches 
> would have had to happen while WeeWX wasn’t running.
>
> Let’s try a day where WeeWX has been running, uninterrupted, since 
> midnight.
>
> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
>
> 
>
> Thanks for the quick response John!
>
> I am running your version of the IP100 for weewx 4 - version 0.5
>
> I did restart the weewx today -- had some network issues, compliments of 
> Comcast.   However, I've witnessed discrepancies between the IP100 Console 
> and weewx for several days -- just finally had a chance to get some data 
> captures.   I may need to capture data again tomorrow (knowing it will be 
> raining buckets again).
>
> At this point in time:
>
>   
> IP100weewx
> Rainfall  
> 0.06   0.15
> Rain Rate  0.00   
> 0.00
>
> Can I truncate (delete all records) from the weewx.sdb (after backing up 
> of course) to start fresh, so that we have a solid baseline to evaluate?
>
> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com wrote:
>
>> Station volts is not in the default map.  It wouldn’t be hard to add.
>>
>> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped 
>> the version to 0.5 in my fork).  I’m presuming you are running it.
>>
>> Although I’m not currently running the driver, I did run it for almost 
>> two years and rain values ALWAYS agreed with my WeeWX instances running the 
>> CC3000 driver and talking to the same RainWise weather station.
>>
>> day_rain_total is used to calculate rain.  It is not, in itself saved to 
>> the database.
>>
>> I have not downloaded your files.  You’ll have to tell me if the ip100 
>> console does not agree with the console for today’s rain and, if not, what 
>> two values you are seeing.  Please list them.
>>
>> If you do have a discrepancy for today’s rain, please state if you 
>> restarted weewx today (or if it restarted on its own today).  That would be 
>> a way to lose rainfall.
>>
>>
>> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
>>
>> 
>>
>> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the IP-100 
>> v0.5 extension.  It appears the IP-100 Console data does not match the data 
>> presented via weewx (using the out-of-box index.html, which is using the 
>> SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've shared screen 
>> shots of both the IP-100 Console and the weewx html
>>
>> Based on some investigation, the log file (attached) indicates the data 
>> which is showing on the IP-100 Console is being captured correctly,   
>> However, looking at the archive table (attached) in the weewx.sdb, it does 
>> not appear the data elements are being posted to the archive table 
>> correctly - specifically day_rain_total (log) vs rain (archive table) and 
>> rain (log) vs rainRate (archive table).
>>
>> Additionally, the station_volts (log file) are not being posted to the 
>> archive table.
>>
>> I'm new to this world, but do have some technical bones -- any guidance 
>> on what actions need to be taken to address the discrepancy would be 
>> appreciated.
>>
>> Thanks in advance!
>>
>> Archive Table 
>> 
>>
>> Syslog 
>>
>> IP-100 Console 
>> 
>>
>> weewx html page 
>> 
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c7fd8f73-fbdc-4a52-a3fc-c04e6df83889n%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.

Re: [weewx-user] Barometer data missing for CWOP

Think I figured it out.

Calculating the altimeter depends on pressure being calculated, but the
list of calculations had pressure in alphabetical order.
I moved pressure in the calculations section before altimeter and my
problem appears to be solved.


wxservices.py line 46

   [[Calculations]]
pressure = prefer_hardware
altimeter = prefer_hardware
appTemp = prefer_hardware
barometer = prefer_hardware
beaufort = prefer_hardware
cloudbase = prefer_hardware
dewpoint = prefer_hardware
ET = prefer_hardware
heatindex = prefer_hardware
humidex = prefer_hardware
inDewpoint = prefer_hardware
maxSolarRad = prefer_hardware
rainRate = prefer_hardware
windchill = prefer_hardware
windrun = prefer_hardware

On Mon, Jan 4, 2021 at 4:45 PM Tom Keffer  wrote:

> Everything looks normal to me. The log shows a post to CW8738:
>
> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: Published
> record 2021-01-04 13:50:00 PST (1609797000)
>
> After that, you did a keyboard interrupt, but the log stops before the
> next reporting cycle.
>
> Taking a look at findu, your packets are also showing up regularly:
> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>
> What are you seeing that causes concern?
>
> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:
>
>> A couple months ago I moved my weather station to run on a Raspberry pi,
>> and things have been running smoothly  with the exception of the data that
>> gets uploaded to CWOP.
>>
>> I upload data to cwop, wunderground, pwsweather, and my own weather
>> site.  The only one missing the data is cwop.
>>
>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage
>> vue weather station.
>>
>> I've attached below the cwop data, loop data, and syslog.
>>
>> Thanks in advance for any help.
>>
>>
>>
>> My raw data for cwop has a  b.  for the barometric data.
>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N
>> /11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>
>> Loop Data looks like:
>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321,
>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784,
>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01,
>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0,
>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0,
>> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3,
>> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0,
>> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0,
>> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0,
>> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate:
>> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0,
>> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset:
>> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir:
>> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10:
>> 28.0, yearET: 0.0, yearRain: 0.4
>>
>> Here's my syslog from the startup with debug = 1
>>
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing
>> weewx version 4.0.0b9
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python
>> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform
>> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is
>> 'en_US.UTF-8'
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using
>> configuration file /home/weewx/weewx.conf
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading
>> station type Vantage (weewx.drivers.vantage)
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert
>> target unit is 0x1
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The
>> following values will be calculated: altimeter=prefer_hardware,
>> appTemp=prefer_hardware, barometer=prefer_hardware,
>> beaufort=prefer_hardware, cloudbase=prefer_hardware,
>> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware,
>> humidex=prefer_hardware, inDewpoint=prefer_hardware,
>> maxSolarRad=prefer_hardware, pressure=prefer_hardware,
>> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The
>> following algorithms will be used for calculations: altimeter=aaASOS,
>> maxSolarRad=RS
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will
>> use data binding wx_binding
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Record
>> generation will be attempted in 'hardware'
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using archive
>> interval

[weewx-user] Re: Barometer Data Missing from CWOP updates

I think I figured it out.  I also have 2 threads on here about this and I 
apologize for that.  The other one I thought I had deleted, but I posted 
the solution there.

On Monday, January 4, 2021 at 7:21:39 PM UTC-8 gjr80 wrote:

> You are correct in that the missing altimeter is your problem, fix that 
> and CWOP will be fine. As long as WeeWX has one of the three pressures it 
> can calculate the other two. Davis stations provide barometer so WeeWX 
> should be calculating pressure and altimeter.
>
> Maybe the contents of your archive records will give some clues. Can you 
> try *running WeeWX directly 
> *. This will 
> display the loop packets (lines starting the LOOP:) and archive records 
> (lines starting with REC:)  on the console. Make a copy of the output and 
> post here, make sure you have a least one archive records and say a few 
> loop packets leading up to the archive record.
>
> Gary 
>
> On Tuesday, 5 January 2021 at 09:57:43 UTC+10 brent...@gmail.com wrote:
>
>> Also tried making sure that the barometer on the vantage vue console was 
>> properly calibrated.
>>
>> The value for altimeter continues to be 'None'.  This used to work when I 
>> ran it on a box I had ubuntu loaded on.
>>
>>
>>
>> On Monday, January 4, 2021 at 3:21:20 PM UTC-8 Brent Dowell wrote:
>>
>>> Well, I think I found something in restx.py.
>>>
>>> For CWOP, there is a line that says
>>> _baro = record.get('altimeter')
>>>
>>> Well, looking at my loop data there is no altimeter field in it.
>>> I do see in the startup that it says 
>>> weewx.wxservices: The following values will be calculated: 
>>> altimeter=prefer_hardware, appTemp=prefer_hardware, 
>>> barometer=prefer_hardware, beaufort=prefer_hardware, 
>>> cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
>>> heatindex=prefer_hardware, humidex=prefer_hardware, 
>>> inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
>>> pressure=prefer_hardware, rainRate=prefer_hardware, 
>>> windchill=prefer_hardware, windrun=prefer_hardware
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>>> following algorithms will be used for calculations: altimeter=aaASOS, 
>>> maxSolarRad=RS
>>>
>>> So, apparently, altimeter is something that is supposed to be 
>>> calculated, but for whatever reason, when code tries to grab it for CWOP, 
>>> it's set to 'None'.
>>>
>>> I've temporarily changed to code to point at barometer, but I'm guessing 
>>> that's the wrong solution and what I need to figure out is why the data for 
>>> altimeter is 'None'
>>>
>>> On Monday, January 4, 2021 at 2:21:10 PM UTC-8 Brent Dowell wrote:
>>>
 A couple months ago I moved my weather station to run on a Raspberry 
 pi, and things have been running smoothly  with the exception of the data 
 that gets uploaded to CWOP.

 I upload data to cwop, wunderground, pwsweather, and my own weather 
 site.  The only one missing the data is cwop.

 I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a 
 vantage vue weather station.

 I've attached below the cwop data, loop data, and syslog.

 Thanks in advance for any help.



 My raw data for cwop has a  b.  for the barometric data. 

 --
 {Manually 
 obfuscated}>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
   

 Loop Data looks like:

 --
 LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
 barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
 consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
 dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
 extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
 extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
 humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
 inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
 monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
 outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, 
 rainRate: 
 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
 soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
 28.0, yearET: 0.0, yearRain: 0.4


 Here's my syslog from the startup with debug = 1

 ---

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

You don’t to delete records.  There isn’t really much to the rain calculation.  
For all rain that occurred while WeeWX is up and running, the day_rain_total 
will increment, the driver will calculate the delta and add it to the loop 
record as ‘rain’.  For the discrepancy to occur, 0.09 inches would have had to 
happen while WeeWX wasn’t running.

Let’s try a day where WeeWX has been running, uninterrupted, since midnight.

> On Jan 4, 2021, at 7:27 PM, tim lambert  wrote:
> 
> 
> Thanks for the quick response John!
> 
> I am running your version of the IP100 for weewx 4 - version 0.5
> 
> I did restart the weewx today -- had some network issues, compliments of 
> Comcast.   However, I've witnessed discrepancies between the IP100 Console 
> and weewx for several days -- just finally had a chance to get some data 
> captures.   I may need to capture data again tomorrow (knowing it will be 
> raining buckets again).
> 
> At this point in time:
> 
>   IP100   
>  weewx
> Rainfall  0.06   
> 0.15
> Rain Rate  0.00   0.00
> 
> Can I truncate (delete all records) from the weewx.sdb (after backing up of 
> course) to start fresh, so that we have a solid baseline to evaluate?
> 
>> On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com wrote:
>> Station volts is not in the default map.  It wouldn’t be hard to add.
>> 
>> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped the 
>> version to 0.5 in my fork).  I’m presuming you are running it.
>> 
>> Although I’m not currently running the driver, I did run it for almost two 
>> years and rain values ALWAYS agreed with my WeeWX instances running the 
>> CC3000 driver and talking to the same RainWise weather station.
>> 
>> day_rain_total is used to calculate rain.  It is not, in itself saved to the 
>> database.
>> 
>> I have not downloaded your files.  You’ll have to tell me if the ip100 
>> console does not agree with the console for today’s rain and, if not, what 
>> two values you are seeing.  Please list them.
>> 
>> If you do have a discrepancy for today’s rain, please state if you restarted 
>> weewx today (or if it restarted on its own today).  That would be a way to 
>> lose rainfall.
>> 
>> 
 On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
 
>>> 
>> 
>>> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the IP-100 
>>> v0.5 extension.  It appears the IP-100 Console data does not match the data 
>>> presented via weewx (using the out-of-box index.html, which is using the 
>>> SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've shared screen 
>>> shots of both the IP-100 Console and the weewx html
>>> 
>>> Based on some investigation, the log file (attached) indicates the data 
>>> which is showing on the IP-100 Console is being captured correctly,   
>>> However, looking at the archive table (attached) in the weewx.sdb, it does 
>>> not appear the data elements are being posted to the archive table 
>>> correctly - specifically day_rain_total (log) vs rain (archive table) and 
>>> rain (log) vs rainRate (archive table).
>>> 
>>> Additionally, the station_volts (log file) are not being posted to the 
>>> archive table.
>>> 
>>> I'm new to this world, but do have some technical bones -- any guidance on 
>>> what actions need to be taken to address the discrepancy would be 
>>> appreciated.
>>> 
>>> Thanks in advance!
>>> 
>>> Archive Table
>>> 
>>> Syslog
>>> 
>>> IP-100 Console
>>> 
>>> weewx html page
>> 
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/c7fd8f73-fbdc-4a52-a3fc-c04e6df83889n%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/633dc989-4be4-4a67-9645-b818367b25b6n%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/C8A3FCC5-20C9-4859-9061-2EE68DF20AFA%40johnkline.com.

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

2021-01-04 Thread tim lambert

Thanks for the quick response John!

I am running your version of the IP100 for weewx 4 - version 0.5

I did restart the weewx today -- had some network issues, compliments of 
Comcast.   However, I've witnessed discrepancies between the IP100 Console 
and weewx for several days -- just finally had a chance to get some data 
captures.   I may need to capture data again tomorrow (knowing it will be 
raining buckets again).

At this point in time:

  
IP100weewx
Rainfall  
0.06   0.15
Rain Rate  0.00   
0.00

Can I truncate (delete all records) from the weewx.sdb (after backing up of 
course) to start fresh, so that we have a solid baseline to evaluate?

On Monday, January 4, 2021 at 7:06:51 PM UTC-8 jo...@johnkline.com wrote:

> Station volts is not in the default map.  It wouldn’t be hard to add.
>
> I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped 
> the version to 0.5 in my fork).  I’m presuming you are running it.
>
> Although I’m not currently running the driver, I did run it for almost two 
> years and rain values ALWAYS agreed with my WeeWX instances running the 
> CC3000 driver and talking to the same RainWise weather station.
>
> day_rain_total is used to calculate rain.  It is not, in itself saved to 
> the database.
>
> I have not downloaded your files.  You’ll have to tell me if the ip100 
> console does not agree with the console for today’s rain and, if not, what 
> two values you are seeing.  Please list them.
>
> If you do have a discrepancy for today’s rain, please state if you 
> restarted weewx today (or if it restarted on its own today).  That would be 
> a way to lose rainfall.
>
>
> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
>
> 
>
> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the IP-100 
> v0.5 extension.  It appears the IP-100 Console data does not match the data 
> presented via weewx (using the out-of-box index.html, which is using the 
> SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've shared screen 
> shots of both the IP-100 Console and the weewx html
>
> Based on some investigation, the log file (attached) indicates the data 
> which is showing on the IP-100 Console is being captured correctly,   
> However, looking at the archive table (attached) in the weewx.sdb, it does 
> not appear the data elements are being posted to the archive table 
> correctly - specifically day_rain_total (log) vs rain (archive table) and 
> rain (log) vs rainRate (archive table).
>
> Additionally, the station_volts (log file) are not being posted to the 
> archive table.
>
> I'm new to this world, but do have some technical bones -- any guidance on 
> what actions need to be taken to address the discrepancy would be 
> appreciated.
>
> Thanks in advance!
>
> Archive Table 
> 
>
> Syslog 
>
> IP-100 Console 
> 
>
> weewx html page 
> 
>
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/c7fd8f73-fbdc-4a52-a3fc-c04e6df83889n%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/633dc989-4be4-4a67-9645-b818367b25b6n%40googlegroups.com.

[weewx-user] Re: Battery Status for TE923

2021-01-04 Thread lecoqacr...@gmail.com

Did the attached file get removed by the google groups filters? or did you 
not attach? Thanks

On Sunday, January 3, 2021 at 1:10:18 PM UTC-6 stelli...@gmail.com wrote:

> Solved it on my own. If others are interested, here is what I did:
>
>1. Copying the sensors.inc file from the Seasons skin to the root 
>folder of the Belchertown skin
>2. Modified the file to change from table to list style
>3. Removed sevction headings of the file
>4. included the sensors.inc via *#include "sensors.inc"*
>5. Adding the information to the Belchertown style.css file to show OK 
>in green and LOW in red
>
> The modified sensors.inc file is attached. The result can be seen on my 
> about site .
>
> Hope that this can be helpful if others want to to adjust this...
>

-- 
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/1d4dba7a-754f-4106-9b00-eeac3d754ee1n%40googlegroups.com.

Re: [weewx-user] Barometer data missing for CWOP

Think I figured it out.

Calculating the altimeter depends on pressure being calculated, but the 
list of calculations had pressure in alphabetical order.
I moved pressure in the calculations section before altimeter and my 
problem appears to be solved.


wxservices.py line 46

   [[Calculations]]
pressure = prefer_hardware
altimeter = prefer_hardware
appTemp = prefer_hardware
barometer = prefer_hardware
beaufort = prefer_hardware
cloudbase = prefer_hardware
dewpoint = prefer_hardware
ET = prefer_hardware
heatindex = prefer_hardware
humidex = prefer_hardware
inDewpoint = prefer_hardware
maxSolarRad = prefer_hardware
rainRate = prefer_hardware
windchill = prefer_hardware
windrun = prefer_hardware

On Monday, January 4, 2021 at 7:07:03 PM UTC-8 Brent Dowell wrote:

> I'm thinking it has something to do with wxservices.py.
>
> At around line 558, there's this code for calculating 'altimeter'. I do 
> not have a value for 'pressure' in the record.  I have 'barometer', which 
> I'm assuming is '
> Sensor Pressure' from reading some of the comments in the python code.
>
>def altimeter(self, record):
> """Calculate the observation type 'altimeter'."""
>
> log.info("VANTAGE DEBUG: calc altimeter: %s","altimeter")
> log.info("VANTAGE DEBUG: calc altimeter record: %s",record)
> 
> if 'pressure' not in record:
> raise weewx.CannotCalculate('altimeter')
>
> And as I keep search, I see that it can calculate pressure from what it 
> has, but that is not in the record. So seems like it shoudl be calculating 
> and adding pressure to the record before the altimeter, but...
>
> Getting a bit out of my depth here.  I can trace through the code a bit on 
> the pi, but getting a bit lost on the details of the code.
>
>
> On Monday, January 4, 2021 at 6:02:40 PM UTC-8 peterq...@gmail.com wrote:
>
>> That b makes me think it's a string/byte python2 vs python 3 issue. I 
>> have no evidence to back that up...
>>
>> On Mon, Jan 4, 2021 at 4:57 PM Brent Dowell  wrote:
>>
>>> I apologize for the duplicate messages.  This was the first one I 
>>> posted, and tried to delete earlier.  There's another post I made that has 
>>> more detailed info.
>>>
>>> On Monday, January 4, 2021 at 4:56:28 PM UTC-8 Brent Dowell wrote:
>>>
 It's not uploading the barometric pressure.


 CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000
 *b.*h46.weewx-4.0.0b9-Vantage  

 Looking at the code, it's supposed to calculate the 'altimeter' value 
 from 'barometer'.  However it's not doing that.   Altimeter is set to 
 None, 
 so when it uploads to CWOP, it skipps the barometer reading, with 'b.'.

 I did experiment around with restx.py and set that to just use the 
 barometer if altimeter is none.

 Just not sure why it's not calculating the altimeter.



 On Monday, January 4, 2021 at 4:46:01 PM UTC-8 tke...@gmail.com wrote:

> Everything looks normal to me. The log shows a post to CW8738:
>
> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
> Published record 2021-01-04 13:50:00 PST (1609797000)
>
> After that, you did a keyboard interrupt, but the log stops before the 
> next reporting cycle.
>
> Taking a look at findu, your packets are also showing up regularly: 
> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>
> What are you seeing that causes concern?
>
> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  
> wrote:
>
>> A couple months ago I moved my weather station to run on a Raspberry 
>> pi, and things have been running smoothly  with the exception of the 
>> data 
>> that gets uploaded to CWOP.
>>
>> I upload data to cwop, wunderground, pwsweather, and my own weather 
>> site.  The only one missing the data is cwop.
>>
>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a 
>> vantage vue weather station.
>>
>> I've attached below the cwop data, loop data, and syslog.
>>
>> Thanks in advance for any help.
>>
>>
>>
>> My raw data for cwop has a  b.  for the barometric data. 
>>
>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>   
>>
>> Loop Data looks like:
>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 
>> 0.01, 
>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>> extraAlarm8: 0, forecastIcon: 3, forecastRule:

[weewx-user] Re: Barometer Data Missing from CWOP updates

You are correct in that the missing altimeter is your problem, fix that and 
CWOP will be fine. As long as WeeWX has one of the three pressures it can 
calculate the other two. Davis stations provide barometer so WeeWX should 
be calculating pressure and altimeter.

Maybe the contents of your archive records will give some clues. Can you 
try *running WeeWX directly 
*. This will display 
the loop packets (lines starting the LOOP:) and archive records (lines 
starting with REC:)  on the console. Make a copy of the output and post 
here, make sure you have a least one archive records and say a few loop 
packets leading up to the archive record.

Gary 

On Tuesday, 5 January 2021 at 09:57:43 UTC+10 brent...@gmail.com wrote:

> Also tried making sure that the barometer on the vantage vue console was 
> properly calibrated.
>
> The value for altimeter continues to be 'None'.  This used to work when I 
> ran it on a box I had ubuntu loaded on.
>
>
>
> On Monday, January 4, 2021 at 3:21:20 PM UTC-8 Brent Dowell wrote:
>
>> Well, I think I found something in restx.py.
>>
>> For CWOP, there is a line that says
>> _baro = record.get('altimeter')
>>
>> Well, looking at my loop data there is no altimeter field in it.
>> I do see in the startup that it says 
>> weewx.wxservices: The following values will be calculated: 
>> altimeter=prefer_hardware, appTemp=prefer_hardware, 
>> barometer=prefer_hardware, beaufort=prefer_hardware, 
>> cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
>> heatindex=prefer_hardware, humidex=prefer_hardware, 
>> inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
>> pressure=prefer_hardware, rainRate=prefer_hardware, 
>> windchill=prefer_hardware, windrun=prefer_hardware
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>> following algorithms will be used for calculations: altimeter=aaASOS, 
>> maxSolarRad=RS
>>
>> So, apparently, altimeter is something that is supposed to be calculated, 
>> but for whatever reason, when code tries to grab it for CWOP, it's set to 
>> 'None'.
>>
>> I've temporarily changed to code to point at barometer, but I'm guessing 
>> that's the wrong solution and what I need to figure out is why the data for 
>> altimeter is 'None'
>>
>> On Monday, January 4, 2021 at 2:21:10 PM UTC-8 Brent Dowell wrote:
>>
>>> A couple months ago I moved my weather station to run on a Raspberry pi, 
>>> and things have been running smoothly  with the exception of the data that 
>>> gets uploaded to CWOP.
>>>
>>> I upload data to cwop, wunderground, pwsweather, and my own weather 
>>> site.  The only one missing the data is cwop.
>>>
>>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
>>> vue weather station.
>>>
>>> I've attached below the cwop data, loop data, and syslog.
>>>
>>> Thanks in advance for any help.
>>>
>>>
>>>
>>> My raw data for cwop has a  b.  for the barometric data. 
>>>
>>> --
>>> {Manually 
>>> obfuscated}>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>>   
>>>
>>> Loop Data looks like:
>>>
>>> --
>>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
>>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
>>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
>>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>>> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
>>> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
>>> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
>>> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
>>> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
>>> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
>>> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
>>> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
>>> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
>>> 28.0, yearET: 0.0, yearRain: 0.4
>>>
>>>
>>> Here's my syslog from the startup with debug = 1
>>>
>>> --
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
>>> weewx version 4.0.0b9
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
>>> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
>>> Linux-4.19.75-v7l+-armv7l-wi

Re: [weewx-user] Barometer data missing for CWOP

I'm thinking it has something to do with wxservices.py.

At around line 558, there's this code for calculating 'altimeter'. I do not 
have a value for 'pressure' in the record.  I have 'barometer', which I'm 
assuming is '
Sensor Pressure' from reading some of the comments in the python code.

   def altimeter(self, record):
"""Calculate the observation type 'altimeter'."""

log.info("VANTAGE DEBUG: calc altimeter: %s","altimeter")
log.info("VANTAGE DEBUG: calc altimeter record: %s",record)

if 'pressure' not in record:
raise weewx.CannotCalculate('altimeter')

And as I keep search, I see that it can calculate pressure from what it 
has, but that is not in the record. So seems like it shoudl be calculating 
and adding pressure to the record before the altimeter, but...

Getting a bit out of my depth here.  I can trace through the code a bit on 
the pi, but getting a bit lost on the details of the code.


On Monday, January 4, 2021 at 6:02:40 PM UTC-8 peterq...@gmail.com wrote:

> That b makes me think it's a string/byte python2 vs python 3 issue. I have 
> no evidence to back that up...
>
> On Mon, Jan 4, 2021 at 4:57 PM Brent Dowell  wrote:
>
>> I apologize for the duplicate messages.  This was the first one I posted, 
>> and tried to delete earlier.  There's another post I made that has more 
>> detailed info.
>>
>> On Monday, January 4, 2021 at 4:56:28 PM UTC-8 Brent Dowell wrote:
>>
>>> It's not uploading the barometric pressure.
>>>
>>>
>>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000
>>> *b.*h46.weewx-4.0.0b9-Vantage  
>>>
>>> Looking at the code, it's supposed to calculate the 'altimeter' value 
>>> from 'barometer'.  However it's not doing that.   Altimeter is set to None, 
>>> so when it uploads to CWOP, it skipps the barometer reading, with 'b.'.
>>>
>>> I did experiment around with restx.py and set that to just use the 
>>> barometer if altimeter is none.
>>>
>>> Just not sure why it's not calculating the altimeter.
>>>
>>>
>>>
>>> On Monday, January 4, 2021 at 4:46:01 PM UTC-8 tke...@gmail.com wrote:
>>>
 Everything looks normal to me. The log shows a post to CW8738:

 Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
 Published record 2021-01-04 13:50:00 PST (1609797000)

 After that, you did a keyboard interrupt, but the log stops before the 
 next reporting cycle.

 Taking a look at findu, your packets are also showing up regularly: 
 http://www.findu.com/cgi-bin/raw.cgi?call=CW8738

 What are you seeing that causes concern?

 On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:

> A couple months ago I moved my weather station to run on a Raspberry 
> pi, and things have been running smoothly  with the exception of the data 
> that gets uploaded to CWOP.
>
> I upload data to cwop, wunderground, pwsweather, and my own weather 
> site.  The only one missing the data is cwop.
>
> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a 
> vantage vue weather station.
>
> I've attached below the cwop data, loop data, and syslog.
>
> Thanks in advance for any help.
>
>
>
> My raw data for cwop has a  b.  for the barometric data. 
>
> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>   
>
> Loop Data looks like:
> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 
> 0.01, 
> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 
> 0, 
> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, 
> rainRate: 
> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
> 28.0, yearET: 0.0, yearRain: 0.4
>
> Here's my syslog from the startup with debug = 1
>
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: 
> Initializing weewx version 4.0.0b9
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
> Python 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
> Jan  4 13:48:41 rasp

Re: [weewx-user] Rainwise IP-100 Data Inconsistency

Station volts is not in the default map.  It wouldn’t be hard to add.

I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped the 
version to 0.5 in my fork).  I’m presuming you are running it.

Although I’m not currently running the driver, I did run it for almost two 
years and rain values ALWAYS agreed with my WeeWX instances running the CC3000 
driver and talking to the same RainWise weather station.

day_rain_total is used to calculate rain.  It is not, in itself saved to the 
database.

I have not downloaded your files.  You’ll have to tell me if the ip100 console 
does not agree with the console for today’s rain and, if not, what two values 
you are seeing.  Please list them.

If you do have a discrepancy for today’s rain, please state if you restarted 
weewx today (or if it restarted on its own today).  That would be a way to lose 
rainfall.

> On Jan 4, 2021, at 6:33 PM, tim lambert  wrote:
> 
> I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the IP-100 
> v0.5 extension.  It appears the IP-100 Console data does not match the data 
> presented via weewx (using the out-of-box index.html, which is using the 
> SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've shared screen 
> shots of both the IP-100 Console and the weewx html
> 
> Based on some investigation, the log file (attached) indicates the data which 
> is showing on the IP-100 Console is being captured correctly,   However, 
> looking at the archive table (attached) in the weewx.sdb, it does not appear 
> the data elements are being posted to the archive table correctly - 
> specifically day_rain_total (log) vs rain (archive table) and rain (log) vs 
> rainRate (archive table).
> 
> Additionally, the station_volts (log file) are not being posted to the 
> archive table.
> 
> I'm new to this world, but do have some technical bones -- any guidance on 
> what actions need to be taken to address the discrepancy would be appreciated.
> 
> Thanks in advance!
> 
> Archive Table
> 
> Syslog
> 
> IP-100 Console
> 
> weewx html page
> -- 
> 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/c7fd8f73-fbdc-4a52-a3fc-c04e6df83889n%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/E80B20EA-091A-46A8-9095-3090DCBCA512%40johnkline.com.

[weewx-user] Just want to verify the location of the Pressure Sensor in the Accurite 02032C

2021-01-04 Thread chris

I want to make sure the pressure sensor for the Accurite 02032C is in 
the indoor console and not in the 5-1 sensor that is placed on a pole 
outdoors.


Thanks,

Chris Maness

--
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/86943363-98eb-25db-d133-92828a837d0d%40gmail.com.


OpenPGP_0x55BE65AD1B41D696.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

[weewx-user] Rainwise IP-100 Data Inconsistency

2021-01-04 Thread tim lambert

I recently stood up a Raspberry Pi 4 running weewx  4.2.0 with the IP-100 
v0.5 extension.  It appears the IP-100 Console data does not match the data 
presented via weewx (using the out-of-box index.html, which is using the 
SeasonsSkin) -- particularly, the Rain and Rain Rate.   I've shared screen 
shots of both the IP-100 Console and the weewx html

Based on some investigation, the log file (attached) indicates the data 
which is showing on the IP-100 Console is being captured correctly,   
However, looking at the archive table (attached) in the weewx.sdb, it does 
not appear the data elements are being posted to the archive table 
correctly - specifically day_rain_total (log) vs rain (archive table) and 
rain (log) vs rainRate (archive table).

Additionally, the station_volts (log file) are not being posted to the 
archive table.

I'm new to this world, but do have some technical bones -- any guidance on 
what actions need to be taken to address the discrepancy would be 
appreciated.

Thanks in advance!

Archive Table 

Syslog 

IP-100 Console 


weewx html page 


-- 
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/c7fd8f73-fbdc-4a52-a3fc-c04e6df83889n%40googlegroups.com.

Re: [weewx-user] Barometer data missing for CWOP

That's the string that restx.py is setting it to if the altimeter value is 
None before it feeds it to CWOP.

I had been using some VERY old code prior to updating to run on the 
raspberry pi, so I'm not surprised there is something broken.

Just debugging my way through the python till I figure out some more 
details.  Right now I'm leaning towards something in uwxutils.py.

Just to be clear, I'm assuming it's something in my configuration or 
implementation that is causing this, not necessarily any bugs in weewx.






On Monday, January 4, 2021 at 6:02:40 PM UTC-8 peterq...@gmail.com wrote:

> That b makes me think it's a string/byte python2 vs python 3 issue. I have 
> no evidence to back that up...
>
> On Mon, Jan 4, 2021 at 4:57 PM Brent Dowell  wrote:
>
>> I apologize for the duplicate messages.  This was the first one I posted, 
>> and tried to delete earlier.  There's another post I made that has more 
>> detailed info.
>>
>> On Monday, January 4, 2021 at 4:56:28 PM UTC-8 Brent Dowell wrote:
>>
>>> It's not uploading the barometric pressure.
>>>
>>>
>>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000
>>> *b.*h46.weewx-4.0.0b9-Vantage  
>>>
>>> Looking at the code, it's supposed to calculate the 'altimeter' value 
>>> from 'barometer'.  However it's not doing that.   Altimeter is set to None, 
>>> so when it uploads to CWOP, it skipps the barometer reading, with 'b.'.
>>>
>>> I did experiment around with restx.py and set that to just use the 
>>> barometer if altimeter is none.
>>>
>>> Just not sure why it's not calculating the altimeter.
>>>
>>>
>>>
>>> On Monday, January 4, 2021 at 4:46:01 PM UTC-8 tke...@gmail.com wrote:
>>>
 Everything looks normal to me. The log shows a post to CW8738:

 Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
 Published record 2021-01-04 13:50:00 PST (1609797000)

 After that, you did a keyboard interrupt, but the log stops before the 
 next reporting cycle.

 Taking a look at findu, your packets are also showing up regularly: 
 http://www.findu.com/cgi-bin/raw.cgi?call=CW8738

 What are you seeing that causes concern?

 On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:

> A couple months ago I moved my weather station to run on a Raspberry 
> pi, and things have been running smoothly  with the exception of the data 
> that gets uploaded to CWOP.
>
> I upload data to cwop, wunderground, pwsweather, and my own weather 
> site.  The only one missing the data is cwop.
>
> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a 
> vantage vue weather station.
>
> I've attached below the cwop data, loop data, and syslog.
>
> Thanks in advance for any help.
>
>
>
> My raw data for cwop has a  b.  for the barometric data. 
>
> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>   
>
> Loop Data looks like:
> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 
> 0.01, 
> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 
> 0, 
> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, 
> rainRate: 
> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
> 28.0, yearET: 0.0, yearRain: 0.4
>
> Here's my syslog from the startup with debug = 1
>
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: 
> Initializing weewx version 4.0.0b9
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
> Python 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
> 'en_US.UTF-8'
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
> configuration file /home/weewx/weewx.conf
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)

Re: [weewx-user] Barometer data missing for CWOP

2021-01-04 Thread p q

That b makes me think it's a string/byte python2 vs python 3 issue. I have
no evidence to back that up...

On Mon, Jan 4, 2021 at 4:57 PM Brent Dowell  wrote:

> I apologize for the duplicate messages.  This was the first one I posted,
> and tried to delete earlier.  There's another post I made that has more
> detailed info.
>
> On Monday, January 4, 2021 at 4:56:28 PM UTC-8 Brent Dowell wrote:
>
>> It's not uploading the barometric pressure.
>>
>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N
>> /11938.56W_315/009g014t050r000p000P000*b.*h46.weewx-4.0.0b9-Vantage
>>
>> Looking at the code, it's supposed to calculate the 'altimeter' value
>> from 'barometer'.  However it's not doing that.   Altimeter is set to None,
>> so when it uploads to CWOP, it skipps the barometer reading, with 'b.'.
>>
>> I did experiment around with restx.py and set that to just use the
>> barometer if altimeter is none.
>>
>> Just not sure why it's not calculating the altimeter.
>>
>>
>>
>> On Monday, January 4, 2021 at 4:46:01 PM UTC-8 tke...@gmail.com wrote:
>>
>>> Everything looks normal to me. The log shows a post to CW8738:
>>>
>>> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP:
>>> Published record 2021-01-04 13:50:00 PST (1609797000)
>>>
>>> After that, you did a keyboard interrupt, but the log stops before the
>>> next reporting cycle.
>>>
>>> Taking a look at findu, your packets are also showing up regularly:
>>> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>>>
>>> What are you seeing that causes concern?
>>>
>>> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:
>>>
 A couple months ago I moved my weather station to run on a Raspberry
 pi, and things have been running smoothly  with the exception of the data
 that gets uploaded to CWOP.

 I upload data to cwop, wunderground, pwsweather, and my own weather
 site.  The only one missing the data is cwop.

 I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a
 vantage vue weather station.

 I've attached below the cwop data, loop data, and syslog.

 Thanks in advance for any help.



 My raw data for cwop has a  b.  for the barometric data.
 CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N
 /11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage

 Loop Data looks like:
 LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321,
 barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784,
 consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01,
 dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0,
 extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0,
 extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3,
 humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0,
 inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0,
 monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0,
 outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate:
 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0,
 soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset:
 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir:
 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10:
 28.0, yearET: 0.0, yearRain: 0.4

 Here's my syslog from the startup with debug = 1

 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine:
 Initializing weewx version 4.0.0b9
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using
 Python 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform
 Linux-4.19.75-v7l+-armv7l-with-debian-10.1
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is
 'en_US.UTF-8'
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using
 configuration file /home/weewx/weewx.conf
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading
 station type Vantage (weewx.drivers.vantage)
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert
 target unit is 0x1
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The
 following values will be calculated: altimeter=prefer_hardware,
 appTemp=prefer_hardware, barometer=prefer_hardware,
 beaufort=prefer_hardware, cloudbase=prefer_hardware,
 dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware,
 humidex=prefer_hardware, inDewpoint=prefer_hardware,
 maxSolarRad=prefer_hardware, pressure=prefer_hardware,
 rainRate=prefer_hardware, windchill=prefer_hardware, 
 windrun=prefer_hardware
 Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The
 following algorithms will be used for calculations

Re: [weewx-user] Barometer data missing for CWOP

I apologize for the duplicate messages.  This was the first one I posted, 
and tried to delete earlier.  There's another post I made that has more 
detailed info.

On Monday, January 4, 2021 at 4:56:28 PM UTC-8 Brent Dowell wrote:

> It's not uploading the barometric pressure.
>
>
> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000
> *b.*h46.weewx-4.0.0b9-Vantage  
>
> Looking at the code, it's supposed to calculate the 'altimeter' value from 
> 'barometer'.  However it's not doing that.   Altimeter is set to None, so 
> when it uploads to CWOP, it skipps the barometer reading, with 'b.'.
>
> I did experiment around with restx.py and set that to just use the 
> barometer if altimeter is none.
>
> Just not sure why it's not calculating the altimeter.
>
>
>
> On Monday, January 4, 2021 at 4:46:01 PM UTC-8 tke...@gmail.com wrote:
>
>> Everything looks normal to me. The log shows a post to CW8738:
>>
>> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: 
>> Published record 2021-01-04 13:50:00 PST (1609797000)
>>
>> After that, you did a keyboard interrupt, but the log stops before the 
>> next reporting cycle.
>>
>> Taking a look at findu, your packets are also showing up regularly: 
>> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>>
>> What are you seeing that causes concern?
>>
>> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:
>>
>>> A couple months ago I moved my weather station to run on a Raspberry pi, 
>>> and things have been running smoothly  with the exception of the data that 
>>> gets uploaded to CWOP.
>>>
>>> I upload data to cwop, wunderground, pwsweather, and my own weather 
>>> site.  The only one missing the data is cwop.
>>>
>>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
>>> vue weather station.
>>>
>>> I've attached below the cwop data, loop data, and syslog.
>>>
>>> Thanks in advance for any help.
>>>
>>>
>>>
>>> My raw data for cwop has a  b.  for the barometric data. 
>>>
>>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>>   
>>>
>>> Loop Data looks like:
>>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
>>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
>>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
>>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>>> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
>>> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
>>> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
>>> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
>>> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
>>> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
>>> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
>>> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
>>> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
>>> 28.0, yearET: 0.0, yearRain: 0.4
>>>
>>> Here's my syslog from the startup with debug = 1
>>>
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
>>> weewx version 4.0.0b9
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
>>> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
>>> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
>>> 'en_US.UTF-8'
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
>>> configuration file /home/weewx/weewx.conf
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
>>> station type Vantage (weewx.drivers.vantage)
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
>>> target unit is 0x1
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>>> following values will be calculated: altimeter=prefer_hardware, 
>>> appTemp=prefer_hardware, barometer=prefer_hardware, 
>>> beaufort=prefer_hardware, cloudbase=prefer_hardware, 
>>> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
>>> humidex=prefer_hardware, inDewpoint=prefer_hardware, 
>>> maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
>>> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>>> following algorithms will be used for calculations: altimeter=aaASOS, 
>>> maxSolarRad=RS
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will 
>>> use data binding wx_binding
>>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Record

Re: [weewx-user] Barometer data missing for CWOP

It's not uploading the barometric pressure.

CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000
*b.*h46.weewx-4.0.0b9-Vantage  

Looking at the code, it's supposed to calculate the 'altimeter' value from 
'barometer'.  However it's not doing that.   Altimeter is set to None, so 
when it uploads to CWOP, it skipps the barometer reading, with 'b.'.

I did experiment around with restx.py and set that to just use the 
barometer if altimeter is none.

Just not sure why it's not calculating the altimeter.



On Monday, January 4, 2021 at 4:46:01 PM UTC-8 tke...@gmail.com wrote:

> Everything looks normal to me. The log shows a post to CW8738:
>
> Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: Published 
> record 2021-01-04 13:50:00 PST (1609797000)
>
> After that, you did a keyboard interrupt, but the log stops before the 
> next reporting cycle.
>
> Taking a look at findu, your packets are also showing up regularly: 
> http://www.findu.com/cgi-bin/raw.cgi?call=CW8738
>
> What are you seeing that causes concern?
>
> On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:
>
>> A couple months ago I moved my weather station to run on a Raspberry pi, 
>> and things have been running smoothly  with the exception of the data that 
>> gets uploaded to CWOP.
>>
>> I upload data to cwop, wunderground, pwsweather, and my own weather 
>> site.  The only one missing the data is cwop.
>>
>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
>> vue weather station.
>>
>> I've attached below the cwop data, loop data, and syslog.
>>
>> Thanks in advance for any help.
>>
>>
>>
>> My raw data for cwop has a  b.  for the barometric data. 
>>
>> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>   
>>
>> Loop Data looks like:
>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
>> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
>> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
>> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
>> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
>> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
>> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
>> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
>> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
>> 28.0, yearET: 0.0, yearRain: 0.4
>>
>> Here's my syslog from the startup with debug = 1
>>
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
>> weewx version 4.0.0b9
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
>> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
>> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
>> 'en_US.UTF-8'
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
>> configuration file /home/weewx/weewx.conf
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>> following values will be calculated: altimeter=prefer_hardware, 
>> appTemp=prefer_hardware, barometer=prefer_hardware, 
>> beaufort=prefer_hardware, cloudbase=prefer_hardware, 
>> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
>> humidex=prefer_hardware, inDewpoint=prefer_hardware, 
>> maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
>> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>> following algorithms will be used for calculations: altimeter=aaASOS, 
>> maxSolarRad=RS
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will 
>> use data binding wx_binding
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using archive 
>> interval of 300 seconds (specified by hardware)
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: 
>> StationRegistry: Station will not be registered: no station_url specified.
>> Jan  4 13:48:41 raspberr

Re: [weewx-user] Barometer data missing for CWOP

2021-01-04 Thread Tom Keffer

Everything looks normal to me. The log shows a post to CW8738:

Jan  4 13:50:18 raspberrypi weewx[11987] INFO weewx.restx: CWOP: Published
record 2021-01-04 13:50:00 PST (1609797000)

After that, you did a keyboard interrupt, but the log stops before the next
reporting cycle.

Taking a look at findu, your packets are also showing up regularly:
http://www.findu.com/cgi-bin/raw.cgi?call=CW8738

What are you seeing that causes concern?

On Mon, Jan 4, 2021 at 1:54 PM Brent Dowell  wrote:

> A couple months ago I moved my weather station to run on a Raspberry pi,
> and things have been running smoothly  with the exception of the data that
> gets uploaded to CWOP.
>
> I upload data to cwop, wunderground, pwsweather, and my own weather site.
> The only one missing the data is cwop.
>
> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage
> vue weather station.
>
> I've attached below the cwop data, loop data, and syslog.
>
> Thanks in advance for any help.
>
>
>
> My raw data for cwop has a  b.  for the barometric data.
> CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N
> /11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>
> Loop Data looks like:
> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321,
> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784,
> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01,
> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0,
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0,
> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3,
> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0,
> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0,
> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0,
> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate:
> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0,
> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset:
> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir:
> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10:
> 28.0, yearET: 0.0, yearRain: 0.4
>
> Here's my syslog from the startup with debug = 1
>
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing
> weewx version 4.0.0b9
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python
> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform
> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is
> 'en_US.UTF-8'
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using
> configuration file /home/weewx/weewx.conf
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading
> station type Vantage (weewx.drivers.vantage)
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert
> target unit is 0x1
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The
> following values will be calculated: altimeter=prefer_hardware,
> appTemp=prefer_hardware, barometer=prefer_hardware,
> beaufort=prefer_hardware, cloudbase=prefer_hardware,
> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware,
> humidex=prefer_hardware, inDewpoint=prefer_hardware,
> maxSolarRad=prefer_hardware, pressure=prefer_hardware,
> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The
> following algorithms will be used for calculations: altimeter=aaASOS,
> maxSolarRad=RS
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will
> use data binding wx_binding
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Record
> generation will be attempted in 'hardware'
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using archive
> interval of 300 seconds (specified by hardware)
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx:
> StationRegistry: Station will not be registered: no station_url specified.
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx:
> Wunderground-PWS: Data for station KNVRENO31 will be posted
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: PWSWeather:
> Data for station KNVRENO31 will be posted
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: CWOP: Data for
> station CW8738 will be posted
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: WOW: Posting
> not enabled.
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: AWEKAS: Posting
> not enabled.
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Starting up
> weewx version 4.0.0b9
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Clock error is
> 0.21 seconds (positive is fast)
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.e

[weewx-user] Re: Barometer Data Missing from CWOP updates

Also tried making sure that the barometer on the vantage vue console was 
properly calibrated.

The value for altimeter continues to be 'None'.  This used to work when I 
ran it on a box I had ubuntu loaded on.



On Monday, January 4, 2021 at 3:21:20 PM UTC-8 Brent Dowell wrote:

> Well, I think I found something in restx.py.
>
> For CWOP, there is a line that says
> _baro = record.get('altimeter')
>
> Well, looking at my loop data there is no altimeter field in it.
> I do see in the startup that it says 
> weewx.wxservices: The following values will be calculated: 
> altimeter=prefer_hardware, appTemp=prefer_hardware, 
> barometer=prefer_hardware, beaufort=prefer_hardware, 
> cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
> heatindex=prefer_hardware, humidex=prefer_hardware, 
> inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
> pressure=prefer_hardware, rainRate=prefer_hardware, 
> windchill=prefer_hardware, windrun=prefer_hardware
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
> following algorithms will be used for calculations: altimeter=aaASOS, 
> maxSolarRad=RS
>
> So, apparently, altimeter is something that is supposed to be calculated, 
> but for whatever reason, when code tries to grab it for CWOP, it's set to 
> 'None'.
>
> I've temporarily changed to code to point at barometer, but I'm guessing 
> that's the wrong solution and what I need to figure out is why the data for 
> altimeter is 'None'
>
> On Monday, January 4, 2021 at 2:21:10 PM UTC-8 Brent Dowell wrote:
>
>> A couple months ago I moved my weather station to run on a Raspberry pi, 
>> and things have been running smoothly  with the exception of the data that 
>> gets uploaded to CWOP.
>>
>> I upload data to cwop, wunderground, pwsweather, and my own weather 
>> site.  The only one missing the data is cwop.
>>
>> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
>> vue weather station.
>>
>> I've attached below the cwop data, loop data, and syslog.
>>
>> Thanks in advance for any help.
>>
>>
>>
>> My raw data for cwop has a  b.  for the barometric data. 
>>
>> --
>> {Manually 
>> obfuscated}>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>>   
>>
>> Loop Data looks like:
>>
>> --
>> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
>> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
>> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
>> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
>> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
>> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
>> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
>> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
>> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
>> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
>> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
>> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
>> 28.0, yearET: 0.0, yearRain: 0.4
>>
>>
>> Here's my syslog from the startup with debug = 1
>>
>> --
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
>> weewx version 4.0.0b9
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
>> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
>> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
>> 'en_US.UTF-8'
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
>> configuration file /home/weewx/weewx.conf
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
>> following values will be calculated: altimeter=prefer_hardware, 
>> appTemp=prefer_hardware, barometer=prefer_hardware, 
>> beaufort=prefer_hardware, cloudbase=prefer_hardware, 
>> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
>> humidex=prefer_hardware, inDewpoint=prefer_hardware, 
>> maxSolarRad=prefer_hardware, pressure=prefer_hardware,

[weewx-user] Version 4.3.0 released

2021-01-04 Thread Tom Keffer

This release fixes a bug in V4.2 that caused average values to be
calculated incorrectly if the archive interval changes.

4.3.0 01/04/2020

Version 4.2.0 had a bug, which caused the sums in the daily summary to be
incorrectly calculated. This version includes a patch to fix the problem. It
runs once at startup. Fixes issue #623.

The WMR200 driver is no longer supported. An unsupported version can be found
at https://github.com/weewx/weewx-wmr200. Support for LaCrosse WS23xx and
Oregon WMR300 will continue.

Service weewx.wxxtypes.StdDelta was inadvertently left out of the list of
services to be run. Fortunately, it is not used. Yet. Added it back in.

Added the "old" NWS algorithm as an option for calculating heat index.

Changed how various undocumented parameters in [StdWXCalculate] are specified.
The only one people are likely to have used is 'ignore_zero_wind'. Its name has
changed to 'force_null', and it has been moved. See the Upgrading Guide.

Documented the various [StdWXCalculate] options.

Fixed corner case for windDir when using software record generation,
ignore_zero_wind=True, and windSpeed=0 for entire record interval. Now emits
last windDir value.

Fixed problem when looking up stars with more than one word in their name.
Fixes issue #620.

Fixed problem where wind gust direction is not available when using software
record generation.

Added --no-prompt action to wee_import allowing wee_import to be run unattended.

Fixed problem that prevented option `observations` from being used in the
simulator. Thanks to user Graham!

Fixed problem where wind chill was calculated incorrectly for METRICWX
databases. PR #627. Thanks to user edi-x!

Allow wind vectors to be converted to unit of beaufort. Fixes issue #629.

Option log_failure under [StdReport] is set to True by the upgrade process.
See the Upgrading Guide.

--
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/CAPq0zEA7erS-vd24NNUgRzfQmHs7zf-gf_UcYZkXHUyZ7DZewg%40mail.gmail.com.

[weewx-user] Re: Barometer Data Missing from CWOP updates

Well, I think I found something in restx.py.

For CWOP, there is a line that says
_baro = record.get('altimeter')

Well, looking at my loop data there is no altimeter field in it.
I do see in the startup that it says 
weewx.wxservices: The following values will be calculated: 
altimeter=prefer_hardware, appTemp=prefer_hardware, 
barometer=prefer_hardware, beaufort=prefer_hardware, 
cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
heatindex=prefer_hardware, humidex=prefer_hardware, 
inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
pressure=prefer_hardware, rainRate=prefer_hardware, 
windchill=prefer_hardware, windrun=prefer_hardware
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following algorithms will be used for calculations: altimeter=aaASOS, 
maxSolarRad=RS

So, apparently, altimeter is something that is supposed to be calculated, 
but for whatever reason, when code tries to grab it for CWOP, it's set to 
'None'.

I've temporarily changed to code to point at barometer, but I'm guessing 
that's the wrong solution and what I need to figure out is why the data for 
altimeter is 'None'

On Monday, January 4, 2021 at 2:21:10 PM UTC-8 Brent Dowell wrote:

> A couple months ago I moved my weather station to run on a Raspberry pi, 
> and things have been running smoothly  with the exception of the data that 
> gets uploaded to CWOP.
>
> I upload data to cwop, wunderground, pwsweather, and my own weather site.  
> The only one missing the data is cwop.
>
> I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
> vue weather station.
>
> I've attached below the cwop data, loop data, and syslog.
>
> Thanks in advance for any help.
>
>
>
> My raw data for cwop has a  b.  for the barometric data. 
>
> --
> {Manually 
> obfuscated}>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
>   
>
> Loop Data looks like:
>
> --
> LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
> barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
> consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
> dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
> humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
> inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
> monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
> outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
> 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
> 1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
> 158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
> 28.0, yearET: 0.0, yearRain: 0.4
>
>
> Here's my syslog from the startup with debug = 1
>
> --
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
> weewx version 4.0.0b9
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
> 2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
> Linux-4.19.75-v7l+-armv7l-with-debian-10.1
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
> 'en_US.UTF-8'
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
> configuration file /home/weewx/weewx.conf
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
> target unit is 0x1
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
> following values will be calculated: altimeter=prefer_hardware, 
> appTemp=prefer_hardware, barometer=prefer_hardware, 
> beaufort=prefer_hardware, cloudbase=prefer_hardware, 
> dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
> humidex=prefer_hardware, inDewpoint=prefer_hardware, 
> maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
> following algorithms will be used for calculations: altimeter=aaASOS, 
> maxSolarRad=RS
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will 
> use data binding wx_binding
> Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.e

Re: [weewx-user] Re: index.html not updating


Bizarre, 8 am still confident there is something in your Seasons 
index.html.tmpl that is causing an error hence it’s not generated. Can you 
post your copy of Seasons index.html.tmpl? Maybe something will stand out.

Gary
On Tuesday, 5 January 2021 at 07:56:51 UTC+10 blu...@gmail.com wrote:

> I just double checked /etc/weewx/weewx.conf and wee_debug and both are 
> showing debug = 1 and [StdReport] log_failure = True.
>
> Did another sudo /etc/init.d/weewx restart, still no DEBUG entries in 
> /var/log/messages.
>
> index.html in /var/www/html/weewx has the 1 January timestamp, but all the 
> graph images are up to date. 
>
> index.html in /var/www/html/weewx/standard, mobile, and smart are all up 
> to date.
>
>
>
>
>
> On Mon, Jan 4, 2021 at 12:34 PM gjr80  wrote:
>
>> Hmm, I’m still not convinced that the log is as it should be, log_failure 
>> under [StdReport] is definitely = True? When reports are generated there 
>> should be entries about skin.conf being found etc. Nonetheless, Seasons 
>> seems to be generating the correct number of files. Can you check the 
>> timestamp on /var/www/html/weewx/index.html, is it changing? Is it current 
>> or stuck on 1 January?
>>
>> Gary
>>
>> On Tuesday, 5 January 2021 at 02:10:09 UTC+10 blu...@gmail.com wrote:
>>
>>> Done.  Nothing new in log.
>>>
>>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Initializing weewx 
>>> version 4.2.0
>>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Using Python 2.7.13 
>>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Platform 
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Locale is 
>>> 'en_US.UTF-8'
>>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Using configuration 
>>> file /etc/weewx/weewx.conf
>>> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Debug is 1
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Loading station 
>>> type Vantage (weewx.drivers.vantage)
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: StdConvert 
>>> target unit is 0x1
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Archive will use 
>>> data binding wx_binding
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Record 
>>> generation will be attempted in 'software'
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using archive 
>>> interval of 300 seconds (software record generation)
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti: 
>>> forecast version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti: 
>>> interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
>>> hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: 
>>> interval=10800 max_age=604800 lid=ORZ006 foid=PQR
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WU: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: OWM: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: UKMO: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Aeris: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WWO: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: DS: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: XTide: forecast 
>>> version 3.3.2
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: StationRegistry: 
>>> Station will be registered.
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: Wunderground: 
>>> Posting not enabled.
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: PWSweather: 
>>> Posting not enabled.
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: CWOP: Posting not 
>>> enabled.
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: WOW: Posting not 
>>> enabled.
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: AWEKAS: Posting 
>>> not enabled.
>>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: service version is 
>>> 0.23
>>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: binding to archive
>>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: topic is 
>>> corbett/weather
>>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: data will be 
>>> uploaded to mqtt://127.0.0.1:1883
>>> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Starting up weewx 
>>> version 4.2.0
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Clock error is 
>>> 1.12 seconds (positive is fast)
>>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using binding 
>>> 'wx_binding' to database 'weewx.sdb'
>>> Ja

Re: [weewx-user] Re: weewx and Klimalogg Pro - looking for advice



On 04.01.2021 22:50, vince wrote:

So you're saying:

  * periodically loses connection to the station
*/rather rarely - but at times (1-5 times in a year, usually due
to maintenance - see below)/**/
/**/it also technically happens during a reboot or a short time
shut down of the RPi
/*/(before, when I had it run on Windows, reboots for update would
interrupt the connection,
and once a power cut)/*/
the hardware - a USB transceiver, is pretty reliable
/*
  * yet when that happens it keeps writing out empty (your words)
records every archive period
/*correct - I guess that's the main issue*/
  * and when you press the button to reconnect to the station, you
expect weewx to grab any historical records ?
/*wouldn't that make sense ??  Or after a reboot or so */

The first one sounds like a hardware issue.  The second one is a 
possible bug.  The third is a feature request.
/*I think 2 and 3 are more or less interconnected - the KLP has this 
memory capacity to allow for disconnections of the software*//*
*//*But then the software should also do it i.e. pick up missed data - 
the Windows version of the software does this by the way, and does it 
properly*/
/*If this could be handled by some simple options, entries in e.g. 
weewx.conf, that would be the advice I'm looking for - I don't know if 
such a thing exists,
hence the question. If the developers of the extension still exist and 
were ready to fix that, this would be even greater.*/


That sound correct to you ? -/*with the addenda in bold italics, yes*/

(I don't have a KLP so I can't speculate on how to fix your periodic 
loss of connectivity thing that starts the avalanche of issues, but I 
wanted to ask if I'm reading the problem description correctly)



On Monday, January 4, 2021 at 1:26:03 PM UTC-8 lang@googlemail.com 
wrote:


not very long (except for the initial check - here are 51,330
records to be covered)

- the story is (I meanwhile checked the data base content and the
syslog) that weewx continues writing (empty) records when it isn't
connected to the console.
I think that's the reason for not reading the missed records as
the is a record (though empty) for the respective timestamps
(archiving window = 1 minute).

Weewx should stop writing (empty records) into the database until
it receives the signal from the console again. Then check (like at
the initial start)
which historical records are missing, i.e. exist in the console
memory but not yet in the weewx database, retrieve and store them
and then continue with business as usual (archiving in the
interval, writing summary records, print charts ...)

below the relevant syslog excerpts:

I had weewx starting from scratch again - empty database - it was
then reading all available historical records in the console and
stored (archived) them
see below


Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1766, records skipped=7,
next=38341.0
Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1772, records skipped=7,
next=38347.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1778, records skipped=7,
next=38353.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1784, records skipped=7,
next=38359.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1790, records skipped=7,
next=38365.0
Jan  4 14:20:52 raspberrypi weewx[29188] INFO user.kl:
handleHistoryData: records cached=1796, records skipped=7,
next=38371.0
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Records
scanned: 1800
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Found 1799
historical records
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle
record 46801: 2021-01-01 11:00:00 CET (1609495200)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle
record 46802: 2021-01-01 11:01:00 CET (1609495260)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:01:00 CET (1609495260) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:01:00 CET (1609495260) to daily summary in
'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle
record 46803: 2021-01-01 11:02:00 CET (1609495320)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:02:00 CET (1609495320) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added
record 2021-01-01 11:02:00 CET (1609495320) to daily summary in
'weewx-kl.sdb'
Jan  4 14:21:01 raspberry

[weewx-user] Barometer Data Missing from CWOP updates

A couple months ago I moved my weather station to run on a Raspberry pi, 
and things have been running smoothly  with the exception of the data that 
gets uploaded to CWOP.

I upload data to cwop, wunderground, pwsweather, and my own weather site.  
The only one missing the data is cwop.

I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
vue weather station.

I've attached below the cwop data, loop data, and syslog.

Thanks in advance for any help.



My raw data for cwop has a  b.  for the barometric data. 
--
{Manually 
obfuscated}>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
  

Loop Data looks like:
--
LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
28.0, yearET: 0.0, yearRain: 0.4


Here's my syslog from the startup with debug = 1
--
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
weewx version 4.0.0b9
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
Linux-4.19.75-v7l+-armv7l-with-debian-10.1
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
'en_US.UTF-8'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
configuration file /home/weewx/weewx.conf
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
target unit is 0x1
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following values will be calculated: altimeter=prefer_hardware, 
appTemp=prefer_hardware, barometer=prefer_hardware, 
beaufort=prefer_hardware, cloudbase=prefer_hardware, 
dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
humidex=prefer_hardware, inDewpoint=prefer_hardware, 
maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following algorithms will be used for calculations: altimeter=aaASOS, 
maxSolarRad=RS
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will 
use data binding wx_binding
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: StationRegistry: 
Station will not be registered: no station_url specified.
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: 
Wunderground-PWS: Data for station {Manually obfuscated} will be posted
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: PWSWeather: Data 
for station {Manually obfuscated} will be posted
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: CWOP: Data for 
station {Manually obfuscated} will be posted
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: WOW: Posting not 
enabled.
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: AWEKAS: Posting 
not enabled.
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Starting up 
weewx version 4.0.0b9
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Clock error is 
0.21 seconds (positive is fast)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.manager: Starting 
backfill of daily summaries
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Starting main 
packet lo

Re: [weewx-user] Re: index.html not updating

2021-01-04 Thread Kevin Davis

I just double checked /etc/weewx/weewx.conf and wee_debug and both are
showing debug = 1 and [StdReport] log_failure = True.

Did another sudo /etc/init.d/weewx restart, still no DEBUG entries in
/var/log/messages.

index.html in /var/www/html/weewx has the 1 January timestamp, but all the
graph images are up to date.

index.html in /var/www/html/weewx/standard, mobile, and smart are all up to
date.





On Mon, Jan 4, 2021 at 12:34 PM gjr80  wrote:

> Hmm, I’m still not convinced that the log is as it should be, log_failure
> under [StdReport] is definitely = True? When reports are generated there
> should be entries about skin.conf being found etc. Nonetheless, Seasons
> seems to be generating the correct number of files. Can you check the
> timestamp on /var/www/html/weewx/index.html, is it changing? Is it current
> or stuck on 1 January?
>
> Gary
>
> On Tuesday, 5 January 2021 at 02:10:09 UTC+10 blu...@gmail.com wrote:
>
>> Done.  Nothing new in log.
>>
>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Initializing weewx
>> version 4.2.0
>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Using Python 2.7.13
>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Platform
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Locale is
>> 'en_US.UTF-8'
>> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: PID file is
>> /var/run/weewx.pid
>> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Using configuration
>> file /etc/weewx/weewx.conf
>> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Debug is 1
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Loading station
>> type Vantage (weewx.drivers.vantage)
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: StdConvert target
>> unit is 0x1
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Archive will use
>> data binding wx_binding
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Record generation
>> will be attempted in 'software'
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using archive
>> interval of 300 seconds (software record generation)
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti:
>> interval=600 max_age=604800 winddir_period=1800 pressure_period=10800
>> hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: interval=10800
>> max_age=604800 lid=ORZ006 foid=PQR
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WU: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: OWM: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: UKMO: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Aeris: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WWO: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: DS: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: XTide: forecast
>> version 3.3.2
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: StationRegistry:
>> Station will be registered.
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: Wunderground:
>> Posting not enabled.
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: PWSweather:
>> Posting not enabled.
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: CWOP: Posting not
>> enabled.
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: WOW: Posting not
>> enabled.
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: AWEKAS: Posting
>> not enabled.
>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: service version is
>> 0.23
>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: binding to archive
>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: topic is
>> corbett/weather
>> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: data will be
>> uploaded to mqtt://127.0.0.1:1883
>> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Starting up weewx
>> version 4.2.0
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Clock error is
>> 1.12 seconds (positive is fast)
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using binding
>> 'wx_binding' to database 'weewx.sdb'
>> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.manager: Starting
>> backfill of daily summaries
>> Jan  4 07:59:12 corbett weewx[32531] INFO weewx.engine: Starting main
>> packet loop.
>> Jan  4 08:00:15 corbett weewx[32531] INFO weewx.manager: Added record
>> 2021-01-04 08:00:00 PST (1609776000) to database 'weewx.sdb'
>> Jan  4 08:00:15 corbett weewx[32531] INFO weewx.manager: Added record
>> 2021-01-04 08:00:00 PST (1609776000) to daily summary i

[weewx-user] Barometer data missing for CWOP

A couple months ago I moved my weather station to run on a Raspberry pi, 
and things have been running smoothly  with the exception of the data that 
gets uploaded to CWOP.

I upload data to cwop, wunderground, pwsweather, and my own weather site.  
The only one missing the data is cwop.

I'm running weewx version 4.0.0b9 on python Python 2.7.16 with a vantage 
vue weather station.

I've attached below the cwop data, loop data, and syslog.

Thanks in advance for any help.



My raw data for cwop has a  b.  for the barometric data. 
CW8738>APRS,TCPXX*,qAX,CWOP-4:@032150z3949.85N/11938.56W_315/009g014t050r000p000P000b.h46.weewx-4.0.0b9-Vantage
  

Loop Data looks like:
LOOP:   2021-01-04 13:48:42 PST (1609796922) appTemp: 27.7561312321, 
barometer: 29.922, beaufort: 7, cloudbase: 6804.06549784, 
consBatteryVoltage: 4.75, dateTime: 1609796922, dayET: 0.0, dayRain: 0.01, 
dewpoint: 39.7661118095, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
extraAlarm8: 0, forecastIcon: 3, forecastRule: 187, heatindex: 50.3, 
humidex: 50.3, inDewpoint: 36.425696503, inHumidity: 32.0, insideAlarm: 0, 
inTemp: 67.3, leafWet4: 0.0, maxSolarRad: 340.146433311, monthET: 0.0, 
monthRain: 0.01, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, 
outTemp: 50.3, pressure: 25.4481125632, rain: None, rainAlarm: 0, rainRate: 
0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, 
soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1609774320.0, sunset: 
1609809312.0, txBatteryStatus: 0, usUnits: 1, windchill: 50.3, windDir: 
158.0, windGust: 36.0, windGustDir: 158.0, windSpeed: 36.0, windSpeed10: 
28.0, yearET: 0.0, yearRain: 0.4

Here's my syslog from the startup with debug = 1

Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Initializing 
weewx version 4.0.0b9
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using Python 
2.7.16 (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Platform 
Linux-4.19.75-v7l+-armv7l-with-debian-10.1
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Locale is 
'en_US.UTF-8'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using 
configuration file /home/weewx/weewx.conf
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: StdConvert 
target unit is 0x1
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following values will be calculated: altimeter=prefer_hardware, 
appTemp=prefer_hardware, barometer=prefer_hardware, 
beaufort=prefer_hardware, cloudbase=prefer_hardware, 
dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
humidex=prefer_hardware, inDewpoint=prefer_hardware, 
maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.wxservices: The 
following algorithms will be used for calculations: altimeter=aaASOS, 
maxSolarRad=RS
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Archive will 
use data binding wx_binding
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: StationRegistry: 
Station will not be registered: no station_url specified.
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: 
Wunderground-PWS: Data for station KNVRENO31 will be posted
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: PWSWeather: Data 
for station KNVRENO31 will be posted
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: CWOP: Data for 
station CW8738 will be posted
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: WOW: Posting not 
enabled.
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.restx: AWEKAS: Posting 
not enabled.
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Starting up 
weewx version 4.0.0b9
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Clock error is 
0.21 seconds (positive is fast)
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.manager: Starting 
backfill of daily summaries
Jan  4 13:48:41 raspberrypi weewx[11987] INFO weewx.engine: Starting main 
packet loop.
Jan  4 13:50:14 raspberrypi dbus-daemon[291]: [system] Activating via 
systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.43' 
(uid=1000 pid=11154 comm="geany ")
Jan  4 13:50:14 raspberrypi systemd[1]: Starting Hostname Service...
Jan  4 13:50:14 raspberrypi dbus-daemon[291]: [system] Successfull

[weewx-user] Re: Light and Dark Theme in Belchertown Skin with Custom Content

2021-01-04 Thread Greg from Oz

In the dark mode the graphic for the moon flips and shows the moon phase 
icon as a different phase

On Tuesday, 5 January 2021 at 08:38:01 UTC+11 vince wrote:

> See if you can do a simple .inc that writes out "my current theme is dark" 
>  or the like based on sessionStorage.getitem('theme') much like the 
> examples in changeTheme( )
>
> belchertown_debug("Theme: sessionStorage.getItem('theme') is now: " + 
> sessionStorage.getItem('theme') );
>
> Now how would you get that to work in a .inc file ?   I dunno.  Not a 
> javascript personbut I'd agree you're looking in the right areas for 
> examples.
>
> On Monday, January 4, 2021 at 12:52:08 PM UTC-8 kk44...@gmail.com wrote:
>
>> I included a custom iframe into one of the index_hook_after_inc 
>> files. This iframe is a link to some foreign site providing a picture. The 
>> link includes a lot of parameters, one of them for light or dark background.
>>
>> I have almost no knowledge about JavaScript. How can I adjust the link 
>> according to the theme in action?
>>
>> Maybe I could insert something into the changeTheme() function in 
>> belchertown.js, but I guess that would be no good idea because the changes 
>> are removed during updates. So the better way seems to be to put some 
>> JavaScript code into the *.inc file. But how would that look like?
>>
>> I hope, someone can help.
>>
>> The *.inc file contains a link like that:
>>
>>  
>> https://www.meteoblue.com/de/wetter/widget/daily/w%c3%b6llsdorf_deutschland_2806358?geoloc=fixed&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&precipunit=MILLIMETER&coloured=coloured&pictoicon=0&pictoicon=1&maxtemperature=0&maxtemperature=1&mintemperature=0&mintemperature=1&windspeed=0&windspeed=1&windgust=0&windgust=1&winddirection=0&winddirection=1&uv=0&humidity=0&precipitation=0&precipitation=1&precipitationprobability=0&precipitationprobability=1&spot=0&pressure=0&pressure=1&layout=light";
>>  
>> frameborder="0" scrolling="NO" allowtransparency="true" 
>> sandbox="allow-same-origin allow-scripts allow-popups 
>> allow-popups-to-escape-sandbox" style="width:378px; height:354px"> 
>>  
>>  
>>  
>> https://www.meteoblue.com/de/wetter/woche/w%c3%b6llsdorf_deutschland_2806358?utm_source=weather_widget&utm_medium=linkus&utm_content=daily&utm_campaign=Weather%2BWidget";
>>  
>> target="_blank">© meteoblue 
>>  
>> 
>>
>> See the option "layout=light" there. It needs to be changed, if the 
>> theme is changed.
>>
>>
>>

-- 
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/cfa796ce-1295-4712-b553-fc14eb4c9e99n%40googlegroups.com.

Re: [weewx-user] Re: weewx and Klimalogg Pro - looking for advice

So you're saying:

   - periodically loses connection to the station
   - yet when that happens it keeps writing out empty (your words) records 
   every archive period
   - and when you press the button to reconnect to the station, you expect 
   weewx to grab any historical records ?

The first one sounds like a hardware issue.  The second one is a possible 
bug.  The third is a feature request.

That sound correct to you ?

(I don't have a KLP so I can't speculate on how to fix your periodic loss 
of connectivity thing that starts the avalanche of issues, but I wanted to 
ask if I'm reading the problem description correctly)


On Monday, January 4, 2021 at 1:26:03 PM UTC-8 lang@googlemail.com 
wrote:

> not very long (except for the initial check - here are 51,330 records to 
> be covered)
>
> - the story is (I meanwhile checked the data base content and the syslog) 
> that weewx continues writing (empty) records when it isn't connected to the 
> console.
> I think that's the reason for not reading the missed records as the is a 
> record (though empty) for the respective timestamps (archiving window = 1 
> minute).
>
> Weewx should stop writing (empty records) into the database until it 
> receives the signal from the console again. Then check (like at the initial 
> start) 
> which historical records are missing, i.e. exist in the console memory but 
> not yet in the weewx database, retrieve and store them
> and then continue with business as usual (archiving in the interval, 
> writing summary records, print charts ...)
>
> below the relevant syslog excerpts:
>
> I had weewx starting from scratch again - empty database - it was then 
> reading all available historical records in the console and stored 
> (archived) them
> see below
> 
>
> Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl: handleHistoryData: 
> records cached=1766, records skipped=7, next=38341.0
> Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl: handleHistoryData: 
> records cached=1772, records skipped=7, next=38347.0
> Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: handleHistoryData: 
> records cached=1778, records skipped=7, next=38353.0
> Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: handleHistoryData: 
> records cached=1784, records skipped=7, next=38359.0
> Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: handleHistoryData: 
> records cached=1790, records skipped=7, next=38365.0
> Jan  4 14:20:52 raspberrypi weewx[29188] INFO user.kl: handleHistoryData: 
> records cached=1796, records skipped=7, next=38371.0
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Records scanned: 
> 1800
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Found 1799 
> historical records
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
> 46801: 2021-01-01 11:00:00 CET (1609495200)
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
> 46802: 2021-01-01 11:01:00 CET (1609495260)
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-01 11:01:00 CET (1609495260) to database 'weewx-kl.sdb'
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-01 11:01:00 CET (1609495260) to daily summary in 'weewx-kl.sdb'
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
> 46803: 2021-01-01 11:02:00 CET (1609495320)
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-01 11:02:00 CET (1609495320) to database 'weewx-kl.sdb'
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-01 11:02:00 CET (1609495320) to daily summary in 'weewx-kl.sdb'
> Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
> 46804: 2021-01-01 11:03:00 CET (1609495380)
>
> .
>
> now the loading comes to an end and weewx runs in normal mode (i.e. 
> reading not history but actual data)
>
> .
>
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: Handle record 
> 51329: 2021-01-04 14:31:00 CET (1609767060)
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-04 14:31:00 CET (1609767060) to database 'weewx-kl.sdb'
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-04 14:31:00 CET (1609767060) to daily summary in 'weewx-kl.sdb'
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: *Handle record 
> 51330:* 2021-01-04 14:32:00 CET (1609767120)
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-04 14:32:00 CET (1609767120) to database 'weewx-kl.sdb'
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added record 
> 2021-01-04 14:32:00 CET (1609767120) to daily summary in 'weewx-kl.sdb'
> Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: *Saved 929 
> historical records; ts last saved record 2021-01-04 14:32:00 CET 
> (1609767120)*
> Jan  4 14:33:50 raspberrypi weewx[2

[weewx-user] rapidfire + rtfreq parametr for WU

2021-01-04 Thread Enrico Re Cecconi

Dears,
I'm a new user from Italy and very grateful for this beautiful software,
i'ts a few days that I'm connected my weather station to weather
underground website.
Currently I'm trying to modify some parameter to improve and customize the
result.

My set-up is:
A meteo station Lacrosse 2350 (old model but new because never used)
Raspberry pi 3B+
Raspian Lite
connection between PWS and Raspberry is made through cable,
connection between Raspberry and internet is made through cable (yes, I
hate Wi-Fi and wireless if possible...)

All works perfectly, till now, I just want to speed up the refresh
frequency in WU page, that currently is 5'.
I tried to set the parameter rapidfire = true
and it seems it works, with a refresh of about 30''.
I don't want a so fast refresh, my idea is a time between 60 to 120'', so I
tried to set the parameter
rtfreq = 60
but without any effect, the time period doesn't increases and frequency
stays faster than my target.

My question are:
1) I'm wrong if I think rtfreq is the proper parameter ?
2) Why it's not present in the configuration file even if is mentioned in
the help ?
3) What can I do or any suggestion to reach the desired target.

Here below a section of weewx.conf (now again = false).
Thank you all very much for your help.
Ciao
Enrico

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = false
# rtfreq = 60 PARAMETRO AGGIUNTO DA ME

--
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/74813c95-8b1e-4721-b48a-e0c5582e1a27n%40googlegroups.com.

[weewx-user] Re: Light and Dark Theme in Belchertown Skin with Custom Content

See if you can do a simple .inc that writes out "my current theme is dark" 
 or the like based on sessionStorage.getitem('theme') much like the 
examples in changeTheme( )

belchertown_debug("Theme: sessionStorage.getItem('theme') is now: " + 
sessionStorage.getItem('theme') );

Now how would you get that to work in a .inc file ?   I dunno.  Not a 
javascript personbut I'd agree you're looking in the right areas for 
examples.

On Monday, January 4, 2021 at 12:52:08 PM UTC-8 kk44...@gmail.com wrote:

> I included a custom iframe into one of the index_hook_after_inc files. 
> This iframe is a link to some foreign site providing a picture. The link 
> includes a lot of parameters, one of them for light or dark background.
>
> I have almost no knowledge about JavaScript. How can I adjust the link 
> according to the theme in action?
>
> Maybe I could insert something into the changeTheme() function in 
> belchertown.js, but I guess that would be no good idea because the changes 
> are removed during updates. So the better way seems to be to put some 
> JavaScript code into the *.inc file. But how would that look like?
>
> I hope, someone can help.
>
> The *.inc file contains a link like that:
>
>  
> https://www.meteoblue.com/de/wetter/widget/daily/w%c3%b6llsdorf_deutschland_2806358?geoloc=fixed&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&precipunit=MILLIMETER&coloured=coloured&pictoicon=0&pictoicon=1&maxtemperature=0&maxtemperature=1&mintemperature=0&mintemperature=1&windspeed=0&windspeed=1&windgust=0&windgust=1&winddirection=0&winddirection=1&uv=0&humidity=0&precipitation=0&precipitation=1&precipitationprobability=0&precipitationprobability=1&spot=0&pressure=0&pressure=1&layout=light";
>  
> frameborder="0" scrolling="NO" allowtransparency="true" 
> sandbox="allow-same-origin allow-scripts allow-popups 
> allow-popups-to-escape-sandbox" style="width:378px; height:354px"> 
>  
>  
>  
> https://www.meteoblue.com/de/wetter/woche/w%c3%b6llsdorf_deutschland_2806358?utm_source=weather_widget&utm_medium=linkus&utm_content=daily&utm_campaign=Weather%2BWidget";
>  
> target="_blank">© meteoblue 
>  
> 
>
> See the option "layout=light" there. It needs to be changed, if the theme 
> is changed.
>
>
>

-- 
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/92ed3bf2-fe13-4a40-94b9-9442c2019381n%40googlegroups.com.

Re: [weewx-user] Re: weewx and Klimalogg Pro - looking for advice

not very long (except for the initial check - here are 51,330 records to 
be covered)


- the story is (I meanwhile checked the data base content and the 
syslog) that weewx continues writing (empty) records when it isn't 
connected to the console.
I think that's the reason for not reading the missed records as the is a 
record (though empty) for the respective timestamps (archiving window = 
1 minute).


Weewx should stop writing (empty records) into the database until it 
receives the signal from the console again. Then check (like at the 
initial start)
which historical records are missing, i.e. exist in the console memory 
but not yet in the weewx database, retrieve and store them
and then continue with business as usual (archiving in the interval, 
writing summary records, print charts ...)


below the relevant syslog excerpts:

I had weewx starting from scratch again - empty database - it was then 
reading all available historical records in the console and stored 
(archived) them

see below


Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1766, records skipped=7, next=38341.0
Jan  4 14:20:50 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1772, records skipped=7, next=38347.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1778, records skipped=7, next=38353.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1784, records skipped=7, next=38359.0
Jan  4 14:20:51 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1790, records skipped=7, next=38365.0
Jan  4 14:20:52 raspberrypi weewx[29188] INFO user.kl: 
handleHistoryData: records cached=1796, records skipped=7, next=38371.0

Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Records scanned: 1800
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Found 1799 
historical records
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46801: 2021-01-01 11:00:00 CET (1609495200)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46802: 2021-01-01 11:01:00 CET (1609495260)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:01:00 CET (1609495260) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:01:00 CET (1609495260) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46803: 2021-01-01 11:02:00 CET (1609495320)
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:02:00 CET (1609495320) to database 'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-01 11:02:00 CET (1609495320) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:21:01 raspberrypi weewx[29188] INFO user.kl: Handle record 
46804: 2021-01-01 11:03:00 CET (1609495380)


.

now the loading comes to an end and weewx runs in normal mode (i.e. 
reading not history but actual data)


.

Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: Handle record 
51329: 2021-01-04 14:31:00 CET (1609767060)
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:31:00 CET (1609767060) to database 'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:31:00 CET (1609767060) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: *Handle record 
51330:* 2021-01-04 14:32:00 CET (1609767120)
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:32:00 CET (1609767120) to database 'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:32:00 CET (1609767120) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:33:50 raspberrypi weewx[29188] INFO user.kl: *Saved 929 
historical records; ts last saved record 2021-01-04 14:32:00 CET 
(1609767120)*
Jan  4 14:33:50 raspberrypi weewx[29188] INFO /*weewx.engine: Starting 
main packet loop.*/
Jan  4 14:34:20 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:34:00 CET (1609767240) to database 'weewx-kl.sdb'
Jan  4 14:34:20 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:34:00 CET (1609767240) to daily summary in 
'weewx-kl.sdb'
Jan  4 14:34:20 raspberrypi weewx[29188] INFO weewx.cheetahgenerator: 
Generated 1 files for report kl in 0.28 seconds
Jan  4 14:34:29 raspberrypi weewx[29188] INFO weewx.imagegenerator: 
Generated 33 images for report kl in 8.42 seconds
Jan  4 14:35:30 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:35:00 CET (1609767300) to database 'weewx-kl.sdb'
Jan  4 14:35:30 raspberrypi weewx[29188] INFO weewx.manager: Added 
record 2021-01-04 14:35:00 CET (1609767300) to daily summary in 
'weewx-kl.

[weewx-user] Re: diffrent upload time to ss

Thank you but unfortunately your log extract does not show the WeeWX 
startup sequence which has important config info. Can you go back to your 
log and copy/post the full WeeWX startup sequence.

Gary

On Tuesday, 5 January 2021 at 07:16:53 UTC+10 hobbyl...@gmail.com wrote:

> Jan  4 23:01:18 metfm weewx[25601] DEBUG weewx.drivers.fousb: live 
> synchronised
> Jan  4 23:01:18 metfm weewx[25601] DEBUG weewx.drivers.fousb: packet 
> timestamp is 21:01:18
> Jan  4 23:01:18 metfm weewx[25601] DEBUG weewx.drivers.fousb: estimated 
> log time 20:43:54 +/- 24s (20:43:30..20:44:18)
> Jan  4 23:02:03 metfm weewx[25601] DEBUG weewx.drivers.fousb: avoid 
> 5.858845472335815
> Jan  4 23:02:09 metfm weewx[25601] DEBUG weewx.drivers.fousb: new data
> Jan  4 23:02:09 metfm weewx[25601] DEBUG weewx.drivers.fousb: packet 
> timestamp is 21:02:06
> Jan  4 23:02:09 metfm weewx[25601] DEBUG weewx.drivers.fousb: estimated 
> log time 20:43:48 +/- 18s (20:43:18..20:44:06)
> Jan  4 23:02:25 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-BEACON-LOSS 
> Jan  4 23:02:29 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-BEACON-LOSS 
> Jan  4 23:02:33 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-BEACON-LOSS 
> Jan  4 23:02:51 metfm weewx[25601] DEBUG weewx.drivers.fousb: avoid 
> 5.866158962249756
> Jan  4 23:02:57 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=0 signal=-83 noise= txrate=19500
> Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: new data
> Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: packet 
> timestamp is 21:02:54
> Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: estimated 
> log time 20:44:00 +/- 6s (20:43:54..20:44:06)
> Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: synchronised 
> to 2021-01-04 20:44:00 for ptr 0x8290
> Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: found 0 
> archive records
> Jan  4 23:02:57 metfm weewx[25601] INFO weewx.engine: Starting main packet 
> loop.
> Jan  4 23:02:58 metfm weewx[25601] INFO weewx.drivers.fousb: station 
> status {'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
> Jan  4 23:03:02 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=1 signal=-73 noise= txrate=26000
> Jan  4 23:03:10 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=0 signal=-83 noise= txrate=19500
> Jan  4 23:03:15 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=1 signal=-81 noise= txrate=39000
> Jan  4 23:03:27 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=0 signal=-83 noise= txrate=19500
> Jan  4 23:03:33 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=1 signal=-71 noise= txrate=19500
> Jan  4 23:04:01 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
> above=1 signal=-69 noise= txrate=39000
> Jan  4 23:05:59 metfm weewx[25601] INFO weewx.manager: Added record 
> 2021-01-04 23:05:00 EET (1609794300) to database 'weewx.sdb'
> Jan  4 23:05:59 metfm weewx[25601] INFO weewx.manager: Added record 
> 2021-01-04 23:05:00 EET (1609794300) to daily summary in 'weewx.sdb'
> Jan  4 23:05:59 metfm weewx[25601] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Jan  4 23:05:59 metfm weewx[25601] DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Jan  4 23:05:59 metfm weewx[25601] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Jan  4 23:06:00 metfm weewx[25601] INFO weewx.restx: WeatherCloud: 
> Published record 2021-01-04 23:05:00 EET (1609794300)
> Jan  4 23:06:00 metfm weewx[25601] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Jan  4 23:06:00 metfm weewx[25601] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  4 23:06:04 metfm dbus-daemon[1104]: [session uid=1000 pid=1104] 
> Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested 
> by ':1.145' (uid=1000 pid=25648 comm="/usr/bin/Thunar ")
> Jan  4 23:06:05 metfm org.freedesktop.thumbnails.Thumbnailer1[1104]: 
> Registered thumbailer atril-thumbnailer -s %s %u %o
> Jan  4 23:06:05 metfm org.freedesktop.thumbnails.Thumbnailer1[1104]: 
> Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
> Jan  4 23:06:05 metfm org.freedesktop.thumbnails.Thumbnailer1[1104]: 
> Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
> Jan  4 23:06:05 metfm dbus-daemon[1104]: [session uid=1000 pid=1104] 
> Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
> Jan  4 23:06:08 metfm weewx[25601] INFO weewx.cheetahgenerator: Generated 
> 9 files for report SeasonsReport in 7.56 seconds
> Jan  4 23:06:08 metfm weewx[25601] DEBUG weewx.manager: Daily summary 
>

[weewx-user] Re: diffrent upload time to ss

2021-01-04 Thread Δημήτρης Βήχος

Jan  4 23:01:18 metfm weewx[25601] DEBUG weewx.drivers.fousb: live 
synchronised
Jan  4 23:01:18 metfm weewx[25601] DEBUG weewx.drivers.fousb: packet 
timestamp is 21:01:18
Jan  4 23:01:18 metfm weewx[25601] DEBUG weewx.drivers.fousb: estimated log 
time 20:43:54 +/- 24s (20:43:30..20:44:18)
Jan  4 23:02:03 metfm weewx[25601] DEBUG weewx.drivers.fousb: avoid 
5.858845472335815
Jan  4 23:02:09 metfm weewx[25601] DEBUG weewx.drivers.fousb: new data
Jan  4 23:02:09 metfm weewx[25601] DEBUG weewx.drivers.fousb: packet 
timestamp is 21:02:06
Jan  4 23:02:09 metfm weewx[25601] DEBUG weewx.drivers.fousb: estimated log 
time 20:43:48 +/- 18s (20:43:18..20:44:06)
Jan  4 23:02:25 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-BEACON-LOSS 
Jan  4 23:02:29 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-BEACON-LOSS 
Jan  4 23:02:33 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-BEACON-LOSS 
Jan  4 23:02:51 metfm weewx[25601] DEBUG weewx.drivers.fousb: avoid 
5.866158962249756
Jan  4 23:02:57 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-83 noise= txrate=19500
Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: new data
Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: packet 
timestamp is 21:02:54
Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: estimated log 
time 20:44:00 +/- 6s (20:43:54..20:44:06)
Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: synchronised 
to 2021-01-04 20:44:00 for ptr 0x8290
Jan  4 23:02:57 metfm weewx[25601] DEBUG weewx.drivers.fousb: found 0 
archive records
Jan  4 23:02:57 metfm weewx[25601] INFO weewx.engine: Starting main packet 
loop.
Jan  4 23:02:58 metfm weewx[25601] INFO weewx.drivers.fousb: station status 
{'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
Jan  4 23:03:02 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-73 noise= txrate=26000
Jan  4 23:03:10 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-83 noise= txrate=19500
Jan  4 23:03:15 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-81 noise= txrate=39000
Jan  4 23:03:27 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-83 noise= txrate=19500
Jan  4 23:03:33 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-71 noise= txrate=19500
Jan  4 23:04:01 metfm wpa_supplicant[432]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-69 noise= txrate=39000
Jan  4 23:05:59 metfm weewx[25601] INFO weewx.manager: Added record 
2021-01-04 23:05:00 EET (1609794300) to database 'weewx.sdb'
Jan  4 23:05:59 metfm weewx[25601] INFO weewx.manager: Added record 
2021-01-04 23:05:00 EET (1609794300) to daily summary in 'weewx.sdb'
Jan  4 23:05:59 metfm weewx[25601] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Jan  4 23:05:59 metfm weewx[25601] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Jan  4 23:05:59 metfm weewx[25601] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jan  4 23:06:00 metfm weewx[25601] INFO weewx.restx: WeatherCloud: 
Published record 2021-01-04 23:05:00 EET (1609794300)
Jan  4 23:06:00 metfm weewx[25601] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jan  4 23:06:00 metfm weewx[25601] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 23:06:04 metfm dbus-daemon[1104]: [session uid=1000 pid=1104] 
Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested 
by ':1.145' (uid=1000 pid=25648 comm="/usr/bin/Thunar ")
Jan  4 23:06:05 metfm org.freedesktop.thumbnails.Thumbnailer1[1104]: 
Registered thumbailer atril-thumbnailer -s %s %u %o
Jan  4 23:06:05 metfm org.freedesktop.thumbnails.Thumbnailer1[1104]: 
Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Jan  4 23:06:05 metfm org.freedesktop.thumbnails.Thumbnailer1[1104]: 
Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Jan  4 23:06:05 metfm dbus-daemon[1104]: [session uid=1000 pid=1104] 
Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Jan  4 23:06:08 metfm weewx[25601] INFO weewx.cheetahgenerator: Generated 9 
files for report SeasonsReport in 7.56 seconds
Jan  4 23:06:08 metfm weewx[25601] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 23:06:11 metfm weewx[25601] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 2.84 seconds
Jan  4 23:06:11 metfm weewx[25601] INFO weewx.reportengine: Copied 5 files 
to /var/www/html/weewx/original
Jan  4 23:06:11 metfm weewx[25601] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jan  4 23:06:11 metfm weewx[25601] DEBUG weewx.reportengine: Report 
'MobileRepor

[weewx-user] Re: diffrent upload time to ss

Hi,

Can you edit weewx.conf, set debug = 1, save weewx.conf and restart WeeWX . 
Let WeeWX run for 15 minutes the take a copy of the log from when you 
restarted WeeWX through until the 15 minutes elapsed. Post the log extract 
here.

Gary

On Tuesday, 5 January 2021 at 06:33:42 UTC+10 hobbyl...@gmail.com wrote:

> i installed the realtime gaquge-data extension and i try to upload every 
> 60 secs.with these settings
>
> # Options for extension 'Rtgd'
> [RealtimeGaugeData]
> date_format = %Y.%m.%d %H:%M
> stale_age = 60
>
> rtgd_path = /var/www/html/weewx/realtime
> scroller_source = text|file|WU|DS|Zambretti
>
> after weewx reload ,realtime gauge uploads every 300 secs with the rest 
> weewx reports. something im doing wrong 
> Στις Τετάρτη, 18 Δεκεμβρίου 2019 στις 2:01:34 π.μ. UTC+2, ο χρήστης gjr80 
> έγραψε:
>
>> I think a little background on timing and WeeWX output might help you 
>> understand what WeeWX can/cannot do and how you might configure WeeWX to 
>> best meet your needs.
>>
>> The archive interval (usually the archive_interval setting under 
>> [StdArchive] in weewx.conf but the value actually in use is logged in 
>> the WeeWX startup) is the basic time period that drives WeeWX operation. 
>> WeeWX will endeavour to save an archive record every archive_interval 
>> seconds and once an archive record is generated/saved a number of other 
>> WeeWX services are kicked off. For example, the StdRESTful service runs 
>> and handles any uploads to WU, WOW etc. The StdReport service is run and 
>> any scheduled reports in the skins are generated. The key point here is 
>> that StdRESTful and StdReport are only run upon an archive record being 
>> generated/saved, so if you archive interval is five minutes StdRESTful 
>> will upload every five minutes and StdReport will generate reports every 
>> five minutes. You cannot have StdRESTful and StdReport run at an 
>> interval that is less than the archive interval (eg if you archive interval 
>> is five minutes you cannot run reports every one minute). You can generate 
>> reports at intervals greater than the archive interval through use of the 
>> report_timing and stale_age options (refer to Scheduling report 
>> generation  
>> in the Customization Guide).
>>
>> Note. StdRESTful can run some uploads at intervals less than the archive 
>> interval (eg WU rapidfire) but this relies on the RESTful service concerned 
>> being written to operate in conjunction with higher frequency loop packets. 
>> As a general rule though the WeeWX provided RESTful services operate on the 
>> archive interval.
>>
>> One approach to say generate a given report every minute and others every 
>> five minutes, is to have an archive interval of one minute and generate the 
>> high frequency report every archive interval, but set the other reports to 
>> generate every five minutes. This may or may not cause issues with 
>> StdRESTful as generally speaking StdRESTful runs every archive interval. 
>> Using a short archive interval such as one minute can cause other issues as 
>> well, particularly if your WeeWX machine is under a heavy load or WeeWX has 
>> many complex reports to generate.
>>
>> Whilst the archive interval is the fundamental time period used by WeeWX 
>> you will see some WeeWX activity occurring more frequently. This is usually 
>> based upon loop packets (loop packets are higher frequency packets of data 
>> emitted by the station/driver which may or may not contain all observations 
>> and may arrive a regular or irregular intervals, eg the Davis stations emit 
>> loop packets every 2.5 odd seconds). Certain events can be triggered on 
>> loop packet arrival, that is how WU rapid fire works. You can also have a 
>> WeeWX service that is triggered on the arrival of loop packets and that 
>> service can generate output (that is how a number of the near realtime 
>> output services operate). Note though that the WeeWX reports available via 
>> StdReport cannot be generated on the arrival of each loop packet. 
>> Generally speaking, if you wish to generate report like output from WeeWX 
>> on every loop packet arrival you need to write a custom WeeWX service to 
>> create the desired output.
>>
>> Use of the SteelSeries gauges are further complicated as the SteelSeries 
>> gauges have their own code that updates the gauges from a data file (
>> gauge-data.txt) at some rate defined in gauges.js. It is fine to set 
>> this as you like, but you need to be aware that if you have gauges.js 
>> update the gauges every one minute but WeeWX only produces gauge-data.txt 
>> every five minutes, your gauges will be updated every one minute but you 
>> will only see a change on your gauges every five (or so) minutes. One 
>> approach is to use a loop based service to generate gauge-data.txt such 
>> as the Realtime gauge-data extension 
>> . T

[weewx-user] Light and Dark Theme in Belchertown Skin with Custom Content

2021-01-04 Thread Karen K

I included a custom iframe into one of the index_hook_after_inc files. 
This iframe is a link to some foreign site providing a picture. The link 
includes a lot of parameters, one of them for light or dark background.

I have almost no knowledge about JavaScript. How can I adjust the link 
according to the theme in action?

Maybe I could insert something into the changeTheme() function in 
belchertown.js, but I guess that would be no good idea because the changes 
are removed during updates. So the better way seems to be to put some 
JavaScript code into the *.inc file. But how would that look like?

I hope, someone can help.

The *.inc file contains a link like that:

 
https://www.meteoblue.com/de/wetter/widget/daily/w%c3%b6llsdorf_deutschland_2806358?geoloc=fixed&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&precipunit=MILLIMETER&coloured=coloured&pictoicon=0&pictoicon=1&maxtemperature=0&maxtemperature=1&mintemperature=0&mintemperature=1&windspeed=0&windspeed=1&windgust=0&windgust=1&winddirection=0&winddirection=1&uv=0&humidity=0&precipitation=0&precipitation=1&precipitationprobability=0&precipitationprobability=1&spot=0&pressure=0&pressure=1&layout=light";
 
frameborder="0" scrolling="NO" allowtransparency="true" 
sandbox="allow-same-origin allow-scripts allow-popups 
allow-popups-to-escape-sandbox" style="width:378px; height:354px"> 
 
 
 
https://www.meteoblue.com/de/wetter/woche/w%c3%b6llsdorf_deutschland_2806358?utm_source=weather_widget&utm_medium=linkus&utm_content=daily&utm_campaign=Weather%2BWidget";
 
target="_blank">© meteoblue 
 


See the option "layout=light" there. It needs to be changed, if the theme 
is changed.


-- 
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/7b965f08-7dd9-451d-8f97-81281120973fn%40googlegroups.com.

[weewx-user] Re: weewx and Klimalogg Pro - looking for advice

How long does this check take when weewx restarts ?   How much data do you 
think is being missed ?

We'd have to see some logs.   Set debug=1 and restart weewx and let it run 
for a couple archive periods.

-- 
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/fe55c5e1-0b37-410f-94bb-9f68c3a2db5dn%40googlegroups.com.

Re: [weewx-user] Re: index.html not updating

Hmm, I’m still not convinced that the log is as it should be, log_failure 
under [StdReport] is definitely = True? When reports are generated there 
should be entries about skin.conf being found etc. Nonetheless, Seasons 
seems to be generating the correct number of files. Can you check the 
timestamp on /var/www/html/weewx/index.html, is it changing? Is it current 
or stuck on 1 January?

Gary

On Tuesday, 5 January 2021 at 02:10:09 UTC+10 blu...@gmail.com wrote:

> Done.  Nothing new in log.
>
> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Initializing weewx 
> version 4.2.0
> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Using Python 2.7.13 
> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Locale is 'en_US.UTF-8'
> Jan  4 07:59:09 corbett weewx[32526] INFO __main__: PID file is 
> /var/run/weewx.pid
> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Debug is 1
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Archive will use 
> data binding wx_binding
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Record generation 
> will be attempted in 'software'
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using archive 
> interval of 300 seconds (software record generation)
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti: 
> interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
> hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: interval=10800 
> max_age=604800 lid=ORZ006 foid=PQR
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WU: forecast version 
> 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: OWM: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: UKMO: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Aeris: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WWO: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: DS: forecast version 
> 3.3.2
> Jan  4 07:59:09 corbett weewxd: forecast: MainThread: XTide: forecast 
> version 3.3.2
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: StationRegistry: 
> Station will be registered.
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: Wunderground: 
> Posting not enabled.
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: PWSweather: Posting 
> not enabled.
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: CWOP: Posting not 
> enabled.
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: WOW: Posting not 
> enabled.
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: AWEKAS: Posting not 
> enabled.
> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: service version is 
> 0.23
> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: binding to archive
> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: topic is 
> corbett/weather
> Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: data will be uploaded 
> to mqtt://127.0.0.1:1883
> Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Starting up weewx 
> version 4.2.0
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Clock error is 
> 1.12 seconds (positive is fast)
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Jan  4 07:59:09 corbett weewx[32531] INFO weewx.manager: Starting backfill 
> of daily summaries
> Jan  4 07:59:12 corbett weewx[32531] INFO weewx.engine: Starting main 
> packet loop.
> Jan  4 08:00:15 corbett weewx[32531] INFO weewx.manager: Added record 
> 2021-01-04 08:00:00 PST (1609776000) to database 'weewx.sdb'
> Jan  4 08:00:15 corbett weewx[32531] INFO weewx.manager: Added record 
> 2021-01-04 08:00:00 PST (1609776000) to daily summary in 'weewx.sdb'
> Jan  4 08:00:15 corbett weewxd: forecast: NWSThread: NWS: downloading 
> forecast from '
> http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=PQR
> '
> Jan  4 08:00:15 corbett weewxd: forecast: ZambrettiThread: Zambretti: 
> generated 1 forecast record
> Jan  4 08:00:15 corbett weewx[32531] INFO weewx.restx: MQTT: Published 
> record 2021-01-04 08:00:00 PST (1609776000)
> Jan  4 08:00:16 corbett weewxd: forecast: NWSThread: NWS: got 38 forecast 
> records for Scap

[weewx-user] Re: diffrent upload time to ss

2021-01-04 Thread Δημήτρης Βήχος

i installed the realtime gaquge-data extension and i try to upload every 60 
secs.with these settings

# Options for extension 'Rtgd'
[RealtimeGaugeData]
date_format = %Y.%m.%d %H:%M
stale_age = 60

rtgd_path = /var/www/html/weewx/realtime
scroller_source = text|file|WU|DS|Zambretti

after weewx reload ,realtime gauge uploads every 300 secs with the rest 
weewx reports. something im doing wrong 
Στις Τετάρτη, 18 Δεκεμβρίου 2019 στις 2:01:34 π.μ. UTC+2, ο χρήστης gjr80 
έγραψε:

> I think a little background on timing and WeeWX output might help you 
> understand what WeeWX can/cannot do and how you might configure WeeWX to 
> best meet your needs.
>
> The archive interval (usually the archive_interval setting under 
> [StdArchive] in weewx.conf but the value actually in use is logged in the 
> WeeWX startup) is the basic time period that drives WeeWX operation. WeeWX 
> will endeavour to save an archive record every archive_interval seconds 
> and once an archive record is generated/saved a number of other WeeWX 
> services are kicked off. For example, the StdRESTful service runs and 
> handles any uploads to WU, WOW etc. The StdReport service is run and any 
> scheduled reports in the skins are generated. The key point here is that 
> StdRESTful and StdReport are only run upon an archive record being 
> generated/saved, so if you archive interval is five minutes StdRESTful 
> will upload every five minutes and StdReport will generate reports every 
> five minutes. You cannot have StdRESTful and StdReport run at an interval 
> that is less than the archive interval (eg if you archive interval is five 
> minutes you cannot run reports every one minute). You can generate reports 
> at intervals greater than the archive interval through use of the 
> report_timing and stale_age options (refer to Scheduling report generation 
>  in the 
> Customization Guide).
>
> Note. StdRESTful can run some uploads at intervals less than the archive 
> interval (eg WU rapidfire) but this relies on the RESTful service concerned 
> being written to operate in conjunction with higher frequency loop packets. 
> As a general rule though the WeeWX provided RESTful services operate on the 
> archive interval.
>
> One approach to say generate a given report every minute and others every 
> five minutes, is to have an archive interval of one minute and generate the 
> high frequency report every archive interval, but set the other reports to 
> generate every five minutes. This may or may not cause issues with 
> StdRESTful as generally speaking StdRESTful runs every archive interval. 
> Using a short archive interval such as one minute can cause other issues as 
> well, particularly if your WeeWX machine is under a heavy load or WeeWX has 
> many complex reports to generate.
>
> Whilst the archive interval is the fundamental time period used by WeeWX 
> you will see some WeeWX activity occurring more frequently. This is usually 
> based upon loop packets (loop packets are higher frequency packets of data 
> emitted by the station/driver which may or may not contain all observations 
> and may arrive a regular or irregular intervals, eg the Davis stations emit 
> loop packets every 2.5 odd seconds). Certain events can be triggered on 
> loop packet arrival, that is how WU rapid fire works. You can also have a 
> WeeWX service that is triggered on the arrival of loop packets and that 
> service can generate output (that is how a number of the near realtime 
> output services operate). Note though that the WeeWX reports available via 
> StdReport cannot be generated on the arrival of each loop packet. 
> Generally speaking, if you wish to generate report like output from WeeWX 
> on every loop packet arrival you need to write a custom WeeWX service to 
> create the desired output.
>
> Use of the SteelSeries gauges are further complicated as the SteelSeries 
> gauges have their own code that updates the gauges from a data file (
> gauge-data.txt) at some rate defined in gauges.js. It is fine to set this 
> as you like, but you need to be aware that if you have gauges.js update 
> the gauges every one minute but WeeWX only produces gauge-data.txt every 
> five minutes, your gauges will be updated every one minute but you will 
> only see a change on your gauges every five (or so) minutes. One approach 
> is to use a loop based service to generate gauge-data.txt such as the 
> Realtime 
> gauge-data extension . 
> This extension is used in conjunction with the WeeWX SteelSeries skin to 
> update the SteelSeries gauges on each loop packet. 
>
> Gary
>  
> On Wednesday, 18 December 2019 06:42:06 UTC+10, Δημήτρης Βήχος wrote:
>>
>>  i was tried yesterday that. 60 secs in ss -via gauges.js- and 300 secs 
>> in [StdArchive]  . after restart weewx all pages including ss was uploated 
>> every 300 secs.
>>
>> Τη Τρίτη,

[weewx-user] weewx and Klimalogg Pro - looking for advice

I'm running weewx on Raspberry Pi with my Klimalogg Pro (KLP) and the KL 
extension/skin.


At the first start it reads all the existing data records from the 
Klimalogg Pro (52,000+) and stores them in the database.

Great!

Now I observed that when the connection for some reason gets lost - or 
the RPi shut down longer than the archive window -
and weewx restarts (or I restart weewx), it seems to to check the 
records stored in the KLP, but skips them all and continues
to store new records only from the new startup date/time and ignores the 
records collected by the KLP in between. Out of this

obviously data storage gaps occur.

Anyone has any idea how to make/force weewx continue storing the missing 
data, i.e. reading them from the KLP and store them based on the last 
timestamp in the database at restart before it continue storing new data ?


Feedback appreciated.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ee5873e8-b915-d27c-ad22-1ad9a31fa11a%40gmail.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

2021-01-04 Thread salinois


hi

happy new year at all

I had already this issue, now I used a disk ssd for my RPi3b.

bye

Patrick

Le 04/01/2021 à 20:18, Xant a écrit :


I recently also had a corrupted SD card. Tried many alternatives to 
recover data, including trying to mount at a Linux machine (at no 
prevail).


The only (Windows) solution that actually worked was, where I was able 
to read and retrieve data, was the freeware "DiskInternals Linux Reader":


https://www.diskinternals.com/linux-reader/ 




Xant

On Monday, January 4, 2021 at 6:19:41 AM UTC-5 Joe wrote:

  GNU nano 3.2 syslog


Here is the log


Jan  4 00:25:33 raspberrypi weewx[677] INFO weewx.restx:
Wunderground-RF: Published record 2021-01-04 00:25:33 CST (1609741533)
Jan  4 00:25:35 raspberrypi weewx[677] INFO weewx.restx:
Wunderground-RF: Published record 2021-01-04 00:25:35 CST (1609741535)
Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.imagegenerator:
Generated 13 images for report StandardReport in 8.04 seconds
Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.reportengine:
Copied 0 files to /var/www/weewx
Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine:
Running report 'SeasonsReport'
Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine:
Found configuration file /etc/weewx/skins/Seasons/skin.conf for
report 'SeasonsReport'
Jan  4 00:25:37 raspberrypi weewx[677] DEBUG
weewx.cheetahgenerator: Using search list
['weewx.cheetahgenerator.Almanac',
'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
'weewx.cheetahg$
Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.manager: Daily
summary version is 2
Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.restx:
Wunderground-RF: Published record 2021-01-04 00:25:49 CST (1609741549)
Jan  4 00:25:49 raspberrypi weewx[677] INFO
weewx.cheetahgenerator: Generated 8 files for report SeasonsReport
in 12.96 seconds
Jan  4 00:25:49 raspberrypi weewx[677] DEBUG weewx.manager: Daily
summary version is 2
Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.imagegenerator:
Generated 14 images for report SeasonsReport in 7.65 seconds
Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.reportengine:
Copied 0 files to /var/www/weewx
Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine:
Running report 'SmartphoneReport'
Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine:
Found configuration file /etc/weewx/skins/Smartphone/skin.conf for
report 'SmartphoneReport'
Jan  4 00:25:58 raspberrypi weewx[677] DEBUG
weewx.cheetahgenerator: Using search list
['weewx.cheetahgenerator.Almanac',
'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
'weewx.cheetahg$
Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily
summary version is 2
Jan  4 00:25:58 raspberrypi weewx[677] INFO
weewx.cheetahgenerator: Generated 6 files for report
SmartphoneReport in 0.75 seconds
Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily
summary version is 2Jan  4 00:26:01 raspberrypi weewx[677] INFO
weewx.restx: Wunderground-RF: Published record 2021-01-04 00:26:01
CST (1609741561)
Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.imagegenerator:
Generated 6 images for report SmartphoneReport in 3.04 seconds
Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.reportengine:
Copied 0 files to /smartphone
Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine:
Running report 'MobileReport'
Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine:
Found configuration file /etc/weewx/skins/Mobile/skin.conf for
report 'MobileReport'
Jan  4 00:26:02 raspberrypi weewx[677] DEBUG
weewx.cheetahgenerator: Using search list
['weewx.cheetahgenerator.Almanac',
'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
'weewx.cheetahg$
Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily
summary version is 2
Jan  4 00:26:02 raspberrypi weewx[677] INFO
weewx.cheetahgenerator: Generated 1 files for report MobileReport
in 0.29 seconds
Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily
summary version is 2
Jan  4 00:26:03 raspberrypi weewx[677] INFO weewx.restx:
Wunderground-RF: Published record 2021-01-04 00:26:03 CST (1609741563)
Jan  4 00:26:04 raspberrypi weewx[677] INFO weewx.imagegenerator:
Generated 4 images for report MobileReport in 2.06 seconds
Jan  4 00:26:04 raspberrypi weewx[677] INFO weewx.reportengine:
Copied 0 files to /mobile
Jan  4 00:26:04 raspberrypi weewx[677] DEBUG weewx.reportengine:
Running report 'FTP'
Jan  4 00:26:04 raspberrypi weew

[weewx-user] Re: Publishing WeeWX to AWS S3

Looks like the Route53 prices came down a lot over the years, so I might 
take another look at it.   I'm paying a buck/month for Google hosting my 
DNS and I like the feature set a lot, but there's something to be said for 
being all-in on one vendor since AWS's APIs are pretty solid.

I guess I'd say don't bother with the CF thing unless you get lots of 
interest from other folks.  Your howto helps a lot in connecting the dots 
for the S3 and IAM parts.

I might take a crack at the automation thing in CF/Ansible/Terraform just 
for the adventure as time permits, mainly to fiddle around.I'm very 
happy with going Lightsail years ago literally the day it was announced, 
but I just rsync my weewx public_html up to nginx with no other services 
there, so maybe it's simpler to go S3 and not need to do ubuntu package 
updates.   Thinking about it...

Thanks for the updates.

On Monday, January 4, 2021 at 1:49:05 AM UTC-8 mi...@cougar.eu.com wrote:

>
>- how do you get your stable .eu.com FQDN onto your website's ip 
>address ?
>
> I moved my service to Rout53 some time ago from DynDNS, this post shows 
> how I did that when I was hosting at home 
> https://www.cougar.eu.com/useful-guides/networking-tips/replacing-dyndns-with-route/index.html
>
> But as the site is now managed by AWS Rout53 and S3 are tightly integrated 
> so I don't have to worry about IP Addresses
>
>
>
>- is the website ip address stable ?
>
> Solid as a Rock
>
>
>- are you using Route53 for your DNS ?  What's that cost ?
>
> Yes, and last month it cost $0.51 US, but you only need this if you have 
> your own domain name
>
>
>- Have you given any thought on scripting your whole setup with 
>something like Ansible / Terraform / CloudFormation ?It would be 
> pretty 
>cool to have an accompanying script or equivalent that did that, once you 
>have the manual step of getting an account and saving the AWS credentials 
>of course.
>
> I haven't but it is relatively easy to put the S3 and IAM creation into a 
> Cloud Formation template, I could do that if there was interest
>
> On Sunday, January 3, 2021 at 7:12:57 PM UTC vince wrote:
>
>> My current setup is an AWS Lightsail instance ($4/month) with DNS 
>> provided by Google DNS ($1/month).
>>
>>- how do you get your stable .eu.com FQDN onto your website's ip 
>>address ?
>>- is the website ip address stable ?
>>- are you using Route53 for your DNS ?  What's that cost ?
>>   - (background - I went Google DNS years ago because Route53 was 
>>   too expensive.  Google DNS also had some nice email and site aliasing 
>>   features that Route53 didn't have back then.   I particularly like the 
>>   ability to add email aliases for the family very easily, pointing to 
>> email 
>>   wherever they want it to be hosted)
>>
>>
>>
>>>

-- 
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/082b8414-233f-48a4-8f11-f3d79e291066n%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

2021-01-04 Thread Xant


I recently also had a corrupted SD card. Tried many alternatives to recover 
data, including trying to mount at a Linux machine (at no prevail).

The only (Windows) solution that actually worked was, where I was able to 
read and retrieve data, was the freeware "DiskInternals Linux Reader":

https://www.diskinternals.com/linux-reader/


Xant

On Monday, January 4, 2021 at 6:19:41 AM UTC-5 Joe wrote:

>   GNU nano 3.2
> syslog  
> 
> 
>
>
> Here is the log
>
>
> Jan  4 00:25:33 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
> Published record 2021-01-04 00:25:33 CST (1609741533)
> Jan  4 00:25:35 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
> Published record 2021-01-04 00:25:35 CST (1609741535)
> Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.imagegenerator: 
> Generated 13 images for report StandardReport in 8.04 seconds
> Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
> files to /var/www/weewx
> Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
> Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
> Published record 2021-01-04 00:25:49 CST (1609741549)
> Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 12.96 seconds
> Jan  4 00:25:49 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.imagegenerator: 
> Generated 14 images for report SeasonsReport in 7.65 seconds
> Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
> files to /var/www/weewx
> Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
> report 'SmartphoneReport'
> Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
> 'SmartphoneReport'
> Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
> Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  4 00:25:58 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
> Generated 6 files for report SmartphoneReport in 0.75 seconds
> Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
> version is 2Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.restx: 
> Wunderground-RF: Published record 2021-01-04 00:26:01 CST (1609741561)
> Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.imagegenerator: 
> Generated 6 images for report SmartphoneReport in 3.04 seconds
> Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
> files to /smartphone
> Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
> report 'MobileReport'
> Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Mobile/skin.conf for report 
> 'MobileReport'
> Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
> Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  4 00:26:02 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
> Generated 1 files for report MobileReport in 0.29 seconds
> Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
> version is 2
> Jan  4 00:26:03 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
> Published record 2021-01-04 00:26:03 CST (1609741563)
> Jan  4 00:26:04 raspberrypi weewx[677] INFO weewx.imagegenerator: 
> Generated 4 images for report MobileReport in 2.06 seconds
> Jan  4 00:26:04 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
> files to /mobile
> Jan  4 00:26:04 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
> report 'FTP'
> Jan  4 00:26:04 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
>
> J

Re: [weewx-user] Re: New to weewx, AW WS-2000

2021-01-04 Thread Bill Arthur

I use a three foot USB extension cord on the GW1000. I had one instance 
where the phone-charger-type power supply generated enough trash to hamper 
the GW1000 reception.

On Monday, January 4, 2021 at 11:07:30 AM UTC-6 lang@googlemail.com 
wrote:

> Correct, for power only. You can use any phone charger, USB hub etc. to 
> keep it running. Even plug it into a USB port of a Raspberry Pi if you have 
> one ... 
> A good idea will be to have the power source connected to a UPS, as well 
> as your weather computer :-), or have it connected to a power-bank which 
> you keep on charging - many possibilities.
> On 04.01.2021 17:38, George Morgan wrote:
>
> Well I ordered a GW1000.  Now I'm thinking about how to power it.  The USB 
> connector is only used for power, right?
>
> On Sun, Jan 3, 2021, 7:52 PM galfert  wrote:
>
>> I meant to say water leak not water lead sensor. 
>>
>>
>> On Sunday, January 3, 2021 at 10:51:34 PM UTC-5 galfert wrote:
>>
>>> The WS-2000 does not support more sensors than the GW1000. Its the other 
>>> way around. The GW1000 supports every single sensor that the WS-2000 
>>> support, plus it supports sensors from Ecowitt that Ambient doesn't sell, 
>>> WH32-EP, WH31-EP, WH45 to name a few, and Ecowitt is working on some 
>>> sensors that they will have before Ambient gets them (new soil moisture 
>>> with temperature). The GW1000 also had support for water lead and lightning 
>>> many months before the WS-2000. 
>>>
>>>
>>>
>>> On Sunday, January 3, 2021 at 8:42:57 PM UTC-5 gm@gmail.com wrote:
>>>
 Thanks for the link to the chart...I need to look at it closer but I 
 think my WS-2000 supports more sensors than the GW1000 so I may be looking 
 at integrating FOSHK plug-in into weewx directly...unless I'm missing 
 something... 

 I also need to look at the license for FOSHK plug-in as that may make 
 this impossible (legally, that is)

 On Sat, Jan 2, 2021, 12:40 PM Rainer Lang  wrote:

> It works with all Ambient Weather sensors which are clones of Fine 
> Offset sensors.
>
> (Ambient also sells non-Fine Offset clone sensors and weather stations)
>
> What sensors these are, you can see at 
>
> https://www.wxforum.net/index.php?topic=40730.0
>
>
> On 02.01.2021 21:34, George Morgan wrote:
>
> Does the GW1000 work with all the AW sensors?
>
> On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:
>
>> Well there is a way to get from WS-2000 AW protocol to WeeWX...but 
>> you need a translator. You can use FOSHKplugin and that will convert AW 
>> protocol to Ecowitt protocol and then you can use the WeeWX Interceptor 
>> driver. 
>>
>>
>> On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com 
>> wrote:
>>
>>> Is there an effort to support the AW protocol for the WS-2000 
>>> server?  As a developer I would be interested in working on this if it 
>>> is 
>>> documented (and maybe even if it is not).  My WS-2000 has the latest 
>>> wifi 
>>> and base firmware installed. 
>>>
>>> I will also look into the GW-1000 and RTL SDR options.
>>>
>>> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>>>
 The best way is to buy the GW1000 and then it will pick up al your 
 WS-2000 sensors. Then you install WeeWX with the GW1000 API driver. 
 https://github.com/gjr80/weewx-gw1000

 There is not telnet with the WS-2000. The Interceptor driver will 
 not pick up all your sensorsif you have added optional sensors. 
 Besides 
 with the WS-2000 it is too convoluted to get the Interceptor working 
 because there is no "Customized" server option with the supported 
 protocol 
 for the Interceptor driver. The WS-2000 newly gained "Customized" 
 server 
 upload option but it is Ambient protocol which is different than what 
 the 
 Interceptor expects.


 On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com 
 wrote:

> Hi All, 
>
> I received a weather station for Christmas and realized really 
> quickly that I want / need something like weewx to make it much more 
> capable.
>
> I saw in the list archives that others are using weewx with the 
> WS-2000, intercepting WU data.   Is there another method where weewx 
> polls 
> the WS-2000 or receives data directly from the WS-2000?  I noticed 
> the 
> telnet protocol info on the AW website but haven't figured out which 
> port 
> the WS-2000 is using for this communication?  If I am barking up the 
> wrong 
> tree, please let me know.
>
> BTW, I have a background in computer networking, software 
> development (day job), system administration (day

RE: [weewx-user] Davis VP2 Console Logger Loop 1 vs Loop 2

2021-01-04 Thread Gary Hammer

Thanks Tom, that is what I see and wanted to ensure the field should not be present in Loop 2.  From: Tom KefferSent: Monday, January 4, 2021 10:59 AMTo: weewx-userSubject: Re: [weewx-user] Davis VP2 Console Logger Loop 1 vs Loop 2 The VantagePro2 and VantageVue offer two different types of LOOP packets, dubbed "LOOP 1" and "LOOP 2". The field txBatteryStatus is offered in LOOP 1 packets, but does not appear at all in LOOP 2 packets. What are you seeing?  On Mon, Jan 4, 2021 at 6:45 AM gary@gmail.com  wrote:What is the difference between Loop1 and Loop 2 for WeeWX?I ask because using Loop 2 alone my transmitter battery value is shown as low where the value is Ok with Loop 1. -- You received this message because you are subscribed to the Google Groups "weewx-user" group.To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/bb30d1f1-e868-4ba7-bd14-68124489682an%40googlegroups.com.-- You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/QKcjBgynogI/unsubscribe.To unsubscribe from this group and all its topics, 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/CAPq0zECMmzfcNoFg0exH-sX9hdCLxWqoVN9dzOv-589hAV4vtQ%40mail.gmail.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/31F8AEF4-DCAD-4337-ADCB-CA0772818D1C%40hxcore.ol.

[weewx-user] Re: New to weewx, AW WS-2000

Correct, for power only. You can use any phone charger, USB hub etc. to 
keep it running. Even plug it into a USB port of a Raspberry Pi if you 
have one ...
A good idea will be to have the power source connected to a UPS, as well 
as your weather computer :-), or have it connected to a power-bank which 
you keep on charging - many possibilities.

On 04.01.2021 17:38, George Morgan wrote:
Well I ordered a GW1000.  Now I'm thinking about how to power it.  The 
USB connector is only used for power, right?


On Sun, Jan 3, 2021, 7:52 PM galfert > wrote:


I meant to say water leak not water lead sensor.


On Sunday, January 3, 2021 at 10:51:34 PM UTC-5 galfert wrote:

The WS-2000 does not support more sensors than the GW1000. Its
the other way around. The GW1000 supports every single sensor
that the WS-2000 support, plus it supports sensors from
Ecowitt that Ambient doesn't sell, WH32-EP, WH31-EP, WH45 to
name a few, and Ecowitt is working on some sensors that they
will have before Ambient gets them (new soil moisture with
temperature). The GW1000 also had support for water lead and
lightning many months before the WS-2000.



On Sunday, January 3, 2021 at 8:42:57 PM UTC-5
gm@gmail.com wrote:

Thanks for the link to the chart...I need to look at it
closer but I think my WS-2000 supports more sensors than
the GW1000 so I may be looking at integrating FOSHK
plug-in into weewx directly...unless I'm missing something...

I also need to look at the license for FOSHK plug-in as
that may make this impossible (legally, that is)

On Sat, Jan 2, 2021, 12:40 PM Rainer Lang
 wrote:

It works with all Ambient Weather sensors which are
clones of Fine Offset sensors.

(Ambient also sells non-Fine Offset clone sensors and
weather stations)

What sensors these are, you can see at

https://www.wxforum.net/index.php?topic=40730.0



On 02.01.2021 21:34, George Morgan wrote:

Does the GW1000 work with all the AW sensors?

On Sat, Jan 2, 2021, 11:41 AM galfert
 wrote:

Well there is a way to get from WS-2000 AW
protocol to WeeWX...but you need a translator.
You can use FOSHKplugin and that will convert AW
protocol to Ecowitt protocol and then you can use
the WeeWX Interceptor driver.


On Saturday, January 2, 2021 at 2:17:39 PM UTC-5
gm@gmail.com wrote:

Is there an effort to support the AW protocol
for the WS-2000 server?  As a developer I
would be interested in working on this if it
is documented (and maybe even if it is not). 
My WS-2000 has the latest wifi and base
firmware installed.

I will also look into the GW-1000 and RTL SDR
options.

On Sat, Jan 2, 2021, 9:58 AM galfert
 wrote:

The best way is to buy the GW1000 and
then it will pick up al your WS-2000
sensors. Then you install WeeWX with the
GW1000 API driver.
https://github.com/gjr80/weewx-gw1000


There is not telnet with the WS-2000. The
Interceptor driver will not pick up all
your sensorsif you have added
optional sensors. Besides with the
WS-2000 it is too convoluted to get the
Interceptor working because there is no
"Customized" server option with the
supported protocol for the Interceptor
driver. The WS-2000 newly gained
"Customized" server upload option but it
is Ambient protocol which is different
than what the Interceptor expects.


On Saturday, January 2, 2021 at 10:29:32
AM UTC-5 gm@gmail.com wrote:

Hi All,

I received a weather station for
Christmas and realized really quickly
that I want / need something like

[weewx-user] Re: Adding new folder to Belchertown skin

2021-01-04 Thread Δημήτρης Βήχος

i was create a file in   seasons  skin (you can do also  it in any skin) 
with html variants .my settings.i name my file zwntana.html.tmp for example.
after that edit the skin.conf in [CheetahGenerator] section.
put this
[[Zwntana]] 
 [[[index]]] 
 template = zwntana.html.tmpl

save the file. in next weewx upload data see the zwntana.html  file . 

[image: Screenshot_2021-01-04_18-58-38.png]


Στις Σάββατο, 2 Ιανουαρίου 2021 στις 1:57:56 μ.μ. UTC+2, ο χρήστης 
weatherl...@gmail.com έγραψε:

> I have added a folder to the Belchertown skin containing some html files 
> which are updated daily. The folder has an index.html.tmpl file and adding 
> to the skin.conf [[ToDate]] list creates the folder and generates the 
> index.html page but the HTML files are not updated. How do I configure it 
> so that its contents are automatically uploaded periodically to the 
> HTML_ROOT?

-- 
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/8d3a4d08-2615-4cbf-b8c3-105984f1ff68n%40googlegroups.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

2021-01-04 Thread George Morgan

Well I ordered a GW1000.  Now I'm thinking about how to power it.  The USB
connector is only used for power, right?

On Sun, Jan 3, 2021, 7:52 PM galfert  wrote:

> I meant to say water leak not water lead sensor.
>
>
> On Sunday, January 3, 2021 at 10:51:34 PM UTC-5 galfert wrote:
>
>> The WS-2000 does not support more sensors than the GW1000. Its the other
>> way around. The GW1000 supports every single sensor that the WS-2000
>> support, plus it supports sensors from Ecowitt that Ambient doesn't sell,
>> WH32-EP, WH31-EP, WH45 to name a few, and Ecowitt is working on some
>> sensors that they will have before Ambient gets them (new soil moisture
>> with temperature). The GW1000 also had support for water lead and lightning
>> many months before the WS-2000.
>>
>>
>>
>> On Sunday, January 3, 2021 at 8:42:57 PM UTC-5 gm@gmail.com wrote:
>>
>>> Thanks for the link to the chart...I need to look at it closer but I
>>> think my WS-2000 supports more sensors than the GW1000 so I may be looking
>>> at integrating FOSHK plug-in into weewx directly...unless I'm missing
>>> something...
>>>
>>> I also need to look at the license for FOSHK plug-in as that may make
>>> this impossible (legally, that is)
>>>
>>> On Sat, Jan 2, 2021, 12:40 PM Rainer Lang  wrote:
>>>
 It works with all Ambient Weather sensors which are clones of Fine
 Offset sensors.

 (Ambient also sells non-Fine Offset clone sensors and weather stations)

 What sensors these are, you can see at

 https://www.wxforum.net/index.php?topic=40730.0


 On 02.01.2021 21:34, George Morgan wrote:

 Does the GW1000 work with all the AW sensors?

 On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:

> Well there is a way to get from WS-2000 AW protocol to WeeWX...but you
> need a translator. You can use FOSHKplugin and that will convert AW
> protocol to Ecowitt protocol and then you can use the WeeWX Interceptor
> driver.
>
>
> On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com
> wrote:
>
>> Is there an effort to support the AW protocol for the WS-2000
>> server?  As a developer I would be interested in working on this if it is
>> documented (and maybe even if it is not).  My WS-2000 has the latest wifi
>> and base firmware installed.
>>
>> I will also look into the GW-1000 and RTL SDR options.
>>
>> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>>
>>> The best way is to buy the GW1000 and then it will pick up al your
>>> WS-2000 sensors. Then you install WeeWX with the GW1000 API driver.
>>> https://github.com/gjr80/weewx-gw1000
>>>
>>> There is not telnet with the WS-2000. The Interceptor driver will
>>> not pick up all your sensorsif you have added optional sensors. 
>>> Besides
>>> with the WS-2000 it is too convoluted to get the Interceptor working
>>> because there is no "Customized" server option with the supported 
>>> protocol
>>> for the Interceptor driver. The WS-2000 newly gained "Customized" server
>>> upload option but it is Ambient protocol which is different than what 
>>> the
>>> Interceptor expects.
>>>
>>>
>>> On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com
>>> wrote:
>>>
 Hi All,

 I received a weather station for Christmas and realized really
 quickly that I want / need something like weewx to make it much more
 capable.

 I saw in the list archives that others are using weewx with the
 WS-2000, intercepting WU data.   Is there another method where weewx 
 polls
 the WS-2000 or receives data directly from the WS-2000?  I noticed the
 telnet protocol info on the AW website but haven't figured out which 
 port
 the WS-2000 is using for this communication?  If I am barking up the 
 wrong
 tree, please let me know.

 BTW, I have a background in computer networking, software
 development (day job), system administration (day job), and have been 
 doing
 automation for many years.

 Please let me know if this is a more appropriate question for the
 dev list.

 Happy New Year!


 --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message be

Re: [weewx-user] Re: index.html not updating

2021-01-04 Thread Kevin Davis

Done.  Nothing new in log.

Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Initializing weewx
version 4.2.0
Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Using Python 2.7.13
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Platform
Linux-4.19.66-v7+-armv7l-with-debian-9.13
Jan  4 07:59:09 corbett weewx[32526] INFO __main__: Locale is 'en_US.UTF-8'
Jan  4 07:59:09 corbett weewx[32526] INFO __main__: PID file is
/var/run/weewx.pid
Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Using configuration
file /etc/weewx/weewx.conf
Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Debug is 1
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Loading station
type Vantage (weewx.drivers.vantage)
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: StdConvert target
unit is 0x1
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Archive will use
data binding wx_binding
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Record generation
will be attempted in 'software'
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using archive
interval of 300 seconds (software record generation)
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti: forecast
version 3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Zambretti:
interval=600 max_age=604800 winddir_period=1800 pressure_period=10800
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: forecast version
3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: NWS: interval=10800
max_age=604800 lid=ORZ006 foid=PQR
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WU: forecast version
3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: OWM: forecast version
3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: UKMO: forecast
version 3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: Aeris: forecast
version 3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: WWO: forecast version
3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: DS: forecast version
3.3.2
Jan  4 07:59:09 corbett weewxd: forecast: MainThread: XTide: forecast
version 3.3.2
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: StationRegistry:
Station will be registered.
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: Wunderground:
Posting not enabled.
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: PWSweather: Posting
not enabled.
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: CWOP: Posting not
enabled.
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: WOW: Posting not
enabled.
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.restx: AWEKAS: Posting not
enabled.
Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: service version is 0.23
Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: binding to archive
Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: topic is
corbett/weather
Jan  4 07:59:09 corbett weewx[32531] INFO user.mqtt: data will be uploaded
to mqtt://127.0.0.1:1883
Jan  4 07:59:09 corbett weewx[32531] INFO __main__: Starting up weewx
version 4.2.0
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Clock error is 1.12
seconds (positive is fast)
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.engine: Using binding
'wx_binding' to database 'weewx.sdb'
Jan  4 07:59:09 corbett weewx[32531] INFO weewx.manager: Starting backfill
of daily summaries
Jan  4 07:59:12 corbett weewx[32531] INFO weewx.engine: Starting main
packet loop.
Jan  4 08:00:15 corbett weewx[32531] INFO weewx.manager: Added record
2021-01-04 08:00:00 PST (1609776000) to database 'weewx.sdb'
Jan  4 08:00:15 corbett weewx[32531] INFO weewx.manager: Added record
2021-01-04 08:00:00 PST (1609776000) to daily summary in 'weewx.sdb'
Jan  4 08:00:15 corbett weewxd: forecast: NWSThread: NWS: downloading
forecast from '
http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=PQR
'
Jan  4 08:00:15 corbett weewxd: forecast: ZambrettiThread: Zambretti:
generated 1 forecast record
Jan  4 08:00:15 corbett weewx[32531] INFO weewx.restx: MQTT: Published
record 2021-01-04 08:00:00 PST (1609776000)
Jan  4 08:00:16 corbett weewxd: forecast: NWSThread: NWS: got 38 forecast
records for Scappoose-Columbia OR 45.77N 122.86W Elev. 49 ft
Jan  4 08:00:16 corbett weewx[32531] INFO weewx.restx: StationRegistry:
Published record 2021-01-04 08:00:00 PST (1609776000)
Jan  4 08:00:21 corbett weewx[32531] INFO weewx.cheetahgenerator: Generated
7 files for report SeasonsReport in 5.30 seconds
Jan  4 08:00:25 corbett weewx[32531] INFO weewx.imagegenerator: Generated
28 images for report SeasonsReport in 4.86 seconds
Jan  4 08:00:26 corbett weewx[32531] INFO weewx.reportengine: Copied 87
files to /var/www/html/weewx
Jan  4 08:00:26 corbett weewx[32531] INFO weewx.cheetahgenerator: Generated
6 files for report SmartphoneReport in 0.35 seconds
Jan  4 08:00:28 corbett weewx[32531] INFO

Re: [weewx-user] Davis VP2 Console Logger Loop 1 vs Loop 2

2021-01-04 Thread Tom Keffer

The VantagePro2 and VantageVue offer two different types of LOOP packets,
dubbed "LOOP 1" and "LOOP 2".

The field txBatteryStatus is offered in LOOP 1 packets, but does not appear
at all in LOOP 2 packets. What are you seeing?

On Mon, Jan 4, 2021 at 6:45 AM gary@gmail.com 
wrote:

> What is the difference between Loop1 and Loop 2 for WeeWX?
> I ask because using Loop 2 alone my transmitter battery value is shown as
> low where the value is Ok with Loop 1.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/bb30d1f1-e868-4ba7-bd14-68124489682an%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/CAPq0zECMmzfcNoFg0exH-sX9hdCLxWqoVN9dzOv-589hAV4vtQ%40mail.gmail.com.

Re: [weewx-user] Re: CentOS is on shakey ground

2021-01-04 Thread WindnFog

The reason I switched from Fedora to CentOS was stability.  Now that weewx 
is running on Raspbian and that's stable, there's no reason not to use 
Fedora for other things.  I like the familiarity of the 
RedHat/Fedora/CentOS distros, and the new "bells and whistles" introduced 
in Fedora are indeed attractive.  Perhaps that is a better choice for 
day-to-day Linux than Ubuntu LTS.

- Paul VE1DX

On Monday, January 4, 2021 at 7:52:32 AM UTC-4 mjenk...@gmail.com wrote:

> Go back and look at Fedora again if you haven't used it in the last few 
> years.It's better than it used to be and is worth a look.
>
> On Sunday, January 3, 2021 at 4:56:37 PM UTC-6 WindnFog wrote:
>
>> I suspect a lot of web hosting companies use CentOS.  The outfit I was 
>> with in Florida sure did. No doubt there’s going to be a scramble to get 
>> Rocky Linux or equivalent going quickly. 
>>
>> I am now hosting my weewx website on a VPS now using Ubuntu and Apache. 
>>  That way I have full control and don’t have to pay a fortune for someone 
>> else to do it.  It cost me $50 USD for the TLS certificate alone! Now I get 
>> my own and install it for free.  I used to use Fedora, but it’s really a 
>> beta version for RedHat and I got tired of the incessant bug fixes and 
>> updates.  CentOS was a great solution as it was familiar and mature. 
>>
>> Anyway, I guess this is not really weewx related. 
>>
>> - Paul VE1DX 
>>
>> On Jan 3, 2021, at 6:20 PM, Mark Jenks  wrote:
>>
>> I use CentOS for everything, except my home server.At home I use 
>> Fedora, since it's RedHat based..
>>
>>
>>
>> On Sunday, January 3, 2021 at 12:48:56 PM UTC-6 WindnFog wrote:
>>
>>> I may have been the only one using CentOS for weewx (before switching to 
>>> a Raspberry Pi about a year ago.)  I note it's still mentioned as a distro 
>>> in the weewx documentation, with RedHat and Fedora.  CentOS was to be 
>>> supported until 31 May 2029. 
>>>
>>> Since the takeover of RedHat by IBM, this has been shortened to 31 
>>> December 2021.  If anyone is still using CentOS for weewx, it's probably a 
>>> good idea to migrate to another distro soon.  There's a movement to replace 
>>> CentOS with "Rocky Linux", but there's no timeframe for its deployment:
>>>
>>> https://wiki.rockylinux.org/
>>>
>>> The "strength" of CentOS was stability because it is a clone of RedHat.  
>>> I still use CentOS for other things than weewx, and rather than wait to see 
>>> if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
>>> least 5 years of support/stability.
>>>
>>> - Paul VE1DX
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/0xzffO8ddEE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d86315f0-d75f-4ff6-924f-aa023c28a8fcn%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/a9bccd85-f2b1-404a-ae64-5110f0514650n%40googlegroups.com.

[weewx-user] Davis VP2 Console Logger Loop 1 vs Loop 2

2021-01-04 Thread gary....@gmail.com

What is the difference between Loop1 and Loop 2 for WeeWX?
I ask because using Loop 2 alone my transmitter battery value is shown as 
low where the value is Ok with Loop 1.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bb30d1f1-e868-4ba7-bd14-68124489682an%40googlegroups.com.

Re: [weewx-user] Re: Weird Barometric Pressure Analysis from Gladstone (CWOP)

2021-01-04 Thread Chris Maness

Thank you sir.

Chris Maness

On Sun, Jan 3, 2021 at 9:48 PM galfert  wrote:

> It is the fault of all your neighbors with poorly calibrated stations. All
> you can do is reach out to all of your neighbors that you feel have done a
> poor job in calibrating their station. You all affect each other.
>
> Your neighbors:
> http://www.findu.com/cgi-bin/wxnear.cgi?call=KQ6UP
>
> Email contact search:
> http://wxqa.com/search.htm
>
>
> On Sunday, January 3, 2021 at 11:58:00 PM UTC-5 ch...@chrismaness.com
> wrote:
>
>> This is a little off topic, but if you look at the attached screenshot,
>> you will see that the predicted barometric pressure by which I am
>> supposed to check my barometric pressure readings oscillate wildly.
>> Anyone seen this before?  What forum or person should I contact to
>> figure out how to get this fixed?  I do believe it is on their end --
>> not mine.
>>
>> Thanks,
>>
>> Chirs KQ6UP
>>
>> --
> 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/b3d31520-1ea9-4db3-a687-f7d95d418d6cn%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/CANnsUMHesxrC1QPJxVSK7%3DYFRYhJ_%2Bcanao9Kt0bv7CC4nUsJw%40mail.gmail.com.

[weewx-user] Re: ignore_zero_wind not working in 4.2.0

Hi Greg,

When 4.3.0 is released shortly you will find the [StdWXCalculate] stanza in 
weewx.conf has been restructured and the previously undocumented settings 
documented. ignore_zero_wind has been deprecated and replaced by a new 
structure and config option force_null. ignore_zero_wind will continue to 
be supported for now though.

The upgrade process to 4.3.0 should take care of things, but if you are an 
‘ignore_zero_wind user’ I would strongly suggest reading the upgrade guide 
closely this time around.

Gary

On Monday, 4 January 2021 at 15:48:19 UTC+10 G Smith wrote:

> Hi, Gary.
> I have also been affected by this change and, fortunately, your solution 
> fixed my problem.  Do you know if this is a temporary regression that will 
> require me to change my .conf again (back to the pre-4.2.0 way) in the near 
> future?  Or is this expected to be a permanent change?
>
> Thanks!
> -- Greg
>
> On Tuesday, November 17, 2020 at 12:52:40 AM UTC-5 gjr80 wrote:
>
>> Bill,
>>
>> There was a change to the StdWXCalculate service in 4.2.0 that has 
>> inadvertently changed the operation of ignore_zero_wind. Normal (expected) 
>> operation should resume if you change the ignore_zero_wind setting to be 
>> the opposite of its current value (ie if under 4.1.1 or earlier you 
>> had ignore_zero_wind = False change it to ignore_zero_wind = True or if you 
>> had ignore_zero_wind = True change it to ignore_zero_wind = False).
>>
>> If you don’t use ignore_zero_wind you are not affected by the change and 
>> need do nothing.
>>
>> Gary
>>
>> On Tuesday, 17 November 2020 at 14:20:55 UTC+10 wa4...@gmail.com wrote:
>>
>>> I have three pi's running weewx, two have been moved up to 4.2.0, one is 
>>> still on 4.1.1. All have ignore_zero_wind set to False. The two that are on 
>>> 4.2.0 no longer work as expected (zero wind shows wind direction) but the 
>>> 4.1.1 still works as expected.
>>>
>>> Did something happen in 4.2.0 that changed the behavior of 
>>> ignore_zero_wind = False?
>>
>>

-- 
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/f4d82c40-7a98-42b4-9467-df48e85415e9n%40googlegroups.com.

Re: [weewx-user] Re: CentOS is on shakey ground

2021-01-04 Thread Mark Jenks

Go back and look at Fedora again if you haven't used it in the last few 
years.It's better than it used to be and is worth a look.

On Sunday, January 3, 2021 at 4:56:37 PM UTC-6 WindnFog wrote:

> I suspect a lot of web hosting companies use CentOS.  The outfit I was 
> with in Florida sure did. No doubt there’s going to be a scramble to get 
> Rocky Linux or equivalent going quickly. 
>
> I am now hosting my weewx website on a VPS now using Ubuntu and Apache. 
>  That way I have full control and don’t have to pay a fortune for someone 
> else to do it.  It cost me $50 USD for the TLS certificate alone! Now I get 
> my own and install it for free.  I used to use Fedora, but it’s really a 
> beta version for RedHat and I got tired of the incessant bug fixes and 
> updates.  CentOS was a great solution as it was familiar and mature. 
>
> Anyway, I guess this is not really weewx related. 
>
> - Paul VE1DX 
>
> On Jan 3, 2021, at 6:20 PM, Mark Jenks  wrote:
>
> I use CentOS for everything, except my home server.At home I use 
> Fedora, since it's RedHat based..
>
>
>
> On Sunday, January 3, 2021 at 12:48:56 PM UTC-6 WindnFog wrote:
>
>> I may have been the only one using CentOS for weewx (before switching to 
>> a Raspberry Pi about a year ago.)  I note it's still mentioned as a distro 
>> in the weewx documentation, with RedHat and Fedora.  CentOS was to be 
>> supported until 31 May 2029. 
>>
>> Since the takeover of RedHat by IBM, this has been shortened to 31 
>> December 2021.  If anyone is still using CentOS for weewx, it's probably a 
>> good idea to migrate to another distro soon.  There's a movement to replace 
>> CentOS with "Rocky Linux", but there's no timeframe for its deployment:
>>
>> https://wiki.rockylinux.org/
>>
>> The "strength" of CentOS was stability because it is a clone of RedHat.  
>> I still use CentOS for other things than weewx, and rather than wait to see 
>> if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
>> least 5 years of support/stability.
>>
>> - Paul VE1DX
>>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/0xzffO8ddEE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/d86315f0-d75f-4ff6-924f-aa023c28a8fcn%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/128b4862-b0a3-49d0-ba43-8d12b49f7f44n%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

2021-01-04 Thread Joe

  GNU nano 3.2  
  syslog

  


Here is the log


Jan  4 00:25:33 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
Published record 2021-01-04 00:25:33 CST (1609741533)
Jan  4 00:25:35 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
Published record 2021-01-04 00:25:35 CST (1609741535)
Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.imagegenerator: Generated 
13 images for report StandardReport in 8.04 seconds
Jan  4 00:25:36 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
files to /var/www/weewx
Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Jan  4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
Jan  4 00:25:37 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
Published record 2021-01-04 00:25:49 CST (1609741549)
Jan  4 00:25:49 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 12.96 seconds
Jan  4 00:25:49 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.imagegenerator: Generated 
14 images for report SeasonsReport in 7.65 seconds
Jan  4 00:25:57 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
files to /var/www/weewx
Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
report 'SmartphoneReport'
Jan  4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
'SmartphoneReport'
Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 00:25:58 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
Generated 6 files for report SmartphoneReport in 0.75 seconds
Jan  4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
version is 2Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.restx: 
Wunderground-RF: Published record 2021-01-04 00:26:01 CST (1609741561)
Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.imagegenerator: Generated 
6 images for report SmartphoneReport in 3.04 seconds
Jan  4 00:26:01 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
files to /smartphone
Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
report 'MobileReport'
Jan  4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Mobile/skin.conf for report 
'MobileReport'
Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$
Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 00:26:02 raspberrypi weewx[677] INFO weewx.cheetahgenerator: 
Generated 1 files for report MobileReport in 0.29 seconds
Jan  4 00:26:02 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary 
version is 2
Jan  4 00:26:03 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: 
Published record 2021-01-04 00:26:03 CST (1609741563)
Jan  4 00:26:04 raspberrypi weewx[677] INFO weewx.imagegenerator: Generated 
4 images for report MobileReport in 2.06 seconds
Jan  4 00:26:04 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 
files to /mobile
Jan  4 00:26:04 raspberrypi weewx[677] DEBUG weewx.reportengine: Running 
report 'FTP'
Jan  4 00:26:04 raspberrypi weewx[677] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'

Jan  4 00:26:05 raspberrypi weewx[677] DEBUG weeutil.ftpupload: Uploaded 
file /var/www/weewx/daywindvec.png to /daywindvec.png
Jan  4 00:26:06 raspberrypi weewx[677] DEBUG weeutil.ftpupload: Uploaded 
file /var/www/weewx/daywind.png to /daywind.png
Jan  4 00:26:06 raspberrypi weewx[677] DEBUG weeutil.ftpupload: Uploaded 
file /var/www/weewx/celestial.html to /celestial.html
Jan  4 00:26:06 raspberrypi weewx[677] DEBUG weeutil.ftpupload: Uploaded 
file /var/www/weewx/tabular.html to /tabular.html
Jan  4 00:26:07 raspberrypi weewx[677] DEBUG weeutil.ftpupload: Uploa

Re: [weewx-user] Re: index.html not updating