Re: [weewx-user] Re: Availability of v5.0.0rc3

[Tom Keffer]

Michael,

I've reverted the StdCalibrate behavior back to the way it was in V4.10. To
appear in the next V5 release.

On Tue, Jan 9, 2024 at 8:43 PM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> It looks very much like it's the loop in my case. For instance,
> extraHumid1 is coming from a different device using the mqttSubscribe
> Service. So it is not in the loop packet from ws28xx. The same with
> supplyVoltage, BTW I messed up the ws28xx stanza, this one is correct,
> failing on both, outHumidity and supplyVoltage:
>
> [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
> #outHumidity = extraHumid1
> barometer = pressure
> altimeter = pressure
> outHumidity = extraHumid1 if extraHumid1 is not None else
> outHumidity
> supplyVoltage = (supplyVoltage + 35) / 1000
>
> In 5.0.0-b13 it didn't crash, so it wasn't only a difference to 4.10.
> Tom Keffer schrieb am Dienstag, 9. Januar 2024 um 21:25:59 UTC+1:
>
>> Michael, I think the issue is that extraHumid1 and/or
>> lightning_strike_count do not appear *at all* in at least some of the
>> loop packers and/or archive records.
>>
>> Version 4.10 swallowed NameErrors, this one does not. Perhaps that's a
>> mistake. Let me think if there's a better solution.
>>
>> -tk
>>
>> On Tue, Jan 9, 2024 at 3:13 AM 'michael.k...@gmx.at' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> I did a pip upgrade from b13 (no new install, no new venv). I run 3
>>> drivers: ws28xx, interceptor and ecowitt gateway driver from the same
>>> installations, using 3 different weewx.conf files and three databases
>>>
>>> After upgrading, two installations are crashing, when having certain
>>> corrections configured. Interestingly, one station (ecowitt gateway) keeps
>>> running, although it has the same correction configured, as the other
>>> crashing (interceptor). Log following, tell me, what else you need. (debug
>>> = 1, etc...)
>>>
>>> Correction stanza for ecowitt gateway (no crashing):
>>> [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
>>> #outHumidity = extraHumid1
>>> radiation = luminosity/126.7 if luminosity is not None else None
>>>#gw1000 fix
>>> lightning_distance = lightning_distance if
>>> lightning_strike_count > 0 else None
>>>
>>> Corrections Stanza for interceptor:
>>> [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
>>> #outHumidity = extraHumid1
>>> barometer = pressure
>>> altimeter = pressure
>>> #outHumidity = extraHumid1 if extraHumid1 is not None else
>>> outHumidity
>>> #supplyVoltage = (supplyVoltage + 35) / 1000
>>> #radiation = luminosity/126.7 if luminosity is not None else
>>> None*#<= this one also caused a crash just before and is already
>>> edited*
>>> lightning_distance = lightning_distance if
>>> lightning_strike_count > 0 else None *#<= removing this will prevent
>>> the crash*
>>> Interceptor log:
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__:
>>> Initializing weewxd version 5.0.0rc3
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Command
>>> line: /home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py
>>> /home/pi/weewx-data/weewx-interceptor.conf
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Using
>>> Python 3.9.2 (default, Feb 28 2021, 17:03:44)
>>> [GCC 10.2.1 20210110]
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Located at
>>> /home/pi/weewx-venv/bin/python3
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Platform
>>> Linux-6.1.42-v8+-aarch64-with-glibc2.31
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Locale:
>>> 'de_AT.UTF-8'
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Entry
>>> path: /home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__:
>>> WEEWX_ROOT: /home/pi/weewx-data
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__:
>>> Configuration file: /home/pi/weewx-data/weewx-interceptor.conf
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: User
>>> module: /home/pi/weewx-data/bin/user
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Debug: 0
>>> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO weewx.engine:
>>> Loading station type Int

[weewx-user] Investigating logs for sporadic loss of sensors during the night

[Invisible Man]

Hi,
Sometimes during the night I lose data from my sensors a couple of hours. 
I've had a look at the logs, but can't see any ERROR message. What type of 
message should I be looking for in weewx.log?

Example: https://biotmeteo.masdescrocodiles.fr/daytempdew.png
My weather station is an EcoWitt HP2551. It uses "Interceptor". Weewx 
4.10.2 is running on a Raspberry Pi.

Thanks,
Axelle.

-- 
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/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%40googlegroups.com.

Re: [weewx-user] Investigating logs for sporadic loss of sensors during the night

[Tom Keffer]

Hard to say without actually seeing the logs, but these
"middle-of-the-night' dropouts are often caused by weak sensor batteries.

On Wed, Jan 10, 2024 at 6:51 AM Invisible Man 
wrote:

> Hi,
> Sometimes during the night I lose data from my sensors a couple of hours.
> I've had a look at the logs, but can't see any ERROR message. What type of
> message should I be looking for in weewx.log?
>
> Example: https://biotmeteo.masdescrocodiles.fr/daytempdew.png
> My weather station is an EcoWitt HP2551. It uses "Interceptor". Weewx
> 4.10.2 is running on a Raspberry Pi.
>
> Thanks,
> Axelle.
>
> --
> 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/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%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/CAPq0zEC9Ce-MmxXeqkMZZFoUeKQXDYcEkg8Z6f8oZ9aZow80%3DA%40mail.gmail.com.

Re: [weewx-user] Re: Availability of v5.0.0rc3

['michael.k...@gmx.at' via weewx-user]

Thanks! Patched the file, it's working again.

Tom Keffer schrieb am Mittwoch, 10. Januar 2024 um 15:23:11 UTC+1:

> Michael,
>
> I've reverted the StdCalibrate behavior back to the way it was in V4.10. 
> To appear in the next V5 release.
>
> On Tue, Jan 9, 2024 at 8:43 PM 'michael.k...@gmx.at' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> It looks very much like it's the loop in my case. For instance, 
>> extraHumid1 is coming from a different device using the mqttSubscribe 
>> Service. So it is not in the loop packet from ws28xx. The same with 
>> supplyVoltage, BTW I messed up the ws28xx stanza, this one is correct, 
>> failing on both, outHumidity and supplyVoltage:
>>
>> [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
>> #outHumidity = extraHumid1
>> barometer = pressure
>> altimeter = pressure
>> outHumidity = extraHumid1 if extraHumid1 is not None else 
>> outHumidity
>> supplyVoltage = (supplyVoltage + 35) / 1000
>>
>> In 5.0.0-b13 it didn't crash, so it wasn't only a difference to 4.10.
>> Tom Keffer schrieb am Dienstag, 9. Januar 2024 um 21:25:59 UTC+1:
>>
>>> Michael, I think the issue is that extraHumid1 and/or 
>>> lightning_strike_count do not appear *at all* in at least some of the 
>>> loop packers and/or archive records.
>>>
>>> Version 4.10 swallowed NameErrors, this one does not. Perhaps that's a 
>>> mistake. Let me think if there's a better solution.
>>>
>>> -tk
>>>
>>> On Tue, Jan 9, 2024 at 3:13 AM 'michael.k...@gmx.at' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
 I did a pip upgrade from b13 (no new install, no new venv). I run 3 
 drivers: ws28xx, interceptor and ecowitt gateway driver from the same 
 installations, using 3 different weewx.conf files and three databases

 After upgrading, two installations are crashing, when having certain 
 corrections configured. Interestingly, one station (ecowitt gateway) keeps 
 running, although it has the same correction configured, as the other 
 crashing (interceptor). Log following, tell me, what else you need. (debug 
 = 1, etc...)

 Correction stanza for ecowitt gateway (no crashing):
 [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
 #outHumidity = extraHumid1
 radiation = luminosity/126.7 if luminosity is not None else 
 None#gw1000 fix
 lightning_distance = lightning_distance if 
 lightning_strike_count > 0 else None

 Corrections Stanza for interceptor:
 [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
 #outHumidity = extraHumid1
 barometer = pressure
 altimeter = pressure
 #outHumidity = extraHumid1 if extraHumid1 is not None else 
 outHumidity
 #supplyVoltage = (supplyVoltage + 35) / 1000
 #radiation = luminosity/126.7 if luminosity is not None else 
 None*#<= this one also caused a crash just before and is already 
 edited*
 lightning_distance = lightning_distance if 
 lightning_strike_count > 0 else None *#<= removing this will prevent 
 the crash*
 Interceptor log:
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: 
 Initializing weewxd version 5.0.0rc3
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Command 
 line: /home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py 
 /home/pi/weewx-data/weewx-interceptor.conf
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Using 
 Python 3.9.2 (default, Feb 28 2021, 17:03:44)
 [GCC 10.2.1 20210110]
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Located 
 at /home/pi/weewx-venv/bin/python3
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Platform 
 Linux-6.1.42-v8+-aarch64-with-glibc2.31
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Locale: 
 'de_AT.UTF-8'
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: Entry 
 path: /home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: 
 WEEWX_ROOT: /home/pi/weewx-data
 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: 
 Configuration file: /home/pi/weewx-data/weewx-interceptor.conf
 2024-

[weewx-user] weewx5 separated wind sensor via weatherlink-live driver - no wind

[puckthefly]

Hello,

I've been trying to get a Davis Weatherlink 6100 to run with the 
WeatherlinkLive Driver in weewx5 for days.
Unfortunately this doesn't work completely, my wind sensor is separated on 
ID2 and the data doesn't seem to arrive in weewx5.
In weewx5 I only see the data from the ISS, in my case via ID1 - but no 
data for wind.

As far as I understand the documentation, it would have to be adjusted like 
this:
mapping = th:1, rain:1, wind:2, th_indoor, baro, battery:1:outTemp:rain, 
battery:2:wind

Has anyone successfully implemented this with a remote wind sensor?

But ID2 definitely comes with values that I see live on the console and I 
can also see them on the Davis WeatherLink Live 6100 
(/v1/current_conditions):

{"data":{"did":"001D0A7145F8","ts":1704740156,"conditions":[{"lsid":612618,"data_structure_type":1,"
*txid":1*,"temp": 22.8, "hum":88.8,"dew_point": 20.0,"wet_bulb": 
21.8,"heat_index": 
22.8,"wind_chill":null,"thw_index":null,"thsw_index":null,"wind_speed_last":null,"wind_dir_last
 
":null,"wind_speed_avg_last_1_min":null,"wind_dir_scalar_avg_last_1_min":null,"wind_speed_avg_last_2_min":null,"wind_dir_scalar_avg_last_2_min":null,"wind_speed_hi_last_2_min":null,"wind_dir_at_hi_speed_last_2_min":null,"wind_speed_avg_last_10
 
*min":null,"wind_dir_scalar_avg_last_10_min": 
null,"wind_speed_hi_last_10_min":null,"wind_dir_at_hi_speed_last_10_min":null,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,
 
"rainfall_last_24_hr":0,"rain_storm":0,"rain_storm_start_at":null,"solar_rad":null,"uv_index":null,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":162,"rainfall_year":162,"rain_storm_last":162,"rain_storm_last_start_at":1704176821,"rain_storm_last_end_at":1704715261},{"lsid":612663,"data_structure_type":1,"txid":2,"temp
 
":null,"hum":null,"dew_point":null,"wet_bulb":null,"heat_index":null,"wind_chill":null,"thw_index":null,"thsw_index":null,"wind_speed_last":
 
4.00,"wind_dir_last":47,"wind_speed_avg_last_1_min":5.31,"wind_dir_scalar_avg_last_1_min":47,"wind_speed_avg_last_2_min":4.75,"wind_dir_scalar_avg_last_2_min":45,"wind_speed_hi_last_2_min":9.00,"wind_dir_at*
 
hi_speed_last_2_min":54,"wind_speed_avg_last_10_min":4.37, 
"wind_dir_scalar_avg_last_10_min":42,"wind_speed_hi_last_10_min":9.00,"wind_dir_at_hi_speed_last_10_min":54,"rain_size":1,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_
 
60_min 
":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":null,"uv_index":null,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":
 
0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":612617,"data_structure_type":4,"temp_in":
 
76.6,"hum_in":29.9,"dew_point_in": 42.8,"heat_index_in": 
74.6},{"lsid":612616,"data_structure_type":3,"bar_sea_level":30.227,"bar_trend":
 
0.043,"bar_absolute": 28,501}]},"error":null}

-- 
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/b3ba03c9-4dfd-468d-90ff-6489fafd23f1n%40googlegroups.com.

[weewx-user] Belchertown AQI for my website

[Ton Karsten]

Assistance requested for setting the AQI on the website.
For my weather station website I use the Belchertown skin.
Until a few months ago, the AQI values were also shown on it, which came 
from the Aeris website. My location is in the Netherlands.
We also have an institution in the Netherlands that can generate the AQI 
values and have them displayed on my website.
I am a retired electrical engineer and have absolutely no knowledge of 
software to make any adjustments.
I am looking for someone who can help me with how to make adjustments to 
this software.
This is the link to activate the readings on my website:
The measurement data from measuring station Wienringerwerf-Medemblikkerweg 
with station number NL10538 are still displayed via the API: 
https://api.luchtmeetnet.nl/open_api/stations/NL10538/measurements?page=1&order=&order_direction=&formula.
This is my website: https://weerstationnibbixwoud.nl/

-- 
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/f78102f4-f533-4865-8753-f85cfb8e7a6fn%40googlegroups.com.

[weewx-user] Re: ValueError: y1 must be greater than or equal to y0 in fresh installed weewx 4.10.2

[Joseph Verreau]

thanks to all for their help on this one.  I see it didn't present on my 
installation until Nov 25th and I didn't notice it right away to boot but 
all is humming again.

On Tuesday, May 23, 2023 at 9:52:57 PM UTC-4 gjr80 wrote:

> If you are running the current WeeWX release you should be fairly safe in 
> downloading the patched utilities.py in place of your current version. To 
> do this:
>
> 1. move aside your current utilities.py so your can revert to it if you 
> run into catastrophic problems, for a WeeWX package install:
>
> $ sudo mv /usr/share/weewx/weeplot/utilities.py 
> /usr/share/weewx/weeplot/utilities_orig.py 
>
> if you have a setup.py install use /home/weewx/bin in place of 
> /usr/share/weewx
>
> 2. download the patched utilities.py from GitHub, for a WeeWX package 
> install:
>
> $ sudo wget -P /usr/share/weewx/weeplot 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weeplot/utilities.py
>
> again, if you have a setup.py install use /home/weewx/bin in place of 
> /usr/share/weewx
>
> 3. restart WeeWX
>
> If you mess up the process simply copy utilities_orig.py back as 
> utilities.py and restart WeeWX.
>
> Gary
> On Sunday, 21 May 2023 at 17:35:00 UTC+10 seano...@gmail.com wrote:
>
>> Hi,
>>
>> I seem to be having this same error but I don't understand exactly how to 
>> rectify it. Please can you explain in a simple way how to apply the patch?
>>
>> Appreciate it, thank you.
>>
>> On Wednesday, April 12, 2023 at 1:01:59 AM UTC+4 Marius Schamschula wrote:
>>
>>> I ran into the same error after a routine update to FreeBSD 13.1 
>>> packages.
>>>
>>> I applied the patch and reinstalled weewx 4.10.2, and all is again 
>>> working as expected!
>>>
>>> On Tuesday, April 4, 2023 at 2:33:53 AM UTC-5 c s (224) wrote:
>>>
 Thank you very much for digging deeper! My solution will then be to 
 simply install an older version of the Pillow library. Thanks a lot!

 c s (224) schrieb am Montag, 3. April 2023 um 13:18:39 UTC+2:

> Hello,
>
> I have just installed weewx as described here: 
> https://weisser-zwerg.dev/posts/ecowitt-gw2000-weewx-docker
>
> And I run into an error that prevents the images from being drawn:
>
> weewx-weewx-1  | Apr  3 13:11:03 weewx[20] ERROR 
> weewx.reportengine:   Generator terminated 
> weewx-weewx-1  | Traceback (most recent call last): 
> weewx-weewx-1  |   File "/home/weewx/bin/weewx/reportengine.py", 
> line 197, in run 
> weewx-weewx-1  | obj.start() 
> weewx-weewx-1  |   File "/home/weewx/bin/weewx/reportengine.py", 
> line 385, in start 
> weewx-weewx-1  | self.run() 
> weewx-weewx-1  |   File 
> "/home/weewx/bin/weewx/imagegenerator.py", line 42, in run 
> weewx-weewx-1  | self.gen_images(self.gen_ts) 
> weewx-weewx-1  |   File 
> "/home/weewx/bin/weewx/imagegenerator.py", line 114, in gen_images 
> weewx-weewx-1  | image = plot.render() 
> weewx-weewx-1  | ^ 
> weewx-weewx-1  |   File "/home/weewx/bin/weeplot/genplot.py", 
> line 222, in render 
> weewx-weewx-1  | self._renderDayNight(sdraw) 
> weewx-weewx-1  |   File "/home/weewx/bin/weeplot/genplot.py", 
> line 266, in _renderDayNight 
> weewx-weewx-1  | sdraw.rectangle(((xleft,self.yscale[0]), 
> weewx-weewx-1  |   File "/home/weewx/bin/weeplot/utilities.py", 
> line 442, in rectangle 
> weewx-weewx-1  | self.draw.rectangle(box_scaled, **options) 
> weewx-weewx-1  |   File 
> "/opt/venv/lib/python3.11/site-packages/PIL/ImageDraw.py", line 294, in 
> rectangle 
> weewx-weewx-1  | self.draw.draw_rectangle(xy, fill, 1) 
> weewx-weewx-1  | ValueError: y1 must be greater than or equal to 
> y0
>
> I have followed the complete set-up process as described in "WeeWX: 
> Installation using setup.py", except that I do use a conda environment 
> and 
> pip packages rather than the OS packages:
>
> > mamba create -n weewx python=3.9
> > conda activate weewx
> > pip3 install configobj paho-mqtt pyserial pyusb Cheetah3 Pillow 
> ephem 
> > wget https://weewx.com/downloads/weewx-4.10.2.tar.gz
> > tar -xzvf weewx-4.10.2.tar.gz
> > cd weewx-4.10.2
> > python3 ./setup.py build
> > python3 ./setup.py install
> > # create the weewx.conf.patch from here: 
> https://weisser-zwerg.dev/posts/ecowitt-gw2000-weewx-docker/
> > patch -p1 weewx.conf < weewx.conf.patch
> > wget -O weewx-mqtt.zip 
> https://github.com/matthewwall/weewx-mqtt/archive/master.zip
> > ./bin/wee_extension --install ./weewx-mqtt.zip
> > wget -O weewx-interceptor.zip 
> https://github.com/matthewwall/weewx-interceptor/archive/master.zip
> > ./bin/wee_extension --install ./weewx-interceptor.zip
> > # ---
> > ./bin/weewx

Re: [weewx-user] Re: How do you enable forecast in Weewx-wdc

[David Bätge]

I just did a quick test run with WeatherUnderground, Aeris and OWM. windGust 
is only saved for the Aeris forecast entries, for OWM and WU it's always 
empty. 

Since it is provided via the OWM API, that's a problem of weewx-forecast 
not saving the data, I guess.

FYI: The skin already shows windGust if it is provided by the forecast - 
but I did never test this and just noticed the windGust just sits behind 
the windSpeed without any label. I 
created https://github.com/Daveiano/weewx-wdc/issues/240 to track this.

[image: weewx-wdc-foreacst-aeris.png]

windGust is 29 km/h for Do, 11 Jan in this example.

Dominic Reich schrieb am Sonntag, 7. Januar 2024 um 19:51:58 UTC+1:

> I think it is possible but not worth the hassle (for non-developers like
> me).
>
> The api reports wind gust, so there should be a way to create an
> extra row in the forecast_table.inc (and maybe more) files from the
> weewx-forecast extension.
>
> #v+
> {
> "dt": 1705082400,
> "main": {
> "temp": 267.72,
> "feels_like": 264.07,
> "temp_min": 267.72,
> "temp_max": 267.72,
> "pressure": 1034,
> "sea_level": 1034,
> "grnd_level": 890,
> "humidity": 67,
> "temp_kf": 0
> },
> "weather": [
> {
> "id": 800,
> "main": "Clear",
> "description": "clear sky",
> "icon": "01n"
> }
> ],
> "clouds": {
> "all": 2
> },
> "wind": {
> "speed": 2.21,
> "deg": 198,
> "gust": 2.38
> },
> "visibility": 1,
> "pop": 0,
> "sys": {
> "pod": "n"
> },
> "dt_txt": "2024-01-12 18:00:00"
> }
> #v-
>
> -dominic
>
> Nicholas Waton  wrote:
>
> >Thank you!
> >
> >Is there a way to show forecasted wind gusts? 
> >I am using the OWM forecast.
> >
> >On Tuesday, October 4, 2022 at 6:06:04 PM UTC-7 David Bätge wrote:
> >
> > There is also a dedicated page for enabling forecast in the wiki of the
> > skin: 
> https://github.com/Daveiano/weewx-wdc/wiki/Support-for-weewx-forecast
> >
> > Let me know if there are still questions!
> >
> > gary@gmail.com schrieb am Sonntag, 2. Oktober 2022 um 17:02:39 
> UTC+1:
> >
> > Don't forget that you will need to add the following to the skin. conf
> > [CheetahGenerator]
> > search_list_extensions 
> >
> > user.forecast.ForecastVariables,
> > user.weewx_wdc_forecast.WdcForecastUtil
> >
> > On Sunday, October 2, 2022 at 11:57:44 AM UTC-4 gary@gmail.com
> > wrote:
> >
> > weewx.conf
> > Adjust HTML_ROOT to your paths
> > Use your WU API key
> > Get your NWS values and use those.
> >
> > [[WdcReport]]
> > skin = weewx-wdc
> > enable = true
> > HTML_ROOT = /home/web/wdc
> > lang = en
> >
> > [[forecast]]
> > skin = forecast
> > HTML_ROOT = /home/web/forecast
> >
> > [Forecast]
> > data_binding = forecast_binding
> > #[[XTide]]
> > #location = "INSERT_LOCATION_HERE (e.g., Boston)"
> > [[Zambretti]]
> > hemisphere = NORTH
> > [[NWS]]
> > lid = MAZ011
> > foid = BOX
> > [[WU]]
> > api_key = 
> > #[[OWM]]
> > #api_key = INSERT_OWM_API_KEY_HERE
> > #[[UKMO]]
> > #api_key = INSERT_UKMO_API_KEY_HERE
> > #location = INSERT_UK_LOCATION_HERE
> > #[[Aeris]]
> > #client_id = INSERT_AERIS_CLIENT_ID_HERE
> > #client_secret = INSERT_AERIS_CLIENT_SECRET_HERE
> > #[[WWO]]
> > #api_key = INSERT_WWO_API_KEY_HERE
> > #[[DS]]
> > #api_key = INSERT_DS_API_KEY_HERE
> >
> >
> > skin.conf
> > Make adjustments for your location.
> >
> > # configuration file for the weewx-wdc skin
> > SKIN_NAME = Weather Data Center
> > SKIN_VERSION = 2.1.0
> >
> > [Extras]
> > # Show a link to the GitHub respository of this skin. Set to
> > False to hide.
> > github_link = True
> >
> > # This radar image would be available as $Extras.radar_img
> > #radar_img = https://www.dwd.de/DWD/wetter/radar/
> > radfilm_sac_akt.gif
> > # This URL will be used as the image hyperlink:
> > #radar_url =https://www.dwd.de/DE/leistungen/radarbild_film
> > /radarbild_film.html
> >
> > [[forecast_zambretti]]
> > enable = True
> > hemisphere = NORTH  
> >
> > [[forecast_table_settings]]
> > source = WU
> > num_periods = 72
> > num_days = 5
> > show_legend = 1
> > show_hourly = 0
> > show_day = 1
> > show_date = 1
> > show_outlook = 1
> > show_temp = 1
> > show_dewpoint = 0
> > show_humidity = 0
> > show_wind = 1
> > show_tides = 0
> > show_sun = 0
> > show_moon = 0
> > show_pop = 1
> > show_precip = 1
> > show_obvis = 0
> >
> > On Thursday, September 29, 2022 at 2:42:44 PM UTC-4 
> > scott.d...@gmail.com wrote:
> >
> > I am having difficulty enabling the forecast feature in
> > weewx-wdc
> > What needs to be included in weewx.conf to have a forecast from
> > WU, AERIS, or NWS?
> >
> >
> >--
> >You received this message because you are subscribed to the Google Groups
> >"weewx-user" 

Re: [weewx-user] Re: How do you enable forecast in Weewx-wdc

[Nicholas Waton]

Very nice! Thanks for testing this with the other forecasts. I just 
switched to Aeris and can see the forecasted gusts.

I added a color coding depending on the wind speed to highlight very windy 
days or forecasted gusts. You can see it running here:
https://status.cal-sailing.org/index.html

On Wednesday, January 10, 2024 at 3:58:38 PM UTC-8 David Bätge wrote:

> I just did a quick test run with WeatherUnderground, Aeris and OWM. 
> windGust is only saved for the Aeris forecast entries, for OWM and WU 
> it's always empty. 
>
> Since it is provided via the OWM API, that's a problem of weewx-forecast 
> not saving the data, I guess.
>
> FYI: The skin already shows windGust if it is provided by the forecast - 
> but I did never test this and just noticed the windGust just sits behind 
> the windSpeed without any label. I created 
> https://github.com/Daveiano/weewx-wdc/issues/240 to track this.
>
> [image: weewx-wdc-foreacst-aeris.png]
>
> windGust is 29 km/h for Do, 11 Jan in this example.
>
> Dominic Reich schrieb am Sonntag, 7. Januar 2024 um 19:51:58 UTC+1:
>
>> I think it is possible but not worth the hassle (for non-developers like 
>> me). 
>>
>> The api reports wind gust, so there should be a way to create an 
>> extra row in the forecast_table.inc (and maybe more) files from the 
>> weewx-forecast extension. 
>>
>> #v+ 
>> { 
>> "dt": 1705082400, 
>> "main": { 
>> "temp": 267.72, 
>> "feels_like": 264.07, 
>> "temp_min": 267.72, 
>> "temp_max": 267.72, 
>> "pressure": 1034, 
>> "sea_level": 1034, 
>> "grnd_level": 890, 
>> "humidity": 67, 
>> "temp_kf": 0 
>> }, 
>> "weather": [ 
>> { 
>> "id": 800, 
>> "main": "Clear", 
>> "description": "clear sky", 
>> "icon": "01n" 
>> } 
>> ], 
>> "clouds": { 
>> "all": 2 
>> }, 
>> "wind": { 
>> "speed": 2.21, 
>> "deg": 198, 
>> "gust": 2.38 
>> }, 
>> "visibility": 1, 
>> "pop": 0, 
>> "sys": { 
>> "pod": "n" 
>> }, 
>> "dt_txt": "2024-01-12 18:00:00" 
>> } 
>> #v- 
>>
>> -dominic 
>>
>> Nicholas Waton  wrote: 
>>
>> >Thank you! 
>> > 
>> >Is there a way to show forecasted wind gusts?  
>> >I am using the OWM forecast. 
>> > 
>> >On Tuesday, October 4, 2022 at 6:06:04 PM UTC-7 David Bätge wrote: 
>> > 
>> > There is also a dedicated page for enabling forecast in the wiki of the 
>> > skin: 
>> https://github.com/Daveiano/weewx-wdc/wiki/Support-for-weewx-forecast 
>> > 
>> > Let me know if there are still questions! 
>> > 
>> > gary@gmail.com schrieb am Sonntag, 2. Oktober 2022 um 17:02:39 
>> UTC+1: 
>> > 
>> > Don't forget that you will need to add the following to the skin. conf 
>> > [CheetahGenerator] 
>> > search_list_extensions  
>> > 
>> > user.forecast.ForecastVariables, 
>> > user.weewx_wdc_forecast.WdcForecastUtil 
>> > 
>> > On Sunday, October 2, 2022 at 11:57:44 AM UTC-4 gary@gmail.com 
>> > wrote: 
>> > 
>> > weewx.conf 
>> > Adjust HTML_ROOT to your paths 
>> > Use your WU API key 
>> > Get your NWS values and use those. 
>> > 
>> > [[WdcReport]] 
>> > skin = weewx-wdc 
>> > enable = true 
>> > HTML_ROOT = /home/web/wdc 
>> > lang = en 
>> > 
>> > [[forecast]] 
>> > skin = forecast 
>> > HTML_ROOT = /home/web/forecast 
>> > 
>> > [Forecast] 
>> > data_binding = forecast_binding 
>> > #[[XTide]] 
>> > #location = "INSERT_LOCATION_HERE (e.g., Boston)" 
>> > [[Zambretti]] 
>> > hemisphere = NORTH 
>> > [[NWS]] 
>> > lid = MAZ011 
>> > foid = BOX 
>> > [[WU]] 
>> > api_key =  
>> > #[[OWM]] 
>> > #api_key = INSERT_OWM_API_KEY_HERE 
>> > #[[UKMO]] 
>> > #api_key = INSERT_UKMO_API_KEY_HERE 
>> > #location = INSERT_UK_LOCATION_HERE 
>> > #[[Aeris]] 
>> > #client_id = INSERT_AERIS_CLIENT_ID_HERE 
>> > #client_secret = INSERT_AERIS_CLIENT_SECRET_HERE 
>> > #[[WWO]] 
>> > #api_key = INSERT_WWO_API_KEY_HERE 
>> > #[[DS]] 
>> > #api_key = INSERT_DS_API_KEY_HERE 
>> > 
>> > 
>> > skin.conf 
>> > Make adjustments for your location. 
>> > 
>> > # configuration file for the weewx-wdc skin 
>> > SKIN_NAME = Weather Data Center 
>> > SKIN_VERSION = 2.1.0 
>> > 
>> > [Extras] 
>> > # Show a link to the GitHub respository of this skin. Set to 
>> > False to hide. 
>> > github_link = True 
>> > 
>> > # This radar image would be available as $Extras.radar_img 
>> > #radar_img = https://www.dwd.de/DWD/wetter/radar/ 
>> > radfilm_sac_akt.gif 
>> > # This URL will be used as the image hyperlink: 
>> > #radar_url =https://www.dwd.de/DE/leistungen/radarbild_film 
>> > /radarbild_film.html 
>> > 
>> > [[forecast_zambretti]] 
>> > enable = True 
>> > hemisphere = NORTH   
>> > 
>> > [[forecast_table_settings]] 
>> > source = WU 
>> > num_periods = 72 
>> > num_days = 5 
>> > show_legend = 1 
>> > show_hourly = 0 
>> > show_day = 1 
>> >

Re: [weewx-user] Investigating logs for sporadic loss of sensors during the night

['michael.k...@gmx.at' via weewx-user]

If it is not the battery, check the signal strength. With the Interceptor 
Driver I don't know how to get the readings for the signal strength. But 
you could try to find out and then see if there are drops in any way. 
Sometimes it doesn't need much to have an inferior signal strength. I, for 
instance, have my gw2000 behind my wall-mounted television. If I tilt it 
too much, the signal for my WS90 drops from perfect to almost nothing.

Tom Keffer schrieb am Mittwoch, 10. Januar 2024 um 15:56:15 UTC+1:

> Hard to say without actually seeing the logs, but these 
> "middle-of-the-night' dropouts are often caused by weak sensor batteries.
>
> On Wed, Jan 10, 2024 at 6:51 AM Invisible Man  
> wrote:
>
>> Hi,
>> Sometimes during the night I lose data from my sensors a couple of hours. 
>> I've had a look at the logs, but can't see any ERROR message. What type of 
>> message should I be looking for in weewx.log?
>>
>> Example: https://biotmeteo.masdescrocodiles.fr/daytempdew.png
>> My weather station is an EcoWitt HP2551. It uses "Interceptor". Weewx 
>> 4.10.2 is running on a Raspberry Pi.
>>
>> Thanks,
>> Axelle.
>>
>> -- 
>> 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/5f18c80e-cc5b-473d-aa59-4cab23ebeccan%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/6e763c4b-10a5-4741-ab8c-15adbb7c2b9dn%40googlegroups.com.