[weewx-user] Re: Tempest WeatherFlow Lightning

[Dan Roman]

Hi John,

I never did quite figure this out so that it works like I expect it to.  I 
have tried it using the Seasons and Belchertown skins with slightly 
different results using what I thought were the same methods.  I'll share 
all my settings with you, it doesn't work exactly as I had hoped, and I 
have not gone back in to debug it all in quite a while.  If you want to 
take a look at what I did, maybe you'll find where I went wrong.  I think I 
need to add some calculations to add things like lightning strikes in the 
last 3 hours, etc.

For lightning, my graphs seem to work in Seasons but not the current 
conditions.  In Belchertown the current observations for lightning don't 
appear to work but the graphs are almost there.  The Belchertown graph 
lightning count looks like it works but I would like them to report the 
minimum distance and I'm not sure that is what I am getting.

Before I get into my particular settings, this guy 
https://weather.sangrephotography.com/ seems to have figured it out. I 
contacted him to see if he would share his Belchertown skin config file but 
he didn't answer me and I have not been able to reverse engineer it.  As 
you can see from his page, he has a section for lightning that includes 
Time since last lightning strike, Strikes the last 3 hours, Strikes the 
last hour,  Distance last strike, and Range of last strike.  I would like 
to figure out how to replicate this.

Here are my settings for the tempest sensor map in the weewx config file:

[[sensor_map]]
# This section is for handling data for the Tempest Weather Station
outTemp = air_temperature.ST-.obs_st
outHumidity = relative_humidity.ST-  .obs_st
pressure = station_pressure.ST-  .obs_st
lightning_strikes = lightning_strike_count.ST-  .obs_st
avg_distance = lightning_strike_avg_distance.ST- .obs_st
outTempBatteryStatus = battery.ST- .obs_st
windSpeed = wind_speed.ST- .rapid_wind
windDir = wind_direction.ST- .rapid_wind
luminosity = illuminance.ST- .obs_st
UV = uv.ST- .obs_st
rain = rain_accumulated.ST- .obs_st
radiation = solar_radiation.ST- .obs_st
lightning_distance = distance.ST- .evt_strike
lightning_strike_count = lightning_strike_count.ST- .obs_st

And also from weewx.conf, the Belchertown observation list:

station_observations = barometer, dewpoint, outHumidity, 
rainWithRainRate, UV, cloud_cover, outTempBatteryStatus, 
lightning_strike_count, lightning_distance

NOTE:  I removed avg_distance and lightning_strikes from the sample I had 
because they displayed Invalid Observation.

And again from weewx.conf:

[StdCalibrate]
[[Corrections]]
lightning_distance = lightning_distance if lightning_strike_count > 
0 else None

and

[Accumulator]
[[lightning_strikes]]
extractor = sum
[[lightning_distance]]
extractor = min
[[avg_distance]]
extractor = avg

Here are some lightning entries for the Seasons skin:

>From skin.conf:

[DisplayOptions]

# This list determines which types will appear in the "current 
conditions"
# section, as well as in which order.
observations_current = outTemp, heatindex, windchill, dewpoint, 
outHumidity, barometer, windSpeed, rain, rainRate, UV, radiation, 
lightning_strikes, lightning_distance, lightning_strike_count, avg_distance

# This list determines which types will appear in the "statistics" and
# "statistical summary" sections, as well as in which order.
observations_stats = outTemp, heatindex, windchill, dewpoint, 
outHumidity, barometer, windSpeed, rain, rainRate, ET, UV, radiation, 
lightning_strikes, lightning_distance, aqi, outTempBatteryStatus

# Some observations display a sum rather than min/max values
obs_type_sum = rain, ET, hail, snow, lightning_strikes

# Some observations display only the max or min value
obs_type_max = rainRate, hailRate, snowRate, UV
obs_type_min = lightning_distance

plot_groups = barometer, tempdew, tempfeel, hum, wind, winddir, 
windvec, rain, ET, UV, radiation, lightning, lightningdistance, volt, hilow

[[day_images]]
x_label_format = %H:%M
bottom_label_format = %x %X
time_length = 97200 # 27 hours

 [[[daylightning]]]
yscale = None, None, 1
plot_type = bar
lightning_strike_count
aggregate_type = sum
aggregate_interval = hour
label = Lightning (hourly total)

[[[daylightningdistance]]]
yscale = 0, 25, 5
line_type = None
marker_type = box
marker_size = 2
#plot_type = bar
lightning_distance
#aggregate_type = min
#aggregate_interval = hour
label

Re: [weewx-user] Re: Belchertown lightning graph

[Dan Roman]

No, I have not.  The consensus was since it is only a warning, and
everything else still works, it wasn't worth trying to muck around and fix
the format in the belly of the beast.  So I just let it be.


On Wed, Feb 14, 2024 at 3:51 PM Joachim Puttkammer 
wrote:

> Except that:
> user.belchertown: Observation lightning_strike_count is using unit count
> that returns %d for StringFormat, rather than float point decimal format
> value - using 0 as rounding
> Is showing in the system log.
>
> Have you solved the problem?
> Mark Fraser schrieb am Dienstag, 20. Juni 2023 um 12:05:47 UTC+2:
>
>> I currently have this in graphs.conf to show lightning strikes over the
>> past 3 hours and it works:
>>
>> [[Lightning_chart]]
>> title = Lightning (Last 3 Hours)
>> time_length = 10800
>> aggregate_interval = 300
>> gapsize = 108000
>> type = column
>>
>> [[[lightning_strike_count]]]
>> name = Lightning Count
>> zIndex = 1
>> aggregate_type = sum
>>
>> Except that:
>> user.belchertown: Observation lightning_strike_count is using unit count
>> that returns %d for StringFormat, rather than float point decimal format
>> value - using 0 as rounding
>> Is showing in the system log.
>>
> --
> 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/8S1zsvbW2v8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d0e589e4-e830-4a04-a184-84991840c69dn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/d0e589e4-e830-4a04-a184-84991840c69dn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Dan Roman
gdann...@gmail.com

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

[weewx-user] Re: Aeris forcast with belchertown

[Dan Roman]

Yes, I am.  When it was failing when I manually entered the URL in a 
browser I got back the following JSON response:

{"success":false,"error":{"code":"maxhits_daily","description":"Maximum 
number of daily accesses reached."},"response":[]}

But as I said, after I waited a day or two it cleared itself up and started 
working again without my needing to change anything.



On Sunday, January 28, 2024 at 7:56:40 PM UTC-5 bchap...@gmail.com wrote:

> Are you using the aeris maps?  That's where I found my issue.  The maps 
> rack up hundreds of requests per hour and max you out real quick.  I turned 
> off aeris maps and now I have less than 300 hits per day.
>
> On Sunday, January 28, 2024 at 1:25:38 PM UTC-5 Dan Roman wrote:
>
>> I had this problem back in October but it cleared itself up.  Never 
>> determined if it was an Aeris or Blechertown problem.  Didn't need to 
>> change my password, delete my account, or anything.  It was just a glitch 
>> in the matrix I guess that went on for a couple of days and then fixed 
>> itself.
>>
>>
>> On Friday, January 26, 2024 at 11:32:57 AM UTC-5 bchap...@gmail.com 
>> wrote:
>>
>>> So, I've solved my problem.  If you're using the aeris free account on 
>>> their contributor plan, do not turn on aeris maps in the belchertown 
>>> settings.  I don't know what has changed on their end because I have had 
>>> the same configuration for many years, but now the map will make thousands 
>>> of hits per hour and they will shut you down when you exceed your allowed 
>>> 5,000 hits.  I turned off the aeris maps and all looks well so far.
>>>
>>> On Wednesday, January 24, 2024 at 11:08:16 PM UTC-5 bchap...@gmail.com 
>>> wrote:
>>>
>>>> I've done that.  Should have mentioned in original post.  I've changed 
>>>> my password, deleted and created a new app.  My hit count reset at 1900EST 
>>>> and within an hour I was at ~600 hits, and that's with forcasting turned 
>>>> off in the conf file.  Aeris tech support has not been able to solve this. 
>>>>  
>>>> I'm thinking I may need to delete my account with them and re-create a new 
>>>> one.  
>>>>
>>>> On Wednesday, January 24, 2024 at 7:38:45 PM UTC-5 bchap...@gmail.com 
>>>> wrote:
>>>>
>>>>> Is anyone else having problems with aeris forcasting?  For the past 
>>>>> few weeks my access credits have been running out resulting in my webpage 
>>>>> not being updated.  I've turned off forcasting in weewx.conf and when I 
>>>>> watch my activity on aeris the hits keep coming.  I don't know who is 
>>>>> making these requests.  My aeris credits are racking up at an average of 
>>>>> a 
>>>>> few hundred an hour, even with forcasting turned off.  I've contacted 
>>>>> aeris 
>>>>> tech support which has not been helpful.
>>>>>
>>>>

-- 
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/52b5adb6-2610-434c-9197-854b2a8a4729n%40googlegroups.com.

[weewx-user] Re: Aeris forcast with belchertown

[Dan Roman]

I had this problem back in October but it cleared itself up.  Never 
determined if it was an Aeris or Blechertown problem.  Didn't need to 
change my password, delete my account, or anything.  It was just a glitch 
in the matrix I guess that went on for a couple of days and then fixed 
itself.


On Friday, January 26, 2024 at 11:32:57 AM UTC-5 bchap...@gmail.com wrote:

> So, I've solved my problem.  If you're using the aeris free account on 
> their contributor plan, do not turn on aeris maps in the belchertown 
> settings.  I don't know what has changed on their end because I have had 
> the same configuration for many years, but now the map will make thousands 
> of hits per hour and they will shut you down when you exceed your allowed 
> 5,000 hits.  I turned off the aeris maps and all looks well so far.
>
> On Wednesday, January 24, 2024 at 11:08:16 PM UTC-5 bchap...@gmail.com 
> wrote:
>
>> I've done that.  Should have mentioned in original post.  I've changed my 
>> password, deleted and created a new app.  My hit count reset at 1900EST and 
>> within an hour I was at ~600 hits, and that's with forcasting turned off in 
>> the conf file.  Aeris tech support has not been able to solve this.  I'm 
>> thinking I may need to delete my account with them and re-create a new 
>> one.  
>>
>> On Wednesday, January 24, 2024 at 7:38:45 PM UTC-5 bchap...@gmail.com 
>> wrote:
>>
>>> Is anyone else having problems with aeris forcasting?  For the past few 
>>> weeks my access credits have been running out resulting in my webpage not 
>>> being updated.  I've turned off forcasting in weewx.conf and when I watch 
>>> my activity on aeris the hits keep coming.  I don't know who is making 
>>> these requests.  My aeris credits are racking up at an average of a few 
>>> hundred an hour, even with forcasting turned off.  I've contacted aeris 
>>> tech support which has not been helpful.
>>>
>>

-- 
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/52afdb7c-adf9-48d6-ac09-efa5536494dfn%40googlegroups.com.

[weewx-user] Re: How to get rid of unknown and n/a?

[Dan Roman]

Dale, it looks like there are a lot of the canned default sensor parameters 
that are not used by your system.  You will need to go into the skin and 
remove or comment out the sensors that are not part of your system.  You 
don't say which skin the N/A and UNKNOWN are showing up in but you may need 
to edit weewx.conf, a skin.conf, and/or the HTML templates for the skin.  
If you let the group know which skin and provide a screenshot I am sure 
people here can help you further.

Dan


On Friday, October 20, 2023 at 2:32:33 AM UTC-4 Dale Chatham wrote:

> Sensor Status  ♦ 
>
> Connectivity
>
> Signal Quality 
> N/A 
> 1 days ago 
> Battery Status
>
> Outside Temperature Battery 
> UNKNOWN 
> 1 days ago 
> Inside Temperature Battery 
> UNKNOWN 
> 1 days ago 
> Rain Battery 
> UNKNOWN 
> 1 days ago 
> Wind Battery 
> UNKNOWN 
> 1 days ago 
> Transmitter Battery 
> From log:
> Oct 20 01:32:03 fedora-workstation python3[97327]: weewx[97327] INFO 
> user.gw1000: GatewayDriver: Packet 2023-10-20 01:32:03 CDT (1697783523): 
> {'dateTime': '1697783523', 'daymaxwind': '1.1', 'inHumidity': '36', 
> 'inTemp': '24.9', 'lightning_distance': 'None', 'lightning_last_det_time': 
> 'None', 'lightning_strike_count': '0', 'lightningcount': '0', 'luminosity': 
> '0.0', 'outHumidity': '54', 'outTemp': '15.6', 'p_dayRain': '0.0', 
> 'p_monthRain': '0.0', 'p_rain': '0.0', 'p_rainRate': '0.0', 'p_stormRain': 
> '0.0', 'p_weekRain': '0.0', 'p_yearRain': '0.0', 'pressure': '991.1', 
> 'relbarometer': '991.1', 'usUnits': '17', 'UV': '0', 'uvradiation': '0.0', 
> 'wh57_batt': '5', 'wh57_sig': '4', 'windDir': '83', 'windGust': '0.6', 
> 'windSpeed': '0.6', 'ws90_batt': '3.16', 'ws90_sig': '4'}
>
> From web page:
>
> UNKNOWN 
> 1 days ago 
> Voltage
>
> Console Battery 
> N/A 
> 1 days ago 
> Heating Battery 
> N/A 
> 1 days ago 
> Supply Voltage 
> N/A 
> 1 days ago 
> Reference Voltage 
> N/A 
> 1 days ago 
>

-- 
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/d11e8504-5fa7-40a3-b899-973731b251cdn%40googlegroups.com.

Re: [weewx-user] Anyone notice a problem with aeris weather API today?

[Dan Roman]

I should have noted that pasting the Aeris API URL into a browser returns
this JSON:

{"success":false,"error":{"code":"maxhits_daily","description":"Maximum
number of daily accesses reached."},"response":[]}




On Fri, Oct 6, 2023 at 2:25 PM Dan Roman  wrote:

> Early this morning I received an error that there were too many requests
> and it has not cleared up all day.  Log is below with ID and key removed.
>
> Wondering if the server was attached and received too many requests
> because I am only asking one per 5 minutes for the past year without
> problems and now it is an issue.  I disable the forecast for now but
> wondering what is happening.
>
> Dan
>
>
> Oct  5 05:00:20 pimatrix weewx[688] INFO weewx.manager: Added record
> 2023-10-05 05:00:00 EDT (1696496400) to database 'weewx.sdb'
> Oct  5 05:00:20 pimatrix weewx[688] INFO weewx.manager: Added record
> 2023-10-05 05:00:00 EDT (1696496400) to daily summary in 'weewx.sdb'
> Oct  5 05:00:25 pimatrix /weewxd: weatherflowudp: MainThread: Listening
> for UDP broadcasts to IP address  on port 50222, with timeout 90
> and share_socket True...
> Oct  5 05:00:26 pimatrix weewx[688] INFO weewx.restx: PWSWeather:
> Published record 2023-10-05 05:00:00 EDT (1696496400)
> Oct  5 05:00:29 pimatrix weewx[688] INFO weewx.cheetahgenerator: Generated
> 8 files for report SeasonsReport in 4.16 seconds
> Oct  5 05:00:34 pimatrix weewx[688] INFO weewx.imagegenerator: Generated
> 28 images for report SeasonsReport in 4.49 seconds
> Oct  5 05:00:34 pimatrix weewx[688] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Oct  5 05:00:34 pimatrix weewx[688] INFO weewx.cheetahgenerator: Generated
> 6 files for report SmartphoneReport in 0.15 seconds
> Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.imagegenerator: Generated
> 12 images for report SmartphoneReport in 1.74 seconds
> Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx/smartphone
> Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.cheetahgenerator: Generated
> 1 files for report MobileReport in 0.06 seconds
> Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.imagegenerator: Generated 4
> images for report MobileReport in 0.29 seconds
> Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx/mobile
> Oct  5 05:00:37 pimatrix weewx[688] ERROR weewx.reportengine: Caught
> unrecoverable exception in generator
> 'weewx.cheetahgenerator.CheetahGenerator'
> Oct  5 05:00:37 pimatrix weewx[688] ERROR weewx.reportengine: 
>  Error downloading forecast data. Check the URL in your configuration and
> try again. You are trying to use URL:
> https://api.aerisapi.com/forecasts/40.84185,-74.53198?&format=json&filter=day&limit=7&client_id=pr3skoHUQ2jtPDj1WTNMc&client_secret=xMjQphHVAyB7xZyyTNmjIQauvdfQmJWjl8cfEf3D,
> and the error is: HTTP Error 429: Too Many Requests
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>  Traceback (most recent call last):
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>File "/usr/share/weewx/user/belchertown.py", line 1273, in
> get_extension_list
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>  response = urlopen(req)
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>  return opener.open(url, data, timeout)
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>File "/usr/lib/python3.7/urllib/request.py", line 531, in open
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>  response = meth(req, response)
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>  'http', request, response, code, msg, hdrs)
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>File "/usr/lib/python3.7/urllib/request.py", line 569, in error
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>  return self._call_chain(*args)
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine: 
>File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
> Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reporte

[weewx-user] Format error in log - string rather than float

[Dan Roman]

I am receiving the error below in the log.

Oct  5 05:00:38 pimatrix weewx[688] INFO user.belchertown: Observation 
lightning_strike_count is using unit count that returns %d for 
StringFormat, rather than float point decimal format value - using 0 as 
rounding

lightning_strike_count is assigned in weewx.conf here:

lightning_strike_count = lightning_strike_count.ST-00102080.obs_st

Not sure where I should be looking to resolve the disconnect, in weewx or 
the Belchertown skin.  I don't see anything in weewx.conf or graphs.conf or 
skin.conf that lets me specify if a value is a string or float.

Thanks.

-- 
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/7365c96d-164c-4ec7-8027-9b61073dfddbn%40googlegroups.com.

[weewx-user] Anyone notice a problem with aeris weather API today?

[Dan Roman]

Early this morning I received an error that there were too many requests 
and it has not cleared up all day.  Log is below with ID and key removed.

Wondering if the server was attached and received too many requests because 
I am only asking one per 5 minutes for the past year without problems and 
now it is an issue.  I disable the forecast for now but wondering what is 
happening.

Dan


Oct  5 05:00:20 pimatrix weewx[688] INFO weewx.manager: Added record 
2023-10-05 05:00:00 EDT (1696496400) to database 'weewx.sdb'
Oct  5 05:00:20 pimatrix weewx[688] INFO weewx.manager: Added record 
2023-10-05 05:00:00 EDT (1696496400) to daily summary in 'weewx.sdb'
Oct  5 05:00:25 pimatrix /weewxd: weatherflowudp: MainThread: Listening for 
UDP broadcasts to IP address  on port 50222, with timeout 90 and 
share_socket True...
Oct  5 05:00:26 pimatrix weewx[688] INFO weewx.restx: PWSWeather: Published 
record 2023-10-05 05:00:00 EDT (1696496400)
Oct  5 05:00:29 pimatrix weewx[688] INFO weewx.cheetahgenerator: Generated 
8 files for report SeasonsReport in 4.16 seconds
Oct  5 05:00:34 pimatrix weewx[688] INFO weewx.imagegenerator: Generated 28 
images for report SeasonsReport in 4.49 seconds
Oct  5 05:00:34 pimatrix weewx[688] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx
Oct  5 05:00:34 pimatrix weewx[688] INFO weewx.cheetahgenerator: Generated 
6 files for report SmartphoneReport in 0.15 seconds
Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.imagegenerator: Generated 12 
images for report SmartphoneReport in 1.74 seconds
Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx/smartphone
Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.cheetahgenerator: Generated 
1 files for report MobileReport in 0.06 seconds
Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.imagegenerator: Generated 4 
images for report MobileReport in 0.29 seconds
Oct  5 05:00:36 pimatrix weewx[688] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx/mobile
Oct  5 05:00:37 pimatrix weewx[688] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Oct  5 05:00:37 pimatrix weewx[688] ERROR weewx.reportengine:  
 Error downloading forecast data. Check the URL in your configuration and 
try again. You are trying to use URL: 
https://api.aerisapi.com/forecasts/40.84185,-74.53198?&format=json&filter=day&limit=7&client_id=pr3skoHUQ2jtPDj1WTNMc&client_secret=xMjQphHVAyB7xZyyTNmjIQauvdfQmJWjl8cfEf3D,
 
and the error is: HTTP Error 429: Too Many Requests
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 Traceback (most recent call last):
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/share/weewx/user/belchertown.py", line 1273, in 
get_extension_list
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 response = urlopen(req)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 return opener.open(url, data, timeout)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/urllib/request.py", line 531, in open
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 response = meth(req, response)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 'http', request, response, code, msg, hdrs)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/urllib/request.py", line 569, in error
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 return self._call_chain(*args)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 result = func(*args)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/urllib/request.py", line 649, in 
http_error_default
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 raise HTTPError(req.full_url, code, msg, hdrs, fp)
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 urllib.error.HTTPError: HTTP Error 429: Too Many Requests
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:   
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:  
 During handling of the above exception, another exception occurred:
Oct  5 05:00:38 pimatrix weewx[688] ERROR weewx.reportengine:   
Oct  5 05:00

[weewx-user] Re: Weewx Belchertown Kiosk page

[Dan Roman]

Thanks Karen.  So I guess it looks good on a pi running on a browser 
because it is a "desktop" but phones and tablets are a problem?  I don't 
know enough about Cascading Style Sheets to attempt an overhaul to get it 
to look right on my own.  Even the pi version doesn't look good compared to 
the git screenshot and desktop vs. tablet.


On Tuesday, October 3, 2023 at 1:40:02 PM UTC-4 Karen K wrote:

> The real reason is, that the Belchertown skin does not obey all the rules 
> of the Bootstrap grid system. And additionally it changes some basic 
> settings within style.css to the worse. 
>
> Dan Roman schrieb am Dienstag, 3. Oktober 2023 um 18:14:08 UTC+2:
>
>> I don't quite understand why the kiosk example on the GIT looks like the 
>> first picture below, which is supposedly sized for a 1280 x 800 screen but 
>> my tablet with a 2048 x 1536 screen looks terrible (second picture).  
>>
>> Is this just a browser issue on the tablet?  Anyone find a easy way to 
>> fix it?  It's an old Samsung 8" tablet I am trying to repurpose.  I tried 
>> Chrome and the Samsung browser and they both look the same.  Kiosk looks 
>> good on my desktop browser but doesn't look good on my phone either (which 
>> is also greater than 1280 x 800 resolution).
>>
>> Github image sample of kiosk:
>> [image: kiosk page]
>>
>> Screenshot from my tablet:
>> [image: Screenshot_20231003-120527.png]
>>
>> Thanks!
>>
>>

-- 
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/26ea2197-3d28-441a-ad24-0e29312c9937n%40googlegroups.com.

Re: [weewx-user] Re: Belchertown lightning graph

[Dan Roman]

An update since I experienced a lot of lightning over the past week.  As a 
refresher, here are my pertinent lines from weewx.conf:

[[sensor_map]]
# This section is for handling data for the Tempest Weather Station
outTemp = air_temperature.ST-00102080.obs_st
outHumidity = relative_humidity.ST-00102080.obs_st
pressure = station_pressure.ST-00102080.obs_st
lightning_strikes = lightning_strike_count.ST-00102080.obs_st
avg_distance = lightning_strike_avg_distance.ST-00102080.obs_st
outTempBatteryStatus = battery.ST-00102080.obs_st
windSpeed = wind_speed.ST-00102080.rapid_wind
windDir = wind_direction.ST-00102080.rapid_wind
luminosity = illuminance.ST-00102080.obs_st
UV = uv.ST-00102080.obs_st
rain = rain_accumulated.ST-00102080.obs_st
#windBatteryStatus = battery.ST-00102080.obs_st
radiation = solar_radiation.ST-00102080.obs_st
lightning_distance = distance.ST-00102080.evt_strike
#lightningYYY = energy.ST-00102080.evt_strike
lightning_strike_count = lightning_strike_count.ST-00102080.obs_st

[StdCalibrate]
[[Corrections]]
lightning_distance = lightning_distance if lightning_strike_count > 0 else 
None

[Accumulator]
[[lightning_strikes]]
extractor = sum
[[lightning_distance]]
extractor = min
[[avg_distance]]
extractor = avg

I experimented with the Seasons skin to double-check what I was doing in 
the Belchertown skin.  These two entries in skin.conf yield the graphs 
shown.  Seems to work ok for both.   But I had to use my new 
lightning_strike_count variable because the Accumulator summing 
lightning_strikes must have been messing up the graphs.  At least that is 
my theory, any input is appreciated.

[[[weeklightning]]]
yscale = None, None, 1
plot_type = bar
lightning_strike_count
aggregate_type = sum
aggregate_interval = day
label = Lightning (daily total)
[image: weeklightning]
[[[weeklightningdistance]]]
yscale = 0, 25, 5
line_type = None
marker_type = box
marker_size = 2
lightning_distance
label = Lightning Distance
[image: weeklightningdistance]

And for Belchertown:
   [[weekLightningInfo]]
title = Lightning
[[[lightning_strike_count]]]
yAxis = 0
yAxis_min = 0
yAxis_tickInterval = 1
yAxis_label = "Number of Strikes"
stacking = normal
color = "orange"
lineWidth = 0
#aggregate_type = sum
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
#aggregate_type = min
marker
enabled = true
radius = 3
states
[hover]
lineWidthPlus = 0
 
[image: Screenshot 2023-09-11 095402.png]
I have to do some further tweaking on the left y-axis tick interval, but 
the data looks good.  Need to figure out how to get rid of the 0 value for 
all the no-strike points.

I tried this, but it yields a blank graph, probably because of the 
aggregate options...
   [[lightningthisweek]]
title = Lightning (hourly total)
time_length = week
aggregate_type = sum
aggregate_interval = 3600
type = column
[[[lightning_strike_count]]]
name = Lightning
[[[lightning_distance]]]
name = Min Distance
aggregate_type = min
yAxis = 1

This one yields a good graph and I will probably try to combine this with 
the lightning strikes/distance graph above.
[image: Screenshot 2023-09-11 100013.png]

This guy's site https://weather.sangrephotography.com/ has a good lightning 
graph (only lightning for the day so you have to wait for a thunderstorm 
for the graph to appear).  I contacted him trying to get the config files 
he uses but he has not responded.

I need to read through and understand High Charts better.

Dan


On Monday, August 28, 2023 at 11:27:01 AM UTC-4 Dan Roman wrote:

> Hi Mark,
>
> Coincidentally I was just working on this last week.  I have not been able 
> to get lightning working completely still. In my configuration 
> lightning_strikes and avg_distance still display as Invalid Observations in 
> Belchertown.  I was able to get the following observations added but have 
> to wait for a thunderstorm to see if it works.  I added a second lig

Re: [weewx-user] Re: Belchertown lightning graph

[Dan Roman]

 graph
observation lightning_strike_count. Error was: unsupported operand type(s)
for %: 'NoneType' and 'int'.

Maybe I have to wait for some lightning data to be added first.

It has been very frustrating!

Dan


On Sun, Aug 27, 2023 at 10:25 AM pmcg...@gmail.com 
wrote:

> Di you ever figure out how to get rid of this?
>
> Observation lightning_strike_count is using unit count that returns %d for
> StringFormat, rather than float point decimal format value - using 0 as
> rounding
>
> Thanks!
>
> On Saturday, June 24, 2023 at 8:15:11 PM UTC-6 Dan Roman wrote:
>
>> Had a thunderstorm today and lightning still does not register at all
>> even after adding the graphs. I don't think lightning is being saved in my
>> database and I have to figure that out first, then I might be able to
>> display it.
>>
>> --
>> Dan Roman
>> gdan...@gmail.com
>>
>> On Thu, Jun 22, 2023, 5:11 AM Mark Fraser  wrote:
>>
>>> On 20/06/2023 14:30, Dan Roman wrote:
>>> > Thanks Mark, I will give it a try and add it to my graphs to see if it
>>> > works with Weatherflow.
>>> >
>>> > Were you able (or did you try) to add a last 3 hours lightning count
>>> to
>>> > the Belchertown main page, for example, "Lightning count last 3 hours:
>>> 15"?
>>> >
>>> > That's one of the things that Alex and I were trying to accomplish as
>>> well.
>>>
>>> Dan,
>>> Any ideas how to get rid of
>>>
>>> "Observation lightning_strike_count is using unit count that returns %d
>>> for StringFormat, rather than float point decimal format value - using 0
>>> as rounding "?
>>>
>>> --
>>> 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/8S1zsvbW2v8/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/fa0a934d-146e-2e89-034c-e4edcf6b394d%40gmail.com
>>> .
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/8S1zsvbW2v8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/8c02666b-adf5-4e75-8b08-efaf4e4612dan%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/8c02666b-adf5-4e75-8b08-efaf4e4612dan%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Dan Roman
gdann...@gmail.com

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

Re: [weewx-user] Re: Belchertown lightning graph

[Dan Roman]

Had a thunderstorm today and lightning still does not register at all even
after adding the graphs. I don't think lightning is being saved in my
database and I have to figure that out first, then I might be able to
display it.

--
Dan Roman
gdann...@gmail.com

On Thu, Jun 22, 2023, 5:11 AM Mark Fraser  wrote:

> On 20/06/2023 14:30, Dan Roman wrote:
> > Thanks Mark, I will give it a try and add it to my graphs to see if it
> > works with Weatherflow.
> >
> > Were you able (or did you try) to add a last 3 hours lightning count to
> > the Belchertown main page, for example, "Lightning count last 3 hours:
> 15"?
> >
> > That's one of the things that Alex and I were trying to accomplish as
> well.
>
> Dan,
> Any ideas how to get rid of
>
> "Observation lightning_strike_count is using unit count that returns %d
> for StringFormat, rather than float point decimal format value - using 0
> as rounding "?
>
> --
> 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/8S1zsvbW2v8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/fa0a934d-146e-2e89-034c-e4edcf6b394d%40gmail.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/CANKdm-MVARpPLkA01C6-%3D2LeVTr0R1mASrkKS53yO-H-nEFJ6w%40mail.gmail.com.

[weewx-user] Re: Belchertown lightning graph

[Dan Roman]

Thanks Mark, I will give it a try and add it to my graphs to see if it 
works with Weatherflow.

Were you able (or did you try) to add a last 3 hours lightning count to the 
Belchertown main page, for example, "Lightning count last 3 hours: 15"?

That's one of the things that Alex and I were trying to accomplish as well.

Dan

On Tuesday, June 20, 2023 at 6:05:47 AM UTC-4 Mark Fraser wrote:

I currently have this in graphs.conf to show lightning strikes over the 
past 3 hours and it works: 

[[Lightning_chart]] 
title = Lightning (Last 3 Hours) 
time_length = 10800 
aggregate_interval = 300 
gapsize = 108000 
type = column 

[[[lightning_strike_count]]] 
name = Lightning Count 
zIndex = 1 
aggregate_type = sum 

Except that: 
user.belchertown: Observation lightning_strike_count is using unit count 
that returns %d for StringFormat, rather than float point decimal format 
value - using 0 as rounding 
Is showing in the system log. 

-- 
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/e4cf68d4-2c97-4580-9830-28cc55e29803n%40googlegroups.com.

Re: [weewx-user] Re: Belchertown and Tempest battery voltage

[Dan Roman]

Hi Alex,

No, I did not figure out how to get it to work.  I saved a few threads that
I think might help out, but I have not had a chance to work on it to try to
figure it out yet.

Dan


On Sun, Jun 18, 2023 at 9:47 AM Alex Chaney  wrote:

> Dan,
>
> Did you happen to figure out how to get the  lightning_strikes to display
> properly?  I am currently going through the same.
>
> On Saturday, April 1, 2023 at 2:59:46 PM UTC-4 Dan Roman wrote:
>
>> Yes Wayne, thanks again.  I've got my brightness and battery voltage
>> displaying properly and well formatted using the Belchertown skin.  We had
>> a thunderstorm this morning but the lightning reading still was not
>> working.  I've removed that observation until I can figure out how to
>> display the number of lightning strikes for the current day.  Some of the
>> information gleaned from the luminosity and battery measurements may help
>> me figure out lightning.
>>
>> I think besides working on lightning I am going to look at how to add
>> data like battery or lightning to the weewx database and playing around
>> with adding more graphs to Belchertown.
>>
>>
>> On Wed, Mar 29, 2023 at 7:54 PM Wayne Rademacher 
>> wrote:
>>
>>> Dan,
>>>
>>> We solved the decimal point issue.
>>>
>>> Check out the conversation:
>>> How do I change the number of displayed decimal places?
>>>
>>> Wayne
>>>
>>> On Tuesday, March 28, 2023 at 9:36:51 PM UTC-5 Dan Roman wrote:
>>>
>>>> Thanks Wayne, very helpful.  I had made some progress but this
>>>> sped things up for me.  I have been slowly learning more about custom
>>>> configuring weewx and its skins.  Info is out there, depending on what you
>>>> are looking for it can be scattered.  My next step is to figure out how to
>>>> change the number of decimal points displayed for the battery voltage and
>>>> to get the lightning strike count working.
>>>>
>>>> I added lightning_strikes to the Belchertown observation list but right
>>>> now it is displaying "Invalid observation".  Not sure if this is because
>>>> there are no thunderstorms or if there is a problem with the reading.  I'll
>>>> wait until I get a thunderstorm and see what is displayed.  I would like to
>>>> dig into the code and figure out if I can change "Invalid observation" to
>>>> "No lightning detected today" or something like that.  Not sure it if is in
>>>> the skin or weewx but greping around should find it.
>>>>
>>>> Thanks again for your help.
>>>>
>>>> Dan
>>>>
>>>>
>>>> On Mon, Mar 27, 2023 at 3:54 PM Wayne Rademacher <
>>>> jordanmac...@gmail.com> wrote:
>>>>
>>>>> Dan,
>>>>> I have a Tempest and the Belchertown skin.
>>>>>
>>>>> All I did to get to display battery voltage was place the "
>>>>> windBatteryStatus" variable in the station observations string.  I
>>>>> also added "luminosity" to the string.  To use luminosity
>>>>> (Brightness) you will need to change the sensor map title from luxXX to
>>>>> luminosity.   I included both the Station Observation string and my sensor
>>>>> map for your reference.  Btw, you can also change the sensor titles in the
>>>>> weewx.conf  file.
>>>>>
>>>>> Wayne
>>>>>
>>>>> station_observations = "barometer","dewpoint","outHumidity","rain",
>>>>> "luminosity", "UV", "cloud_cover", "windBatteryStatus"
>>>>>
>>>>> [[sensor_map]]
>>>>> outTemp = air_temperature.ST-00105xxx.obs_st
>>>>> outHumidity = relative_humidity.ST-00105xxx.obs_st
>>>>> pressure = station_pressure.ST-00105xxx.obs_st
>>>>> lightning_strikes = lightning_strike_count.ST-00105xxx.obs_st
>>>>> avg_distance = lightning_strike_avg_distance.ST-00105xxx.obs_st
>>>>> outTempBatteryStatus = battery.ST-00105xxx.obs_st
>>>>> windSpeed = wind_speed.ST-00105xxx.rapid_wind
>>>>> windDir = wind_direction.ST-00105xxx.rapid_wind
>>>>> luminosity = illuminance.ST-00105xxx.obs_st
>>>>> UV = uv.ST-00105xxx.obs_st
>>>>> rain = rain_accum

Re: [weewx-user] Re: Belchertown and Tempest battery voltage

[Dan Roman]

Yes Wayne, thanks again.  I've got my brightness and battery voltage
displaying properly and well formatted using the Belchertown skin.  We had
a thunderstorm this morning but the lightning reading still was not
working.  I've removed that observation until I can figure out how to
display the number of lightning strikes for the current day.  Some of the
information gleaned from the luminosity and battery measurements may help
me figure out lightning.

I think besides working on lightning I am going to look at how to add data
like battery or lightning to the weewx database and playing around with
adding more graphs to Belchertown.


On Wed, Mar 29, 2023 at 7:54 PM Wayne Rademacher <
jordanmachinela...@gmail.com> wrote:

> Dan,
>
> We solved the decimal point issue.
>
> Check out the conversation:
> How do I change the number of displayed decimal places?
>
> Wayne
>
> On Tuesday, March 28, 2023 at 9:36:51 PM UTC-5 Dan Roman wrote:
>
>> Thanks Wayne, very helpful.  I had made some progress but this
>> sped things up for me.  I have been slowly learning more about custom
>> configuring weewx and its skins.  Info is out there, depending on what you
>> are looking for it can be scattered.  My next step is to figure out how to
>> change the number of decimal points displayed for the battery voltage and
>> to get the lightning strike count working.
>>
>> I added lightning_strikes to the Belchertown observation list but right
>> now it is displaying "Invalid observation".  Not sure if this is because
>> there are no thunderstorms or if there is a problem with the reading.  I'll
>> wait until I get a thunderstorm and see what is displayed.  I would like to
>> dig into the code and figure out if I can change "Invalid observation" to
>> "No lightning detected today" or something like that.  Not sure it if is in
>> the skin or weewx but greping around should find it.
>>
>> Thanks again for your help.
>>
>> Dan
>>
>>
>> On Mon, Mar 27, 2023 at 3:54 PM Wayne Rademacher 
>> wrote:
>>
>>> Dan,
>>> I have a Tempest and the Belchertown skin.
>>>
>>> All I did to get to display battery voltage was place the "
>>> windBatteryStatus" variable in the station observations string.  I also
>>> added "luminosity" to the string.  To use luminosity (Brightness) you
>>> will need to change the sensor map title from luxXX to luminosity.   I
>>> included both the Station Observation string and my sensor map for your
>>> reference.  Btw, you can also change the sensor titles in the weewx.conf
>>> file.
>>>
>>> Wayne
>>>
>>> station_observations = "barometer","dewpoint","outHumidity","rain",
>>> "luminosity", "UV", "cloud_cover", "windBatteryStatus"
>>>
>>> [[sensor_map]]
>>> outTemp = air_temperature.ST-00105xxx.obs_st
>>> outHumidity = relative_humidity.ST-00105xxx.obs_st
>>> pressure = station_pressure.ST-00105xxx.obs_st
>>> lightning_strikes = lightning_strike_count.ST-00105xxx.obs_st
>>> avg_distance = lightning_strike_avg_distance.ST-00105xxx.obs_st
>>> outTempBatteryStatus = battery.ST-00105xxx.obs_st
>>> windSpeed = wind_speed.ST-00105xxx.rapid_wind
>>> windDir = wind_direction.ST-00105xxx.rapid_wind
>>> luminosity = illuminance.ST-00105xxx.obs_st
>>> UV = uv.ST-00105xxx.obs_st
>>> rain = rain_accumulated.ST-00105xxx.obs_st
>>> windBatteryStatus = battery.ST-00105xxx.obs_st
>>> radiation = solar_radiation.ST-00105xxx.obs_st
>>> lightningXXX = distance.ST-00105xxx.evt_strike
>>> lightningYYY = energy.ST-00105xxx.evt_strike
>>> radiation = solar_radiation.ST-00105xxx.obs_st
>>> lightningXXX = distance.ST-00105xxx.evt_strike
>>> lightningYYY = energy.ST-001056xxx.evt_strike
>>>
>>> On Saturday, March 25, 2023 at 8:51:25 PM UTC-5 vince wrote:
>>>
>>>> You need to actually call the get_battery_status() routine too...
>>>>
>>>> Take a look at what the Seasons skin does...
>>>>
>>>> On Saturday, March 25, 2023 at 5:06:29 PM UTC-7 Dan Roman wrote:
>>>>
>>>>> I've been running stock Weewx for about a year and finally got around
>>>>> to trying other skins.  First one I tried is Belchertown and I like it a
>>>>> lot.  

Re: [weewx-user] Re: Belchertown and Tempest battery voltage

[Dan Roman]

Thanks Wayne, very helpful.  I had made some progress but this sped things
up for me.  I have been slowly learning more about custom configuring weewx
and its skins.  Info is out there, depending on what you are looking for it
can be scattered.  My next step is to figure out how to change the number
of decimal points displayed for the battery voltage and to get the
lightning strike count working.

I added lightning_strikes to the Belchertown observation list but right now
it is displaying "Invalid observation".  Not sure if this is because there
are no thunderstorms or if there is a problem with the reading.  I'll wait
until I get a thunderstorm and see what is displayed.  I would like to dig
into the code and figure out if I can change "Invalid observation" to "No
lightning detected today" or something like that.  Not sure it if is in the
skin or weewx but greping around should find it.

Thanks again for your help.

Dan


On Mon, Mar 27, 2023 at 3:54 PM Wayne Rademacher <
jordanmachinela...@gmail.com> wrote:

> Dan,
> I have a Tempest and the Belchertown skin.
>
> All I did to get to display battery voltage was place the "
> windBatteryStatus" variable in the station observations string.  I also
> added "luminosity" to the string.  To use luminosity (Brightness) you
> will need to change the sensor map title from luxXX to luminosity.   I
> included both the Station Observation string and my sensor map for your
> reference.  Btw, you can also change the sensor titles in the weewx.conf
> file.
>
> Wayne
>
> station_observations = "barometer","dewpoint","outHumidity","rain",
> "luminosity", "UV", "cloud_cover", "windBatteryStatus"
>
> [[sensor_map]]
> outTemp = air_temperature.ST-00105xxx.obs_st
> outHumidity = relative_humidity.ST-00105xxx.obs_st
> pressure = station_pressure.ST-00105xxx.obs_st
> lightning_strikes = lightning_strike_count.ST-00105xxx.obs_st
> avg_distance = lightning_strike_avg_distance.ST-00105xxx.obs_st
> outTempBatteryStatus = battery.ST-00105xxx.obs_st
> windSpeed = wind_speed.ST-00105xxx.rapid_wind
> windDir = wind_direction.ST-00105xxx.rapid_wind
> luminosity = illuminance.ST-00105xxx.obs_st
> UV = uv.ST-00105xxx.obs_st
> rain = rain_accumulated.ST-00105xxx.obs_st
> windBatteryStatus = battery.ST-00105xxx.obs_st
> radiation = solar_radiation.ST-00105xxx.obs_st
> lightningXXX = distance.ST-00105xxx.evt_strike
> lightningYYY = energy.ST-00105xxx.evt_strike
> radiation = solar_radiation.ST-00105xxx.obs_st
> lightningXXX = distance.ST-00105xxx.evt_strike
> lightningYYY = energy.ST-001056xxx.evt_strike
>
> On Saturday, March 25, 2023 at 8:51:25 PM UTC-5 vince wrote:
>
>> You need to actually call the get_battery_status() routine too...
>>
>> Take a look at what the Seasons skin does...
>>
>> On Saturday, March 25, 2023 at 5:06:29 PM UTC-7 Dan Roman wrote:
>>
>>> I've been running stock Weewx for about a year and finally got around to
>>> trying other skins.  First one I tried is Belchertown and I like it a lot.
>>> I have most things working but when I tried to update about.inc to display
>>> the Tempest battery voltage the same way I added it to the Seasons skin, it
>>> does not seem to work.  Do I need to do something differently?  Below is
>>> what I added to sensors.inc in the Seasons skin.  I copied and pasted it
>>> into about.inc and it does not display anything.
>>>
>>> I did a little digging around in the Seasons skin to see if anything in
>>> the configuration was different and needed to be added to the configuration
>>> of Belchertown but did not see anything obvious.
>>>
>>> Thanks!
>>>
>>> ## Modified battery code for Tempest
>>> #def get_battery_status($x)
>>>   #set $y = "{:.2f}".format($x)
>>>   #if $x >= 2.455
>>> OK - $y
>>>   #else
>>> #if $x >= 2.41
>>>   LOW - mode 1 - $y
>>> #else
>>>   #if $x >= 2.39
>>> LOW - mode 2 - $y
>>>   #else
>>> LOW - mode 3 - $y
>>>   #end if
>>> #end if
>>>   #end if
>>> #end def
>>>
>>> --
> 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/huVKwO86oqs/unsubscribe.
> To uns

[weewx-user] Belchertown and Tempest battery voltage

[Dan Roman]

I've been running stock Weewx for about a year and finally got around to 
trying other skins.  First one I tried is Belchertown and I like it a lot.  
I have most things working but when I tried to update about.inc to display 
the Tempest battery voltage the same way I added it to the Seasons skin, it 
does not seem to work.  Do I need to do something differently?  Below is 
what I added to sensors.inc in the Seasons skin.  I copied and pasted it 
into about.inc and it does not display anything.

I did a little digging around in the Seasons skin to see if anything in the 
configuration was different and needed to be added to the configuration of 
Belchertown but did not see anything obvious.

Thanks!

## Modified battery code for Tempest
#def get_battery_status($x) 
  #set $y = "{:.2f}".format($x)
  #if $x >= 2.455
OK - $y
  #else
#if $x >= 2.41
  LOW - mode 1 - $y
#else
  #if $x >= 2.39
LOW - mode 2 - $y
  #else
LOW - mode 3 - $y
  #end if
#end if
  #end if
#end def

-- 
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/650b834e-c4d7-43c1-bc58-7ba7056696c6n%40googlegroups.com.

Re: [weewx-user] Re: No updates after sensor failure and replacement

[Dan Roman]

Yep, you were right Vince.  Once I used your listener to see the packets it
is indeed using the serial number burned into the firmware and not the
"name" of the device, which was renamed to the serial number of my old
device.  Weewx is collecting data again.

Thanks!

Dan


On Sat, Jan 21, 2023 at 2:08 AM vince  wrote:

> If you're running weewx with the reference driver, you're listening to the
> UDP which has the sensor id in it.
>
> If you're running wfpiconsole, you're connecting to the WF REST interface
> for your station.  I think they're different.
>
> Just for grins, substitute in the new tempest id in weewx, restart weewx,
> and see if magic happens.  It's already not working, so you can't break
> anything by doing a quick test.  Alternately run my listener program and
> see what UDP is coming across the LAN (or run a sniffer or equivalent).
>
>
> On Friday, January 20, 2023 at 7:27:02 PM UTC-8 gdan...@gmail.com wrote:
>
>> Thanks Vince, but the Tempest phone app has a replacement feature that
>> renames the new unit to the old sensor so that history is not lost.  My new
>> sensor is now also  ST-00044122 when I look at it in the phone app, and as
>> I mentioned, the wfpiconsole works like a charm without any changes to the
>> configuration, just left it as  ST-00044122 and it works fine.  Something
>> else is going on.
>>
>> Dan
>>
>>
>> On Friday, January 20, 2023 at 2:58:39 PM UTC-5 vince wrote:
>>
>>> Each Tempest has a unique ID. If you replaced your Tempest sensor,
>>> your ST-00044122 is now incorrect and you need to edit weewx.conf to use
>>> the new sensor's device ID so the driver looks for readings from 'that' new
>>> device.
>>>
>>> --
> 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/xFQzEcRbNHo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/40d3450e-e626-4b79-bd4a-af6599fb947an%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/40d3450e-e626-4b79-bd4a-af6599fb947an%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Dan Roman
gdann...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CANKdm-PbMWto5kih4PBGimK4QcZ%3DEpNccKpyaK7y3hu%2BQ%3DobvA%40mail.gmail.com.

[weewx-user] Re: No updates after sensor failure and replacement

[Dan Roman]

Thanks Vince, but the Tempest phone app has a replacement feature that 
renames the new unit to the old sensor so that history is not lost.  My new 
sensor is now also  ST-00044122 when I look at it in the phone app, and as 
I mentioned, the wfpiconsole works like a charm without any changes to the 
configuration, just left it as  ST-00044122 and it works fine.  Something 
else is going on.

Dan


On Friday, January 20, 2023 at 2:58:39 PM UTC-5 vince wrote:

> Each Tempest has a unique ID. If you replaced your Tempest sensor, 
> your ST-00044122 is now incorrect and you need to edit weewx.conf to use 
> the new sensor's device ID so the driver looks for readings from 'that' new 
> device.
>
>

-- 
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/4e215f7f-f1b6-4da3-a0c2-9df24353475dn%40googlegroups.com.

[weewx-user] Re: No updates after sensor failure and replacement

[Dan Roman]

 weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_binding
Jan 20 14:41:28 pimatrix weewx[7533]: Starting weewx weather system: weewx.
Jan 20 14:41:28 pimatrix systemd[1]: Started LSB: weewx weather system.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.manager: Daily summary 
version is 4.0
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdDelta
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdDelta
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.engine: Archive will use 
data binding wx_binding
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.restx: StationRegistry: 
Registration not requested.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.restx: Wunderground: 
Posting not enabled.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.restx: PWSweather: Posting 
not enabled.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdPWSweather
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.restx.StdCWOP
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.restx: CWOP: Posting not 
enabled.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdCWOP
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.restx.StdWOW
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.restx: WOW: Posting not 
enabled.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWOW
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.restx.StdAWEKAS
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdAWEKAS
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.engine.StdPrint
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdPrint
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Loading service 
weewx.engine.StdReport
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.engine: 'pyephem' not 
detected, extended almanac data is not available
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdReport
Jan 20 14:41:28 pimatrix weewx[7549] INFO __main__: Starting up weewx 
version 4.9.1
Jan 20 14:41:28 pimatrix weewx[7549] DEBUG weewx.engine: Station does not 
support reading the time
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.manager: Starting backfill 
of daily summaries
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.manager: Daily summaries up 
to date
Jan 20 14:41:28 pimatrix weewx[7549] INFO weewx.engine: Starting main 
packet loop.
Jan 20 14:41:28 pimatrix /weewxd: weatherflowudp: MainThread: Listening for 
UDP broadcasts to IP ad

[weewx-user] No updates after sensor failure and replacement

[Dan Roman]

I have weewx running for over a year on a Pi 3 running debian 10.13.  I am 
using a Tempest sensor and the weatherflowudp.  My sensor died and I have 
replaced it using the replace feature, which duplicates the old sensor by 
duplicating the name, so all my config files can remain unchanged.  I am 
also using wfpiconsole and that picked up seamlessly when the new sensor 
came online.  I have not changed /etc/weewx/weewx.conf

I have stopped/started and rebooted, but there are no data updates.  The 
syslog after starting is below.  My last data update was from January 9 at 
7:55 pm local time and when I look at the  /var/www/html/weewx/ folder and 
the FTP folder on an external webserver everything is frozen at the January 
9 7:55 time.

Where can I look or what can I do to get this going again?  I don't see any 
errors that jump out to me in the syslog.

Thanks,

Dan

Jan 20 14:15:55 pimatrix systemd[1]: Starting LSB: weewx weather system...
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Initializing weewx 
version 4.9.1
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Using Python 3.7.3 
(default, Oct 31 2022, 14:04:00) #012[GCC 8.3.0]
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Located at /bin/python3
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Platform 
Linux-5.10.103-v7+-armv7l-with-debian-10.13
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Locale is 'en_US.UTF-8'
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: Debug is 0
Jan 20 14:15:55 pimatrix weewx[6919] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 20 14:15:55 pimatrix weewx[6923] INFO weewx.engine: Loading station 
type WeatherFlowUDP (user.weatherflowudp)
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: driver 
version is 1.10
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: sensor map is 
{'outTemp': 'air_temperature.ST-00044122.obs_st', 'outHumidity': 
'relative_humidity.ST-00044122.obs_st', 'pressure': 
'station_pressure.ST-00044122.obs_st', 'lightning_strikes': 
'lightning_strike_count.ST-00044122.obs_st', 'avg_distance': 
'lightning_strike_avg_distance.ST-00044122.obs_st', 'outTempBatteryStatus': 
'battery.ST-00044122.obs_st', 'windSpeed': 
'wind_speed.ST-00044122.rapid_wind', 'windDir': 
'wind_direction.ST-00044122.rapid_wind', 'luxXXX': 
'illuminance.ST-00044122.obs_st', 'UV': 'uv.ST-00044122.obs_st', 'rain': 
'rain_accumulated.ST-00044122.obs_st', 'radiation': 
'solar_radiation.ST-00044122.obs_st', 'lightningXXX': 
'distance.ST-00044122.evt_strike', 'lightningYYY': 
'energy.ST-00044122.evt_strike'}
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: *** Sensor 
names per packet type
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: packet 
obs_air: ('time_epoch', 'station_pressure', 'air_temperature', 
'relative_humidity', 'lightning_strike_count', 
'lightning_strike_avg_distance', 'battery', 'report_interval')
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: packet 
obs_sky: ('time_epoch', 'illuminance', 'uv', 'rain_accumulated', 
'wind_lull', 'wind_avg', 'wind_gust', 'wind_direction', 'battery', 
'report_interval', 'solar_radiation', 'local_day_rain_accumulation', 
'precipitation_type', 'wind_sample_interval')
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: packet 
rapid_wind: ('time_epoch', 'wind_speed', 'wind_direction')
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: packet 
evt_precip: time_epoch
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: packet 
evt_strike: ('time_epoch', 'distance', 'energy')
Jan 20 14:15:55 pimatrix /weewxd: weatherflowudp: MainThread: packet 
obs_st: ('time_epoch', 'wind_lull', 'wind_avg', 'wind_gust', 
'wind_direction', 'wind_sample_interval', 'station_pressure', 
'air_temperature', 'relative_humidity', 'illuminance', 'uv', 
'solar_radiation', 'rain_accumulated', 'precipitation_type', 
'lightning_strike_avg_distance', 'lightning_strike_count', 'battery', 
'report_interval')
Jan 20 14:15:55 pimatrix weewx[6923] INFO weewx.engine: StdConvert target 
unit is 0x1
Jan 20 14:15:55 pimatrix weewx[6923] INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_binding
Jan 20 14:15:55 pimatrix weewx[6923] INFO weewx.engine: Archive will use 
data binding wx_binding
Jan 20 14:15:56 pimatrix weewx[6923] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jan 20 14:15:56 pimatrix weewx[6923] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Jan 20 14:15:56 pimatrix weewx[6908]: Starting weewx weather system: weewx.
Jan 20 14:15:56 pimatrix systemd[1]: Started LSB: weewx weather system.
Jan 20 14:15:56 pimatrix weewx[6923] INFO weewx.restx: StationRegistry: 
Registration not requested.
Jan 20 14:15:56 pimatrix weewx[6923] INFO weewx.restx: Wunderground: 
Posting not enabled.
Jan 20 14:15:56 pimatrix weewx[6923] INF