Re: [weewx-user] Purple-Air causes imagegenerator crash in 5.0.2 but not in 4

[Clay Jackson]

This version works perfectly!

On Monday, April 29, 2024 at 6:39:44 PM UTC-7 John Kline wrote:

> It’s my extension.  MySQL doesn’t like the select when 
> sql_mode=only_full_group_by.
>
> clayj, please replace purple.py with the attached file.  If it works for 
> you, I’ll release it as v3.9.2.
>
>

-- 
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/79503a55-1a42-43db-9122-3225604af037n%40googlegroups.com.

[weewx-user] Purple-Air causes imagegenerator crash in 5.0.2 but not in 4

[Clay Jackson]

I'm updating from WeeWx Version 4 to 5.0.2 and when I do, the sample 
dashboard for Purple causes imgagegenerator to crash - here's the output 
from syslog.

Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  (1140, 
"In aggregated query without GROUP BY, expression #2 
 of SELECT list 
contains nonaggregated column 'weewx.archive.usUnits
'; this is incompatible with sql_mode=only_full_group_by")
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
Traceback (most recent call last):
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/weewx/xtypes.py", line 
109, in get_series
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  return 
xtype.get_series(obs_type, timespan, db_manager, aggregate_type,
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
TypeError: AQI.get_series() got an unexpected keyword argument 'SKIN_ROOT'
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine: 
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  During 
handling of the above exception, another exception occurred:
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine: 
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
Traceback (most recent call last):
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line 
53, in guarded_fn
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  return 
fn(*args, **kwargs)
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line 
247, in execute
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
self.cursor.execute(mysql_string, tuple(sql_tuple))
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/cursors.py", 
line 153, in execute
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  result = 
self._query(query)
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/cursors.py", 
line 322, in _query
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
conn.query(q)
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", 
line 558, in query
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", 
line 822, in _read_query_result
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
result.read()
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", 
line 1200, in read
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  
first_packet = self.connection._read_packet()
Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", 
line 772, in _read_packet
Apr 29 16:26:12 weewx python3[2282]: Traceback (most recent call last):
Apr 29 16:26:12 weewx python3[2282]: File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/weewx/xtypes.py", line 
109, in get_series
Apr 29 16:26:12 weewx python3[2282]: return xtype.get_series(obs_type, 
timespan, db_manager, aggregate_type,
Apr 29 16:26:12 weewx python3[2282]: TypeError: AQI.get_series() got an 
unexpected keyword argument 'SKIN_ROOT'
Apr 29 16:26:12 weewx python3[2282]: During handling of the above 
exception, another exception occurred:
Apr 29 16:26:12 weewx python3[2282]: Traceback (most recent call last):
Apr 29 16:26:12 weewx python3[2282]: File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line 
53, in guarded_fn
Apr 29 16:26:12 weewx python3[2282]: return fn(*args, **kwargs)
Apr 29 16:26:12 weewx python3[2282]: File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line 
247, in execute
Apr 29 16:26:12 weewx python3[2282]: self.cursor.execute(mysql_string, 
tuple(sql_tuple))
Apr 29 16:26:12 weewx python3[2282]: File 
"/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/cursors.py", 
line 153, in execute
Apr 29 16:26:12 weewx python3[2282]: result = self._query(query)
Apr 29 16:26:12 weewx python3[2282]: File 

[weewx-user] A tale of two radios (reception issues)

[Clay Jackson]

I have two weewx servers running - one for "development" and one that runs 
my "real" web site. (www.n7qnm.net/weewx).I'm running 4.5.1 on the real 
site, and 4.8.0 in my dev environment.   The two Raspbberry Pi's are 
located within 10' of each other.

On the production system, I have an NESDR SmarTee V1 radio.   On the Dev 
system, I HAD a NooElec R820T NESDR mini.

I'm in an "rf rich" environment.   I have at least 10 433Mhz sensors, an 
Amateur Radio Repeater on 442.300 and there are close to 100 WiFi 
"emitters" (router and clients) on 2.5 and 5 Ghz within "hearing range".

After I added "yet another 433Mhz sensor", my dev system started throwing 
"wild" decodes for rain, lighting strikes and wind (1000 lightning strikes 
in a 5 min period, 100 inches of rain, 90 Mph wind gusts).  I tried 
swapping locations and antennas, but the problem stayed with the Dev 
system.  

After some tracing and discussions on the RTL and SDR mailing lists, I 
decided to try a new radio for my Dev system.   Got a SmarTee V2, and the 
problem has cleared up.

>From specs, it looks like the SmarTee's use 820T2 and the Mini uses an 
820T.'

Granted, it's not really "scientific"; but at least in this one case, "You 
get what you pay for".


-- 
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/262cdf62-681a-42ac-9823-b7304ef1a4f7n%40googlegroups.com.

[weewx-user] Lighting Strikes erroneous count

[Clay Jackson]

I've got an Accurite lightning sensor. right now feeding WeeWx 4.8 and also 
4.5.1.  It's configured like this:

strikes_total = strikes_total.002B.AcuriteLightningPacket
[[deltas]]
lightning_strike_count = strikes_total

In 4.5.1,  I see no strikes, but during the same time period, 4.8 reports 
seemingly RANDOM strike counts.

I ran debug, and in 4.8. found ALL the LOOP records with 94 as 
strikes_total.  However, I found several (but not ALL) REC records with 
values like 95.586. and the a non-zero strike count.

Is something going on in the deltas calculation in 4.8?   And what are REC 
records?

Thanks

Clay Jackson


-- 
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/8f906a79-5dc0-44ca-9640-2c866bd4ddbdn%40googlegroups.com.

Re: [weewx-user] Errors in 4.3

[Clay Jackson]

OK - haven't tried Python3 yet - back on the rain issue.   We've had some 
rain this morning, and it is NOT picking up in WeeWx; captured some debug 
this morning; but will not be able to look at it until later today or 
perhaps over the weekend.   As I recall, this happened when I upgraded to 
4.2 and one of  fix (in addition to changes in sdr) was to add the "rain = 
prefer_hardware" line.

Will try to do some debugging over the weekend and let you know.  Working 
on a Pi based Snow Depth detector as well, since we're getting snow now.

Clay

On Monday, January 18, 2021 at 9:47:00 AM UTC-8 tke...@gmail.com wrote:

> If you're on buster, then it's simple enough to switch to Python 3. 
> Basically, just follow the directions in the Debian guide 
> <http://www.weewx.com/docs/debian.htm>:
>
> wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
> /etc/apt/sources.list.d/weewx.list
> sudo apt-get update
> sudo apt-get install weewx
>
>
>
> On Mon, Jan 18, 2021 at 9:33 AM Clay Jackson  wrote:
>
>> Don't know WHERE I got Squeeze - just checked and confirmed; it's Buster, 
>> so would definitely like to at least try to get rid of python 2.   
>>
>> On the rain = prefer_hardware, I looked at my old config files, and it 
>> seems it's "bounced" back and forth, probably depending on what version of 
>> sdr I had..   I honestly can't remember why.
>>
>> On Sunday, January 17, 2021 at 6:12:24 AM UTC-8 tke...@gmail.com wrote:
>>
>>> The type 'totalRain' has been in the code for a long time. What I'm 
>>> wondering about is where did the line
>>>
>>> rain = prefer_hardware
>>>
>>> come from. 
>>>
>>> If you are still on squeeze, you're best off staying with Python 2. Not 
>>> all of the Python 3 pre-requisites are available through the repositories.
>>>
>>> -tk
>>>
>>> On Sat, Jan 16, 2021 at 8:31 PM Clay Jackson  wrote:
>>>
>>>> OK - thanks.  Had a bit of a scare when I corrupted my config file and 
>>>> NOTHING would start.   I commented rain and rainRate out of StdWXCaiculate 
>>>> and looks good now.  I AM getting an N/A in RanRate om the disp;lay, but 
>>>> that's OK for the time being.   Will check when we  next get rain to see 
>>>> what happens.  
>>>>
>>>>  It would be nice to know where totalRain came from - I tried grep'ing 
>>>> for it in all the .py files and only found it in accum and units.  Before 
>>>> I 
>>>> posted, I actually commented those lines out and that did NOT work. Any 
>>>> thoughts on that?
>>>>
>>>> Also, I notice from the log I'm still using Python 2, which is what 
>>>> /usr/bin/python points to by default on squeeze, which is what I'm running 
>>>> right now.  Are there notes on how to force weewx to use python3?
>>>>
>>>> Thanks!
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Jan 16, 2021 at 5:36 PM Tom Keffer  wrote:
>>>>
>>>>> Try removing the line 
>>>>>
>>>>> rain = prefer_hardware
>>>>>
>>>>> It's what's causing the StdWXCalculate service to try and calculate a 
>>>>> value.
>>>>>
>>>>> I wonder where that line came from. I don't recall it ever being part 
>>>>> of weewx.conf
>>>>>
>>>>> -tk
>>>>>
>>>>> On Sat, Jan 16, 2021 at 4:58 PM Clay Jackson  
>>>>> wrote:
>>>>>
>>>>>> I'm using an Accurite 5n1 - this has been working since early 3.x; 
>>>>>> just stopped in 4.3,  I AM using my 4.2 config files and skins.
>>>>>>
>>>>>> [StdWXCalculate]
>>>>>>
>>>>>> [[Calculations]]
>>>>>> # Derived quantities are calculated by this service. Possible 
>>>>>> values are:
>>>>>> #  hardware- use the value provided by hardware
>>>>>> #  software- use the value calculated by weewx
>>>>>> #  prefer_hardware - use value provide by hardware if 
>>>>>> available,
>>>>>> #  otherwise use value calculated by weewx
>>>>>>
>>>>>> pressure = prefer_hardware
>>>>>> barometer = prefer_hardware
>>>>>>     altimeter = software
>>>>>> windchill = sof

Re: [weewx-user] Errors in 4.3

[Clay Jackson]

Don't know WHERE I got Squeeze - just checked and confirmed; it's Buster, 
so would definitely like to at least try to get rid of python 2.   

On the rain = prefer_hardware, I looked at my old config files, and it 
seems it's "bounced" back and forth, probably depending on what version of 
sdr I had..   I honestly can't remember why.

On Sunday, January 17, 2021 at 6:12:24 AM UTC-8 tke...@gmail.com wrote:

> The type 'totalRain' has been in the code for a long time. What I'm 
> wondering about is where did the line
>
> rain = prefer_hardware
>
> come from. 
>
> If you are still on squeeze, you're best off staying with Python 2. Not 
> all of the Python 3 pre-requisites are available through the repositories.
>
> -tk
>
> On Sat, Jan 16, 2021 at 8:31 PM Clay Jackson  wrote:
>
>> OK - thanks.  Had a bit of a scare when I corrupted my config file and 
>> NOTHING would start.   I commented rain and rainRate out of StdWXCaiculate 
>> and looks good now.  I AM getting an N/A in RanRate om the disp;lay, but 
>> that's OK for the time being.   Will check when we  next get rain to see 
>> what happens.  
>>
>>  It would be nice to know where totalRain came from - I tried grep'ing 
>> for it in all the .py files and only found it in accum and units.  Before I 
>> posted, I actually commented those lines out and that did NOT work. Any 
>> thoughts on that?
>>
>> Also, I notice from the log I'm still using Python 2, which is what 
>> /usr/bin/python points to by default on squeeze, which is what I'm running 
>> right now.  Are there notes on how to force weewx to use python3?
>>
>> Thanks!
>>
>>
>>
>>
>> On Sat, Jan 16, 2021 at 5:36 PM Tom Keffer  wrote:
>>
>>> Try removing the line 
>>>
>>> rain = prefer_hardware
>>>
>>> It's what's causing the StdWXCalculate service to try and calculate a 
>>> value.
>>>
>>> I wonder where that line came from. I don't recall it ever being part of 
>>> weewx.conf
>>>
>>> -tk
>>>
>>> On Sat, Jan 16, 2021 at 4:58 PM Clay Jackson  wrote:
>>>
>>>> I'm using an Accurite 5n1 - this has been working since early 3.x; just 
>>>> stopped in 4.3,  I AM using my 4.2 config files and skins.
>>>>
>>>> [StdWXCalculate]
>>>>
>>>> [[Calculations]]
>>>> # Derived quantities are calculated by this service. Possible 
>>>> values are:
>>>> #  hardware- use the value provided by hardware
>>>> #  software- use the value calculated by weewx
>>>> #  prefer_hardware - use value provide by hardware if available,
>>>> #  otherwise use value calculated by weewx
>>>>
>>>> pressure = prefer_hardware
>>>> barometer = prefer_hardware
>>>> altimeter = software
>>>> windchill = software
>>>> heatindex = software
>>>> dewpoint = software
>>>> inDewpoint = prefer_hardware
>>>> rainRate = prefer_hardware
>>>> rain = prefer_hardware
>>>> ET = software
>>>> maxSolarRad = prefer_hardware
>>>> cloudbase = prefer_hardware
>>>>     humidex = prefer_hardware
>>>> appTemp = prefer_hardware
>>>> windrun = prefer_hardware
>>>>
>>>>
>>>> On Sat, Jan 16, 2021 at 4:45 PM Tom Keffer  wrote:
>>>>
>>>>> Normally, the driver does it, but if asked, WeeWX can calculate 'rain' 
>>>>> from cumulative quantities such as totalRain, by taking a difference. 
>>>>>
>>>>> Your configuration file seems to be asking to do so, but totalRain is 
>>>>> not available. As for why it's asking, that's not clear.
>>>>>
>>>>> What does the section [StdWXCalculate] in your file weewx.conf look 
>>>>> like?
>>>>>
>>>>>
>>>>> On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson  
>>>>> wrote:
>>>>>
>>>>>> I just upgraded (through apt update, using raspbian) to 4.3.0 and am 
>>>>>> seeing the following error. 
>>>>>> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is 
>>>>>> /var/run/weewx.pid
>>>>>> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system: 
>>>>

[weewx-user] Re: sensor for the snow depth

[Clay Jackson]

I'm working on one now using an Ultrasonic Distance sensor - hopefully will 
have it up and running on my bench sometime this week.   My goal is to get 
it mounted outside before our next forecast snow (Friday).

On Sunday, January 17, 2021 at 5:48:12 AM UTC-8 sali...@gmail.com wrote:

>
> Has anyone already made a sensor for the snow depth to connect it to the 
> RPi and display the data on Weewx?
>
> bye
>
> Patrick
>

-- 
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/32f384e5-4e81-483a-9d11-54ab525a1386n%40googlegroups.com.

Re: [weewx-user] Errors in 4.3

[Clay Jackson]

OK - thanks.  Had a bit of a scare when I corrupted my config file and
NOTHING would start.   I commented rain and rainRate out of StdWXCaiculate
and looks good now.  I AM getting an N/A in RanRate om the disp;lay, but
that's OK for the time being.   Will check when we  next get rain to see
what happens.

 It would be nice to know where totalRain came from - I tried grep'ing for
it in all the .py files and only found it in accum and units.  Before I
posted, I actually commented those lines out and that did NOT work. Any
thoughts on that?

Also, I notice from the log I'm still using Python 2, which is what
/usr/bin/python points to by default on squeeze, which is what I'm running
right now.  Are there notes on how to force weewx to use python3?

Thanks!




On Sat, Jan 16, 2021 at 5:36 PM Tom Keffer  wrote:

> Try removing the line
>
> rain = prefer_hardware
>
> It's what's causing the StdWXCalculate service to try and calculate a
> value.
>
> I wonder where that line came from. I don't recall it ever being part of
> weewx.conf
>
> -tk
>
> On Sat, Jan 16, 2021 at 4:58 PM Clay Jackson  wrote:
>
>> I'm using an Accurite 5n1 - this has been working since early 3.x; just
>> stopped in 4.3,  I AM using my 4.2 config files and skins.
>>
>> [StdWXCalculate]
>>
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>>
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = software
>> windchill = software
>> heatindex = software
>> dewpoint = software
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>> rain = prefer_hardware
>> ET = software
>> maxSolarRad = prefer_hardware
>> cloudbase = prefer_hardware
>> humidex = prefer_hardware
>> appTemp = prefer_hardware
>> windrun = prefer_hardware
>>
>>
>> On Sat, Jan 16, 2021 at 4:45 PM Tom Keffer  wrote:
>>
>>> Normally, the driver does it, but if asked, WeeWX can calculate 'rain'
>>> from cumulative quantities such as totalRain, by taking a difference.
>>>
>>> Your configuration file seems to be asking to do so, but totalRain is
>>> not available. As for why it's asking, that's not clear.
>>>
>>> What does the section [StdWXCalculate] in your file weewx.conf look like?
>>>
>>>
>>> On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson 
>>> wrote:
>>>
>>>> I just upgraded (through apt update, using raspbian) to 4.3.0 and am
>>>> seeing the following error.
>>>> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is
>>>> /var/run/weewx.pid
>>>> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system:
>>>> weewx.
>>>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration
>>>> file /etc/weewx/weewx.conf
>>>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
>>>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station
>>>> type SDR (user.sdr)
>>>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is
>>>> 0.78
>>>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is
>>>> {u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed':
>>>> u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp':
>>>> u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity':
>>>> u'humidity.04C9.Acurite5n1PacketV2', u'rain_total':
>>>> u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus':
>>>> u'battery.04C9.Acurite5n1PacketV2', u'inTemp':
>>>> u'temperature.4:0.AmbientF007THPacket', u'inHumidity':
>>>> u'humidity.4:0.AmbientF007THPacket', u'lightning_distance':
>>>> u'distance.002B.AcuriteLightningPacket', u'soilTemp1':
>>>> u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5':
>>>> u'temperature.0F66.Acurite00275MPacket', u'extraHumid3':
>>>> u'humidity.0F66.Acurite00275MPacket', u'extraTemp1':
>>>> u'temperature.002B.AcuriteLightningPacket', u'extraHumid1':
>>>> u'humidity.002B.AcuriteLightningPacket', u'strikes_total':
>>>> u's

Re: [weewx-user] Errors in 4.3

[Clay Jackson]

I'm using an Accurite 5n1 - this has been working since early 3.x; just
stopped in 4.3,  I AM using my 4.2 config files and skins.

[StdWXCalculate]

[[Calculations]]
# Derived quantities are calculated by this service. Possible
values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = software
windchill = software
heatindex = software
dewpoint = software
inDewpoint = prefer_hardware
rainRate = prefer_hardware
rain = prefer_hardware
ET = software
maxSolarRad = prefer_hardware
cloudbase = prefer_hardware
humidex = prefer_hardware
appTemp = prefer_hardware
windrun = prefer_hardware


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

> Normally, the driver does it, but if asked, WeeWX can calculate 'rain'
> from cumulative quantities such as totalRain, by taking a difference.
>
> Your configuration file seems to be asking to do so, but totalRain is not
> available. As for why it's asking, that's not clear.
>
> What does the section [StdWXCalculate] in your file weewx.conf look like?
>
>
> On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson  wrote:
>
>> I just upgraded (through apt update, using raspbian) to 4.3.0 and am
>> seeing the following error.
>> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is
>> /var/run/weewx.pid
>> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system:
>> weewx.
>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration
>> file /etc/weewx/weewx.conf
>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station
>> type SDR (user.sdr)
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is 0.78
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is
>> {u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed':
>> u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp':
>> u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity':
>> u'humidity.04C9.Acurite5n1PacketV2', u'rain_total':
>> u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus':
>> u'battery.04C9.Acurite5n1PacketV2', u'inTemp':
>> u'temperature.4:0.AmbientF007THPacket', u'inHumidity':
>> u'humidity.4:0.AmbientF007THPacket', u'lightning_distance':
>> u'distance.002B.AcuriteLightningPacket', u'soilTemp1':
>> u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5':
>> u'temperature.0F66.Acurite00275MPacket', u'extraHumid3':
>> u'humidity.0F66.Acurite00275MPacket', u'extraTemp1':
>> u'temperature.002B.AcuriteLightningPacket', u'extraHumid1':
>> u'humidity.002B.AcuriteLightningPacket', u'strikes_total':
>> u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2':
>> u'temperature.1:0.AmbientF007THPacket', u'extraTemp3':
>> u'temperature.2:0.AmbientF007THPacket', u'extraTemp4':
>> u'temperature.3:0.AmbientF007THPacket', u'extraHumid2':
>> u'humidity.3:0.AmbientF007THPacket'}
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: deltas is
>> {u'lightning_strike_count': u'strikes_total', u'rain': u'rain_total'}
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: startup process
>> 'rtl_433 -M utc -F json'
>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: StdConvert target
>> unit is 0x1
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Archive will use
>> data binding wx_binding
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Record generation
>> will be attempted in 'hardware'
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using archive
>> interval of 300 seconds (specified in weewx configuration)
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: Wunderground-PWS:
>> Data for station KWAPROSS22 will be posted
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: CWOP: Data for
>> station N7QNM-13 will be posted
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: service version is
>> 0.23
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: binding to archive
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: topic is temps
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: data will be
>> uploaded to mqtt://@localhost:1883/
>> Jan 16 15:59:13 Weather weewx[17291] INFO __main__: Starting up weewx
>> version 4.3.0
>>

[weewx-user] Errors in 4.3

[Clay Jackson]

I just upgraded (through apt update, using raspbian) to 4.3.0 and am seeing 
the following error. 
Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system: weewx.
Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station 
type SDR (user.sdr)
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is 0.78
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is 
{u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed': 
u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp': 
u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity': 
u'humidity.04C9.Acurite5n1PacketV2', u'rain_total': 
u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus': 
u'battery.04C9.Acurite5n1PacketV2', u'inTemp': 
u'temperature.4:0.AmbientF007THPacket', u'inHumidity': 
u'humidity.4:0.AmbientF007THPacket', u'lightning_distance': 
u'distance.002B.AcuriteLightningPacket', u'soilTemp1': 
u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5': 
u'temperature.0F66.Acurite00275MPacket', u'extraHumid3': 
u'humidity.0F66.Acurite00275MPacket', u'extraTemp1': 
u'temperature.002B.AcuriteLightningPacket', u'extraHumid1': 
u'humidity.002B.AcuriteLightningPacket', u'strikes_total': 
u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2': 
u'temperature.1:0.AmbientF007THPacket', u'extraTemp3': 
u'temperature.2:0.AmbientF007THPacket', u'extraTemp4': 
u'temperature.3:0.AmbientF007THPacket', u'extraHumid2': 
u'humidity.3:0.AmbientF007THPacket'}
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: deltas is 
{u'lightning_strike_count': u'strikes_total', u'rain': u'rain_total'}
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: startup process 
'rtl_433 -M utc -F json'
Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: StdConvert target 
unit is 0x1
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Archive will use 
data binding wx_binding
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: Wunderground-PWS: 
Data for station KWAPROSS22 will be posted
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: CWOP: Data for 
station N7QNM-13 will be posted
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: service version is 0.23
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: binding to archive
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: topic is temps
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: data will be uploaded 
to mqtt://@localhost:1883/
Jan 16 15:59:13 Weather weewx[17291] INFO __main__: Starting up weewx 
version 4.3.0
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx'
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.manager: Starting backfill 
of daily summaries
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Starting main 
packet loop.
Jan 16 15:59:34 Weather weewx[17291] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jan 16 15:59:34 Weather weewx[17291] INFO user.sdr: shutdown process 
rtl_433 -M utc -F json
Jan 16 15:59:45 Weather weewx[17291] ERROR user.sdr: process did not 
respond to kill, shutting down anyway
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: Caught 
unrecoverable exception:
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
'totalRain'
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   Traceback 
(most recent call last):
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 154, in main
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
engine.run()
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 210, in run
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
callback(event)
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
self.do_calculations(event.packet)
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/wxservices.py", line 66, in do_calculations
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:

Re: [weewx-user] Anybody using weewx + rtl_433 + Acurite5n1 ?? <-- No rain gauge data

[Clay Jackson]

Charlie - I have the same config; I’ll send you  snips of my configuration when 
I get home later tonight or tomorrow AM

Sent from my iPhone
Clay Jackson


> On Jan 2, 2019, at 4:36 PM, Charlie Thompson  wrote:
> 
> Everything is working but I'm not getting the rain gauge data...at all.
> Attached are my sdr.py and weewx.conf files.  
> There must be something wrong in one of them!
> 
> From the Acurite 5n1 sensor:
> 
> Wind speed works
> Wind direction works
> Humidity works
> Temperature works
> Rain gauge does NOT work.
> 
> Any help appreciated.
> 
> Thanks,
> -Charlie
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 

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

Re: [weewx-user] WU API ?

[Clay Jackson]

So, perhaps we should consider not giving away our data

Sent from my iPhone
Clay Jackson


> On May 17, 2018, at 6:48 AM, Thomas Keffer <tkef...@gmail.com> wrote:
> 
> Funny how they are only too happy to take our user-generated data for free, 
> but make you pay to get it back.
> 
>> On Thu, May 17, 2018 at 1:30 AM, gjr80 <gjroder...@gmail.com> wrote:
>> I guess we are all aware of the issues that have plagued WU for some time. I 
>> have stuck with them, uploading data and downloading various pieces of data 
>> via their API, it's just kept on working for me. I noticed a post on 
>> wxforum.net re WU no longer issuing API keys, I found this on WU.
>> 
>> https://www.wunderground.com/weather/api/
>> 
>> Maybe some folks more acquainted with WU/The Weather Company/The Weather 
>> Channel might have more info. There is nothing I found to indicate the cost 
>> of whatever replaces the API, when I followed the various links I just went 
>> around in corporate double speak circles.
>> 
>> Looking like the the forecast extension might need a version 4.
>> 
>> Gary
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: [weewx-user] Lightning Strikes on weewx-sdr Issue

[Clay Jackson]

Ah, thanks for the clarification!   

Sent from my iPhone
Clay Jackson


> On Sep 23, 2017, at 5:44 PM, mwall <mw...@users.sourceforge.net> wrote:
> 
>> On Saturday, September 23, 2017 at 7:11:55 PM UTC-4, Clay Jackson wrote:
>> I'm having the same issue - and just caught the FLOAT vs INTEGER problem.   
>> Don't understand the accumulator piece, shouldn't that be default?
> 
> the accumulator determines how values will be aggregated over time periods.  
> for example, observations such as rain are treated differently than 
> observations such as temperature.
> 
> when you add a new field to the database, you typically have to specify a few 
> things:
> 
> - the database type, e.g., 'INTEGER'
> - the unit group
> - the accumulator behavior
> 
> right now each of these is done in a different place - the type is in the 
> schema as python code (typically user/schema.py or user/extensions.py), the 
> unit group is in python code (typically user/extensions.py), and the 
> accumulator behavior is in weewx configuration file.
> 
> it might make sense to put all these things together, for example completely 
> in the weewx configuration file.
> 
> however, such a system has not yet been designed.
> 
> 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.

-- 
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] Lightning Strikes on weewx-sdr Issue

[Clay Jackson]

I'm having the same issue - and just caught the FLOAT vs INTEGER problem.   
Don't understand the accumulator piece, shouldn't that be default?

Sent from my iPhone
Clay Jackson


> On Sep 23, 2017, at 2:40 PM, Paul Oversmith <p...@overweb.com> wrote:
> 
> I am having a real problem with the graph for lightning strikes using an 
> Acurite 6045 lighting detector and the weewx-sdr driver.
> 
> The total number of strikes and distance reports correctly, the strikes 
> (delta) is not right (the strike are reported as .02 to .06 rather than an 
> integer count, please see attached image).  
> I have put monitors in the _calculate_delta(label, newtotal, oldtotal) 
> routine and the values for newtotal and oldtotal are correct and show a 
> difference of 1 when there is a strike.
> 
> I tried several different setup options, but none fixed the situation.  I 
> suspect it has something to do with the time frame and the averaging of 
> strikes over an interval rather than just reporting the quality,
> 
> But I am at a loss to see what I have setup incorrectly.
> 
> Hope someone has a suggestion to fix the problem.
> 
> My setup:
> 
> Schemia:
> 
> # AcuRite Lightning 
>('OutTempBalcony', 'REAL'),
>('OutHumidityBalcony', 'REAL'),
>('LightningStrikes',   'INTEGER'),
>('LightningStrikesTotal',  'INTEGER'),
>('LightningDistance',  'INTEGER'),
> 
> Acurite.conf (a seperate instants and database; I also have a Davis Pro):
> 
> [SDR]
> driver = user.sdr
> cmd = /usr/local/bin/rtl_433 -q -U -F json -R40 -R41
> log_unknown_sensors = False
> log_unmapped_sensors = True
> 
> OutTempBalcony = temperature.E76F.AcuriteLightningPacket
> OutHumidityBalcony = humidity.E76F.AcuriteLightningPacket
> LightningStrikes = strikes.E76F.AcuriteLightningPacket
> LightningStrikesTotal = strikes_total.E76F.AcuriteLightningPacket
> LightningDistance = distance.E76F.AcuriteLightningPacket
> 
> [[deltas]]
> LightningStrikes = LightningStrikesTotal
> 
> Skin configuration [Image Generator]:
> 
> [[[dayLightningStrikes]]]
> LightningStrikes
>   plot_type = bar
>   color = 0x4242b4
>   label = Lightning Strikes
> [[[dayLightningDistance]]]
>   plot_type = bar
>   yscale =0, 50, 5
>   color = 0x4242b4
>   LightningDistance
>   Label = 'Storm Head Distance'
>   
> Skin.tmpl:
> 
> 
>   Lighting Strikes(Last Hour)
>   
> class='popup'>$hour($hours_ago=1).LightningStrikes.sum
>   
>   
>#if ($day.LightningStrikes.sum.formatted == "0")
>0
>0
>#else
>%p')'>$day.LightningStrikes.sum
>%p')'>$day.LightningDistance.min
> #end if
>   
>
> strikesmiles 
>   
>   Storm Head(Last Hour)
>   
> #if ($day.LightningStrikes.sum.formatted == "0")
> 0
>#else
>  class='popup'>$hour($hours_ago=1).LightningDistance.min
> #end if
>   
>   
>   miles
>   
>   Lighting StrikeCount
>   
> class='popup'>$current.LightningStrikesTotal
>   
>   Last StormHead Distance
>   
>  class='popup'>$current.LightningDistance.formatted
>   
>   miles
>  
> 
> Units.py:
> 
> bs_group_dict = ListOfDicts({"altitude"   : "group_altitude",
> 
>   "TempFreezer": "group_temperature",
>   "LightningStrikes"   : "group_count",
>   "LightningStrikesTotal"  : "group_count",
>   "LightningDistance"  : "group_distance",
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 

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

Re: [weewx-user] WeeWx integration with custom home-built weather station

[Clay Jackson]

Hey, Sean - lots of different ways to accomplish what you're after.  The 
customization guide is the place to start, and then Matt and others have some 
great code samples in hit.  I'll send you a snippet I did that grabs the 
barometric pressure from an AORS string a bit later today

Sent from my iPhone
Clay Jackson


> On Jul 30, 2017, at 6:37 AM, Thomas Keffer <tkef...@gmail.com> wrote:
> 
> Hello, Sean
> 
> That's quite an ambitious project you're doing! Sounds like fun.
> 
> To start, make sure you take a look at the Weewx Customizing Guide. It 
> explains how weewx works under the hood.
> 
> Weewx expects a stream of raw sensor data, while your raw data seems to be a 
> mix of sensor data plus aggregates and historical data. I don't know how 
> wedded you are to your data stream (and underlying MySQL model), but if you 
> are, it could be very difficult to adapt the weewx reporting machinery to it. 
> 
> Alternatively, you could keep your database schema, and run weewx in parallel 
> with it. Don't know why you'd want two different databases holding what is 
> essentially the same data, but that would work.
> 
> Another approach would be to do ditch your database and PHP script and 
> substitute weewx's logging capability in their place.
> 
> The last two alternatives would require that you either write a custom 
> driver, or adapt an existing driver, to log the data coming off the Arduino. 
> See the Customizing Guide for instructions on how to write a custom driver. 
> 
> Give the Customizing Guide a read and think this over. Once you decide what 
> approach you want to take we can discuss the details.
> 
> Would love to see some pictures of the hardware you built!
> 
> -tk
> 
> 
>> On Sat, Jul 29, 2017 at 2:55 PM, Sean Coston <sdcos...@gmail.com> wrote:
>> Hi all. First post here.
>> 
>> I have been on a several month journey of building my own weather station 
>> using an  Arduino Mega and an ESP8266 wifi communications module along with 
>> a number of sensors.
>> I have 3-D printed anenometer, wind-vane, and rain-meter parts of my own 
>> design and have calibrated these instruments. The data I am getting from my 
>> set up seems to be reliable compared to readings from a nearby weather 
>> station posted on WU.
>> Right now, I have the data from the weather station being sent to a very 
>> simple web server that I built on a Linux 16.04 virtual machine running on 
>> my FreeNAS11 box. I've written a php script that accepts posts from the 
>> ESP8266 (data passed to it from the Arduino) and the php script takes live 
>> data and constructs a web page that I can access from any browser. The php 
>> script also writes posted sensor data to a MySQL database on the Linux 
>> server, and queries the same database to receive conditioned data like 
>> max/min temps, averaged data, etc. The php script also writes to a "|" 
>> (vertical bar) delimited raw data file (similar to that used by WD, and 
>> others) that is constantly updated and can be read by any program with 
>> simple parsing techniques.
>> 
>> Attached are a screen shot of my webpage, and a copy of my raw data file 
>> with some data in it.
>> My question to this group is, is there any way to "show" custom weather 
>> station data to weewx so the robust data display tools can be used? I have 
>> had fun up to now, but really don't want to reinvent the wheel when it comes 
>> to data display.
>> 
>> 
>> 
>> 
>> 
>> 
>> I'm not looking for anyone to hold my hand, just to maybe explain how WeeWx 
>> gets its data so maybe I can mimic that and thus "present" my data to WeeWx 
>> as if it were coming from an already developed weather station platform.
>> 
>> Thanks to anyone responding to this.
>> 
>> Sean
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

RE: [weewx-user] Re: 3.7.0 with MySQL quitting with database error

[Clay Jackson]

One more thing – the service (if you’re using Linux) won’t restart after the 
error until you STOP it first.

 

Clay

 

 

From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On 
Behalf Of Craig Thom
Sent: Sunday, March 12, 2017 8:09 PM
To: weewx-user 
Subject: [weewx-user] Re: 3.7.0 with MySQL quitting with database error

 

3.6.2

I started with the new weewx.conf and made changes one at a time, testing each 
one.

Everything is fine until I change

[DataBindings]



[[wx_binding]]

from database = archive_sqlite to archive_mysql

I used the default values when I set it up, so all the schema,table, user name, 
password, etc., stuff is the same.




On Sunday, March 12, 2017 at 10:44:55 PM UTC-4, mwall wrote:

craig,

what version of weewx were you running before you upgraded to 3.7.0?

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.

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

RE: [weewx-user] Re: 3.7.0 with MySQL quitting with database error

[Clay Jackson]

Hi, Craig – I had exactly the same issue!   I’m actually using MariaDB (the 
“real” OpenSource database derived from MySQL). 

 

I fixed it by stopping maria, editing the my.cnf file (/etc/mysql/my.cnf) and 
changing the line that read

 

binlog_format = row

 

to

 

binlog_format = mixed

 

and then restarting maria

 

I honestly have NO idea what that does – that’s tomorrow’s research project.

 

Clay Jackson

 

 

From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On 
Behalf Of Craig Thom
Sent: Sunday, March 12, 2017 7:48 PM
To: weewx-user <weewx-user@googlegroups.com>
Subject: [weewx-user] Re: 3.7.0 with MySQL quitting with database error

 

I forgot to say I installed initially and upgraded using the .deb package using 
apt-get

I saved my old weewx.conf and am now using the new one.  I then edited it for 
all the personal data and site updates and restarted weewx.

Next I change the database to MySQL if this works.

On Sunday, March 12, 2017 at 10:18:45 PM UTC-4, Craig Thom wrote:

I am running on Raspbian on a Raspberry Pi.

I kept my old weewx.conf file.

The only edit I made was to set Wunderground Rapidfire to 'TRUE', but after I 
set it back to false I got the same error.

This log was captured after I rebooted the Pi.

Mar 12 22:03:56 weatherpi weewx[608]: engine: retrying..
Mar 12 22:03:56 weatherpi weewx[608]: engine: Using configuration file 
/etc/weewx/weewx.conf
Mar 12 22:03:56 weatherpi weewx[608]: engine: Loading station type AcuRite 
(weewx.drivers.acurite)
Mar 12 22:03:56 weatherpi weewx[608]: acurite: driver version is 0.24
Mar 12 22:03:56 weatherpi weewx[608]: acurite: R2 will be decoded using sensor 
constants
Mar 12 22:03:56 weatherpi weewx[608]: engine: StdConvert target unit is 0x1
Mar 12 22:03:56 weatherpi weewx[608]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Mar 12 22:03:56 weatherpi weewx[608]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Mar 12 22:03:56 weatherpi weewx[608]: engine: Archive will use data binding 
wx_binding
Mar 12 22:03:56 weatherpi weewx[608]: engine: Record generation will be 
attempted in 'hardware'
Mar 12 22:03:56 weatherpi weewx[608]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Mar 12 22:03:56 weatherpi weewx[608]: engine: Using binding 'wx_binding' to 
database 'weewx'
Mar 12 22:03:56 weatherpi weewx[608]: manager: Starting backfill of daily 
summaries
Mar 12 22:03:56 weatherpi weewx[608]: forecast: MainThread: Zambretti: forecast 
version 3.2.14
Mar 12 22:03:56 weatherpi weewx[608]: forecast: MainThread: Zambretti: 
interval=3600 max_age=604800 winddir_period=1800 pressure_period=10800 
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Mar 12 22:03:56 weatherpi weewx[608]: restx: StationRegistry: Station will be 
registered
Mar 12 22:03:56 weatherpi weewx[608]: restx: Wunderground-RF: Data for station 
KKYLOUIS186 will be posted
Mar 12 22:03:56 weatherpi weewx[608]: restx: PWSWeather: Data for station 
HEDORAH will be posted
Mar 12 22:03:56 weatherpi weewx[608]: restx: CWOP: Data for station FW0615 will 
be posted
Mar 12 22:03:56 weatherpi weewx[608]: restx: WOW: Data for station 
cf9ccbbc-a8f8-e611-93ff-0003ff599b64 will be posted
Mar 12 22:03:56 weatherpi weewx[608]: restx: AWEKAS: Posting not enabled.
Mar 12 22:03:56 weatherpi weewx[608]: engine: Starting up weewx version 3.7.0
Mar 12 22:03:56 weatherpi weewx[608]: engine: Starting main packet loop.
Mar 12 22:05:27 weatherpi weewx[608]: engine: Caught unrecoverable exception in 
engine:
Mar 12 22:05:27 weatherpi weewx[608]:   (1665, 'Cannot execute 
statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT 
and at least one table uses a storage engine limited to row-based logging. 
InnoDB is limited to row-logging when transaction isolation level is READ 
COMMITTED or READ UNCOMMITTED.')
Mar 12 22:05:27 weatherpi weewx[608]:   Traceback (most recent call 
last):
Mar 12 22:05:27 weatherpi weewx[608]: File 
"/usr/share/weewx/weewx/engine.py", line 880, in main
Mar 12 22:05:27 weatherpi weewx[608]:   engine.run()
Mar 12 22:05:27 weatherpi weewx[608]: File 
"/usr/share/weewx/weewx/engine.py", line 201, in run
Mar 12 22:05:27 weatherpi weewx[608]:   
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
Mar 12 22:05:27 weatherpi weewx[608]: File 
"/usr/share/weewx/weewx/engine.py", line 223, in dispatchEvent
Mar 12 22:05:27 weatherpi weewx[608]:   callback(ev

Re: [weewx-user] Re: extraTemp1 units wrong

[Clay Jackson]

Yeah, turns out the sensor is bad :-)  Called Acurite, I gave them the QC code 
and they said "We'll send you a new one"

Sent from my iPhone
Clay Jackson


> On Feb 18, 2017, at 7:35 AM, mwall <mw...@users.sourceforge.net> wrote:
> 
> 
> 
>> On Monday, February 13, 2017 at 7:14:55 PM UTC-5, Clay Jackson wrote:
>> Trying to use an Acurite Lightning Sensor in my greenhouse as extraTemp1. 
>> 
>>  
>> 
>> I changed all of .tmpl files from “Pond” to Grenhouse (did not change the 
>> var names) and the graph/texts are showing up fine; BUT., the units are 
>> wrong.  The sensor is reporting degrees F; but somewhere BEFORE it lands in 
>> the database (archive and extraTemp tables) the value (around 43 f) is 
>> getting converted as if it was centigrade (what’s stored in the database is 
>> around 109).
>> 
>>  
>> 
>> I looked in units.py and extraTemp1 is in the temperature group, which is 
>> set for degrees F.
>> 
>>  
>> 
>> Any suggestions on where to fix this?
>> 
> 
> clay,
> 
> did you figure this out?
> 
> you are probably inserting a value for temperature in F into a loop packet or 
> archive record whose unit system is METRIC or METRICWX
> 
> 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.

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

[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>  
[mailto:weewx-user@googlegroups.com] On Behalf Of Clay Jackson
Sent: Thursday, February 16, 2017 3:20 PM
To: weewx-user@googlegroups.com <mailto: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 <cl...@nwlink.com 
<mailto:cl...@nwlink.com> > 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>  
[mailto:weewx-user@googlegroups.com] On Behalf Of mwall
Sent: Tuesday, February 14, 2017 6:52 AM
To: weewx-user <weewx-user@googlegroups.com 
<mailto:weewx-user@googlegroups.com> >
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, appT

RE: [weewx-user] acurite lightning detector

[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 <cl...@nwlink.com 
<mailto:cl...@nwlink.com> > 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>  
[mailto:weewx-user@googlegroups.com] On Behalf Of mwall
Sent: Tuesday, February 14, 2017 6:52 AM
To: weewx-user <weewx-user@googlegroups.com 
<mailto:weewx-user@googlegroups.com> >
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 g

Re: [weewx-user] acurite lightning detector

[Clay Jackson]

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

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

RE: [weewx-user] acurite lightning detector

[Clay Jackson]

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 <weewx-user@googlegroups.com>
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 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.

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

Re: [weewx-user] acurite lightning detector

[Clay Jackson]

Actually, no - what I'm seeing is just the string I sent in the message.  Will 
try some more debugging tomorrow nite or Thursday.

Sent from my iPhone
Clay Jackson


> On Feb 14, 2017, at 6:52 AM, mwall <mw...@users.sourceforge.net> wrote:
> 
> >    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.
> 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] extraTemp1 units wrong

[Clay Jackson]

Trying to use an Acurite Lightning Sensor in my greenhouse as extraTemp1.  

 

I changed all of .tmpl files from “Pond” to Grenhouse (did not change the var 
names) and the graph/texts are showing up fine; BUT., the units are wrong.  The 
sensor is reporting degrees F; but somewhere BEFORE it lands in the database 
(archive and extraTemp tables) the value (around 43 f) is getting converted as 
if it was centigrade (what’s stored in the database is around 109).

 

I looked in units.py and extraTemp1 is in the temperature group, which is set 
for degrees F.

 

Any suggestions on where to fix this?

 

Thanks!



Clay Jackson

 

-- 
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] Get rid of Indoor Temp Graph

[Clay Jackson]

Newbie question – I have a SDR “station” that doesn’t (yet) have an indoor 
temp.

 

I used “if $day.inTemp.has_data” (week, month,year) tro suppress the tabular 
stuff; but can’t seem to figure out how to suppress the graph.

 

Help?

 

Clay Jackson

 

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

RE: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

[Clay Jackson]

Yeah – and now that I’ve done it; it definitely makes sense – caught me by 
surprise more than anything.

 

 

 

From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On 
Behalf Of Andrew Milner
Sent: Sunday, February 5, 2017 9:57 PM
To: weewx-user <weewx-user@googlegroups.com>
Subject: Re: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

 

Aha - that makes more sense now - a little bit more than just a reconfiguration 
(depending on how you were running the simulator and what dates/times you were 
using).  Yes, switching from 'test mode' to 'live mode' would more than likely 
require the database tables being dropped, NOAA files deleting and probably 
more things cleaned up also.  Thanks for the additional info.

On Monday, 6 February 2017 07:36:19 UTC+2, Clay Jackson wrote:

Yeah – I changed the station type from simulator (testing) to SDR (I have an 
Acurite 5n1 with a console that does not support USB).

 

 

From: weewx...@googlegroups.com   
[mailto:weewx...@googlegroups.com  ] On Behalf Of Andrew Milner
Sent: Sunday, February 5, 2017 8:12 PM
To: weewx-user <weewx...@googlegroups.com  >
Subject: Re: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

 

Clay - since weewx configuration changes do not usually require a database to 
be dropped and recreated empty can you clarify what reconfiguration changes you 
had made and what the logs showed?

 



On Sunday, 5 February 2017 22:26:35 UTC+2, Clay Jackson wrote:

Problem solved!   Turns out that after a reconfigure changes the station, the 
database needs to dropped and recreated empty.

 

Thanks!

Clay Jackson

 

 

From: weewx...@googlegroups.com <mailto:weewx...@googlegroups.com>  
[mailto:weewx...@googlegroups.com] On Behalf Of mwall
Sent: Sunday, February 5, 2017 5:47 AM
To: weewx-user <weewx...@googlegroups.com <mailto:weewx...@googlegroups.com> >
Subject: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

 

On Sunday, February 5, 2017 at 2:47:32 AM UTC-5, Clay Jackson wrote:

Just getting started with weewx and an Acurite station that does not support 
USB - so, I'm using SDR/RTL.

If I set up to use a MySQL (Maria, actually) database on a different server, 
when I start weewx, the RTL process starts and then IMMEDIATELTY shuts down.
I haven't done a LOT more debugging on this, yet - wanted to see if anyone else 
has run into this.


i'll bet it has nothing to do with sdr and everything to do with maria.

set debug=1 in weewxconf.  run weewx directly (not as a daemon) in one shell as 
you monitor the log in a second shell.

then report what you find.

m

-- 
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/Z5w7qUFUUBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user...@googlegroups.com <mailto:weewx-user...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Z5w7qUFUUBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+...@googlegroups.com  .
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Z5w7qUFUUBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto:weewx-user+unsubscr...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.

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

RE: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

[Clay Jackson]

Yeah – I changed the station type from simulator (testing) to SDR (I have an 
Acurite 5n1 with a console that does not support USB).

 

 

From: weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] On 
Behalf Of Andrew Milner
Sent: Sunday, February 5, 2017 8:12 PM
To: weewx-user <weewx-user@googlegroups.com>
Subject: Re: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

 

Clay - since weewx configuration changes do not usually require a database to 
be dropped and recreated empty can you clarify what reconfiguration changes you 
had made and what the logs showed?

 



On Sunday, 5 February 2017 22:26:35 UTC+2, Clay Jackson wrote:

Problem solved!   Turns out that after a reconfigure changes the station, the 
database needs to dropped and recreated empty.

 

Thanks!

Clay Jackson

 

 

From: weewx...@googlegroups.com   
[mailto:weewx...@googlegroups.com  ] On Behalf Of mwall
Sent: Sunday, February 5, 2017 5:47 AM
To: weewx-user <weewx...@googlegroups.com  >
Subject: [weewx-user] Re: SDR/RTL Process stops when using MySQL Database

 

On Sunday, February 5, 2017 at 2:47:32 AM UTC-5, Clay Jackson wrote:

Just getting started with weewx and an Acurite station that does not support 
USB - so, I'm using SDR/RTL.

If I set up to use a MySQL (Maria, actually) database on a different server, 
when I start weewx, the RTL process starts and then IMMEDIATELTY shuts down.
I haven't done a LOT more debugging on this, yet - wanted to see if anyone else 
has run into this.


i'll bet it has nothing to do with sdr and everything to do with maria.

set debug=1 in weewxconf.  run weewx directly (not as a daemon) in one shell as 
you monitor the log in a second shell.

then report what you find.

m

-- 
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/Z5w7qUFUUBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user...@googlegroups.com  .
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Z5w7qUFUUBQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto: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.