Re: [weewx-user] interceptor driver, HP2560 and WS90

[Jason Gibson]

Hi Rainer,

Thanks for your reply.

Rainfall data priority is set to piezo.

Standalone interceptor driver output below:

mapped packet: {'dateTime': 1686696648, 'usUnits': 1, 'pressure': 29.604, 
'outHumidity': 85.0, 'inHumidity': 40.0, 'outTemp': 50.7, 'inTemp': 73.4, 
'windSpeed': 8.5, 'windGust': 11.18, 'windDir': 279.0, 'radiation': 71.59, 
'UV': 0.0}

It seems that I had mapped the rain fields sort of correctly.  Although I 
am not sure 'rain' and 'drain_piezo' are actually the same quantity.  There 
does not appear to be an equivalent to the database field 'rain' in the 
output from the HP2560.  It has only rain rate, daily, weekly, monthly and 
yearly rain totals.  Not rain since last interval, which is my 
understanding of what the database fieldname 'rain' is meant to represent.

Having looked at the wview-extended.py schema I can see that I had the 
wrong database field names for the battery values.   I have since changed 
the mapping as seen below, still no rain or battery data.

  [[sensor_map_extensions]]
  rain = drain_piezo
  rainRate = rrain_piezo
  supplyVoltage = wh90batt
  referenceVoltage = ws90cap_volt

Not sure where to go from here.

Cheers,

Jason

On Wednesday, June 14, 2023 at 3:41:00 AM UTC+10 Rainer Lang wrote:

> Hi Jason
>
> 1. the local API (local Ecowitt Gateway API aka GW1000 API) was never 
> implemented in the HP25x0, HP350x, WH2910 consoles => so no such thing like 
> depreciation
> you want to know which console supports which API, look up 
> https://www.wxforum.net/index.php?topic=40730.0 😎
>
> 2. the reason why you may not receive WS90 (piezo rain) data via the 
> custom server could be that your WS90 has not been set in the console as 
> primary rain device.
> gear wheel --> setup (more) --> rain priority (has to be set to piezo).
>
> 3. could you run the interceptor driver stand-alone and post here the 
> result of one console post ?
> (or run weewx in debug = 3 mode and copy from the syslog)
>
> regards
>
> Rainer
> On 13.06.2023 02:28, Jason Gibson wrote:
>
> Hi All, 
>
> I have been trying to coax rain data out of the WS90 and into weewx.
>
> I assume that the local API is deprecated on the HP2560 as I can't appear 
> to get any details out of it on port 45000.
>
> I am currently using the interceptor driver in listen mode on port 8080.  
> And I am able to  log all data in WeeWX except rain from the piezo sensor, 
> and battery voltages.
>
> I have tried mapping sensors to fields as below, to no avail, is anyone 
> able to assist with the interceptor driver, or is there another driver 
> better suited to my hardware?
>
> Hardware:
> -
> HP2564 - HP2560 & WS90
>
> HP2560_C:
>   Hardware revision V2.0
>   Firmware: Pro_V1.9.0
>   EasyWeatherProv5.11
> WS90: 
>   Firmware 1.3.3
>
> weewx.conf extract:
> 
>
> driver = user.interceptor
> device_type = ecowitt-client
> port = 8080
> iface = ens18
> [[sensor_map_extensions]]
>   rain = drain_piezo
>   rainRate = rrain_piezo
>   bat_wind = wh90batt
>   bat_rain = ws90cap_volt
>
> Am I using the right field names?  Example output from the ws90 is as 
> follows:
>
> PASSKEY: 
> stationtype:  EasyWeatherPro_V5.1.1
> runtime: 2
> dateutc: 2023-06-11 01:53:27
> tempinf: 77.0
> humidityin: 40
> baromrelin: 30.224
> baromabsin: 29.946
> tempf: 61.2
> humidity: 60
> winddir: 12
> windspeedmph: 5.14
> windgustmph: 6.93
> maxdailygust: 10.74
> solarradiation: 270.64
> uv: 2
> rrain_piezo: 0.000
> erain_piezo: 0.000
> hrain_piezo: 0.000
> drain_piezo: 0.000
> wrain_piezo: 0.000
> mrain_piezo: 1.209
> yrain_piezo: 1.209
> ws90cap_volt: 5.2
> ws90_ver: 133
> gain10_piezo: 1.15
> gain20_piezo: 1.05
> gain30_piezo: 1.00
> gain40_piezo: 1.00
> gain50_piezo: 1.00
> wh90batt: 3.10
> freq: 433M
> model: HP2564CA_Pro_V1.9.0
> interval: 30
>
> Cheers,
>
> Jason
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/8828c0f2-f040-4558-bf6d-f2ff1dedb0ben%40googlegroups.com
>  
> 
> .
>
>

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

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[Kevin Crivelli]

I don't have an [Accumulator] section in my .conf

On Tuesday, June 13, 2023 at 3:49:28 PM UTC-4 Eric K wrote:

> Ahhh an external Acurite lightning detector.  That explains why your 
> lightning data variable does not end in ".AcuriteAtlasPacket"
>
> Of note, unlike the 2nd post in this thread, my [Accumulator] setion of 
> weewx.conf file is blank, because the Atlas lightning number is already an 
> accuulated value.
>
> #
> [Accumulator]
>
> #
>
> On Tuesday, June 13, 2023 at 2:34:24 PM UTC-5 Kevin Crivelli wrote:
>
>> oh I forgot to mention that I use a separate acurite lightning detector 
>> than the atlas detector. I do not have the atlas detector even installed 
>> because there are too many electronics near the main station that I have 
>> false positive lightning strikes when using the atlas detector so I use the 
>> acurite lightning detector in a different location for those readings. 
>> can't imagine that would have anything to do with my situation however I 
>> thought I'd tell you so you wouldn't be confused as to why mine is 
>> different than yours even though we both use Atlas's
>>
>> On Tue, Jun 13, 2023 at 3:17 PM Kevin Crivelli  
>> wrote:
>>
>>> mines definitely a little different. This is what I already have. It 
>>> seems to follow the logic you shared above in your configuration but my 
>>> packets are named differently. where you have "Atlas_strike_count = 
>>> strike_count.0011.AcuriteAtlasPacket" I have "strikes_total = 
>>> strikes_total.1255.AcuriteLightningPacket". from looking at my deltas 
>>> section, does it look as though I have this set up correctly or am I off a 
>>> little bit?
>>>
>>> [SDR]
>>> # This section is for the software-defined radio driver.
>>> 
>>> # The driver to use
>>> driver = user.sdr
>>>
>>> 
>>> [[sensor_map]]
>>> outTemp = temperature.030B.AcuriteAtlasPacket
>>> outHumidity = humidity.030B.AcuriteAtlasPacket
>>> windSpeed = wind_speed.030B.AcuriteAtlasPacket
>>> windDir = wind_dir.030B.AcuriteAtlasPacket
>>> UV = uv.030B.AcuriteAtlasPacket
>>> rain_total = rain_total.030B.AcuriteAtlasPacket
>>> radiation = lux.030B.AcuriteAtlasPacket
>>> lux = lux.030B.AcuriteAtlasPacket
>>> outTempBatteryStatus = battery.030B.AcuriteAtlasPacket
>>> lightning_distance = distance.1255.AcuriteLightningPacket
>>> strikes_total = strikes_total.1255.AcuriteLightningPacket
>>> inTemp = temperature.3071.AcuriteTowerPacketV2
>>> inHumidity = humidity.3071.AcuriteTowerPacketV2
>>> pressure = pressure.171.FOWH32BPacket
>>> 
>>> 
>>> [[deltas]]
>>> rain = rain_total
>>> lightning_strike_count = strikes_total
>>>
>>>
>>>
>>> On Tue, Jun 13, 2023 at 3:11 PM Eric K  wrote:
>>>
 I forgot about the [SDR] section of the weewx.conf file.
 weewx needs to convert the lightning strike count reported by the 
 Acurite Atlas to a lightning strike delta number.
 This is because the Atlas counts up lightning strikes and keeps 
 incrementing the accumulated strike number (such as 5).
 When the next strike ocurrs the Atlas will increment the number to 6, 
 and so on.
 You need weewx to watch for a change in that Atlas lightning strike 
 number and report that difference (delta) between the last count and the 
 current count.

 from my weewx.conf file:

 ##

 [SDR]
 # This section is for the software-defined radio driver.
 # collect data from Acurite-Atlas sensor 0011
 
 # The driver to use
 driver = user.sdr
 cmd = rtl_433 -R 40 -M utc -F json
 
 [[sensor_map]]
 outTemp = temperature.0011.AcuriteAtlasPacket
 outHumidity = humidity.0011.AcuriteAtlasPacket
 windSpeed = wind_speed.0011.AcuriteAtlasPacket
 windDir = wind_dir.0011.AcuriteAtlasPacket
 UV = uv.0011.AcuriteAtlasPacket
 luminosity = lux.0011.AcuriteAtlasPacket
 Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
 Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
 lightning_distance = strike_distance.0011.AcuriteAtlasPacket
 windBatteryStatus = battery.0011.AcuriteAtlasPacket
 batteryStatus1 = battery.0011.AcuriteAtlasPacket
 
 [[deltas]]
 rain = Atlas_rain_total
 lightning_strike_count = Atlas_strike_count


 ##

 On Tuesday, June 13, 2023 at 1:58:17 PM UTC-5 Kevin Crivelli wrote:

> I added the line 
> lightning_distance = lightning_distance / 1.609 if 
> lightning_strike_count > 0 else Non

Re: [weewx-user] Re: bad strike count data 4,000+ strikes, how to remove from database or ignore such data in charts

[Kevin Crivelli]

Rainer, that worked. I had figured it out just before you'd sent that 
message. I just had to add the full path for weewx.conf to the command. 
"/etc/weewx/weewx.conf"

Everything is back to normal. Thank you! 




On Tuesday, June 13, 2023 at 4:53:46 PM UTC-4 Rainer Lang wrote:

> you should read and apply the proper synthax:
>
> try wee_database --help 
> and apply 
> when you mention weewx.conf then as --config=/etc/weewx/weewx.conf
> if you have only one database and one respective weewx.conf, you don't 
> need to mention it (but you can, however, then correctly)
>
> (sudo) wee_database --drop-daily
> and
> (sudo) weew_database --rebuild-daily
> should suffice
>
> if you want to mention weewx.conf, then:
> (sudo) wee_database --drop-daily --config=/etc/weewx/weewx.conf
> etc
> On 13.06.2023 22:46, Kevin Crivelli wrote:
>
> I was able to delete the entries from the database using the guide 
> provided at 
> https://github.com/weewx/weewx/wiki/Cleaning%20up%20old%20'bad'%20data 
> however, when I got to the section for cleaning up the daily summaries I 
> ran into an error with the commands provided
>
> wee_database weewx.conf --drop-daily and wee_database weewx.conf 
> --rebuild-daily gave me this error
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_database", line 1168, in 
> main()
>   File "/usr/share/weewx/wee_database", line 187, in main
> config_path, config_dict = weecfg.read_config(options.config_path, 
> args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 146, in read_config
> config_path = find_file(config_path, args,
>   File "/usr/share/weewx/weecfg/__init__.py", line 117, in find_file
> raise IOError("%s is not a file" % file_path)
> OSError: weewx.conf is not a file
> On Tuesday, June 13, 2023 at 4:12:46 PM UTC-4 Kevin Crivelli wrote:
>
>> there were 3 entries over 3,000 strikes in a matter of minutes that 
>> pushed my count to 11,970 for the day. There has to be a way to remove 
>> those entries. please let me know if anyone knows how. 
>>
>> [image: lightning strike error.JPG]
>>
>> On Tuesday, June 13, 2023 at 3:47:46 PM UTC-4 Kevin Crivelli wrote:
>>
>>> I'm not sure how or why it happened but today around 3:25pm I received a 
>>> strike count of over 4,000 strikes. Is there a way to go into the database 
>>> and remove this entry? or perhaps I can add a correction in the corrections 
>>> section if lightning_strike_count is < 4,000 = none or something?
>>>
>>> thanks for any help on this matter. really odd
>>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/889e23f5-eeac-4c0a-9cf9-aab1f564f9f7n%40googlegroups.com
>  
> 
> .
>
>

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

Re: [weewx-user] Re: bad strike count data 4,000+ strikes, how to remove from database or ignore such data in charts

['Rainer Lang' via weewx-user]

you should read and apply the proper synthax:

try wee_database --help
and apply 
when you mention weewx.conf then as --config=/etc/weewx/weewx.conf
if you have only one database and one respective weewx.conf, you don't 
need to mention it (but you can, however, then correctly)


(sudo) wee_database --drop-daily
and
(sudo) weew_database --rebuild-daily
should suffice

if you want to mention weewx.conf, then:
(sudo) wee_database --drop-daily --config=/etc/weewx/weewx.conf
etc

On 13.06.2023 22:46, Kevin Crivelli wrote:
I was able to delete the entries from the database using the guide 
provided at 
https://github.com/weewx/weewx/wiki/Cleaning%20up%20old%20'bad'%20data 
however, when I got to the section for cleaning up the daily summaries 
I ran into an error with the commands provided


wee_database weewx.conf --drop-daily and wee_database weewx.conf 
--rebuild-daily gave me this error


Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 1168, in 
    main()
  File "/usr/share/weewx/wee_database", line 187, in main
    config_path, config_dict = weecfg.read_config(options.config_path, 
args)

  File "/usr/share/weewx/weecfg/__init__.py", line 146, in read_config
    config_path = find_file(config_path, args,
  File "/usr/share/weewx/weecfg/__init__.py", line 117, in find_file
    raise IOError("%s is not a file" % file_path)
OSError: weewx.conf is not a file
On Tuesday, June 13, 2023 at 4:12:46 PM UTC-4 Kevin Crivelli wrote:

there were 3 entries over 3,000 strikes in a matter of minutes
that pushed my count to 11,970 for the day. There has to be a way
to remove those entries. please let me know if anyone knows how.

lightning strike error.JPG

On Tuesday, June 13, 2023 at 3:47:46 PM UTC-4 Kevin Crivelli wrote:

I'm not sure how or why it happened but today around 3:25pm I
received a strike count of over 4,000 strikes. Is there a way
to go into the database and remove this entry? or perhaps I
can add a correction in the corrections section if
lightning_strike_count is < 4,000 = none or something?

thanks for any help on this matter. really odd

--
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/889e23f5-eeac-4c0a-9cf9-aab1f564f9f7n%40googlegroups.com 
.


--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9339a17-8ff1-546a-a58e-18a472995af8%40gmail.com.

[weewx-user] Re: bad strike count data 4,000+ strikes, how to remove from database or ignore such data in charts

[Kevin Crivelli]

I was able to delete the entries from the database using the guide provided 
at https://github.com/weewx/weewx/wiki/Cleaning%20up%20old%20'bad'%20data 
however, when I got to the section for cleaning up the daily summaries I 
ran into an error with the commands provided

wee_database weewx.conf --drop-daily and wee_database weewx.conf 
--rebuild-daily gave me this error

Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 1168, in 
main()
  File "/usr/share/weewx/wee_database", line 187, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/share/weewx/weecfg/__init__.py", line 146, in read_config
config_path = find_file(config_path, args,
  File "/usr/share/weewx/weecfg/__init__.py", line 117, in find_file
raise IOError("%s is not a file" % file_path)
OSError: weewx.conf is not a file
On Tuesday, June 13, 2023 at 4:12:46 PM UTC-4 Kevin Crivelli wrote:

> there were 3 entries over 3,000 strikes in a matter of minutes that pushed 
> my count to 11,970 for the day. There has to be a way to remove those 
> entries. please let me know if anyone knows how. 
>
> [image: lightning strike error.JPG]
>
> On Tuesday, June 13, 2023 at 3:47:46 PM UTC-4 Kevin Crivelli wrote:
>
>> I'm not sure how or why it happened but today around 3:25pm I received a 
>> strike count of over 4,000 strikes. Is there a way to go into the database 
>> and remove this entry? or perhaps I can add a correction in the corrections 
>> section if lightning_strike_count is < 4,000 = none or something?
>>
>> thanks for any help on this matter. really odd
>>
>

-- 
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/889e23f5-eeac-4c0a-9cf9-aab1f564f9f7n%40googlegroups.com.

[weewx-user] Re: bad strike count data 4,000+ strikes, how to remove from database or ignore such data in charts

[Kevin Crivelli]

there were 3 entries over 3,000 strikes in a matter of minutes that pushed 
my count to 11,970 for the day. There has to be a way to remove those 
entries. please let me know if anyone knows how. 

[image: lightning strike error.JPG]

On Tuesday, June 13, 2023 at 3:47:46 PM UTC-4 Kevin Crivelli wrote:

> I'm not sure how or why it happened but today around 3:25pm I received a 
> strike count of over 4,000 strikes. Is there a way to go into the database 
> and remove this entry? or perhaps I can add a correction in the corrections 
> section if lightning_strike_count is < 4,000 = none or something?
>
> thanks for any help on this matter. really odd
>

-- 
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/d04360ab-8ffa-41fb-a4e0-dc0ef9e21e3fn%40googlegroups.com.

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[Kevin Crivelli]

yeah I don't have an accumulator section. I just received some really bad 
strike count data over 3,000 strikes, I have a feeling it was due to some 
sort of interference on the detector, I want to create a correction that 
causes any strike count totals greater than a specific number be registered 
as 0. I am trying to figure out how to make that entry but I get an error 
no matter what I put in. I know this is changing topics but I'm freakin out 
a little. Any ideas?

On Tuesday, June 13, 2023 at 3:49:28 PM UTC-4 Eric K wrote:

> Ahhh an external Acurite lightning detector.  That explains why your 
> lightning data variable does not end in ".AcuriteAtlasPacket"
>
> Of note, unlike the 2nd post in this thread, my [Accumulator] setion of 
> weewx.conf file is blank, because the Atlas lightning number is already an 
> accuulated value.
>
> #
> [Accumulator]
>
> #
>
> On Tuesday, June 13, 2023 at 2:34:24 PM UTC-5 Kevin Crivelli wrote:
>
>> oh I forgot to mention that I use a separate acurite lightning detector 
>> than the atlas detector. I do not have the atlas detector even installed 
>> because there are too many electronics near the main station that I have 
>> false positive lightning strikes when using the atlas detector so I use the 
>> acurite lightning detector in a different location for those readings. 
>> can't imagine that would have anything to do with my situation however I 
>> thought I'd tell you so you wouldn't be confused as to why mine is 
>> different than yours even though we both use Atlas's
>>
>> On Tue, Jun 13, 2023 at 3:17 PM Kevin Crivelli  
>> wrote:
>>
>>> mines definitely a little different. This is what I already have. It 
>>> seems to follow the logic you shared above in your configuration but my 
>>> packets are named differently. where you have "Atlas_strike_count = 
>>> strike_count.0011.AcuriteAtlasPacket" I have "strikes_total = 
>>> strikes_total.1255.AcuriteLightningPacket". from looking at my deltas 
>>> section, does it look as though I have this set up correctly or am I off a 
>>> little bit?
>>>
>>> [SDR]
>>> # This section is for the software-defined radio driver.
>>> 
>>> # The driver to use
>>> driver = user.sdr
>>>
>>> 
>>> [[sensor_map]]
>>> outTemp = temperature.030B.AcuriteAtlasPacket
>>> outHumidity = humidity.030B.AcuriteAtlasPacket
>>> windSpeed = wind_speed.030B.AcuriteAtlasPacket
>>> windDir = wind_dir.030B.AcuriteAtlasPacket
>>> UV = uv.030B.AcuriteAtlasPacket
>>> rain_total = rain_total.030B.AcuriteAtlasPacket
>>> radiation = lux.030B.AcuriteAtlasPacket
>>> lux = lux.030B.AcuriteAtlasPacket
>>> outTempBatteryStatus = battery.030B.AcuriteAtlasPacket
>>> lightning_distance = distance.1255.AcuriteLightningPacket
>>> strikes_total = strikes_total.1255.AcuriteLightningPacket
>>> inTemp = temperature.3071.AcuriteTowerPacketV2
>>> inHumidity = humidity.3071.AcuriteTowerPacketV2
>>> pressure = pressure.171.FOWH32BPacket
>>> 
>>> 
>>> [[deltas]]
>>> rain = rain_total
>>> lightning_strike_count = strikes_total
>>>
>>>
>>>
>>> On Tue, Jun 13, 2023 at 3:11 PM Eric K  wrote:
>>>
 I forgot about the [SDR] section of the weewx.conf file.
 weewx needs to convert the lightning strike count reported by the 
 Acurite Atlas to a lightning strike delta number.
 This is because the Atlas counts up lightning strikes and keeps 
 incrementing the accumulated strike number (such as 5).
 When the next strike ocurrs the Atlas will increment the number to 6, 
 and so on.
 You need weewx to watch for a change in that Atlas lightning strike 
 number and report that difference (delta) between the last count and the 
 current count.

 from my weewx.conf file:

 ##

 [SDR]
 # This section is for the software-defined radio driver.
 # collect data from Acurite-Atlas sensor 0011
 
 # The driver to use
 driver = user.sdr
 cmd = rtl_433 -R 40 -M utc -F json
 
 [[sensor_map]]
 outTemp = temperature.0011.AcuriteAtlasPacket
 outHumidity = humidity.0011.AcuriteAtlasPacket
 windSpeed = wind_speed.0011.AcuriteAtlasPacket
 windDir = wind_dir.0011.AcuriteAtlasPacket
 UV = uv.0011.AcuriteAtlasPacket
 luminosity = lux.0011.AcuriteAtlasPacket
 Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
 Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
 lightning_distance = strike_distance.0011.AcuriteAtlasPacket
 windBatteryStatus = battery.0011.AcuriteAtlasPacket
 batteryStatus1 = battery.0011.AcuriteAtlasPacket

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[Eric K]

Ahhh an external Acurite lightning detector.  That explains why your 
lightning data variable does not end in ".AcuriteAtlasPacket"

Of note, unlike the 2nd post in this thread, my [Accumulator] setion of 
weewx.conf file is blank, because the Atlas lightning number is already an 
accuulated value.

#
[Accumulator]

#

On Tuesday, June 13, 2023 at 2:34:24 PM UTC-5 Kevin Crivelli wrote:

> oh I forgot to mention that I use a separate acurite lightning detector 
> than the atlas detector. I do not have the atlas detector even installed 
> because there are too many electronics near the main station that I have 
> false positive lightning strikes when using the atlas detector so I use the 
> acurite lightning detector in a different location for those readings. 
> can't imagine that would have anything to do with my situation however I 
> thought I'd tell you so you wouldn't be confused as to why mine is 
> different than yours even though we both use Atlas's
>
> On Tue, Jun 13, 2023 at 3:17 PM Kevin Crivelli  
> wrote:
>
>> mines definitely a little different. This is what I already have. It 
>> seems to follow the logic you shared above in your configuration but my 
>> packets are named differently. where you have "Atlas_strike_count = 
>> strike_count.0011.AcuriteAtlasPacket" I have "strikes_total = 
>> strikes_total.1255.AcuriteLightningPacket". from looking at my deltas 
>> section, does it look as though I have this set up correctly or am I off a 
>> little bit?
>>
>> [SDR]
>> # This section is for the software-defined radio driver.
>> 
>> # The driver to use
>> driver = user.sdr
>>
>> 
>> [[sensor_map]]
>> outTemp = temperature.030B.AcuriteAtlasPacket
>> outHumidity = humidity.030B.AcuriteAtlasPacket
>> windSpeed = wind_speed.030B.AcuriteAtlasPacket
>> windDir = wind_dir.030B.AcuriteAtlasPacket
>> UV = uv.030B.AcuriteAtlasPacket
>> rain_total = rain_total.030B.AcuriteAtlasPacket
>> radiation = lux.030B.AcuriteAtlasPacket
>> lux = lux.030B.AcuriteAtlasPacket
>> outTempBatteryStatus = battery.030B.AcuriteAtlasPacket
>> lightning_distance = distance.1255.AcuriteLightningPacket
>> strikes_total = strikes_total.1255.AcuriteLightningPacket
>> inTemp = temperature.3071.AcuriteTowerPacketV2
>> inHumidity = humidity.3071.AcuriteTowerPacketV2
>> pressure = pressure.171.FOWH32BPacket
>> 
>> 
>> [[deltas]]
>> rain = rain_total
>> lightning_strike_count = strikes_total
>>
>>
>>
>> On Tue, Jun 13, 2023 at 3:11 PM Eric K  wrote:
>>
>>> I forgot about the [SDR] section of the weewx.conf file.
>>> weewx needs to convert the lightning strike count reported by the 
>>> Acurite Atlas to a lightning strike delta number.
>>> This is because the Atlas counts up lightning strikes and keeps 
>>> incrementing the accumulated strike number (such as 5).
>>> When the next strike ocurrs the Atlas will increment the number to 6, 
>>> and so on.
>>> You need weewx to watch for a change in that Atlas lightning strike 
>>> number and report that difference (delta) between the last count and the 
>>> current count.
>>>
>>> from my weewx.conf file:
>>>
>>> ##
>>>
>>> [SDR]
>>> # This section is for the software-defined radio driver.
>>> # collect data from Acurite-Atlas sensor 0011
>>> 
>>> # The driver to use
>>> driver = user.sdr
>>> cmd = rtl_433 -R 40 -M utc -F json
>>> 
>>> [[sensor_map]]
>>> outTemp = temperature.0011.AcuriteAtlasPacket
>>> outHumidity = humidity.0011.AcuriteAtlasPacket
>>> windSpeed = wind_speed.0011.AcuriteAtlasPacket
>>> windDir = wind_dir.0011.AcuriteAtlasPacket
>>> UV = uv.0011.AcuriteAtlasPacket
>>> luminosity = lux.0011.AcuriteAtlasPacket
>>> Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
>>> Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
>>> lightning_distance = strike_distance.0011.AcuriteAtlasPacket
>>> windBatteryStatus = battery.0011.AcuriteAtlasPacket
>>> batteryStatus1 = battery.0011.AcuriteAtlasPacket
>>> 
>>> [[deltas]]
>>> rain = Atlas_rain_total
>>> lightning_strike_count = Atlas_strike_count
>>>
>>>
>>> ##
>>>
>>> On Tuesday, June 13, 2023 at 1:58:17 PM UTC-5 Kevin Crivelli wrote:
>>>
 I added the line 
 lightning_distance = lightning_distance / 1.609 if 
 lightning_strike_count > 0 else None#convert distance to miles 

 to the [StdCalibrate] [[Corrections]] section and I added your chart to 
 my graphs.conf 

 I am still getting the persistant distance of 5 miles as per the last 
 lightning di

[weewx-user] bad strike count data 4,000+ strikes, how to remove from database or ignore such data in charts

[Kevin Crivelli]

I'm not sure how or why it happened but today around 3:25pm I received a 
strike count of over 4,000 strikes. Is there a way to go into the database 
and remove this entry? or perhaps I can add a correction in the corrections 
section if lightning_strike_count is < 4,000 = none or something?

thanks for any help on this matter. really odd

-- 
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/11a5ce46-fa97-4cae-a265-ee4e0c2a23d7n%40googlegroups.com.

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[Kevin Crivelli]

oh I forgot to mention that I use a separate acurite lightning detector
than the atlas detector. I do not have the atlas detector even installed
because there are too many electronics near the main station that I have
false positive lightning strikes when using the atlas detector so I use the
acurite lightning detector in a different location for those readings.
can't imagine that would have anything to do with my situation however I
thought I'd tell you so you wouldn't be confused as to why mine is
different than yours even though we both use Atlas's

On Tue, Jun 13, 2023 at 3:17 PM Kevin Crivelli 
wrote:

> mines definitely a little different. This is what I already have. It seems
> to follow the logic you shared above in your configuration but my packets
> are named differently. where you have "Atlas_strike_count =
> strike_count.0011.AcuriteAtlasPacket" I have "strikes_total =
> strikes_total.1255.AcuriteLightningPacket". from looking at my deltas
> section, does it look as though I have this set up correctly or am I off a
> little bit?
>
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
>
>
> [[sensor_map]]
> outTemp = temperature.030B.AcuriteAtlasPacket
> outHumidity = humidity.030B.AcuriteAtlasPacket
> windSpeed = wind_speed.030B.AcuriteAtlasPacket
> windDir = wind_dir.030B.AcuriteAtlasPacket
> UV = uv.030B.AcuriteAtlasPacket
> rain_total = rain_total.030B.AcuriteAtlasPacket
> radiation = lux.030B.AcuriteAtlasPacket
> lux = lux.030B.AcuriteAtlasPacket
> outTempBatteryStatus = battery.030B.AcuriteAtlasPacket
> lightning_distance = distance.1255.AcuriteLightningPacket
> strikes_total = strikes_total.1255.AcuriteLightningPacket
> inTemp = temperature.3071.AcuriteTowerPacketV2
> inHumidity = humidity.3071.AcuriteTowerPacketV2
> pressure = pressure.171.FOWH32BPacket
>
>
> [[deltas]]
> rain = rain_total
> lightning_strike_count = strikes_total
>
>
>
> On Tue, Jun 13, 2023 at 3:11 PM Eric K  wrote:
>
>> I forgot about the [SDR] section of the weewx.conf file.
>> weewx needs to convert the lightning strike count reported by the Acurite
>> Atlas to a lightning strike delta number.
>> This is because the Atlas counts up lightning strikes and keeps
>> incrementing the accumulated strike number (such as 5).
>> When the next strike ocurrs the Atlas will increment the number to 6, and
>> so on.
>> You need weewx to watch for a change in that Atlas lightning strike
>> number and report that difference (delta) between the last count and the
>> current count.
>>
>> from my weewx.conf file:
>>
>> ##
>>
>> [SDR]
>> # This section is for the software-defined radio driver.
>> # collect data from Acurite-Atlas sensor 0011
>>
>> # The driver to use
>> driver = user.sdr
>> cmd = rtl_433 -R 40 -M utc -F json
>>
>> [[sensor_map]]
>> outTemp = temperature.0011.AcuriteAtlasPacket
>> outHumidity = humidity.0011.AcuriteAtlasPacket
>> windSpeed = wind_speed.0011.AcuriteAtlasPacket
>> windDir = wind_dir.0011.AcuriteAtlasPacket
>> UV = uv.0011.AcuriteAtlasPacket
>> luminosity = lux.0011.AcuriteAtlasPacket
>> Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
>> Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
>> lightning_distance = strike_distance.0011.AcuriteAtlasPacket
>> windBatteryStatus = battery.0011.AcuriteAtlasPacket
>> batteryStatus1 = battery.0011.AcuriteAtlasPacket
>>
>> [[deltas]]
>> rain = Atlas_rain_total
>> lightning_strike_count = Atlas_strike_count
>>
>>
>> ##
>>
>> On Tuesday, June 13, 2023 at 1:58:17 PM UTC-5 Kevin Crivelli wrote:
>>
>>> I added the line
>>> lightning_distance = lightning_distance / 1.609 if
>>> lightning_strike_count > 0 else None#convert distance to miles
>>>
>>> to the [StdCalibrate] [[Corrections]] section and I added your chart to
>>> my graphs.conf
>>>
>>> I am still getting the persistant distance of 5 miles as per the last
>>> lightning distance that was recorded weeks ago. not sure where to go from
>>> here but thank you for providing all of that for me.
>>>
>>> [image: lightning5.JPG]
>>>
>>>
>>> On Sunday, June 11, 2023 at 5:09:28 PM UTC-4 Eric K wrote:
>>>
 Hi Kevin,

 In the graphs.conf file (Belchertown skin) I have this:

 [[chart6]]
 title = Lightning
 [[[lightning_strike_count]]]
 yAxis = 0
 yAxis_min = 0
 yAxis_tickInterval = 1
 yAxis_label = "Number of Strikes"
 stacking = normal
 color = "orange"
 lineWidth = 0

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[Kevin Crivelli]

mines definitely a little different. This is what I already have. It seems
to follow the logic you shared above in your configuration but my packets
are named differently. where you have "Atlas_strike_count =
strike_count.0011.AcuriteAtlasPacket" I have "strikes_total =
strikes_total.1255.AcuriteLightningPacket". from looking at my deltas
section, does it look as though I have this set up correctly or am I off a
little bit?

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

# The driver to use
driver = user.sdr


[[sensor_map]]
outTemp = temperature.030B.AcuriteAtlasPacket
outHumidity = humidity.030B.AcuriteAtlasPacket
windSpeed = wind_speed.030B.AcuriteAtlasPacket
windDir = wind_dir.030B.AcuriteAtlasPacket
UV = uv.030B.AcuriteAtlasPacket
rain_total = rain_total.030B.AcuriteAtlasPacket
radiation = lux.030B.AcuriteAtlasPacket
lux = lux.030B.AcuriteAtlasPacket
outTempBatteryStatus = battery.030B.AcuriteAtlasPacket
lightning_distance = distance.1255.AcuriteLightningPacket
strikes_total = strikes_total.1255.AcuriteLightningPacket
inTemp = temperature.3071.AcuriteTowerPacketV2
inHumidity = humidity.3071.AcuriteTowerPacketV2
pressure = pressure.171.FOWH32BPacket


[[deltas]]
rain = rain_total
lightning_strike_count = strikes_total



On Tue, Jun 13, 2023 at 3:11 PM Eric K  wrote:

> I forgot about the [SDR] section of the weewx.conf file.
> weewx needs to convert the lightning strike count reported by the Acurite
> Atlas to a lightning strike delta number.
> This is because the Atlas counts up lightning strikes and keeps
> incrementing the accumulated strike number (such as 5).
> When the next strike ocurrs the Atlas will increment the number to 6, and
> so on.
> You need weewx to watch for a change in that Atlas lightning strike number
> and report that difference (delta) between the last count and the current
> count.
>
> from my weewx.conf file:
>
> ##
>
> [SDR]
> # This section is for the software-defined radio driver.
> # collect data from Acurite-Atlas sensor 0011
>
> # The driver to use
> driver = user.sdr
> cmd = rtl_433 -R 40 -M utc -F json
>
> [[sensor_map]]
> outTemp = temperature.0011.AcuriteAtlasPacket
> outHumidity = humidity.0011.AcuriteAtlasPacket
> windSpeed = wind_speed.0011.AcuriteAtlasPacket
> windDir = wind_dir.0011.AcuriteAtlasPacket
> UV = uv.0011.AcuriteAtlasPacket
> luminosity = lux.0011.AcuriteAtlasPacket
> Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
> Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
> lightning_distance = strike_distance.0011.AcuriteAtlasPacket
> windBatteryStatus = battery.0011.AcuriteAtlasPacket
> batteryStatus1 = battery.0011.AcuriteAtlasPacket
>
> [[deltas]]
> rain = Atlas_rain_total
> lightning_strike_count = Atlas_strike_count
>
>
> ##
>
> On Tuesday, June 13, 2023 at 1:58:17 PM UTC-5 Kevin Crivelli wrote:
>
>> I added the line
>> lightning_distance = lightning_distance / 1.609 if lightning_strike_count
>> > 0 else None#convert distance to miles
>>
>> to the [StdCalibrate] [[Corrections]] section and I added your chart to
>> my graphs.conf
>>
>> I am still getting the persistant distance of 5 miles as per the last
>> lightning distance that was recorded weeks ago. not sure where to go from
>> here but thank you for providing all of that for me.
>>
>> [image: lightning5.JPG]
>>
>>
>> On Sunday, June 11, 2023 at 5:09:28 PM UTC-4 Eric K wrote:
>>
>>> Hi Kevin,
>>>
>>> In the graphs.conf file (Belchertown skin) I have this:
>>>
>>> [[chart6]]
>>> title = Lightning
>>> [[[lightning_strike_count]]]
>>> yAxis = 0
>>> yAxis_min = 0
>>> yAxis_tickInterval = 1
>>> yAxis_label = "Number of Strikes"
>>> stacking = normal
>>> color = "orange"
>>> lineWidth = 0
>>> marker
>>> enabled = true
>>> radius = 4
>>> states
>>> [hover]
>>> lineWidthPlus = 0
>>> [[[lightning_distance]]]
>>> yAxis = 1
>>> yAxis_min = 0
>>> yAxis_label = "Distance (miles)"
>>> stacking = normal
>>> color = "blue"
>>> lineWidth = 0
>>> marker
>>> enabled = true
>>> radius = 3
>>> states
>>> [hover]
>>> lineWidthPlus = 0
>>>
>>>
>>> For the distance correction (conversion to miles) I have an entry in the
>>> StdCalibrate section of weewx.

[weewx-user] Re: Lightning Data Stored in weewx.sdb

[Eric K]

I forgot about the [SDR] section of the weewx.conf file.
weewx needs to convert the lightning strike count reported by the Acurite 
Atlas to a lightning strike delta number.
This is because the Atlas counts up lightning strikes and keeps 
incrementing the accumulated strike number (such as 5).
When the next strike ocurrs the Atlas will increment the number to 6, and 
so on.
You need weewx to watch for a change in that Atlas lightning strike number 
and report that difference (delta) between the last count and the current 
count.

from my weewx.conf file:
##

[SDR]
# This section is for the software-defined radio driver.
# collect data from Acurite-Atlas sensor 0011

# The driver to use
driver = user.sdr
cmd = rtl_433 -R 40 -M utc -F json

[[sensor_map]]
outTemp = temperature.0011.AcuriteAtlasPacket
outHumidity = humidity.0011.AcuriteAtlasPacket
windSpeed = wind_speed.0011.AcuriteAtlasPacket
windDir = wind_dir.0011.AcuriteAtlasPacket
UV = uv.0011.AcuriteAtlasPacket
luminosity = lux.0011.AcuriteAtlasPacket
Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
lightning_distance = strike_distance.0011.AcuriteAtlasPacket
windBatteryStatus = battery.0011.AcuriteAtlasPacket
batteryStatus1 = battery.0011.AcuriteAtlasPacket

[[deltas]]
rain = Atlas_rain_total
lightning_strike_count = Atlas_strike_count

##

On Tuesday, June 13, 2023 at 1:58:17 PM UTC-5 Kevin Crivelli wrote:

> I added the line 
> lightning_distance = lightning_distance / 1.609 if lightning_strike_count 
> > 0 else None#convert distance to miles 
>
> to the [StdCalibrate] [[Corrections]] section and I added your chart to my 
> graphs.conf 
>
> I am still getting the persistant distance of 5 miles as per the last 
> lightning distance that was recorded weeks ago. not sure where to go from 
> here but thank you for providing all of that for me. 
>
> [image: lightning5.JPG]
>
>
> On Sunday, June 11, 2023 at 5:09:28 PM UTC-4 Eric K wrote:
>
>> Hi Kevin,
>>
>> In the graphs.conf file (Belchertown skin) I have this:
>>
>> [[chart6]]
>> title = Lightning
>> [[[lightning_strike_count]]]
>> yAxis = 0
>> yAxis_min = 0
>> yAxis_tickInterval = 1
>> yAxis_label = "Number of Strikes"
>> stacking = normal
>> color = "orange"
>> lineWidth = 0
>> marker
>> enabled = true
>> radius = 4
>> states
>> [hover]
>> lineWidthPlus = 0
>> [[[lightning_distance]]]
>> yAxis = 1
>> yAxis_min = 0
>> yAxis_label = "Distance (miles)"
>> stacking = normal
>> color = "blue"
>> lineWidth = 0
>> marker
>> enabled = true
>> radius = 3
>> states
>> [hover]
>> lineWidthPlus = 0 
>>
>>
>> For the distance correction (conversion to miles) I have an entry in the 
>> StdCalibrate section of weewx.conf:
>>
>> ##
>>
>> #   This section can adjust data using calibration expressions.
>>
>> [StdCalibrate]
>> 
>> [[Corrections]]
>> # For each type, an arbitrary calibration expression can be given.
>> # It should be in the units defined in the StdConvert section.
>> # Example:  foo = foo + 0.2
>> outTemp = outTemp + 0.0
>> barometer = barometer + 1.025
>> radiation = luminosity * 0.00789 if luminosity > 0 else None
>> lightning_distance = lightning_distance / 1.609 if 
>> lightning_strike_count > 0 else None#convert distance to miles
>>
>>
>> ##
>>
>>
>>
>> On Sunday, June 11, 2023 at 3:36:30 PM UTC-5 Kevin Crivelli wrote:
>>
>> Eric K, could you provide the chart.conf configuration for that chart and 
>> also what ended up being the correct way to add the correction in 
>> weewx.conf? Your chart is essentially what I am trying to accomplish
>>
>> On Tuesday, May 25, 2021 at 12:36:09 PM UTC-4 Eric K wrote:
>>
>> It's working as desired now!
>> Thanks for noticing the incorrect location of the [[Corrections]]
>>
>> [image: lightning_distance working.JPG]
>>
>> On Monday, May 24, 2021 at 7:39:25 AM UTC-5 gjr80 wrote:
>>
>> I can't explain it, it would require some detailed knowledge of how the 
>> Acurite lightning sensor behaves. For example, the Ecowitt lightning sensor 
>> reports distance when 

[weewx-user] Re: Lightning Data Stored in weewx.sdb

[Kevin Crivelli]

I added the line 
lightning_distance = lightning_distance / 1.609 if lightning_strike_count > 
0 else None#convert distance to miles 

to the [StdCalibrate] [[Corrections]] section and I added your chart to my 
graphs.conf 

I am still getting the persistant distance of 5 miles as per the last 
lightning distance that was recorded weeks ago. not sure where to go from 
here but thank you for providing all of that for me. 

[image: lightning5.JPG]


On Sunday, June 11, 2023 at 5:09:28 PM UTC-4 Eric K wrote:

> Hi Kevin,
>
> In the graphs.conf file (Belchertown skin) I have this:
>
> [[chart6]]
> title = Lightning
> [[[lightning_strike_count]]]
> yAxis = 0
> yAxis_min = 0
> yAxis_tickInterval = 1
> yAxis_label = "Number of Strikes"
> stacking = normal
> color = "orange"
> lineWidth = 0
> marker
> enabled = true
> radius = 4
> states
> [hover]
> lineWidthPlus = 0
> [[[lightning_distance]]]
> yAxis = 1
> yAxis_min = 0
> yAxis_label = "Distance (miles)"
> stacking = normal
> color = "blue"
> lineWidth = 0
> marker
> enabled = true
> radius = 3
> states
> [hover]
> lineWidthPlus = 0 
>
>
> For the distance correction (conversion to miles) I have an entry in the 
> StdCalibrate section of weewx.conf:
>
> ##
>
> #   This section can adjust data using calibration expressions.
>
> [StdCalibrate]
> 
> [[Corrections]]
> # For each type, an arbitrary calibration expression can be given.
> # It should be in the units defined in the StdConvert section.
> # Example:  foo = foo + 0.2
> outTemp = outTemp + 0.0
> barometer = barometer + 1.025
> radiation = luminosity * 0.00789 if luminosity > 0 else None
> lightning_distance = lightning_distance / 1.609 if 
> lightning_strike_count > 0 else None#convert distance to miles
>
>
> ##
>
>
>
> On Sunday, June 11, 2023 at 3:36:30 PM UTC-5 Kevin Crivelli wrote:
>
> Eric K, could you provide the chart.conf configuration for that chart and 
> also what ended up being the correct way to add the correction in 
> weewx.conf? Your chart is essentially what I am trying to accomplish
>
> On Tuesday, May 25, 2021 at 12:36:09 PM UTC-4 Eric K wrote:
>
> It's working as desired now!
> Thanks for noticing the incorrect location of the [[Corrections]]
>
> [image: lightning_distance working.JPG]
>
> On Monday, May 24, 2021 at 7:39:25 AM UTC-5 gjr80 wrote:
>
> I can't explain it, it would require some detailed knowledge of how the 
> Acurite lightning sensor behaves. For example, the Ecowitt lightning sensor 
> reports distance when strikes are detected and that distance value persists 
> for some time before eventually reporting 0. If you had debug logging of 
> the SDR output (as you have in the log extract above) going on for some 
> time previous you could probably work through the log looking at the 
> distance value being obtained by the SDR driver from the Acurite. One thing 
> is certain though, the SDR driver was not applying the correction as the 
> SDR driver contains no code to read those config settings. And if the 
> correction was not under [StdCalibrate] [[Corrections]] then WeeWX wasn't 
> applying the correction either.
>
> Might just have to remain a mystery.
>
> Gary
>
> On Monday, 24 May 2021 at 07:33:56 UTC+10 Eric K wrote:
>
> Thanks for the pointer.  
> I also had a [[Corrections]] sections under [StdCalibrate].
>
> I just moved the lightning_distance correction to the [StdCalibrate] 
> section.
> We'll see if that helps.
>
> Isn't it odd that it worked, when the lightning_distance was something 
> other than 10?
>
>
> On Sunday, May 23, 2021 at 3:10:54 PM UTC-5 gjr80 wrote:
>
> I think you might find the [[Corrections]] stanza belongs under 
> [StdCalibrate]  rather 
> than the SDR driver.
>
> Gary
> On Monday, 24 May 2021 at 02:32:14 UTC+10 Eric K wrote:
>
> Here's a relevant section of the log which shows the Acurite Atlas 
> lightning sensor sending the last distance (10) reading over and over.  
> This is expected Acurite Atlas behavior, and the reason we have to put the 
> "if > 0 else None" statement in our [[Corrections]] section.
>
> Referring back to the 5.64705882352941 value seen in my database:
> I wonder if weewx isn't expecting a decimal reading to be in 
> lightning_distance?
> And that sends it into confusion?
>
> May 23 10:56:24 Ubuntu20-WEEWX weewx

[weewx-user] Re: weewx mqtt

[kufuu]

That is what happened,  Thanks very much


On Tuesday, June 13, 2023 at 12:09:33 PM UTC-4 vince wrote:

> You are trying to install a file 
> /usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz that is not found.You 
> likely downloaded it to a different directory.
>
> On Tuesday, June 13, 2023 at 5:38:24 AM UTC-7 kufuu wrote:
>
>> Trying to install mqtt subscribe in ubuntu and on a rpi zero-w and get 
>> the same issue
>>
>> wee_extension --install=/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz
>> Request to install '/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz'
>> Traceback (most recent call last):
>> File "/usr/share/weewx/wee_extension", line 92, in
>> main()
>> File "/usr/share/weewx/wee_extension", line 84, in main
>> ext.install_extension(options.install)
>> File "/usr/share/weewx/weecfg/extension.py", line 139, in 
>> install_extension
>> raise InstallError("Extension '%s' not found." % extension_path)
>> weecfg.extension.InstallError: Extension 
>> '/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz' not found.
>>
>> What am i doing wrong ?
>
>

-- 
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/3731c1de-1e0b-4fc7-b2ff-220baa4a123cn%40googlegroups.com.

Re: [weewx-user] Weewx keeps restarting

[Mark Fraser]

On 13/06/2023 17:16, Graham Eddy wrote:
assuming you rolled everything back, then rolled forward one step at a 
time until it started to fail, what was the last step causing it to fail?

*⊣GE⊢*


It is something the Seasons skin is trying to do as if I disable it in 
weewx.conf it works. I have made a backup of my Seasons skin and tried 
using the one from https://github.com/weewx/weewx and it still it:


Jun 13 19:10:50 weather-new systemd[1]: weewx.service: Main process 
exited, code=killed, status=11/SEGV
Jun 13 19:10:50 weather-new systemd[1]: weewx.service: Failed with 
result 'signal'.


--
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/1e67eb3e-06e5-cf10-9616-5e812fb8bb3c%40gmail.com.

[weewx-user] interceptor driver, HP2560 and WS90 [2]

['Rainer Lang' via weewx-user]

One more thing - regarding mapping and field names

the weewx names to map to are the database field names of the database 
schema you use for your database
(nowadays usually wview-extended - look up the schema in 
/usr/share/weewx/schemas/wview-extended.py)

[or /home/weewx/bin/schemas  depending on your setup]
you have to map the (additional) field names from the interceptor.py to 
the respective weewx (database) fields from wview-extended.py

(either inside the interceptor.py or via a field-map extension)

if you want to store the new fields which are not in the wview-extended 
schema, you will either have to repurpose existing but unused database 
fields

or extend your database schema with the respective columns

On 13.06.2023 19:40, Rainer Lang wrote:


Hi Jason

1. the local API (local Ecowitt Gateway API aka GW1000 API) was never 
implemented in the HP25x0, HP350x, WH2910 consoles => so no such thing 
like depreciation
you want to know which console supports which API, look up 
https://www.wxforum.net/index.php?topic=40730.0 😎


2. the reason why you may not receive WS90 (piezo rain) data via the 
custom server could be that your WS90 has not been set in the console 
as primary rain device.

gear wheel --> setup (more) --> rain priority (has to be set to piezo).

3. could you run the interceptor driver stand-alone and post here the 
result of one console post ?

(or run weewx in debug = 3 mode and copy from the syslog)

regards

Rainer

On 13.06.2023 02:28, Jason Gibson wrote:

Hi All,

I have been trying to coax rain data out of the WS90 and into weewx.

I assume that the local API is deprecated on the HP2560 as I can't 
appear to get any details out of it on port 45000.


I am currently using the interceptor driver in listen mode on port 
8080.  And I am able to  log all data in WeeWX except rain from the 
piezo sensor, and battery voltages.


I have tried mapping sensors to fields as below, to no avail, is 
anyone able to assist with the interceptor driver, or is there 
another driver better suited to my hardware?


Hardware:
-
HP2564 - HP2560 & WS90

HP2560_C:
  Hardware revision V2.0
  Firmware: Pro_V1.9.0
  EasyWeatherProv5.11
WS90:
  Firmware 1.3.3

weewx.conf extract:


driver = user.interceptor
    device_type = ecowitt-client
    port = 8080
    iface = ens18
    [[sensor_map_extensions]]
          rain = drain_piezo
          rainRate = rrain_piezo
          bat_wind = wh90batt
          bat_rain = ws90cap_volt

Am I using the right field names?  Example output from the ws90 is as 
follows:


PASSKEY: 
stationtype: EasyWeatherPro_V5.1.1
runtime: 2
dateutc: 2023-06-11 01:53:27
tempinf: 77.0
humidityin: 40
baromrelin: 30.224
baromabsin: 29.946
tempf: 61.2
humidity: 60
winddir: 12
windspeedmph: 5.14
windgustmph: 6.93
maxdailygust: 10.74
solarradiation: 270.64
uv: 2
rrain_piezo: 0.000
erain_piezo: 0.000
hrain_piezo: 0.000
drain_piezo: 0.000
wrain_piezo: 0.000
mrain_piezo: 1.209
yrain_piezo: 1.209
ws90cap_volt: 5.2
ws90_ver: 133
gain10_piezo: 1.15
gain20_piezo: 1.05
gain30_piezo: 1.00
gain40_piezo: 1.00
gain50_piezo: 1.00
wh90batt: 3.10
freq: 433M
model: HP2564CA_Pro_V1.9.0
interval: 30

Cheers,

Jason
--
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/8828c0f2-f040-4558-bf6d-f2ff1dedb0ben%40googlegroups.com 
.


--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dc415326-02ca-9b63-8653-5b25318b8e9d%40gmail.com.

Re: [weewx-user] interceptor driver, HP2560 and WS90

['Rainer Lang' via weewx-user]

Hi Jason

1. the local API (local Ecowitt Gateway API aka GW1000 API) was never 
implemented in the HP25x0, HP350x, WH2910 consoles => so no such thing 
like depreciation
you want to know which console supports which API, look up 
https://www.wxforum.net/index.php?topic=40730.0 😎


2. the reason why you may not receive WS90 (piezo rain) data via the 
custom server could be that your WS90 has not been set in the console as 
primary rain device.

gear wheel --> setup (more) --> rain priority (has to be set to piezo).

3. could you run the interceptor driver stand-alone and post here the 
result of one console post ?

(or run weewx in debug = 3 mode and copy from the syslog)

regards

Rainer

On 13.06.2023 02:28, Jason Gibson wrote:

Hi All,

I have been trying to coax rain data out of the WS90 and into weewx.

I assume that the local API is deprecated on the HP2560 as I can't 
appear to get any details out of it on port 45000.


I am currently using the interceptor driver in listen mode on port 
8080.  And I am able to  log all data in WeeWX except rain from the 
piezo sensor, and battery voltages.


I have tried mapping sensors to fields as below, to no avail, is 
anyone able to assist with the interceptor driver, or is there another 
driver better suited to my hardware?


Hardware:
-
HP2564 - HP2560 & WS90

HP2560_C:
  Hardware revision V2.0
  Firmware: Pro_V1.9.0
  EasyWeatherProv5.11
WS90:
  Firmware 1.3.3

weewx.conf extract:


driver = user.interceptor
    device_type = ecowitt-client
    port = 8080
    iface = ens18
    [[sensor_map_extensions]]
          rain = drain_piezo
          rainRate = rrain_piezo
          bat_wind = wh90batt
          bat_rain = ws90cap_volt

Am I using the right field names?  Example output from the ws90 is as 
follows:


PASSKEY: 
stationtype: EasyWeatherPro_V5.1.1
runtime: 2
dateutc: 2023-06-11 01:53:27
tempinf: 77.0
humidityin: 40
baromrelin: 30.224
baromabsin: 29.946
tempf: 61.2
humidity: 60
winddir: 12
windspeedmph: 5.14
windgustmph: 6.93
maxdailygust: 10.74
solarradiation: 270.64
uv: 2
rrain_piezo: 0.000
erain_piezo: 0.000
hrain_piezo: 0.000
drain_piezo: 0.000
wrain_piezo: 0.000
mrain_piezo: 1.209
yrain_piezo: 1.209
ws90cap_volt: 5.2
ws90_ver: 133
gain10_piezo: 1.15
gain20_piezo: 1.05
gain30_piezo: 1.00
gain40_piezo: 1.00
gain50_piezo: 1.00
wh90batt: 3.10
freq: 433M
model: HP2564CA_Pro_V1.9.0
interval: 30

Cheers,

Jason
--
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/8828c0f2-f040-4558-bf6d-f2ff1dedb0ben%40googlegroups.com 
.


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

Re: [weewx-user] Weewx keeps restarting

[Mark Fraser]

On 13/06/2023 17:16, Graham Eddy wrote:
assuming you rolled everything back, then rolled forward one step at a 
time until it started to fail, what was the last step causing it to fail?


At the moment I've disabled the seasons skin and am just running 
Belchertown which is working. So, I need to look into the seasons skin 
config, but I haven't changed anything in there.


--
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/c93e3d21-4062-7ed0-d454-3743485bf039%40gmail.com.

Re: [weewx-user] Weewx keeps restarting

[Graham Eddy]

assuming you rolled everything back, then rolled forward one step at a time 
until it started to fail, what was the last step causing it to fail?
⊣GE⊢

> On 14 Jun 2023, at 1:09 am, Mark Fraser  wrote:
> 
>  I can't think of anything I've changed that would cause this

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/11AABE7B-E104-4C5A-A1FF-D376430A2841%40geddy.au.

[weewx-user] Re: weewx mqtt

[vince]

You are trying to install a file 
/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz that is not found.You 
likely downloaded it to a different directory.

On Tuesday, June 13, 2023 at 5:38:24 AM UTC-7 kufuu wrote:

> Trying to install mqtt subscribe in ubuntu and on a rpi zero-w and get the 
> same issue
>
> wee_extension --install=/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz
> Request to install '/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz'
> Traceback (most recent call last):
> File "/usr/share/weewx/wee_extension", line 92, in
> main()
> File "/usr/share/weewx/wee_extension", line 84, in main
> ext.install_extension(options.install)
> File "/usr/share/weewx/weecfg/extension.py", line 139, in install_extension
> raise InstallError("Extension '%s' not found." % extension_path)
> weecfg.extension.InstallError: Extension 
> '/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz' not found.
>
> What am i doing wrong ?

-- 
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/17c5998c-b343-4723-91b8-d3f3eaae8e8en%40googlegroups.com.

Re: [weewx-user] Weewx keeps restarting

[Mark Fraser]

On 11/06/2023 15:32, Graham Eddy wrote:

disable everythng back to bare bones, then add them back again one at a time
*⊣GE⊢*


Comparing 2 logs for where it succeeded and failed:


Jun 13 06:25:40 weather-new weewx[22104] DEBUG weewx.cheetahgenerator: 
Using search list ['user.forecast.ForecastVariables', 
'weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Jun 13 06:25:40 weather-new weewx[22104] DEBUG weewx.manager: Daily 
summary version is 4.0
Jun 13 06:25:44 weather-new weewx[22104] DEBUG weewx.cheetahgenerator: 
Skip 'celestial.html': last_mod=1686633634.2798502 
age=310.23253083229065 stale=3600
Jun 13 06:25:44 weather-new weewx[22104] INFO weewx.cheetahgenerator: 
Generated 10 files for report SeasonsReport in 4.37 seconds
Jun 13 06:25:44 weather-new weewx[22104] DEBUG weewx.manager: Daily 
summary version is 4.0
Jun 13 06:25:45 weather-new systemd[1]: weewx.service: Main process 
exited, code=killed, status=11/SEGV
Jun 13 06:25:45 weather-new systemd[1]: weewx.service: Failed with 
result 'signal'.


Jun 13 06:20:31 weather-new weewx[22104] DEBUG weewx.cheetahgenerator: 
Using search list ['user.forecast.ForecastVariables', 
'weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Jun 13 06:20:31 weather-new weewx[22104] DEBUG weewx.manager: Daily 
summary version is 4.0
Jun 13 06:20:34 weather-new weewx[22104] INFO weewx.cheetahgenerator: 
Generated 11 files for report SeasonsReport in 3.63 seconds
Jun 13 06:20:34 weather-new weewx[22104] DEBUG weewx.manager: Daily 
summary version is 4.0
Jun 13 06:20:36 weather-new weewx[22104] INFO weewx.imagegenerator: 
Generated 17 images for report SeasonsReport in 1.51 seconds


It seems to be failing when generating the images, I can't think of 
anything I've changed that would cause this.


--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9e3cc41a-7b02-9b5c-cd4b-5ac5f1a6734e%40gmail.com.

[weewx-user] weewx mqtt

[kufuu]

Trying to install mqtt subscribe in ubuntu and on a rpi zero-w and get the 
same issue

wee_extension --install=/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz
Request to install '/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz'
Traceback (most recent call last):
File "/usr/share/weewx/wee_extension", line 92, in
main()
File "/usr/share/weewx/wee_extension", line 84, in main
ext.install_extension(options.install)
File "/usr/share/weewx/weecfg/extension.py", line 139, in install_extension
raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension 
'/usr/local/bin/WeeWX-MQTTSubscribe/v2.2.2.tar.gz' not found.

What am i doing wrong ?

-- 
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/d3c73a33-22c6-4e4f-9776-7e0bc7c1644cn%40googlegroups.com.