[weewx-user] Re: Steel Series Gauges and RealTime update - 2.5 second interval - how?

2017-02-17 Thread tempus 
On Tuesday, February 14, 2017 at 7:48:18 AM UTC-8, tempus wrote:
>
> On Tuesday, February 14, 2017 at 6:47:13 AM UTC-8, tempus wrote:
>>
>> Gosh - First mistake you ever made!!!
>>
>> I will try the fix. Thanks for your quick response.
>>
>> Bob
>>
>> On Tuesday, February 14, 2017 at 4:40:50 AM UTC-8, mwall wrote:
>>>
>>> sorry, again.  please use crt-0.20rc2.py
>>>
>>>
> crt-0.20rc2.py has only been running a few minutes, but seems to work. 
> Thanks for the fix..
>  
> Bob
>
> I left on a trip right after upgrading to 0.20 rc2 and the gauges had 
starting working.  Since arriving back last night gauge temperatures are 
-20 degrees, pressure is 990, and everything else is zero, like before the 
upgrade.  realtimegaugesT.txt is still updating at approximately 2.5 second 
intervals and the data looks valid, but it isn't getting to the gauges.

Any ideas?

-Bob
 

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

[weewx-user] Introducing the Growing Degree Days (GDD Base10 °C)

2017-02-17 Thread José Miguel Castellet Martí 


I introduced the Growing Degree Days (GDD) Base10 (°C) in weewx. To do 
that, I created a new template, NOAA--MM_ampliado.txt.tmpl, to produce 
the MONTHLY CLIMATOLOGICAL EXTENDED SUMMARY NOAA file, based on the 
standard NOAA--MM.txt.tmpl (MONTHLY CLIMATOLOGICAL SUMMARY).  As you 
can see, it contains several additional variables already available in 
weewx.

You can see the result in 
http://www3.uji.es/~pepe/weewx/NOAA/NOAA-2017-02_ampliado.txt

The modified code (*see bold characters*) in the 
NOAA--MM_ampliado.txt.tmpl is:

…

   TEMPERATURE ($unit.label.outTemp.strip()), RAIN 
($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip()), 
HUMIDITY ($unit.label.outHumidity.strip()), BAROMETER 
($unit.label.barometer.strip()), *Growing Degree Days/GDD Base10 
($unit.label.outTemp.strip())*

DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH   
TIMEDIR  HUMID   HIGH   TIMELOW   TIME  BAROM   HIGH   TIME
LOW   TIME*GDD*

-
*---*

## jmcm mie 11 ene 2017 21:50:00 CET calculo el acumulado mensual GDD (suma 
te’rmica, ST)

*#set $monthGDD=0*

*##*

#for $day in $month.days

#if $day.barometer.count.raw

*#if $day.outTemp.avg.raw>10*

*#if $day.outTemp.avg.raw<30*

*#set $GDD=$day.outTemp.avg.raw-10*

*#else*

*#set $GDD=20*

*#end if*

*#else*

*#set $GDD=0*

*#end if*

*#set $monthGDD=$monthGDD+$GDD*

##

$day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE) 
$day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time) 
$day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time) 
$day.heatdeg.sum.nolabel($Te

mp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE) 
$day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE) 
$day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time) 
$day.wind.vecdir.nolabel($Dir,$NONE) $day.outHumidit

y.avg.nolabel($Humid,$NONE) $day.outHumidity.max.nolabel($Humid,$NONE) 
$day.outHumidity.maxtime.format($Time) 
$day.outHumidity.min.nolabel($Humid,$NONE) 
$day.outHumidity.mintime.format($Time) 
$day.barometer.avg.nolabel($Barom,$NONE) $day

.barometer.max.nolabel($Barom,$NONE) $day.barometer.maxtime.format($Time) 
$day.barometer.min.nolabel($Barom,$NONE) 
$day.barometer.mintime.format($Time) *#echo ('%6.2f' % $GDD).replace('.', 
',')#*

#else

$day.dateTime.format($D)

#end if

#end for



$month.outTemp.avg.nolabel($Temp,$NONE) 
$month.outTemp.max.nolabel($Temp,$NONE)
$month.outTemp.maxtime.format($D) 
$month.outTemp.min.nolabel($Temp,$NONE)
$month.outTemp.mintime.format($D) $month.heatdeg.sum.nolabel($Temp,$NONE)

 $month.cooldeg.sum.nolabel($Temp,$NONE) 
$month.rain.sum.nolabel($Rain,$NONE) $month.wind.avg.nolabel($Wind,$NONE) 
$month.wind.max.nolabel($Wind,$NONE)$month.wind.maxtime.format($D) 
$month.wind.vecdir.nolabel($Dir) $month.outHumidity

.avg.nolabel($Humid,$NONE) $month.outHumidity.max.nolabel($Humid,$NONE)
$month.outHumidity.maxtime.format($D) 
$month.outHumidity.min.nolabel($Humid,$NONE)
$month.outHumidity.mintime.format($D) $month.barometer.avg.nolabel($Barom,$N

ONE) $month.barometer.max.nolabel($Barom,$NONE)
$month.barometer.maxtime.format($D) 
$month.barometer.min.nolabel($Barom,$NONE)
$month.barometer.mintime.format($D) *#echo ('%6.2f' % 
$monthGDD).replace('.', ',')#*


Hope that helps ;-)

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

RE: [weewx-user] acurite lightning detector

2017-02-17 Thread Clay Jackson 
And I just talked to Acurite – read them the “QC” number off the battery cover 
and they said “we’re sending you a new one”.  :)

 

 

From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On 
Behalf Of Clay Jackson
Sent: Friday, February 17, 2017 11:28 AM
To: weewx-user@googlegroups.com
Subject: RE: [weewx-user] acurite lightning detector

 

Just did the “hard reset” routine – left batteries out for several hours.   The 
sensor is in a room where the tempo ranges from about 64-75.   Last night, for 
about 2 hours, it APPEARED to be reading OK – fluctuating right around 65, in 
line with a mercury thermometer I use for testing.   Came in this morning, it 
started a few degrees low (61 – mercury was 66) but has since climbed WAY 
above, mercury reading 75, sensor reading 87.8

 

Other than a bad sensor, anyone have any ideas?

 

Thanks in advance!

Clay Jackson

 

 

From: weewx-user@googlegroups.com   
[mailto:weewx-user@googlegroups.com] On Behalf Of Clay Jackson
Sent: Thursday, February 16, 2017 3:20 PM
To: weewx-user@googlegroups.com  
Subject: Re: [weewx-user] acurite lightning detector

 

Downloaded and it's now capturing - temp is way off (30+ degrees high); but I 
suspect that's either an RTL or Acurite issue

Sent from my iPhone

Clay Jackson

 


On Feb 16, 2017, at 12:21 PM, Clay Jackson  > wrote:

Hi, Matt – so, here’s what I see in weewx.log

 

Feb 16 12:18:41 Weather weewx[14361]: sdr: MainThread: AcuriteLightningPacket: 
unrecognized data: '2017-02-16 20:18:41 Acurite lightning 0x2B6F Ch A Msg Type 
0x4f: 67 C 66 % RH Strikes 3 Distance 31 - c0  2b  6f  42  cf  c3  03  9f  
d0*#012'

 

And here’s the SDR part of my config

[SDR]

# This section is for the software-defined radio driver.

 

# The driver to use

driver = user.sdr

path = /usr/local/bin

[[sensor_map]]

windDir = wind_dir.04C9.Acurite5n1Packet

windSpeed = wind_speed.04C9.Acurite5n1Packet

outTemp = temperature.04C9.Acurite5n1Packet

outHumidity = humidity.04C9.Acurite5n1Packet

rain_total = rain_total.04C9.Acurite5n1Packet

extraTemp1 = temperature.2B6F.AcuriteLightningPacket

extraHumid1 = humidity.2B6F.AcuriteLightningPacket

strikes = strikes_total.2B6F.AcuriteLightningPacket

[[deltas]]

strikes = strikes_total

Haven’t done a debug yet;  but will report that next.

 

From: weewx-user@googlegroups.com   
[mailto:weewx-user@googlegroups.com] On Behalf Of mwall
Sent: Tuesday, February 14, 2017 6:52 AM
To: weewx-user  >
Subject: [weewx-user] acurite lightning detector

 

>From: Clay Jackson
>Subject: Acurite Lighning Sensor
>Date: 13 February 2017 23:21:23 EST
>
> Hi, Matthew – new topic/question.   I have one of the Acurite Lighting 
> sensors and would like to
> integrate it into the weewx SDR.  It looks right now as if it’s not really 
> supported. I tried just
> mapping the senors and got some screwy results (see an earlier post).  Then I 
> went back
> and read the code; and it looks like the RTL driver is just dumping data, 
> rather than doing
> a “real” decode.   I’d be happy to work with you on seeing if we can get it 
> working – let me
> know if you’d like to try that.
> 
> Thanks!
> 
> Clay Jackson

clay,

this is typical output from the lightning detector, as returned by rtl_433:

2016-11-04 04:34:58 Acurite lightning 0x536F Ch A Msg Type 0x51: 15 C 58 % RH 
Strikes 50 Distance 69 - c0  53  6f  3a  d1  0f  b2  c5  13*
2016-11-04 04:43:14 Acurite lightning 0x536F Ch A Msg Type 0x51: 15 C 58 % RH 
Strikes 55 Distance 5 - c0  53  6f  3a  d1  0f  b7  05  58*

with a SDR configuration and sensor_map like this:

[SDR]
driver = user.sdr
cmd = rtl_433 -q -U -G -F json
[[sensor_map]]
windDir = wind_dir.0BFA.Acurite5n1Packet
windSpeed = wind_speed.0BFA.Acurite5n1Packet
outTemp = temperature.0BFA.Acurite5n1Packet
outHumidity = humidity.0BFA.Acurite5n1Packet
outTempBatteryStatus = battery.0BFA.Acurite5n1Packet
inTemp = temperature.24A4.AcuriteTowerPacket
inHumidity = humidity.24A4.AcuriteTowerPacket
txBatteryStatus = battery.24A4.AcuriteTowerPacket
extraTemp2 = temperature.526F.AcuriteLightningPacket
extraHumid2 = humidity.526F.AcuriteLightningPacket
distance = distance.526F.AcuriteLightningPacket
strikes_total = strikes_total.526F.AcuriteLightningPacket
[[deltas]]
strikes = strikes_total

the weewx-sdr driver parses lightning sensor output into packets something like 
this:

LOOP:   2017-02-14 09:50:31 EST (1487083831) altimeter: None, appTemp: None, 
barometer: None, cloudbase: None, dateTime: 1487083831, dewpoint: None, 
distance: 15.0,

RE: [weewx-user] acurite lightning detector

2017-02-17 Thread Clay Jackson 
Just did the “hard reset” routine – left batteries out for several hours.   The 
sensor is in a room where the tempo ranges from about 64-75.   Last night, for 
about 2 hours, it APPEARED to be reading OK – fluctuating right around 65, in 
line with a mercury thermometer I use for testing.   Came in this morning, it 
started a few degrees low (61 – mercury was 66) but has since climbed WAY 
above, mercury reading 75, sensor reading 87.8

 

Other than a bad sensor, anyone have any ideas?

 

Thanks in advance!



Clay Jackson

 

 

From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On 
Behalf Of Clay Jackson
Sent: Thursday, February 16, 2017 3:20 PM
To: weewx-user@googlegroups.com
Subject: Re: [weewx-user] acurite lightning detector

 

Downloaded and it's now capturing - temp is way off (30+ degrees high); but I 
suspect that's either an RTL or Acurite issue

Sent from my iPhone

Clay Jackson

 


On Feb 16, 2017, at 12:21 PM, Clay Jackson  > wrote:

Hi, Matt – so, here’s what I see in weewx.log

 

Feb 16 12:18:41 Weather weewx[14361]: sdr: MainThread: AcuriteLightningPacket: 
unrecognized data: '2017-02-16 20:18:41 Acurite lightning 0x2B6F Ch A Msg Type 
0x4f: 67 C 66 % RH Strikes 3 Distance 31 - c0  2b  6f  42  cf  c3  03  9f  
d0*#012'

 

And here’s the SDR part of my config

[SDR]

# This section is for the software-defined radio driver.

 

# The driver to use

driver = user.sdr

path = /usr/local/bin

[[sensor_map]]

windDir = wind_dir.04C9.Acurite5n1Packet

windSpeed = wind_speed.04C9.Acurite5n1Packet

outTemp = temperature.04C9.Acurite5n1Packet

outHumidity = humidity.04C9.Acurite5n1Packet

rain_total = rain_total.04C9.Acurite5n1Packet

extraTemp1 = temperature.2B6F.AcuriteLightningPacket

extraHumid1 = humidity.2B6F.AcuriteLightningPacket

strikes = strikes_total.2B6F.AcuriteLightningPacket

[[deltas]]

strikes = strikes_total

Haven’t done a debug yet;  but will report that next.

 

From: weewx-user@googlegroups.com   
[mailto:weewx-user@googlegroups.com] On Behalf Of mwall
Sent: Tuesday, February 14, 2017 6:52 AM
To: weewx-user  >
Subject: [weewx-user] acurite lightning detector

 

>From: Clay Jackson
>Subject: Acurite Lighning Sensor
>Date: 13 February 2017 23:21:23 EST
>
> Hi, Matthew – new topic/question.   I have one of the Acurite Lighting 
> sensors and would like to
> integrate it into the weewx SDR.  It looks right now as if it’s not really 
> supported. I tried just
> mapping the senors and got some screwy results (see an earlier post).  Then I 
> went back
> and read the code; and it looks like the RTL driver is just dumping data, 
> rather than doing
> a “real” decode.   I’d be happy to work with you on seeing if we can get it 
> working – let me
> know if you’d like to try that.
> 
> Thanks!
> 
> Clay Jackson

clay,

this is typical output from the lightning detector, as returned by rtl_433:

2016-11-04 04:34:58 Acurite lightning 0x536F Ch A Msg Type 0x51: 15 C 58 % RH 
Strikes 50 Distance 69 - c0  53  6f  3a  d1  0f  b2  c5  13*
2016-11-04 04:43:14 Acurite lightning 0x536F Ch A Msg Type 0x51: 15 C 58 % RH 
Strikes 55 Distance 5 - c0  53  6f  3a  d1  0f  b7  05  58*

with a SDR configuration and sensor_map like this:

[SDR]
driver = user.sdr
cmd = rtl_433 -q -U -G -F json
[[sensor_map]]
windDir = wind_dir.0BFA.Acurite5n1Packet
windSpeed = wind_speed.0BFA.Acurite5n1Packet
outTemp = temperature.0BFA.Acurite5n1Packet
outHumidity = humidity.0BFA.Acurite5n1Packet
outTempBatteryStatus = battery.0BFA.Acurite5n1Packet
inTemp = temperature.24A4.AcuriteTowerPacket
inHumidity = humidity.24A4.AcuriteTowerPacket
txBatteryStatus = battery.24A4.AcuriteTowerPacket
extraTemp2 = temperature.526F.AcuriteLightningPacket
extraHumid2 = humidity.526F.AcuriteLightningPacket
distance = distance.526F.AcuriteLightningPacket
strikes_total = strikes_total.526F.AcuriteLightningPacket
[[deltas]]
strikes = strikes_total

the weewx-sdr driver parses lightning sensor output into packets something like 
this:

LOOP:   2017-02-14 09:50:31 EST (1487083831) altimeter: None, appTemp: None, 
barometer: None, cloudbase: None, dateTime: 1487083831, dewpoint: None, 
distance: 15.0, extraHumid2: 35.0, extraTemp2: 55.4, heatindex: None, humidex: 
None, inDewpoint: None, maxSolarRad: None, rainRate: 0, strikes: 0.0, 
strikes_total: 61.0, usUnits: 1, windchill: None

is that what you see?

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com

Re: [weewx-user] Name of "day of week"

2017-02-17 Thread Thomas Keffer 
How about (NOT TESTED):

#set $day=$current.dateTime.format("%A")

The day of the week is $day.capitalize()

-tk


On Fri, Feb 17, 2017 at 3:15 AM, Ruben Navarro Huedo 
wrote:

> Hello:
>
> I have been reading customization guide but i don't find how i could do
> this.
>
> Using $week.barometer.maxtime (or other $week.* variables) in a template
> gives me this result:
>
> 14:56:03 (martes)
>
> I know i can change time format in skin.conf but i want to have the name
> of day (martes) with capital letter in the beginning.
>
> Can i do this? How?
>
> A lot of thank's
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: Name of "day of week"

2017-02-17 Thread Ruben Navarro Huedo 
A lot of thanks 
Do you know if locale can be edited?

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

[weewx-user] Re: WMRS200 : wrong rainBatteryStatus values in database

2017-02-17 Thread wysiwyg 
Hello !

does the wmrs200 base station provide any indication of battery status? => 
No, there are only 4 red lights on it, just saying if a sensor is connected 
or not.

does the software that comes with wmrs200 provide battery status 
indicators? => No idea my last windows PC died 10years ago never 
used the Oregon software, only vview and now weewx since a couple of years

But I do have a WMR86 console (that as no USB or anything else to connect, 
pure display): it does show a low battery pic when battery is low for a 
sensor , just like all other sensors: only 1 or 0.

Best regards,
Frederic



Le jeudi 16 février 2017 22:30:46 UTC+1, mwall a écrit :
>
> On Thursday, February 16, 2017 at 3:12:11 AM UTC-5, wysiwyg wrote:
>>
>> Hello ! 
>>
>> While checking out some improvement of my battery monitoring, I notice 
>> some value of rainBatteryStatus higher then 1 !
>> ...
>> isn't it a bit weird ?
>>
>
> does the wmrs200 base station provide any indication of battery status?
>
> does the software that comes with wmrs200 provide battery status 
> indicators?
>
> if so, do these show a binary value ('ok' and 'not ok'), or something else?
>
> m
>

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

[weewx-user] Re: Name of "day of week"

2017-02-17 Thread gjr80 
Hi,

I am no Spanish or locale expert but of the searching I just did all the 
Spanish days of the week were shown as lower case only. Secondly, and 
probably most telling, setting the python locale to es_ES.UTF-8 lists the 
days of the week as 

['lunes', 'martes', 'mi\xc3\xa9rcoles', 'jueves', 'viernes', 's\xc3\xa1bado'
, 'domingo']

I suspect that the only way you will get initial capitals is to manually 
format them yourself with a little in-line python.

Gary

On Friday, 17 February 2017 21:15:33 UTC+10, Ruben Navarro Huedo wrote:
>
> Hello:
>
> I have been reading customization guide but i don't find how i could do 
> this.
>
> Using $week.barometer.maxtime (or other $week.* variables) in a template 
> gives me this result:
>
> 14:56:03 (martes)
>
> I know i can change time format in skin.conf but i want to have the name 
> of day (martes) with capital letter in the beginning.
>
> Can i do this? How?
>
> A lot of thank's
>
>
>

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

[weewx-user] Re: Name of "day of week"

2017-02-17 Thread Andrew Milner 
what format are you actually using??  I think that %a and %A should be 
capitalised by default when used in strftime strings.

On Friday, 17 February 2017 13:15:33 UTC+2, Ruben Navarro Huedo wrote:
>
> Hello:
>
> I have been reading customization guide but i don't find how i could do 
> this.
>
> Using $week.barometer.maxtime (or other $week.* variables) in a template 
> gives me this result:
>
> 14:56:03 (martes)
>
> I know i can change time format in skin.conf but i want to have the name 
> of day (martes) with capital letter in the beginning.
>
> Can i do this? How?
>
> A lot of thank's
>
>
>

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

[weewx-user] Name of "day of week"

2017-02-17 Thread Ruben Navarro Huedo 
Hello:

I have been reading customization guide but i don't find how i could do 
this.

Using $week.barometer.maxtime (or other $week.* variables) in a template 
gives me this result:

14:56:03 (martes)

I know i can change time format in skin.conf but i want to have the name of 
day (martes) with capital letter in the beginning.

Can i do this? How?

A lot of thank's


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