[weewx-user] Re: Discrepancies between FTPd site and internal website

[Karen K]

vince schrieb am Sonntag, 6. Oktober 2024 um 22:18:11 UTC+2:

Your two images are from different times.


That does not explain the differences in sunrise and sunset time and in the 
highs and lows, I guess. 

What about the upload? Does it take place at all?

-- 
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/9730e357-26c6-4c6c-8ed9-a2ff3ca5fc10n%40googlegroups.com.

Re: [weewx-user] NOAA Reports - Heating Degree Days

[Karen K]

Rory Gillies schrieb am Montag, 30. September 2024 um 15:11:04 UTC+2:

Thanks for the detailed response Gary, I should have said I am still on 
4.10.2, are the base temperature stanzas available in this version? I like 
the idea of putting it in the Weewx config rather than the skin.


Not changed between these versions.
 

-- 
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/a8dc978a-4263-44c1-af6a-6b64c3bf3d25n%40googlegroups.com.

Re: [weewx-user] Re: Calculating a moving average for wind dir / speed

[Karen K]

James Pattinson schrieb am Montag, 30. September 2024 um 14:36:29 UTC+2:

I've tested this out. I am not exactly sure if I understand this correctly, 
but it looks like that the loop and archive data is getting intermingled 
somehow. 


Yes, they do.

You can distinguish LOOP packets and ARCHIVE records within the MQTT data 
by looking at interval_minute. If this observation type is included, it is 
an ARCHIVE record, if not, a LOOP packet.

-- 
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/00e4c6e3-c44d-414d-8540-dcb0caff1345n%40googlegroups.com.

Re: [weewx-user] Hang ups on Raspberry Pi

[Karen K]

You could enter

sudo journalctl -u weewx >weewxlog.txt

and post the resulting file weewxlog.txt here. What you posted is not 
complete.



ANDREI ROZWADOWSKI schrieb am Montag, 30. September 2024 um 13:09:52 UTC+2:

> I reinstalled RaspOS. Now it's Bookworm ( 32-bit ) .
> After that I've installed Weewx.
> I use Davis Vantage Pro2 with data-logger
> This station is connected to RaspPi via usb cable (direct connection).
> I checked folder /var/www/html/weewx/. It's empty.
> There isn't the file "index.html".
> And I didn't find folder "/dev/vantage"
> I agree with vince and Warren Gill that Vantage drivers (/dev/ttyUSB0) is 
> not installed correctly.
>
> Also I printed logs:
>
> pi@raspberrypi:~ $ sudo systemctl status weewx
> × weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
> enable>
>  Active: failed (Result: exit-code) since Sun 2024-09-29 16:06:19 MSK; 
> 1h 3>
>Duration: 1.229s
>Docs: https://weewx.com/docs
> Process: 2788 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 2788 (code=exited, status=4)
> CPU: 1.148s
>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>Fi>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  >
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>Fi>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  >
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  seri>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: Unable to 
> load dri>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__:  
>  Exiting.>
> Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Main process 
> exited, cod>
> Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Failed with result 
> 'exit>
> Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Consumed 1.148s CPU 
> time.
> ...skipping...
> × weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
> enable>
>  Active: failed (Result: exit-code) since Sun 2024-09-29 16:06:19 MSK; 
> 1h 3>
>Duration: 1.229s
>Docs: https://weewx.com/docs
> Process: 2788 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 2788 (code=exited, status=4)
> CPU: 1.148s
>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>Fi>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  >
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>Fi>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  >
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  seri>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: Unable to 
> load dri>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__:  
>  Exiting.>
> Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Main process 
> exited, cod>
> Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Failed with result 
> 'exit>
> Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Consumed 1.148s CPU 
> time.
> ~
> ~
> ~
> ~
>
>
> pi@raspberrypi:~ $ sudo journalctl -u weewx
> Sep 29 16:06:18 raspberrypi systemd[1]: Started weewx.service - WeeWX.
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Initializing 
> weewxd ve>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Command line: 
> /usr/sha>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Using Python: 
> 3.11.2 (>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Located at:   
> /usr/bin>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Platform: 
> Linux-6.>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Locale:   
> 'en_US.U>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Entry path:   
> /usr/sha>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: WEEWX_ROOT:   
> /etc/wee>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Config file: 
>  /etc/wee>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: User module: 
>  /etc/wee>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Debug:0
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: User: 
> weewx
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Group:   
>  weewx
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Groups:   
> weewx
> Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO weewx.engine: Loading 
> station ty>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: ERROR weewx.engine: Import of 
> driver >
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>  Trac>
> Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine:  
>Fi>
> Sep 29 16:06:19 raspberrypi weewxd[

[weewx-user] Re: Calculating a moving average for wind dir / speed

[Karen K]

James Pattinson schrieb am Montag, 30. September 2024 um 09:08:00 UTC+2:

That's a good idea. My Python skills aren't brilliant (I still write 
scripts like I'm in the 1990s) but I had considered writing a script 
totally outside of WeeWX to subscribe to the MQTT topics, perform this 
calculation, and emit the average. Doing with a WeeWX service would be a 
more elegant solution, so I will take a look at some examples.


Such a service would look like this:

*class *YourService(StdService):


*def *__init__(self, engine, conf_dict):

super(YourService,self).__init__(engine, conf_dict)

self.wind_readings_cache = []

self.bind(weewx.NEW_LOOP_PACKET, self.new_loop_packet)


*def *new_loop_packet(self, event):

wind = event.packet.get('windSpeed')

if wind is not None:

# do some calculations involving self.wind_readings_cache

event.packet['windSpeedAvg'] = ...


 This is a rough sketch. There are more details to consider to complete it.

-- 
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/32a2ef9a-2fdb-4a16-9df6-719bc399b094n%40googlegroups.com.

[weewx-user] Re: Calculating a moving average for wind dir / speed

[Karen K]

If you have some experience in Python, you could write a little WeeWX 
service, which registers with the LOOP packet loop. So, every time a new 
wind value is received you could store it in a variable, then calculate the 
moving average and then add it to the LOOP packet. There are a lot of 
little services around there to provide an example, how to do so.

James Pattinson schrieb am Sonntag, 29. September 2024 um 20:53:54 UTC+2:

> Bit of background, I have been asked to set up a simple weather screen for 
> an airfield manned by hobbyists. They bought a Davis ISS and 6313 console 
> combo, and I found that the console is essentially a closed/cloud system 
> and not good for real time data.
>
> So, I've since installed a Pi with an RTLSDR dongle and WeeWx. It's 
> receiving data from the iSS and populating reports every 5 minutes.
>
> At the airfield we generally need a pretty up to date wind direction and 
> speed, averaged over the last 1 or 2 minutes, and a real time 'instant' 
> wind display.
>
> The instant wind I am OK with. I've installed the MQTT extension to WeeWx 
> so I get the LOOP data every few seconds with the wind info.
>
> Now, I'm not sure how to go about getting the average wind. Ideally, what 
> I want is that at every update of the raw wind value (ie at the LOOP time) 
> it also computes the average wind speed / vector over the last 1,2 and 10 
> minutes, so basically three moving averages all updated every few seconds, 
> so I think these updates will be quite 'smooth' and not jumping all over 
> the place like the instant wind reading.
>
> Problem is I've no idea where to start with this, or even if it's 
> possible. I would appreciate any ideas anyone may have.
>
>
>

-- 
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/9dea5a0f-ca5e-4126-b0eb-8336037c6002n%40googlegroups.com.

[weewx-user] Re: Data Import

[Karen K]

And take in mind there is one record per hour in AWAKAS only.

-- 
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/4b378f81-7991-4743-b3c7-0060a91c259bn%40googlegroups.com.

[weewx-user] Re: newbie question on drivers

[Karen K]

Kurt Rosenberger schrieb am Samstag, 28. September 2024 um 20:15:13 UTC+2:

Hey everyone
OK, this really shouldn't be that hard, but somehow I can't get it to work. 
I'm trying to use an Airmar PB200 sensor with weewx on a RasPi 3B+, and 
downloaded the driver from the user group. I have put the driver in 
etc/weewx/bin/user as suggested, and added Airmar as the station in my 
.conf file (driver = weewx.drivers.airmar), but weewx can't seem to find 
the driver. What am I doing wrong? See output from systemctl status below:


I highlighted the relevant lines in your post. You said you put the file to 
the user directory, but in the configuration file you said it would be at 
/usr/share/weewx/weewx/drivers. 

So try using driver = user.airmar.

 

-- 
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/0a30a712-75b6-4d5b-ad96-eb180228d9ean%40googlegroups.com.

Re: [weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

I added an example to download a map from the Finnish Meteorological 
Institute 
.
 
They offer a long list of layers.

-- 
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/377576b0-0e37-4b35-a1cd-9bc87c777e3dn%40googlegroups.com.

[weewx-user] Re: WeeWX considerations in shopping for sensors/hardware

[Karen K]

Gregory schrieb am Mittwoch, 18. September 2024 um 19:26:07 UTC+2:

I had been intending to purchase a Davis Vantage Pro 2, but it appears that 
I would have to use Davis's Weatherlink cloud service to get the data into 
WeeWX. If I'm mistaken about this, 


No, there are other possibilities than using Davis's cloud.

One possibility is to use the old console together with an adaptor 6510SER, 
6510USB, or (if you can get a used one) 6555 IP. The other possibility is 
to use the WeatherLink Live 6100 device. You need Davis's cloud to 
configure that device, but you do *not* need the cloud to get the readings 
out of the device. There are several drivers for WeeWX to do that. 

-- 
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/bc758ec0-28cd-4ae1-90cb-2f48b56269ddn%40googlegroups.com.

Re: [weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

I now looked at the server of EUMETSAT. There are a lot of different kinds 
of satellite pictures and calculated maps available there.

weewx-DWD EUMETSAT download example 


EUMETSAT website . Click 
"API access" there and then "WMS" and get a list of available layers.

-- 
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/9bddac8d-b622-4683-b8ca-713a7178265cn%40googlegroups.com.

[weewx-user] Re: MQTT change GPS coordinates' units from None to compass_degrees or " °"

[Karen K]

You can configure the amount of decimal digits in skin.conf in section 
[Units], sub-section [[StringFormats]]. Add a line naming the unit and 
format string like this: degree_compass = %.3f.

Stefan Gliessmann schrieb am Freitag, 13. September 2024 um 14:59:09 UTC+2:

> I have now made These changes in the Extensions.py file.
> I now gut the unit correct to °, but have only integer values and no 
> digits after the decimal.
> For the direction of a compass that is perfectly fine. For GPS coordinate, 
> no digits after the decimal is pretty useless for displaying purposes.
>
> As you can see, I tried to play arround with '%.3f', but that caused more 
> errors and weewx to exit ... 
>
> So, how to I format the GPS coordinates with three digits after the 
> decimal, but keep the compass direction as an integer?
>
> #
> #Copyright (c) 2009-2015 Tom Keffer 
> #
> #See the file LICENSE.txt for your full rights.
> #
>
> """User extensions module
>
> This module is imported from the main executable, so anything put here 
> will be
> executed before anything else happens. This makes it a good place to put 
> user
> extensions.
> """
>
> import locale
> import weewx.units
>
> # This sets the locale for all categories to the user’s default setting 
> (typically specified in the
> # LANG environment variable). See: 
> https://docs.python.org/3/library/locale.html#locale.setlocale
> locale.setlocale(locale.LC_ALL, '')
>
> import weewx.units ## works, but has no digits after the decimal
>
> for group in weewx.units.std_groups:
> 
> weewx.units.std_groups[group].setdefault('group_coordinate','degree_compass')
> weewx.units.obs_group_dict.setdefault('latitude','group_coordinate')
> weewx.units.obs_group_dict.setdefault('longitude','group_coordinate')
>
> # Create a custom formatter for the latitude and longitude observations
> #formatter = weewx.units.Formatter({'latitude': '%.3f', 'longitude': 
> '%.3f'})
>
> # Set the formatter for the latitude and longitude observations
> #weewx.units.obs_group_dict['latitude'] = ('degree_latitude', 
> 'group_coordinate', formatter)
> #weewx.units.obs_group_dict['longitude'] = ('degree_longitude', 
> 'group_coordinate', formatter)
>
>
> On Wednesday, August 21, 2024 at 4:13:51 PM UTC+2 Karen K wrote:
>
>> Each observation type needs an assignment to a unit group. So if you 
>> define a new observation type you have to write somewhere:
>>
>>
>> weewx.units.obs_group_dict.setdefault('your_observation_type','group_something')
>>
>> The unit group must exist. group_direction is an example of a unit group 
>> that is connected to the unit degree_compass. 
>>
>> Please also not the name of the unit degree_compass, not otherwise round.
>>
>> If you want to define a new unit group, say group_coordinate, you have 
>> to write:
>>
>> *for* group *in* weewx.units.std_groups:
>>
>> weewx.units.std_groups[group].setdefault('group_coordinate',
>> 'degree_compass')
>>
>> You can include that code in user/extensions.py.
>>
>>
>> Stefan Gliessmann schrieb am Mittwoch, 21. August 2024 um 15:46:28 UTC+2:
>>
>>> A GPS device in my RV sends the current coordinates via MQTT to my weewx 
>>> server.
>>> The coordinates are displayed with units = None.
>>> Trying to change them to units = degree_compass or units = " °" results 
>>> in the below error:
>>>
>>> Aug 21 15:28:26 rvwx weewx[1590] DEBUG weewx.units: Unable to convert 
>>> from None to  °
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: MQTT: Unexpected 
>>> exception of type 
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** Traceback (most 
>>> recent call last):
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
>>> "/usr/share/weewx/weewx/restx.py", line 382, in run_loop
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** 
>>> self.process_record(_record, dbmanager)
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
>>> "/usr/share/weewx/user/mqtt.py", line 516, in process_record
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** data = 
>>> self.filter_data(record)
>>> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
>>> "/usr/share/weewx/user/mqtt.py&qu

[weewx-user] Re: Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Karen K]

Could you report what was the difference between the belchertown.py that 
created the error and the belchertown.py that works?

Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 15:04:49 
UTC+2:

> well - I just did another:
>
> sudo wget 
> https://github.com/poblabs/weewx-belchertown/raw/master/bin/user/belchertown.py
>
> and now, it works 
>
> Thank you, again, Tom!
> On Thursday, September 12, 2024 at 2:50:36 PM UTC+2 Stefan Gliessmann 
> wrote:
>
>> Actually, the updated belchertown.py (three months ago) is already in 
>> place on my server.
>> Please notice that this is Ubuntu 24.04.01
>>
>> Before the upgrade, it was running just fine on Ubuntu 24.04.
>>
>> I did re-install "locales" already:
>>
>> sudo apt-get update
>> sudo apt-get install --reinstall locales
>>
>> A little test script return the correct format, too:
>>
>> import locale
>> locale.setlocale(locale.LC_ALL, '')
>> print(locale.format_string("%g", 12345.6789, grouping=True))
>>
>>  Hmm ...
>>
>> On Thursday, September 12, 2024 at 2:43:54 PM UTC+2 Stefan Gliessmann 
>> wrote:
>>
>>> Thank you Tom!
>>>
>>> I need to improve my search skills in this group!
>>>
>>> Cheers,
>>> Stefan
>>>
>>>
>>> On Thursday, September 12, 2024 at 2:30:20 PM UTC+2 Karen K wrote:
>>>
>>>> I guess you may want to re-install some Python modules. The error 
>>>> message reports an error regarding the "locale" module. I see no 
>>>> connection 
>>>> to the Belchertown skin itself.
>>>>
>>>> Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 14:18:37 
>>>> UTC+2:
>>>>
>>>>> Dear All -
>>>>>
>>>>> I just finished upgrading my weewx server's OS from Ubuntu 24.04. to 
>>>>> Ubuntu 24.04.01 LTS.
>>>>>
>>>>> After the reboot, things booted up just fine.
>>>>> But no new reports were generated.
>>>>> Going to the logfile, I found:
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
>>>>> unrecoverable exception in generator 
>>>>> 'weewx.cheetahgenerator.CheetahGenerator'*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>   module 'locale' has no attribute 'format'*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>   Traceback (most recent call last):*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>> File "/usr/share/weewx/weewx/reportengine.py", line 248, in run*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>   obj.start()*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>> File "/usr/share/weewx/weewx/reportengine.py", line 465, in start*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>   self.run()*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in 
>>>>> run*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>   ngen = self.generate(gen_dict[section_name], section_name, 
>>>>> self.gen_ts)*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>  
>>>>> *
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>>>>> generate*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>>>>
>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine

[weewx-user] Re: Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Karen K]

I guess you may want to re-install some Python modules. The error message 
reports an error regarding the "locale" module. I see no connection to the 
Belchertown skin itself.

Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 14:18:37 
UTC+2:

> Dear All -
>
> I just finished upgrading my weewx server's OS from Ubuntu 24.04. to 
> Ubuntu 24.04.01 LTS.
>
> After the reboot, things booted up just fine.
> But no new reports were generated.
> Going to the logfile, I found:
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 
> 'weewx.cheetahgenerator.CheetahGenerator'*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   module 'locale' has no attribute 'format'*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   Traceback (most recent call last):*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 248, in run*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   obj.start()*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 465, in start*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   self.run()*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   ngen = self.generate(gen_dict[section_name], section_name, 
> self.gen_ts)*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>  
> *
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
> generate*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   ^^*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
> generate*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   ^^*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in 
> generate*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   searchList = self._getSearchList(encoding, timespan,*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>    ^^^*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 401, in 
> _getSearchList*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   search_list += obj.get_extension_list(timespan, db_lookup)*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>  ^^^*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
> File "/etc/weewx/bin/user/belchertown.py", line 612, in 
> get_extension_list*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   locale.format("%g", float(year_outTemp_max_range_total)),*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   ^*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   AttributeError: module 'locale' has no attribute 'format'. Did you 
> mean: '_format'?*
>
> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>   Generator terminated*
>
>
> I read that the upgrade might have changed the installed modules of 
> python3.
>
> Is this really the root cause of this error message? And if so,  how do I 
> fix it? Re-install the belchertown skin?
>
>
> Anybodyelse did the Ubuntu upgrade recently?
>

-- 
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/7327a109-3033-4a33-b0c8-97212ba

[weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

David Hathaway schrieb am Sonntag, 18. August 2024 um 14:35:05 UTC+2:

This is really interesting. Can you get underlaying geo features, like 
roads or topology?


I did some further investigations, and I ask one of the weather services 
for that. If the server that provides the readings does not provide geo 
features, you can use any other server to get that additional information 
as long as you specify the same bbox, width, height and crs parameters. 
There is an example in the KNMI wiki page 
,
 
and you could even use their geo feature server as it covers the whole 
world including U.S. Use the GetCapabilities request to get a list of the 
layers and their names.

-- 
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/7d737d05-4eaa-4e4a-b2a0-71d5c4965f7en%40googlegroups.com.

[weewx-user] Re: weewx-DWD starts supporting KNMI

[Karen K]

There was the question how to put the country borders and the coast line 
below the radar data in the example. I asked the KNMI for that, and they 
replied immediately. So I updated the wiki page with HTML code and an 
example picture.

https://github.com/roe-dl/weewx-DWD/wiki/Koninklijk-Nederlands-Meteorologisch-Instituut-(KNMI)#knmi-ogc-server

Karen K schrieb am Donnerstag, 5. September 2024 um 07:57:23 UTC+2:

> weewx-DWD <https://github.com/roe-dl/weewx-DWD> starts supporting the 
> dutch weather service KNMI. See KNMI wiki page 
> <https://github.com/roe-dl/weewx-DWD/wiki/Koninklijk-Nederlands-Meteorologisch-Instituut-(KNMI)>
>  for 
> more details. 
>
> KNMI uses a sophisticated interface that involves several steps to 
> retrieve one file. You cannot simply download it from their web server. 
> weewx-DWD supports this interface now, but I guess, there is still some 
> work to do left.
>

-- 
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/4508e074-2c5c-472d-aa8e-7a6424b42d0fn%40googlegroups.com.

[weewx-user] Re: How long will an SD card last?

[Karen K]

There were some comments about UPSs some posts before saying they are not 
really necessary. And when I read the post of Michael.K I remember another 
thing. It were not SD-Cards or RPis, that failed repeatedly, but LED lamps. 
So we measured the grid voltage in our home and recorded the readings 
during one year. It turned out, that it was always near the upper limit, 
and sometimes even above it. We then complained to the electric power 
supplier company and presented our measurements. They reacted very quickly 
and changed the settings of the transformer. Since then the voltage is 
within the limits. I guess this can influence the lifetime of the 
equipment, too. I know, there is a power supply between grid and RPi that 
transforms the voltage. But it cannot always filter all peaks of 
overvoltage.


-- 
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/efc97322-3a9a-4d09-ae60-7228f7f58026n%40googlegroups.com.

[weewx-user] weewx-DWD starts supporting KNMI

[Karen K]

weewx-DWD  starts supporting the dutch 
weather service KNMI. See KNMI wiki page 

 for 
more details. 

KNMI uses a sophisticated interface that involves several steps to retrieve 
one file. You cannot simply download it from their web server. weewx-DWD 
supports this interface now, but I guess, there is still some work to do 
left.

-- 
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/6258e0fc-e8bc-4727-bbb9-83086b93fa3cn%40googlegroups.com.

[weewx-user] Re: How long will an SD card last?

[Karen K]

Thank you for sharing this experience.

-- 
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/e8e5a997-73e1-40fc-841a-8ca04f92ceden%40googlegroups.com.

[weewx-user] Re: MQTT error after upgrading to weewx 5.1 from 4.10

[Karen K]

The error message says the database one unit system and weewx.conf is the 
other. One of them is US, the other one is METRIC. That is not possible.

-- 
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/d3c75978-2367-4b1f-ab28-773bdc3d6598n%40googlegroups.com.

[weewx-user] Re: Weather Forecast

[Karen K]

There is a wiki page regarding Open-Meteo 
 
available 
now.

-- 
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/d434d018-b4b2-41d1-b828-ac02117bc8e9n%40googlegroups.com.

[weewx-user] Re: OpenWeather current data support in weewx-DWD

[Karen K]

Now there is a more detailed description of the interface including a list 
of observation types available at the OpenWeather wiki article 
<https://github.com/roe-dl/weewx-DWD/wiki/OpenWeather-(English)>.

Karen K schrieb am Freitag, 23. August 2024 um 17:06:34 UTC+2:

weewx-DWD <https://github.com/roe-dl/weewx-DWD> provides an interface to 
various weather services. It uses their APIs to retrieve weather and 
forecast data for use in WeeWX.

OpenWeather <https://openweather.co.uk> is an UK based company that 
provides weather data based on calculations for every point on earth.

Now weewx-DWD was updated to support retrieving actual weather data from 
OpenWeather by their API. It includes additional observation types to the 
archive record. The observation types are named like the standard 
observation types of core WeeWX, but prepended by a configurable prefix. 
You can retrieve data for more than one location in parallel.

The configuration is simple. Specify latitude and longitude and the 
language, the text messages should be provided in. You need an API key 
which you get from OpenWeather for free. The configuration section in 
weewx.conf could look like this:

[WeatherServices]

path = '.'

[[current]]

[[[FichtelbergOWM]]]

provider = OpenWeather

station = Fichtelberg

latitude = 50.4283

longitude = 12.9536

lang = 'en'

prefix = 'xyz'

api_key = 'API key that you got from OpenWeather'

This would retrieve current weather data for mount Fichtelberg in Saxony. 
You can specify any other location around the world.

The prefix is set to 'xyz' here. This means, if you want to display the 
temperature you would write $current.xyzOutTemp in the skin template. 
$current.xyzIcon.raw provides an icon file name, and 
$current.xyzIcontitle.raw a text message describing the current weather.

As OpenWeather does not provide dewpoint, it is calculated within weewx-DWD 
using the WeeWX formula.

WeeWX uses a constant archive interval, but OpenWeather provides their data 
with a varying interval. Therefore, weewx-DWD stores the data it got from 
OpenWeather to a separate database. This database can be made available to 
WeeWX by configuring an appropriate binding. 

I see no use in putting downloaded data into LOOP packets here, as their 
data is updated at most once per 5 minutes.

There is an additional feature I could not test: If your station is mounted 
on a vehicle and its location is available in WeeWX by observation types 
called latitude and longitude, you can specify "station = mobile", and data 
is always retrieved for the current location of the station as defined by 
the observation types latitude and longitude. I am sure there is at least 
one person who wants to try this feature.

-- 
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/e95bc508-d66f-41d4-af5e-4e1231d56aa6n%40googlegroups.com.

[weewx-user] Re: Does Weewx have a complete parameter list.htm?

[Karen K]

How to use observation types in templates is described in the customization 
guide in chapter The Cheetah generator 
. 

There is no complete list of observation types. Which observation types are 
available, depends on the driver. You may want to look into the file 
units.py, which contains a list of pre-defined observation types.

uweheid...@googlemail.com schrieb am Samstag, 24. August 2024 um 18:03:52 
UTC+2:

> I'm looking for a complete parameter list.htm so that weewx can enter the 
> data there and I can use this file as a template.
> WView had a file like this:
> stationName=
> tempUnit=
> insideTemp=
> I hope someone can help me?
>
> Thank you very much
>

-- 
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/5e253d18-7137-475b-96e7-c3a79b9a2ca3n%40googlegroups.com.

[weewx-user] OpenWeather current data support in weewx-DWD

[Karen K]

weewx-DWD  provides an interface to 
various weather services. It uses their APIs to retrieve weather and 
forecast data for use in WeeWX.

OpenWeather  is an UK based company that 
provides weather data based on calculations for every point on earth.

Now weewx-DWD was updated to support retrieving actual weather data from 
OpenWeather by their API. It includes additional observation types to the 
archive record. The observation types are named like the standard 
observation types of core WeeWX, but prepended by a configurable prefix. 
You can retrieve data for more than one location in parallel.

The configuration is simple. Specify latitude and longitude and the 
language, the text messages should be provided in. You need an API key 
which you get from OpenWeather for free. The configuration section in 
weewx.conf could look like this:

[WeatherServices]

path = '.'

[[current]]

[[[FichtelbergOWM]]]

provider = OpenWeather

station = Fichtelberg

latitude = 50.4283

longitude = 12.9536

lang = 'en'

prefix = 'xyz'

api_key = 'API key that you got from OpenWeather'

This would retrieve current weather data for mount Fichtelberg in Saxony. 
You can specify any other location around the world.

The prefix is set to 'xyz' here. This means, if you want to display the 
temperature you would write $current.xyzOutTemp in the skin template. 
$current.xyzIcon.raw provides an icon file name, and 
$current.xyzIcontitle.raw a text message describing the current weather.

As OpenWeather does not provide dewpoint, it is calculated within weewx-DWD 
using the WeeWX formula.

WeeWX uses a constant archive interval, but OpenWeather provides their data 
with a varying interval. Therefore, weewx-DWD stores the data it got from 
OpenWeather to a separate database. This database can be made available to 
WeeWX by configuring an appropriate binding. 

I see no use in putting downloaded data into LOOP packets here, as their 
data is updated at most once per 5 minutes.

There is an additional feature I could not test: If your station is mounted 
on a vehicle and its location is available in WeeWX by observation types 
called latitude and longitude, you can specify "station = mobile", and data 
is always retrieved for the current location of the station as defined by 
the observation types latitude and longitude. I am sure there is at least 
one person who wants to try this feature.

-- 
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/d0ed8be5-9cb4-4124-8525-262d1f57f611n%40googlegroups.com.

[weewx-user] Re: MQTT change GPS coordinates' units from None to compass_degrees or " °"

[Karen K]

Each observation type needs an assignment to a unit group. So if you define 
a new observation type you have to write somewhere:

weewx.units.obs_group_dict.setdefault('your_observation_type','group_something')

The unit group must exist. group_direction is an example of a unit group 
that is connected to the unit degree_compass. 

Please also not the name of the unit degree_compass, not otherwise round.

If you want to define a new unit group, say group_coordinate, you have to 
write:

*for* group *in* weewx.units.std_groups:

weewx.units.std_groups[group].setdefault('group_coordinate',
'degree_compass')

You can include that code in user/extensions.py.


Stefan Gliessmann schrieb am Mittwoch, 21. August 2024 um 15:46:28 UTC+2:

> A GPS device in my RV sends the current coordinates via MQTT to my weewx 
> server.
> The coordinates are displayed with units = None.
> Trying to change them to units = degree_compass or units = " °" results in 
> the below error:
>
> Aug 21 15:28:26 rvwx weewx[1590] DEBUG weewx.units: Unable to convert from 
> None to  °
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: MQTT: Unexpected 
> exception of type 
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** Traceback (most 
> recent call last):
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 382, in run_loop
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** 
> self.process_record(_record, dbmanager)
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/user/mqtt.py", line 516, in process_record
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** data = 
> self.filter_data(record)
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/user/mqtt.py", line 496, in filter_data
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** v = 
> weewx.units.convert(from_t, to_units)[0]
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/units.py", line 1454, in convert
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** 
> conversion_func = conversionDict[val_t[1]][target_unit]
> Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** KeyError: None
> Aug 21 15:28:26 rvwx weewx[1590] CRITICAL weewx.restx: MQTT: Thread 
> terminating. Reason: None
>
> Here is the relevant section from weewx.conf to display coordinates in 
> belchertown skin:
>  [[MQTT]]
> server_url = mqtt://
> :yy...@wxvm.bz3gfkrlqtrsc3sv.myfritz.net:1883/ 
> 
> topic = RV
> unit_system = METRIC
> binding = loop, archive
> log_success = true
>[[[inputs]]]
> latitude
> # units = " °"
>  format = %.3f
>
> and MQTT subscribe to Write the GPS data received via MQTT into the weewx 
> db:
> [MQTTSubscribeService]
> # This section is for the MQTTSubscribe service.
>
> # Turn the service on and off.
> # Default is: true
> # Only used by the service.
> enable = true
> log = true
>
> # The MQTT server.
> # Default is localhost.
> host = "wxvm.bz3gfkrlqtrsc3sv.myfritz.net"
>
> # The port to connect to.
> # Default is 1883.
> port = 1883
>
> # Maximum period in seconds allowed between communications with the 
> broker.
> # Default is 60.
> keepalive = 60
>
> # username for broker authentication.
> # Default is None.
> username = 
>
> # password for broker authentication.
> # Default is None.
> password = 
>
> # The binding, loop or archive.
> # Default is: loop
> # Only used by the service.
> binding = loop
>
> # The message handler to use
> [[message_callback]]
> # The format of the MQTT payload.
> # Currently support: individual, json, keyword
> # Must be specified.
> type = json
>
> # The topics to subscribe to.
> [[topics]]
> # Units for MQTT payloads without unit value.
> # Valid values: US, METRIC, METRICWX
> # Default is: US
> unit_system = US
> #adjust_start_time = 1
> use_server_datetime = True
> use_topic_as_fieldname = true
>
> [[[RVGPS/#]]]
> # The WeeWX name.
> # Default is the name from MQTT.
> #name = Latitude
>
> # True if the incoming data should not be processed into WeeWX.
> # Valid values: True, False
> # Default is False
> ignore = False
>
> # True if the incoming data is cumulative.
> # Valid values: True, False
> # Default is False
> #contains_total = False
>
> # The conversion type necessary for WeeWX compatibility
> # Valid values: bool, float, int, none
> # Default is float
> #conversion_type = in

[weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

David Hathaway schrieb am Sonntag, 18. August 2024 um 14:35:05 UTC+2:

Can you get underlaying geo features, like roads or topology?


That depends on the server. Some servers provide them, some not. Generally 
you can set up a list of layers. So you can start or end the list with a 
layer of topographic data, if the server provides it. I did not check all 
the servers for their features. So you may want to ask the provider of the 
server of your choice.

-- 
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/916972cd-974a-4e96-aec1-e5acb52c33b2n%40googlegroups.com.

[weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

   
   - I added an English description, containing an example for querying the 
   NOAA server: Query Open Geospatial Consortium (OGC) Servers (English) 
   

   .
   - The german description as at: Open Geospatial Consortium (OGC) Server 
   abfragen 
   

   .
   

A lot of weather services (like NOAA, DWD etc.) operate an OGC server to 
provide weather maps, warnings maps, satellite pictures etc. What data to 
download is defined by a special set of URL parameters. weewx-DWD 
 provides a configuration interface to 
access such servers. You can easily set up the download parameters in 
weewx.conf as described in the Wiki pages mentioned above.

Besides querying OGC servers the module can also download arbitrary files 
from every server specified in weewx.conf by the url key.

-- 
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/ff68ef0f-cf25-43ac-8be9-fb9e49a56ee3n%40googlegroups.com.

[weewx-user] Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[Karen K]

A lot of weather services (like NOAA, DWD etc.) operate an OGC server to 
provide weather maps, warnings maps, satellite pictures etc. What data to 
download is defined by a special set of URL parameters. weewx-DWD 
 provides a configuration interface to 
access such servers. You can easily set up the download parameters in 
weewx.conf as described in this Wiki article 
.
 
The module makes sure, the downloaded files are available just before skin 
creation starts after the end of the archive interval. 

Besides querying OGC servers the module can also download arbitrary files 
from every server specified in weewx.conf by the url key.

-- 
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/e4bd862e-0602-4425-9018-60186f9f488fn%40googlegroups.com.

Re: [weewx-user] Re: Biowetter and Pollen forecast in weewx-DWD

[Karen K]

I created some icons used to indicate thermal stress:


-- 
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/5e61b5fc-d049-4af5-8757-d1a3b93fd5fan%40googlegroups.com.

[weewx-user] Re: It struck me like a lightning

[Karen K]

Heftig.

(I don't know how to say in English.)

-- 
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/770c751a-f3be-456d-a8a8-54f99c60ae97n%40googlegroups.com.

[weewx-user] Re: wee_database --calc-missing / weectl database calc-missing seem to not call shutDown() at the end

[Karen K]

gjr80 schrieb am Samstag, 27. Juli 2024 um 22:07:51 UTC+2:

The OP of the referenced thread can apply the fix to an his existing v5 
install by downloading the fixed database.py 


I was informed that that solved the problem for him.

-- 
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/849cb88d-51d6-47cf-8d45-c25475ee6e40n%40googlegroups.com.

[weewx-user] Re: New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

[Karen K]

You should state whether this is a package installation or a pip 
installation. What you have to do differs between the two.

-- 
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/9e24e8bc-d9fa-4597-aa84-618f7890c723n%40googlegroups.com.

[weewx-user] Re: wee_database --calc-missing / weectl database calc-missing seem to not call shutDown() at the end

[Karen K]

Thank you.

gjr80 schrieb am Samstag, 27. Juli 2024 um 22:07:51 UTC+2:

> Yes, class CalcMissing should call DummyEngine.shutDown() on closing so 
> that any invoked services have the chance to properly shut down. Fixed at 
> commit bf80fb8 
> 
>  
> to appear in the next release.
>
> The OP of the referenced thread can apply the fix to an his existing v5 
> install by downloading the fixed database.py using 
> https://raw.githubusercontent.com/weewx/weewx/development/src/weecfg/database.py
>  
> and replacing /usr/share/weewx/weecfg/database.py with the downloaded 
> database.py (alternatively he can run WeeWX with calc_missing = False in 
> his import config file to see if this is the source of his problem - as 
> long as he changes back to calc_missing = True before the end of the day 
> there will be no effect on his imported data)
>
> Gary
>
> On Sunday 28 July 2024 at 01:00:03 UTC+10 kk44...@gmail.com wrote:
>
>> This refers to https://groups.google.com/g/weewx-user/c/ZLn1scFWuMk
>>
>> If you call wee_database --calc-missing or weectl database calc-missing 
>> all the services defined in weewx.conf are loaded. If some of those 
>> services create threads, the command does not finish. Instead it waits 
>> indefinitely for the threads finishing.
>>
>> It seems to me, that wee-database --calc-missing and weectl database 
>> calc-missing do not call the shutDown() method of the services after 
>> finishing the calculation. So the services do not know it's time to shut 
>> down the threads they created. 
>>
>> Could that be?
>>
>>
>> Excerpt from the log:
>>
>> Jul 27 16:16:09 LokalWiki wee_database[*1320746*] INFO __main__: 
>> Preparing to calculate missing derived observations...
>>
>> Jul 27 16:16:09 LokalWiki wee_database[*1320746*] INFO __main__: Missing 
>> derived observations will be calculated from 2021-02-02 00:00:01 CET 
>> (1612220401) through to 2021-02-03 00:00:00 CET (1612306800) inclusive.
>>
>> Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.manager: 
>> Daily summary version is 4.0
>>
>> Jul 27 16:16:34 LokalWiki wee_database[*1320746*] INFO __main__: 
>> Calculating missing derived observations...
>>
>> Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.engine: 
>> Loading service weewx.engine.StdTimeSynch
>>
>> Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.engine: 
>> Finished loading service weewx.engine.StdTimeSynch
>>
>> Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.engine: 
>> Loading service ...
>>
>> Jul 27 16:16:39 LokalWiki wee_database[*1320746*] INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>>
>> Jul 27 16:16:39 LokalWiki wee_database[*1320746*] DEBUG weewx.manager: 
>> Daily summary version is 4.0
>>
>> Jul 27 16:16:39 LokalWiki wee_database[*1320746*] message repeated 3 
>> times: [ DEBUG weewx.manager: Daily summary version is 4.0]
>>
>> Jul 27 16:16:39 LokalWiki wee_database[*1320746*] INFO weewx.wxxtypes: 
>> Type beaufort has been deprecated. Use unit beaufort instead.
>>
>> Jul 27 16:16:39 LokalWiki wee_database[*1320746*] INFO weewx.manager: 
>> Starting backfill of daily summaries
>>
>> Jul 27 16:16:40 LokalWiki wee_database[*1320746*] INFO weewx.manager: 
>> Processed 288 records to backfill 1 day summaries in 0.71 seconds
>>
>> Jul 27 16:16:40 LokalWiki wee_database[*1320746*] INFO weecfg.database: 
>> Processed 1 day consisting of 288 records. 1 day consisting of 288 records 
>> were updated in 6.63 seconds.
>>
>> Jul 27 16:16:40 LokalWiki wee_database[*1320746*] INFO __main__: Missing 
>> derived observations calculated in 6.64 seconds
>>
>> ...
>>
>> Jul 27 16:18:53 LokalWiki wee_database[*1320746*] DEBUG 
>> urllib3.connectionpool: Starting new HTTPS connection (1): 
>> opendata.dwd.de:443
>>
>> Jul 27 16:18:54 LokalWiki wee_database[*1320746*] DEBUG 
>> urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
>> /weather/radar/composite/wn/WN_LATEST.tar.bz2 HTTP/1.1" 200 5501583
>>
>> Jul 27 16:18:55 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
>> successfully downloaded 
>> https://opendata.dwd.de/weather/radar/composite/wn/WN_LATEST.tar.bz2 in 
>> 1.66 seconds
>>
>> Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
>> urllib3.connectionpool: Starting new HTTPS connection (1): 
>> opendata.dwd.de:443
>>
>> Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
>> urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
>> /weather/text_forecasts/html/VHDL50_DWLG_LATEST_html HTTP/1.1" 200 609
>>
>> Jul 27 16:18:59 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
>> successfully downloaded 
>> https://opendata.dwd.de/weather/text_forecasts/html/VHDL50_DWLG_LATEST_html 
>> in 0.11 seconds
>>
>> Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
>> urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
>> /weather/text_forecasts/html/VHDL51_DWLG_LATEST_html HTTP/1

[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

Sebastian E schrieb am Montag, 22. Juli 2024 um 13:56:45 UTC+2:

Hello everyone, I currently have the problem that my RAM is regularly full 
and I have to restart the server. 

I have now seen that the weectl import service is not stopped. I'm 
attaching the output. Does anyone have an idea what this Area 31 30 means? 
That's where it seems to hang. Thank you


See https://groups.google.com/g/weewx-user/c/x0YJIz-aMYg/m/wx3ZgWGpAAAJ for 
explanation and further instructions. 

-- 
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/c779fd8e-8c12-4da9-9e8b-2268ea413502n%40googlegroups.com.

[weewx-user] weewx-DWD Nutzer gesucht

[Karen K]

Die Erweiterung scheint ja eine gewisse Verbreitung gefunden zu haben. Ich 
würde gern Nutzungsbeispiele verlinken. Dazu habe ich eine Wiki-Seite 
Beispiele  angelegt:

https://github.com/roe-dl/weewx-DWD/wiki/Beispiele

Wer möchte, kann da selbst einen Link auf seine Site eintragen.

-- 
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/df302d6a-63dc-4134-8201-86d65581d919n%40googlegroups.com.

[weewx-user] wee_database --calc-missing / weectl database calc-missing seem to not call shutDown() at the end

[Karen K]

This refers to https://groups.google.com/g/weewx-user/c/ZLn1scFWuMk

If you call wee_database --calc-missing or weectl database calc-missing all 
the services defined in weewx.conf are loaded. If some of those services 
create threads, the command does not finish. Instead it waits indefinitely 
for the threads finishing.

It seems to me, that wee-database --calc-missing and weectl database 
calc-missing do not call the shutDown() method of the services after 
finishing the calculation. So the services do not know it's time to shut 
down the threads they created. 

Could that be?


Excerpt from the log:

Jul 27 16:16:09 LokalWiki wee_database[*1320746*] INFO __main__: Preparing 
to calculate missing derived observations...

Jul 27 16:16:09 LokalWiki wee_database[*1320746*] INFO __main__: Missing 
derived observations will be calculated from 2021-02-02 00:00:01 CET 
(1612220401) through to 2021-02-03 00:00:00 CET (1612306800) inclusive.

Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.manager: 
Daily summary version is 4.0

Jul 27 16:16:34 LokalWiki wee_database[*1320746*] INFO __main__: 
Calculating missing derived observations...

Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.engine: 
Loading service weewx.engine.StdTimeSynch

Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.engine: 
Finished loading service weewx.engine.StdTimeSynch

Jul 27 16:16:34 LokalWiki wee_database[*1320746*] DEBUG weewx.engine: 
Loading service ...

Jul 27 16:16:39 LokalWiki wee_database[*1320746*] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding

Jul 27 16:16:39 LokalWiki wee_database[*1320746*] DEBUG weewx.manager: 
Daily summary version is 4.0

Jul 27 16:16:39 LokalWiki wee_database[*1320746*] message repeated 3 times: 
[ DEBUG weewx.manager: Daily summary version is 4.0]

Jul 27 16:16:39 LokalWiki wee_database[*1320746*] INFO weewx.wxxtypes: Type 
beaufort has been deprecated. Use unit beaufort instead.

Jul 27 16:16:39 LokalWiki wee_database[*1320746*] INFO weewx.manager: 
Starting backfill of daily summaries

Jul 27 16:16:40 LokalWiki wee_database[*1320746*] INFO weewx.manager: 
Processed 288 records to backfill 1 day summaries in 0.71 seconds

Jul 27 16:16:40 LokalWiki wee_database[*1320746*] INFO weecfg.database: 
Processed 1 day consisting of 288 records. 1 day consisting of 288 records 
were updated in 6.63 seconds.

Jul 27 16:16:40 LokalWiki wee_database[*1320746*] INFO __main__: Missing 
derived observations calculated in 6.64 seconds

...

Jul 27 16:18:53 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: Starting new HTTPS connection (1): 
opendata.dwd.de:443

Jul 27 16:18:54 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
/weather/radar/composite/wn/WN_LATEST.tar.bz2 HTTP/1.1" 200 5501583

Jul 27 16:18:55 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
successfully downloaded 
https://opendata.dwd.de/weather/radar/composite/wn/WN_LATEST.tar.bz2 in 
1.66 seconds

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: Starting new HTTPS connection (1): 
opendata.dwd.de:443

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
/weather/text_forecasts/html/VHDL50_DWLG_LATEST_html HTTP/1.1" 200 609

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
successfully downloaded 
https://opendata.dwd.de/weather/text_forecasts/html/VHDL50_DWLG_LATEST_html 
in 0.11 seconds

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
/weather/text_forecasts/html/VHDL51_DWLG_LATEST_html HTTP/1.1" 200 478

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
successfully downloaded 
https://opendata.dwd.de/weather/text_forecasts/html/VHDL51_DWLG_LATEST_html 
in 0.03 seconds

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
/weather/text_forecasts/html/VHDL52_DWLG_LATEST_html HTTP/1.1" 200 340

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
successfully downloaded 
https://opendata.dwd.de/weather/text_forecasts/html/VHDL52_DWLG_LATEST_html 
in 0.04 seconds

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
/weather/text_forecasts/html/VHDL53_DWLG_LATEST_html HTTP/1.1" 200 270

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
successfully downloaded 
https://opendata.dwd.de/weather/text_forecasts/html/VHDL53_DWLG_LATEST_html 
in 0.06 seconds

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] DEBUG 
urllib3.connectionpool: https://opendata.dwd.de:443 "GET 
/weather/text_forecasts/html/VHDL54_DWLG_LATEST_html HTTP/1.1" 200 516

Jul 27 16:18:59 LokalWiki wee_database[*1320746*] INFO user.DWD.base: 
successfully downloaded 
https://opendata.dwd.de/wea

Re: [weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

Thank you for clarification.

Tom Keffer schrieb am Donnerstag, 25. Juli 2024 um 21:10:27 UTC+2:

> See issue #95 <https://github.com/weewx/weewx/issues/95>.
>
> It's true that the reporting service probably does not need to be loaded, 
> but it's difficult for weectl to make a decision on what's needed and what 
> is not. Hence the decision to load everything.
>
> On Thu, Jul 25, 2024 at 11:45 AM Karen K  wrote:
>
>> Digging further into this issue I found out, that weectl loads all the 
>> services including restful services and report services to calculate 
>> missing derived values. This makes no sense to me, because those services 
>> are not used during calculation of missing derived values. The same applies 
>> to data_services. Or do I miss something?
>>
>> -- 
>> 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/964bde45-4c97-4edb-b363-425d295877d3n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/964bde45-4c97-4edb-b363-425d295877d3n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/3ba22914-e56d-418f-8054-e05b1d6273f5n%40googlegroups.com.

[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

Digging further into this issue I found out, that weectl loads all the 
services including restful services and report services to calculate 
missing derived values. This makes no sense to me, because those services 
are not used during calculation of missing derived values. The same applies 
to data_services. Or do I miss something?

-- 
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/964bde45-4c97-4edb-b363-425d295877d3n%40googlegroups.com.

[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

Sebastian E schrieb am Mittwoch, 24. Juli 2024 um 11:35:09 UTC+2:

data_services = user.weatherservices.DWDservice


Which services are still activated now?

-- 
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/1ac09107-ca57-42d2-96cd-7b2a93fff90dn%40googlegroups.com.

[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

Sebastian E schrieb am Dienstag, 23. Juli 2024 um 13:41:03 UTC+2:

Here is a longer excerpt from journalctl


What I get from that log is, that weectl starts report generation after 
importing data. And I see, the Belchertown skin is involved. So there is a 
possibility that this problem is involved: v5 performance troubleshooting 
.
 

-- 
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/cd81318a-275d-44d4-b3ae-bb7763d2e18bn%40googlegroups.com.

[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

If - as Gary suggests - GTS is the reason, you could try and comment out 
user.GTS.GTSService in weewx.conf and try again. If that makes a 
difference, this would be a path to look further.

-- 
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/d00bdbcf-51d8-493a-8220-32f002a13edcn%40googlegroups.com.

[weewx-user] Re: RAM is running full. Apparently it's due to the weectl import

[Karen K]

Gary,

may be, it is a little bit of a language problem. I heard of this case 
before, so I may add some explanation, but I cannot explain all.

The user seems to call weectl import from the command line or from crontab 
to retrieve data from Wunderground. The command first runs as expected. 
Data is imported and saved to the database. But then, the command does not 
end. It hangs. So I suggested to the user to press CTRL-C several times. 
This resulted in an error message saying that the command hang in the 
threading module while waiting for a lock.

First question: Where does weectl import use threading? Or does this point 
to the problem that threading is involved at all?

I had a short glance at the sources, but I did not see it.

Then, there are some hints that third party extensions are involved in the 
problem. Does weectl import load WeeWX extensions? I do not see a reason to 
do so. But the output "area 30 31" at the end of the first post is from an 
extension, not from the command itself.

Karen

-- 
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/d5c8d2e7-aa8c-4ac1-8352-ce12ac0db156n%40googlegroups.com.

[weewx-user] Download of Maps and other Files from Weather Services

[Karen K]

Regarding pip install issues documented here 
, I started to update 
weewx-DWD .

Several weather services provide maps and other graphic and text files for 
general use. They can be used to enhance private weather websites. But some 
of them state in their conditions, that it is not allowed to link to those 
files directly for load reasons. Instead you have to download the files and 
provide a copy of it on your own web server. 

For that purpose a new module in weewx-DWD 
 checks for updates at user defined 
URLs. If an update is observed, the file is downloaded to a directory 
within the skin of the user's choice. This is all done just before the end 
of the archive interval. So the file is there when the report thread 
starts, and it is uploaded to the user's web server together with the other 
files of the skin. This is all easy, only specify the URL, and that is it.

Additionally encoding of the file can be changed in case of text files. For 
example, if the file is provided in ISO8859-1, and you need it with HTML 
entities, this module can do the conversion.

For some common data provided by the German Weather Service DWD there are 
shortcuts for the configuration. So you need not enter the whole URL for 
those cases.
But it is not only the german weather service, the module works with every 
weather service.

-- 
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/c65d5f29-3b9d-43c8-b1c5-0ed657bb6014n%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

Tom Keffer schrieb am Dienstag, 16. Juli 2024 um 16:20:57 UTC+2:

Question: do you expect the same script to be used for installations that 
have done a package install, as well as a pip install? 


Yes. 

Primarily those scripts are invoked by crontab and create some files that 
are later used in skins by #include. Later on, when I added more modules to 
this extension, I wrote a WeeWX service that creates a thread, and that 
thread downloads data from some provider and processes them and then sleeps 
until new data are scheduled.

So I guess, I will have to set the migration of those old scripts into a 
WeeWX service to a higher priority.
 

-- 
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/93e82688-7653-41d9-8553-3f994f6668a2n%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

michael.k...@gmx.at schrieb am Dienstag, 16. Juli 2024 um 09:39:11 UTC+2:

bin/user?


You need a directory for that purpose that is included in $PATH. Otherwise 
the shell does not find the script. And bin/user is not. 

-- 
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/43def605-b216-4969-9aaf-eb63507536e8n%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

The result is: If the virtual environment (venv) is used, weectl must not 
be invoked by sudo. Without sudo, the correct paths are found. Thank you, 
Tom, for pointing to this.

Additional question: Where can I place a script that can be invoked by the 
user from the command line in such an environment? 

-- 
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/0729fe8e-74ac-4282-9b26-5d6d7059e52dn%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

Thank you. I will ask.

Tom Keffer schrieb am Sonntag, 14. Juli 2024 um 22:08:51 UTC+2:

> Let's back up a bit. On closer inspection of your user's log, I see 
> entries such as /usr/share/weewx. That implies a package install, so 
> weewx-venv is not involved. Yet, weewx.conf was not found in 
> /etc/weewx/weewx.conf, its normal location with a package install.
>
> You'll have to get clarification from your user how s/he did the original 
> install. It appears non-standard.
>
> On Sun, Jul 14, 2024 at 12:41 PM Karen K  wrote:
>
>> Tom Keffer schrieb am Sonntag, 14. Juli 2024 um 21:24:24 UTC+2:
>>
>> On Sun, Jul 14, 2024 at 12:13 PM Karen K  wrote:
>>
>> I read a little bit through the pip installation guide 
>> <https://weewx.com/docs/5.0/quickstarts/pip/>. There all calls of weectl 
>> are preceded by "source ~/weewx-venv/bin/activate". Could it be, that 
>> for installing extensions this is necessary, too? 
>>
>>
>> Absolutely. Sourcing the "activate" file nominates the Python 
>> interpreter, the Python runtime library, and the WeeWX code that is to be 
>> used. 
>>
>>
>> So I will have to update all the installation instructions of my 
>> extensions to reflect this requirement. 
>>
>> Would it be an idea to mention that there 
>> <https://weewx.com/docs/5.0/utilities/weectl-extension/>?
>>  
>>
>> -- 
>>
> 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/c7eba711-9f44-41b1-a0b5-8d263099828bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/c7eba711-9f44-41b1-a0b5-8d263099828bn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/a866bc08-d431-417e-afb0-8ee30df52c73n%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

Tom Keffer schrieb am Sonntag, 14. Juli 2024 um 21:24:24 UTC+2:

On Sun, Jul 14, 2024 at 12:13 PM Karen K  wrote:

I read a little bit through the pip installation guide 
<https://weewx.com/docs/5.0/quickstarts/pip/>. There all calls of weectl 
are preceded by "source ~/weewx-venv/bin/activate". Could it be, that for 
installing extensions this is necessary, too? 


Absolutely. Sourcing the "activate" file nominates the Python interpreter, 
the Python runtime library, and the WeeWX code that is to be used. 


So I will have to update all the installation instructions of my extensions 
to reflect this requirement. 

Would it be an idea to mention that there 
<https://weewx.com/docs/5.0/utilities/weectl-extension/>?
 

-- 
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/c7eba711-9f44-41b1-a0b5-8d263099828bn%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

Thank you all.

I read a little bit through the pip installation guide 
. There all calls of weectl 
are preceded by "source ~/weewx-venv/bin/activate". Could it be, that for 
installing extensions this is necessary, too? 

@Tom: When I wrote the first parts of this extension, I was new to WeeWX, 
and I used some separate scripts to create files that are later included 
into the skin using the #include directive. Later I was asked to publish 
those scripts. So they were included into this extension, and I had to deal 
with the installation of them. Not easy.

-- 
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/59ef1c29-61d7-4ce4-9c83-bfd2b35d6dben%40googlegroups.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

vince schrieb am Sonntag, 14. Juli 2024 um 20:19:45 UTC+2:

Agree. Your install.py should 'not' be run under sudo, you also need to 
modify it to be able to copy and symlink into /usr/local/bin (which 
requires sudo).


I am afraid, the installation crashes before all those copying and linking. 
It looks for weewx.conf and does not find it. Why?
 

Why aren't the /usr/local/bin items simply installed and running out of the 
bin/user directory 


I found no way to get the original location of the files within the 
configure() method. That's the reason.

-- 
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/c7b9e991-67fd-4c24-861e-7b3ca8c766c1n%40googlegroups.com.

[weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

[Karen K]

One user tried to install weewx-DWD  into 
an WeeWX installation made by pip. The error messages refer to files of 
core WeeWX:

(weewx-venv) user@pc:~$ sudo weectl extension install weewx-dwd.zip
[sudo] Passwort für user:
Error parsing config file: Unable to find file 'weewx.conf'. Tried 
directories ['/root/weewx-data', '/etc/weewx', '/home/weewx']
Traceback (most recent call last):
File "/usr/share/weewx/weeutil/startup.py", line 86, in start_app
config_path, config_dict = weecfg.read_config(config_option, [config_arg])
^^^
File "/usr/share/weewx/weecfg/*init*.py", line 147, in read_config
config_path = find_file(option_path, args, locations=locations, 
file_name=file_name)
^^
File "/usr/share/weewx/weecfg/*init*.py", line 104, in find_file
raise OSError(f"Unable to find file '{file_name}'. Tried directories 
{locations}")
OSError: Unable to find file 'weewx.conf'. Tried directories 
['/root/weewx-data', '/etc/weewx', '/home/weewx']


I have no glue what happens there. The messages say, that weewx.conf could 
not be found. Looking for that file is not part of install.py. 

Unfortunately I cannot try the installation myself actually. And I have no 
experience with weewx-venv.

See install.py 
 here.

There is a configure() method in this case, which is not widely used. But 
there is no reference to weewx.conf in it. I would have expected that the 
copying and linking in it may fail within a virtual environment, but the 
error messages say otherwise.

-- 
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/91c18ebb-c9b1-4bdf-b1b6-8e6224e4d537n%40googlegroups.com.

Re: [weewx-user] Re: Biowetter and Pollen forecast in weewx-DWD

[Karen K]

Some instructions:

   - Biowettervorhersage 
   
   - Pollenflugvorhersage 
   
   

-- 
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/d0f8f2dc-a2c0-46cc-b8df-603eae113223n%40googlegroups.com.

Re: [weewx-user] Re: Biowetter and Pollen forecast in weewx-DWD

[Karen K]

So I learnt a new word: PNW.

But there are other regions in Germany. The small town Ilmenau 
 in Thuringia claims that the sky is always 
blue there and the weather is fair. They included it in their town logo 
which reads "himmelblau" (English: blue like the sky). And in case you are 
interested in german literature you should have been there.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/834335d1-09f2-4964-90dc-4eb0f7f3360bn%40googlegroups.com.

[weewx-user] Biowetter and Pollen forecast in weewx-DWD

[Karen K]

I updated the weewx-DWD  extension.

As I heard there is no such thing like "Biowetter" in English. It means how 
the weather influences how people feel, whether the weather is positive or 
negative to mental performance, and how the weather influences the symptoms 
of certain chronic diseases like asthma, rheumatics, migraine etc. The 
pollen forecast is important to people suffering from allergies. Anyway, 
the word "biometerology" is known in English, too.

So there is a new module. It gets the biowetter and pollen forecasts from 
the German Weather Service DWD and provides observation types containing 
the actual values as well as HTML tables for including in skins.

See here  
for 
an example.

For the future I plan to replace the risk description texts by symbols that 
are easier to recognize. 

Along with this update I made some changes to increase thread safety and to 
replace old files by new ones in an atomic way. This is, because during 
testing I experienced some freezing of the report thread, and I did not 
know the reason. So I assumed there could be some kind of race condition.

-- 
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/b337b20b-eb1b-4bcc-9303-3152f7f5c7bbn%40googlegroups.com.

Re: [weewx-user] Re: windRun charts?

[Karen K]

The keywords for graphs.conf differ a little bin from those in weewx.conf. 
The plot type is "type" only. "yscale" is not available. Use "yAxis_min", 
"yAxis_max", and "yAxis_tickinterval" instead. "windrun" must be included 
in the database. If not, use "weectl database" to insert it.

vince schrieb am Dienstag, 4. Juni 2024 um 20:51:13 UTC+2:

> FWIW, this seems to generate the same high peak for the year that matches 
> Belchertown's records page for the year, although I'm at a bit of a loss 
> regarding .
>
> See if this works for you in your [year] section of graphs.conf
>
>  [[yearwindrun]]
>title = Wind Run
>yscale = None, None, 0.02
>plot_type = bar
>[[[windrun]]]
>   aggregate_type = sum
>   aggregate_interval = 86400
>
> If you want to generate a similar graph in cheetah for a normal 
> (non-highcharts) skin, just add one level of [ ] around the example above 
> and stick it in skin.conf
>
> I'm terrible at tweaking cheetah vs. highcharts graphs so I don't have a 
> good solution if you want stuff in your week or month graphs.   Basically 
> you want the sum of the windrun for a day.
>
> On Tuesday, June 4, 2024 at 9:58:29 AM UTC-7 vince wrote:
>
>> You give up quickly.  If windrun is in your db and your Belchertown 
>> 'records' page, you just need to find the right incantation to graph it 
>> however you want.
>>
>> First check your db to be sure
>>
>> My VP2 data from the archive table
>>
>> sqlite> select datetime(dateTime,'unixepoch','localtime'),windrun from 
>> archive order by rowid desc limit 5;
>> 2024-06-04 09:40:00|0.5
>> 2024-06-04 09:35:00|0.583
>> 2024-06-04 09:30:00|0.5
>> 2024-06-04 09:25:00|0.5
>> 2024-06-04 09:20:00|0.333
>>
>> or from the day summary table
>>
>> select 
>> datetime(dateTime,'unixepoch','localtime'),dateTime,min,max,sum,wsum from 
>> archive_day_windrun order by rowid desc limit 10;
>>
>> sqlite> select datetime(dateTime,'unixepoch','localtime'),sum,wsum from 
>> archive_day_windrun order by rowid desc limit 5;
>> 2024-06-04 00:00:00|29.75|8925.0
>> 2024-06-03 00:00:00|117.0|35100.0
>> 2024-06-02 00:00:00|60.25|18075.0
>> 2024-06-01 00:00:00|25.16667|7550.0
>> 2024-05-31 00:00:00|37.7|11300.0
>>
>> (the last few days have been very windy here and it's only 9am)
>>
>> and the Belchertown skin 'Records' page should show your yearly and 
>> alltime record totals for a day
>>
>> Highest Daily Wind Run188.83 milesJanuary 9, 2024228.67 milesNovember 
>> 15, 2021
>>
>>
>>

-- 
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/980909c5-17c0-4990-97de-5f1d8e2a8110n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

@Jacques: I now added your extension to the configuration. The calculated 
values will be stored to the database. After some time I will publish the 
readings here.

-- 
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/d7e70130-6712-4bdb-84ee-fb016dcaaea3n%40googlegroups.com.

Re: [weewx-user] Wlink doesn't run

[Karen K]

Justin Wenk schrieb am Samstag, 18. Mai 2024 um 21:25:35 UTC+2:

short update: I have now finally installed this extension 
https://github.com/WernerKr/davisconsoleapi. Now runs stable via the 
weatherlink.com API V2. API V1 is not supported by the Davis console 6313 - 
that's why it didn't work with the other extension.


Thank you for this update. I added Werner Krenn's driver to the german 
summary of WeeWX.

-- 
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/96d3c94b-784c-457d-9530-324a329265a1n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Karen K]

Gábor Szabados schrieb am Freitag, 17. Mai 2024 um 16:51:21 UTC+2:

Where did you get those values from?



   - https://www.netzfrequenz.info/aktuelle-netzfrequenz-full
   - https://www.mainsfrequency.com
   -  https://www.udo-leuschner.de/basiswissen/SB124-04.htm (german only)

Before 1990, within the eastern european grid, the tolerance was much 
higher. I don't remember the exact value, but in the GDR the mains 
frequency was always considerably below 50.0 Hz. In Germany we also have 
VDE standards. They sometimes differ from EN.

-- 
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/ec4570fc-e478-4f69-80ea-9742cd1acfa1n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Karen K]

michael.k...@gmx.at schrieb am Donnerstag, 16. Mai 2024 um 18:57:09 UTC+2:

Gauß would connect to your power grid :D


You know what Churchill said about statistics?

If I do the histogram with 3 decimals as Cameron did I get the maximum at 
49.997 Hz. That is almost the same what Cameron got.

And if you consider those readings there is a drift of about 0.1 seconds 
per day in mains frequency. So an astronomer would laugh about that low 
accuracy. ;-)

-- 
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/d2ac3667-15dc-483d-ab8f-95ff90788eb9n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Karen K]

Gábor Szabados schrieb am Freitag, 17. Mai 2024 um 14:46:55 UTC+2:

As I remember the EU specs is 50Hz +/-1%, so all those look good to me.


No. The tolerance is much smaller. +-0.02 Hz (0.04%) is the normal 
operation range. Up to +-0.2 Hz (0.4%) the European electicity 
administration uses standardized and automated processes to stabilize the 
frequency. Outside that range the situation is considered dangerous. Real 
people get involved. Below 49 Hz they start switching off load. Above 50.2 
Hz private photovolatics inverters start reducing power output.
 

-- 
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/56185fef-3051-4370-9d19-7b2afabe5ac1n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Karen K]

michael.k...@gmx.at schrieb am Donnerstag, 16. Mai 2024 um 15:46:28 UTC+2:

Since the (public) power grid is part of the hardware your local weewx 
installation is running on, this is far from being off-topic. 


There are 3 types of UPS available: off-line, stand-by, and on-line. The 
first one is off as long as grid power is available and starts when the 
grid power goes off. The second one is similar, but it is in stand-by. So 
it start faster than the first one. The on-line one separates the grid and 
the output entirely. They are connected by DC only. So this type can 
additionally filter surges etc. The output frequency for the on-line type 
only depends on the internal circuit, while for the off-line and stand-by 
type the output frequency is always the same as the grid frequency.

I use an on-line UPS and hope that will result in less damage in case of 
over-voltage, surges, and lightning strokes.

To compare to Cameron's histogram I did one myself, based on 5 minutes 
averages of the grid frequency (NOT the UPS output frequency):

[image: netzfrequenzhistogramm.png]

This one has the peak at 50.00 Hz.

-- 
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/78c65e41-5ac1-4e13-9644-e46beb078147n%40googlegroups.com.

Re: [weewx-user] Wlink doesn't run

[Karen K]

If the PC running WeeWX and the Weatherlink device is on the same network, 
you could try to retrieve data directly from the device instead of fetching 
it from weatherlink.com. You may want to try the WeatherLinkLiveUDP driver 
 for this. Or if you 
have a paid account with weatherlink.com you could try WLLDriver 
.

John Kline schrieb am Donnerstag, 16. Mai 2024 um 01:25:06 UTC+2:

> It looks like there is a 3 year old PR that Matthew never merged to port 
> it to Python 3.
>
> Justin, you might try:
> [image: weewx-wlink.png]
>
> sshambar/weewx-wlink at work 
> 
> github.com 
> 
>
> Note: I have not tried it myself.
>
> On May 15, 2024, at 3:32 PM, Tom Keffer  wrote:
>
> 
>
> It looks like the wlink extension was never ported to Python 3.
>
> On Wed, May 15, 2024 at 3:35 AM Justin Wenk  wrote:
>
>> Hi everyone! I have the following problem: I want to use the “Wlink” 
>> extension (https://github.com/weewx/weewx/wiki/wlink). I followed the 
>> instructions but I always get an error. I use WeeWX on macOS (Sonoma 
>> 14.13.1).
>>
>> *Log:*
>>
>> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Initializing weewxd 
>> version 5.0.2
>> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Command line: 
>> /Users/justin/weewx-venv/bin/weewxd
>> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Using Python 3.12.3 
>> (v3.12.3:f6650f9ad7, Apr  9 2024, 08:18:47) [Clang 13.0.0 
>> (clang-1300.0.29.30)]
>> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Located at 
>> /Users/justin/weewx-venv/bin/python3
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Platform 
>> macOS-14.3.1-arm64-arm-64bit
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Locale: 'de_DE.UTF-8'
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Entry path: 
>> /Users/justin/weewx-venv/lib/python3.12/site-packages/weewxd.py
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: WEEWX_ROOT: 
>> /Users/justin/weewx-data
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Configuration file: 
>> /Users/justin/weewx-data/weewx.conf
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: User module: 
>> /Users/justin/weewx-data/bin/user
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Debug: 1
>> 2024-05-15 12:01:33 weewxd[2676]: DEBUG weewxd: Initializing engine
>> 2024-05-15 12:01:33 weewxd[2676]: INFO weewx.engine: Loading station type 
>> WeatherLink (user.wlink)
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: Caught unrecoverable 
>> exception:
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   multiple 
>> exception types must be parenthesized (wlink.py, line 180)
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   Traceback 
>> (most recent call last):
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File 
>> "/Users/justin/weewx-venv/lib/python3.12/site-packages/weewxd.py", line 
>> 160, in main
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   engine = 
>> weewx.engine.StdEngine(config_dict)
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:    
>> ^^^
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File 
>> "/Users/justin/weewx-venv/lib/python3.12/site-packages/weewx/engine.py", 
>> line 77, in __init__
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:  
>>  self.setupStation(config_dict)
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File 
>> "/Users/justin/weewx-venv/lib/python3.12/site-packages/weewx/engine.py", 
>> line 104, in setupStation
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:  
>>  __import__(driver)
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File 
>> "/Users/justin/weewx-data/bin/user/wlink.py", line 180
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   except 
>> (urllib2.URLError, socket.error,
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:  
>> ^
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   SyntaxError: 
>> multiple exception types must be parenthesized
>>
>> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   Exiting.
>>
>>
>>
>>
>>
>>
>>
>> 
>> Wlink.py is located in the /weewx-data/bin/user folder.
>>
>> *A part from the weewx.conf:*
>>
>>
>> ##
>>
>> #   This section is for information about the station.
>>
>> [Station]
>> 
>> # Description of the station location, such as your town.
>> location = HalleWetter
>>

Re: [weewx-user] Sunshine Duration

[Karen K]

Oh, that are very interesting data. 

Jacques Terrettaz schrieb am Montag, 13. Mai 2024 um 18:36:27 UTC+2:

Globally  the data derived from the formula give a higher sunshine 
duration.  


We cannot expect to get the same values from that different measurement 
principles, I guess. Nevertheless, I find it useful to compare and to 
discuss about it.
 

But  I am not sure if your sunshine duration sensor is located at the same 
place or near the Davis radiation sensor . If it is not the case , any 
comparison will be useless !


No, it is not at same place. The Davis weather station (and with it the 
radiation sensor) is located at 2 meters above the ground, as the rules 
say. There is some shadow from a tree at about 15:00 o'clock in winter. The 
sunshine duration sensor is mounted on a mast at about 10 meters above the 
ground (near the wind sensor). No shadow is around there.
 

You can "browse" your data here , with the "ticks" calculates bye the 
formula :  http://meteo-sciez.fr/site/graph_frame_karen.php  and by 
choosing the date of interest, and clicking at  the legend of each series 
to show  or hide .


I will have a look at it. 
 
I guess, we should validate the measurements by checking sunshine manually 
at different points of the day and the sunshine condition. Actually the sky 
is blue, and no cloud is to be seen. So we have to wait for clouds to get 
some useful data.

-- 
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/6444183f-adac-4e54-aba3-66f176ed9d52n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

Jacques Terrettaz schrieb am Montag, 13. Mai 2024 um 09:29:49 UTC+2:

.. only one estimation for a 5 min period, based of the archive radiation 
measurement , which is the mean radiation measured over of archive period .


Unfortunately I cannot provide the raw sensor readings. We do not save 
them. We do only save the mean over the archive interval.

-- 
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/6889d2d1-739a-43e0-a0b0-5ade06443a96n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

jterr...@gmail.com schrieb am Freitag, 10. Mai 2024 um 20:35:20 UTC+2:

One more question : in your csv file,  the maximum values of the sunshine 
duration measured by the Weerhuisje/Instromet sunshine duration sensor , 
for a period of 5 minutes, are 324 seconds , higher than the 300 seconds 
interval. 
How should we interpret all these values ? Scale them proportionally so 
that a value of 324 correspond to a 300 second sunshine ?


The sensor sends a pulse every 36 seconds if the sun shines. 8 pulses are 
288 seconds, 9 pulses are 324 seconds. If the sun shines continuously, 
sometimes you get 8 pulses within one archive interval and sometimes 9. 
That is the reason for those values. So you may add those additional 24 
seconds to the previous or next archive interval.

-- 
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/7eac2de9-d869-451e-b76d-630c9170d955n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

jterr...@gmail.com schrieb am Freitag, 10. Mai 2024 um 19:49:06 UTC+2:

Karen, thanks. 
I will do the calculation, and let you know. It will be interesting to have 
a comparison , but I need some more information , particularly the 
 latitude and longitude of the place where your sensors are installed. I 
will send you a private email .


I included the actual solar altitude in the file. So you can use it within 
the calculation.

-- 
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/71e6d7cc-968b-476f-b278-d5dc79b9cab9n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

Jacques Terrettaz schrieb am Dienstag, 7. Mai 2024 um 13:07:08 UTC+2:

The term "sunshine" and  "sunshine duration" is the one used by  WMO - see 
https://library.wmo.int/viewer/68695/?offset=#page=331&viewer=picture&o=bookmark&n=0&q=
 .


And this link reads: "According to WMO (2010), sunshine duration during a 
given period is defined as the sum of the time for which the *direct* solar 
irradiance exceeds 120 W/m^2." 

Note the word "*direct*".

The sensor, most private weather stations use, measures the global 
irradiance, that is from the sun as well as from the sky. So there the 
threshold of 120 W/m^2 does not apply. Nevertheless, people use it that way.

The pyrheliometer can measure the direct solar irradiance, only. And I 
hope, that shadow device can be (and is) calibrated precisely enough.

-- 
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/01c77bd6-2e7b-450c-99e9-e53468f58030n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

Ton vanN schrieb am Dienstag, 7. Mai 2024 um 11:02:33 UTC+2:

Rereading this thread come to understand that definition/semantics is a 
critical aspect in this discussion.
*Bluntly* summarized:
- Sunshine = seeing difference between lighted area and shadowed area.
Like KarenK's device is doing
- Lightlevel = level of undirected solar radiation, not/hardly 
differentating on wavelength.
Like most light sensors in 'private' PWSes will provide.


There is a third device, the pyrheliometer 
. It is mounted on a solar 
tracker . See also direct 
insolation  (please note 
the character o in the middle of the word, not u).

I am not sure, if "lightlevel" is the appropriate name for that kind of 
observation type. See global tilted irradiance (GTI) 
.
 

-- 
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/0e06da8c-81a0-414f-a39c-c213f703b830n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

n7uv...@gmail.com schrieb am Samstag, 4. Mai 2024 um 05:12:04 UTC+2:


What is "direct solar irradiance"? Is there someone at the sensor deciding 
that it's direct? 


As Jaques wrote, this is a sensor that sees a very small angle of the sky 
(approximately half a degree) and it is moving and always looking at the 
position, where the sun should be seen.

-- 
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/90a7111c-d9b9-4853-bf47-1c26e419ac37n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

Hi Jon,

I am not sure I know which paper you referenced, but I agree with you that 
the 120 w/m^2 threshold is a little bit arbitrary. To my experience, in a 
sunny morning the radiation is less than those 120 w/m^2. Unfortunately, 
instruments that can really distinguish between the direct sun light and 
the diffusive radiation from the sky are very expensive. Most people only 
have a general radiation sensor, which cannot know whether the sun is 
shining or the sky is bright. Light is light. You cannot fill in the lack 
of information by calculation.

After considering this all I bought a sunshine duration sensor from 
Instromet <https://instromet.co.uk/sun-duration-sensor/>. This device is 
expensive, too, but still achievable to normal people. It uses a shadow 
bar. If the radiation differs between before and behind the bar, this is 
considered sunshine. A well-defined shadow is not necessary here.

Karen


n7uv...@gmail.com schrieb am Freitag, 3. Mai 2024 um 01:23:52 UTC+2:

> Hi Karen -
>
> I went and read the paper that is referenced for the sunshine duration 
> method. It describes an empirical approach to estimating whether or not the 
> sun is "shining". To me, as you suggest, if I have a crisp, well-defined 
> shadow, then there is indeed a 6000 K point source in the sky. If I meausre 
> in a low humidity, low atmospheric turbidity environment, with low 
> atmospheric particulate count, that shadow should indeed be crisp and well 
> defined. If I measure in a location where the sun is clearly above the 
> horizon, but the shadow is less well defined due to those confounding 
> factors and others, I can still assert that it is sunny, yet it is a degree 
> less sunny than at the former location. 
>
> If one looks at brewster76/
>
>- util-archer <https://github.com/brewster76/util-archer/tree/master>
>- /user <https://github.com/brewster76/util-archer/tree/master/user>
>
> /radiationhours.py 
>
>
> there is an arbitrary value (to be inserted by the user) on what 
> constitutes full sunlight. 
>
> _
> Adds a new observation field to weewx: [sunshine_hours]
>
> If the radiation observed during an interval of time exceeds 120 W/m2, 
> then the interval is considered sunny,
> and [sunshine_hours] is set the length of the time interval.
>
> When [sunshine_hours] is summed over a day, the result is the number of 
> hours during the day when radiation
> exceeded 120 W/m2, or 'hours of sunshine'.
>
> The threshold of 120 W/m2 can be overwritten in weewx.conf:
>
> [RadiationDays]
> min_sunshine = 120
> ___
>
> so, for Brewster76, 120 w/m^2 is the threshold. This is more or less 
> consistent with the original paper, which attempts to get the necessary 
> fudge factors on atmospheric clarity via long--term empirical observations 
> vs the theoretical value for the insolation at that minute at that 
> location. It by no means is a measure of the shadow, or just how crisp it 
> might be.
>
> Various places in the USA all claim to have the most sunshine. I always 
> wondered how they measured that, and what constituted sunshine. If indeed 
> it is via models like what is presented in the paper and the subsequent 
> code examples, it is just a marketing term.
>
> If there is a measuring device, I call it the umbrameter, that can 
> actually measure the depth of shadow cast, and quantitatively show that 
> indeed it is a sunny minute, that would be a cool instrument. I think a 
> quality video camera or other 2D sensor could inspect the image of the sun 
> and, through sufficient training, could say that "this image is within x% 
> of the expected image of the sun taken above the atmosphere, that would be 
> a useful instrument.
>
> Sunny days and sunshine duration appear to be a matter of opinion.
>
> Cheers - Jon N7UV
> On Thursday, May 2, 2024 at 12:03:15 AM UTC-7 Karen K wrote:
>
>> n7uv...@gmail.com schrieb am Donnerstag, 2. Mai 2024 um 01:01:52 UTC+2:
>>
>> When I hear "sunshine duration", I'm not sure whether that means the 
>> duration that the scary fiery (I live in PHX %^) ball of plasma is at and 
>> above the horizon (which is already provided under the Celestial tab) 
>> [image: Screenshot 2024-05-01 155959.png]
>> or something about the total energy delivered to a square meter of the 
>> ground over the period of a day. 
>>
>>
>> Sunshine duration means the time the sun is really seen in the sky and 
>> typically casts a shadow. The standard instrument to measure sunshine 
>> duration is the Campbell-Stokes sunshine recorder 
>> <https://en.wikiped

Re: [weewx-user] Sunshine Duration

[Karen K]

n7uv...@gmail.com schrieb am Donnerstag, 2. Mai 2024 um 01:01:52 UTC+2:

When I hear "sunshine duration", I'm not sure whether that means the 
duration that the scary fiery (I live in PHX %^) ball of plasma is at and 
above the horizon (which is already provided under the Celestial tab) 
[image: Screenshot 2024-05-01 155959.png]
or something about the total energy delivered to a square meter of the 
ground over the period of a day. 


Sunshine duration means the time the sun is really seen in the sky and 
typically casts a shadow. The standard instrument to measure sunshine 
duration is the Campbell-Stokes sunshine recorder 
. 

Sunshine duration is *not* total daylight time.

If a cloud is situated before the sun, this is considered no sunshine. If 
clouds are elsewhere in the sky it does not matter.

-- 
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/a10c6bba-0a86-4b66-a11e-3e6597ceaf1cn%40googlegroups.com.

[weewx-user] Re: Can not find: wee_device

[Karen K]

christian@gmail.com schrieb am Montag, 22. April 2024 um 12:53:58 UTC+2:

Now I have the problem that I can't find wee_device in the system. I 
searched the whole system but I couldn't find wee_device.
What can I do there?


http://weewx.com/docs/5.0/utilities/weectl-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/10d67580-c0e7-4035-bd25-3b10fd000c91n%40googlegroups.com.

Re: [weewx-user] change locale for html.tmpl with weewx 5.0.2

[Karen K]

Juan Antonio Mosquera Casais schrieb am Freitag, 12. April 2024 um 07:03:31 
UTC+2:

Oh... works... but, show units, i can delete units??


Replace .formatted by .format(add_label=False)
 

-- 
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/1e3eda68-4d8b-4da3-adb7-71ae06351c89n%40googlegroups.com.

[weewx-user] Re: "outHumAbs" in microgramms per cube meter on Station info on Belchertown Skin.

[Karen K]

mh081...@gmail.com schrieb am Donnerstag, 14. März 2024 um 09:53:53 UTC+1:

Can anybody, who already changed this, share his config?


In graphs.conf I use it like this:

[[humidity]]

title = "Luftfeuchtigkeit"

[[[outHumidity]]]

name = "relativ"

[[[outHumAbs]]]

name = "absolut"

yAxis = 1

unit = gram_per_meter_cubed

numberFormat

decimals = 1

For the current readings at the home page it is more difficult. If you want 
to show relative and absolute humidity in one line you have add some lines 
into belchertown.py:

*if* obs=='outHumidity':

humabs_output = getattr(current,'outHumAbs',*None*)

*if* humabs_output *is* *not* *None*:

humabs_output = humabs_output.gram_per_meter_cubed

station_obs_html += "  "

station_obs_html += '%s' % humabs_output

I added it before the lines

station_obs_html += ""

station_obs_html += ""

In the MQTT configuration in weewx.conf you need to add

outHumAbs

units = gram_per_meter_cubed

in section [[[inputs]]].

I am not sure if that were all changes.








-- 
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/cea2d009-3296-4df9-9092-98566754n%40googlegroups.com.

Re: [weewx-user] Fahrenheit instead of celsius in weewx.sdb? / csv export: wrong datetime format

[Karen K]

I would suggest to use the SQL statement 

select datetime(`dateTime`,'unixepoch','localtime'),* from archive;

to extract the data out of the database. Please note the different quotes. 


-- 
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/4b8a27a4-16b4-4dd5-afb4-1370b8e49a76n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

It turned out that this thread was only a step on the way for me. I ended 
up writing an issue (#939)  after 
all.

-- 
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/ec559475-7e09-46f9-a786-ec50e619f1dbn%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

I guess PR #929 is an entirely different topic.

It seams to me, that the if condition in 
weewx.tags.ObservationBinder.has_data is useless, because what happens 
afterwards is almost the same in both cases. 

May be, the intension for that function was like that really:

@property
def has_data(self):
db_manager = self.db_lookup(self.data_binding)
# First see if the type exists in the database.
if db_manager.exists(self.obs_type):
# Yes. Is it non-null?
val = bool(db_manager.has_data(self.obs_type, self.timespan))
else:
# Nope. Try the xtypes system.
val = weewx.xtypes.has_data(self.obs_type, self.timespan, 
db_manager)
return val

See the changed line with yellow background. There could be a connection to 
the performance issues some people experience I guess. Unfortunately I 
still have no 5.0 installation working to do tests. 

-- 
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/0cddb249-fefb-4179-84c3-d9fff8e70bc6n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Ah.

Tom Keffer schrieb am Samstag, 24. Februar 2024 um 00:00:07 UTC+1:

You should not have to implement either.


For WeeWX 5.0 people experienced that the "GTS", "yearGDD", and "seasonGDD" 
observation types (XTypes calculated out of "outTemp") were not graphed any 
more. After an explicit implementation of "not_null" the graph appeared 
again.

   - https://github.com/roe-dl/weewx-GTS/issues/26
   - https://github.com/roe-dl/weewx-GTS/blob/master/bin/user/GTS.py
   
tags.ObservationBinder.has_data has changed from WeeWX 4.X to 5.0. The old 
version only looked into the database by calling 
self.db_lookup(self.data_binding).has_data(self.obs_type, 
self.timespan). The new version is:

@property
def has_data(self):
db_manager = self.db_lookup(self.data_binding)
# First see if the type exists in the database.
if db_manager.exists(self.obs_type):
# Yes. Is it non-null?
val = bool(weewx.xtypes.get_aggregate(self.obs_type, 
self.timespan,
  'not_null', 
db_manager)[0])
else:
# Nope. Try the xtypes system.
val = weewx.xtypes.has_data(self.obs_type, self.timespan, 
db_manager)
return val

If you look into weewx.xtypes.get_aggregate(...,'not_null',...) and 
weewx.xtypes.has_data() they do almost the same. There is a loop over xtypes, 
and for each xtype get_aggreate() is called. If I understand the code 
right, the result of the has_data property in WeeWX 5.0 is independent of 
the value of the condition of the if statement. And the database lookup, 
that is used in WeeWX 4.X, has gone at all.

-- 
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/e5010568-d6cd-4297-a608-89d1dee91bf0n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Ah.

Tom Keffer schrieb am Samstag, 24. Februar 2024 um 00:00:07 UTC+1:

You should not have to implement either.


For WeeWX 5.0 people experienced that the "GTS", "yearGDD", and "seasonGDD" 
observation types (XTypes calculated out of "outTemp")  were not graphed 
any more. After an explicit implementation of "not_null" the graph appeared 
again. 

https://github.com/roe-dl/weewx-GTS/issues/26

https://github.com/roe-dl/weewx-GTS/blob/master/bin/user/GTS.py




-- 
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/270bcad8-5fce-4356-a921-33ac77d9dc42n%40googlegroups.com.

[weewx-user] Re: Seeking Data Logging Options

[Karen K]

What do you mean by "logging"? WeeWX, as it is shipped, stores the readings 
to a database. You can then take that database and do what you have to do 
with it. If you use the default settings, that database is a SQLITE file, 
which can be read and processed by a lot of other software.

-- 
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/2b53f2ff-2615-4c2f-8e1e-02ca8e05e745n%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Do I have to implement both the not_null and has_data aggregation in an 
XType extension?


Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:

The aggregation not_null does not check first to see if the type exists. If 
you know the type exists, it's slightly faster. 

In practice, I don't think it's very useful. I may remove it from the 
documentation.

On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:

What is the difference between the aggregation types has_data and not_null 
according to the documentation in 
http://weewx.com/docs/5.0/reference/aggtypes/.

-- 
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/8abfecfb-7fe5-4e6c-aace-540ed933ea8en%40googlegroups.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

Thank you.

Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:

> The aggregation not_null does not check first to see if the type exists. 
> If you know the type exists, it's slightly faster. 
>
> In practice, I don't think it's very useful. I may remove it from the 
> documentation.
>
> On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:
>
>> What is the difference between the aggregation types has_data and 
>> not_null according to the documentation in 
>> http://weewx.com/docs/5.0/reference/aggtypes/. 
>>
>> -- 
>> 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/3eef09c7-c2fe-49a2-9e89-f1957c731a54n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/3eef09c7-c2fe-49a2-9e89-f1957c731a54n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/92bba5f3-93ed-4d16-963e-06e520c606c1n%40googlegroups.com.

[weewx-user] Difference between aggregation types has_data and not_null

[Karen K]

What is the difference between the aggregation types has_data and not_null 
according to the documentation 
in http://weewx.com/docs/5.0/reference/aggtypes/.

-- 
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/3eef09c7-c2fe-49a2-9e89-f1957c731a54n%40googlegroups.com.

[weewx-user] Alltime Statistics

[Karen K]

I just read a post about slow skin creation in a german weather forum. This 
made me think about something. There were threads about the same topic here.

Sometime the DaySummaryManager was introduced. And I guess the reason was 
to speed up aggregations. Instead of 288 records a day one record had to be 
read only. This can make the difference for large databases.

Now if I think of a database of 10, 20 or more years. And I want to see 
some alltime statistics. Even the day summary table is large in those 
cases. 

So I wonder if it would help to have a year summary table, too.

-- 
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/31290546-1043-4bda-8aac-646e9dd74c88n%40googlegroups.com.

[weewx-user] Re: Can we upgrade to WeeWX 5.0x WITHOUT MAJOR RISK?

[Karen K]

I would suggest creating a backup first. Backups are always a good idea, 
independent of what you want to do. You will surely beat yourself if you 
have not created it. This includes a whole copy of the hard disk.

-- 
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/88344a99-a1d0-4638-8be3-e1195e648ea3n%40googlegroups.com.

[weewx-user] Re: SOLVED as3935 lightining module not detected by I2c on a Rpi4

[Karen K]

May be you want to try option -a:

sudo i2cdetect -a -y 1

Adresses below 0x8 are reserved at Raspberry Pi 4. But the lightning module 
can address 0x0, 0x1, 0x2, or 0x3 only.

-- 
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/693d7c1a-7862-4e6a-8c33-50601df302adn%40googlegroups.com.

[weewx-user] Re: SOLVED as3935 lightining module not detected by I2c on a Rpi4

[Karen K]

May be, you want to try option -a:

sudo i2cdetect -a -y 1 

-- 
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/a26ea589-fb86-414e-bfdb-defd66d25873n%40googlegroups.com.

[weewx-user] Re: Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Karen K]

WeeWX 4.* runs as root. WeeWX 5.* does not run as root. As you write the 
permissions of /dev/ttyAMA0 are user root and group dialout. You may 
include the user weewx into group dialout or follow the instructions Tom 
and Matthew gave in several of the previous threads regarding this issue.

Mark Conner schrieb am Dienstag, 6. Februar 2024 um 20:45:35 UTC+1:

> Hi,
>
> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my 
> Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start 
> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a 
> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to 
> 5.0.0 and still have the same issue.  Here are the weewxd related lines 
> from startup from /var/log/syslog: 
>
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing 
>> weewxd version 5.0.0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python 
>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at 
>> /usr/bin/python3
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform 
>> Linux-6.1.21-v7+-armv7l-with-glibc2.31
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale: 
>> 'en_US'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Configuration 
>> file: /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import 
>> of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13] 
>> Permission denied: '/dev/ttyAMA0' (> 'serial.serialutil.SerialException'>)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File 
>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322, 
>> in open
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | 
>> os.O_NONBLOCK)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   During handling of the above exception, another exception occurred:
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in 
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in 
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.port.openPort()
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in 
>> openPort
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.serial_port = serial.Serial(self.port, self.baudrate, 
>> timeout=self.timeout)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/local/lib/python3.9/dist-packages/serial/serialutil.py", 
>> line 2

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

michael.k...@gmx.at schrieb am Freitag, 12. Januar 2024 um 20:04:50 UTC+1:

Würde das auch gerne als Option für den Bootstrap Skin übernehmen.


@Michael: Wenn das dann umgesetzt ist, könnte ich einen Link setzen, daß 
die Leute sehen, daß sie da eine Skin installieren können, die das nutzt.
 

-- 
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/9bd9960e-7e8c-4435-9670-028f7ea6af97n%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

English version below.

Es gibt zu diesem Thema noch etwas Neues: eine 
Kurzfrist-Niederschlagsvorhersage. Da kann man  für die nächsten 2 Stunden 
im 5-Minuten-Abstand erfahren, ob man einen Platzregen zu gewärtigen hat. 
Die Radardaten des Deutschen Wetterdienstes enthalten eine solche 
Vorhersage (siehe die animierte GIF-Datei weiter oben). Hier kann man sie 
nun für einen beliebigen Ort herausziehen und als Tabelle oder sonst 
irgendwie darstellen, was die Kreativität beim Schreiben von Skin-Templates 
hergibt. Eine bloße Tabelle ist recht einfach:



#*set* $forecast = $day.radarRVRainRateForecast.series

#for $i *in* $forecast



$i[0]$i[1]$i[2]



#end for



Der Zeitraum (hier $day) ist dabei egal. Es wird immer die ganze Vorhersage 
zurückgeliefert. Man kann auch ein Template schreiben, das eine JSON-Datei 
daraus erzeugt, die dann von HighCharts in eine Graphik verwandelt wird. 
Voraussetzung, daß die Vorhersage abgerufen werden kann, ist, daß für den 
betreffenden Ort eine Abfrage des aktuellen Wertes konfiguriert ist. d.h. 
um radarRVRainRateForecast zu haben, muß es radarRVRainRate geben. Im 
Moment eignet sich das Wetter leider nur wenig zum Testen dieser 
Funktionalität, aber warten wir auf das nächste Tiefdruckgebiet.

Abgedeckt werden Deutschland, Luxemburg, die österreichischen Bundesländer 
Tirol (teilweise) und Vorarlberg sowie Nordwesttschechien. Die Genauigkeit 
wird durch das Raster von 1 km begrenzt.



Included in their radar data products the German Weather Service DWD 
provides a short time forecast of precipitation intensity with 5 minutes 
interval. This extension extracts those forecasts for locations specified 
by the user in the weewx.conf configuration file. So you can see if you may 
face a rain of cats and dogs at your station within the next 2 hours or 
something. The service covers Germany, Lëtzebuerg, Austrian states Tirol 
(parts of) and Vorarlberg as well as the north west of Czechia including 
Praha. The accuracy is limited by the 1 km grid.

It is simple to display the forecast as a table:



#*set* $forecast = $day.radarRVRainRateForecast.series

#for $i *in* $forecast



$i[0]$i[1]$i[2]



#end for



The timespan (here: $day) is irrelevant. You always get the whole forecast.

Unfortunately there is no chance to test this functionality now. You will 
have to wait for the next cyclone.

-- 
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/832fb8cb-1e1d-42d0-97f9-975f7190ff39n%40googlegroups.com.

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

[Karen K]

@Tom: May be, you want to have a look into the belchertown.py file. It 
contains a lot of SQL queries, that do not use the normal way to access the 
WeeWX database. They are used to get several alltime statistics and other 
aggregations. Could there be some reason?

-- 
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/bbb39ec1-5663-4c39-856d-94d3b43ed650n%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

Noch kommt hier relativ schnell etwas hinzu. Kartenausschnitte zeigten die 
Ortsnamen ziemlich pixelig. Das hat sich jetzt verbessert. Es werden auch 
mehr Orte angezeigt, wenn der Ausschnitt kleiner ist. Damit man die Grenzen 
nicht so mühsam in Pixeln heraussuchen muß, kann man jetzt beim Schlüssel "
map" anstelle der vier Zahlen auch ein Bundesland im ISO3166-2-Code 
angeben, z.B. "DE-MV" für Mecklenburg-Vorpommern. Bis jetzt funktioniert 
das allerdings nur für die ostdeutschen Bundesländer sowie die 
österreichischen Bundesländer Vorarlberg (AT-8) und Tirol (AT-7). Außerdem 
geht es für das Gebirge Harz ("Harz"), Deutschland im Ganzen ("DE") und - 
für Tests der Skalierung - die ostdeutschen Bundesländer zusammen ("DE-Ost
").

-- 
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/5589bc66-c39c-4bfb-919e-6febe688767fn%40googlegroups.com.

Re: [weewx-user] V5.0.0 available

[Karen K]

Congratulations from me, too. It is a lot of work to design, to discuss, to 
code, and finally to test and find the bugs. 

-- 
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/f046d7ca-d8f6-4bb4-82a6-54fa3de54a4en%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

hesf...@gmail.com schrieb am Sonntag, 14. Januar 2024 um 12:49:44 UTC+1:

und die Datei "radar-HG.png"  wird erzeugt, jedoch ohne die Landegrenzen.


Bitte die Datei countrycoords.txt vorerst hier herunterladen: 
https://www.woellsdorf-wetter.de/dwd/countrycoords.txt

P.S.: Auch "WN" und "RV" sollten inzwischen ein Ergebnis liefern.

-- 
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/e9662ce1-7b99-4a2b-a1f3-81eda23a0716n%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

Und hier haben wir dann Anfänge einer Anleitung 
.

-- 
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/3f16c0b3-b76a-493d-aeab-adf3878be945n%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

Darstellung der Farblegende:

#from user.weatherservicesradar import DwdRadar

...

 #for $idx,$val in $DwdRadar.TEXT['de'].items()

 

 

 $val

 

 #end for

Und in einer CSS-Datei:

*.statusIcon* {

  *width*:14px;

  *height*:14px;

  *display*:inline-block;

  *border*:1px solid #808080;

}

[image: Farblegende.png]

-- 
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/a6c72b4b-e268-4a7a-b3a0-fc14038d321cn%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

michael.k...@gmx.at schrieb am Freitag, 12. Januar 2024 um 20:04:50 UTC+1:

Hört sich nach einem Geniestreich an. Da sich mein Standort in Österreich 
noch in dem Ausschnitt der Karte befindet, melde ich mein Interesse an. 
Würde das auch gerne als Option für den Bootstrap Skin übernehmen.


Das ist skin-unabhängig. Man muß nur weewx-DWD 
 installiert haben. Die Beispiele in 
der Dokumentation beziehen sich teilweise auf die Belchertown-Skin, aber 
man kann "Belchertown" auch durch einen anderen Namen ersetzen.

Als Warnung muß ich noch den Thread "Report thread freezes after weewx.conf 
change " 
voranstellen. Wenn es solche Probleme gibt, muß man die Option "include" 
nutzen. Wenn nicht, kann man die Konfiguration direkt in weewx.conf 
eintragen.

Sämtliche Konfigurationsinformationen für weewx-DWD finden sich im 
Abschnitt "[WeatherServices]". Das gilt auch für die Radardaten. Die 
Konfiguration sieht ungefähr so aus:

[WeatherServices]

path = /etc/weewx/skins/SKINNAME/dwd

...

[[radar]]

[[[Station]]]

provider = DWD

model = HG

easting = replace_me

northing = replace_me

prefix = ""

latitude = replace_me

longitude = replace_me

[[[Karte]]]

provider = DWD

model = HG

prefix = ""

map = 100, 100, 900, 1000

borders = countrycoords.txt

"path" ist der Ort, wohin die Graphikdatei geschrieben werden soll. Das 
kann auch /var/lib/weewx oder irgendwo anders sein. latitude und longitude 
sind, denke ich, klar. Spannend wird es mit easting und northing. Dazu muß 
ich ausholen. Das folgt weiter unten. map gibt die Koordinaten des 
Ausschnitts in Pixeln an, für den die Karte erzeugt werden soll. Die ersten 
beiden Zahlen sind die linke *untere* Ecke, die anderen beiden Breite und 
Höhe. Die Breite kann maximal 1100 sein, die Höhe 1200. prefix ist ein 
Namenspräfix, falls man mehrere Stationen oder mehrere Karten hat.

Deutschland ist hier in ein 1km-Raster eingeteilt. easting (deutsch: 
Rechtswert) und northing (deutsch: Hochwert) sind die Koordinaten innerhalb 
dieses Rasters in Metern. Allerdings ist hier der Koordinatenursprung weit 
außerhalb. Nun ist die Frage, wie man diese Werte bekommt. Da die Erde rund 
ist, kann man ein ebenes Raster nicht einfach so über das Land legen. Man 
braucht eine kartographische Projektion. Dazu gibt der Deutsche 
Wetterdienst an, man soll das Programm "proj" benutzen. Zum Glück gibt es 
das auch für Linux, und man kann es ganz normal mit "apt-get" installieren. 
Der Aufruf ist wie folgt:

echo longitude latitude | proj +proj=stere +lat_0=90 +lat_ts=60 +lon_0=10 
+a=6378137 +b=6356752.3142451802 +no_defs +x_0=543196.83521776402 
+y_0=3622588.8619310018

Bitte aufpassen, die Reihenfolge ist umgekehrt wie üblich.

Als Ergebnis spuckt das Programm die beiden Werte aus, die man als easting 
und northing eintragen muß.

Die Datei countrycoords.txt kann Linien enthalten, die als Grenzen o.ä. in 
die Graphik eingezeichnet werden sollen. Pro Zeile muß ein Koordinatenpaar 
stehen, wieder mit dem Programm "proj" erzeugt, dem man dazu direkt eine 
Liste von geographischen Koordinaten übergeben kann. Anfang und Ende einer 
Linie wird durch eine Zeile mit zwei Sternchen und einem Leerzeichen 
dazwischen gekennzeichnet.

Soweit erst einmal die grobe Übersicht.

-- 
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/97a04787-ae4c-4d1d-a28d-6ca111aa4d58n%40googlegroups.com.

[weewx-user] Report thread freezes after weewx.conf change

[Karen K]

Please note: This is not reproducable. The only question is, if someones 
knows about threading issues in Python, that may produce such behavior. So 
don't ask about the log etc. I explain it below why.

It happened while I wrote an extension.

I added some entries at the end of weewx.conf. They are for the new 
extension, but the extension itself is not loaded (not added to 
data_services so far). After the restart of WeeWX all was working as 
expected, except that no report was created any more. 

The log was identical, except the missing messages about reports. The same 
applies if debug is set to 1.

There was no error message. There was no exception.

If I removed some unused lines from weewx.conf (NOT in section StdReport), 
the reports were created again.

I found out, that the StdReportEngine thread freezes at the beginning of 
the report loop
(statement: enabled = to_bool(self.config_dict['StdReport'][report].get(
'enable', True))).

I did a lot of debugging, and finally I added a logging statement 
(log.info) between every line of code in reportengine.py.

After that all reports were created again. (But lots of messages in syslog 
of course)

So why do I not provide a log excerpt? Unfortunately all this happens in my 
production environment only. The test environment does not show this 
behavior. And I don't want to perform more tests on the production 
environment.

There are a lot of findings at Google about freezing threads in Python, but 
I did not find something appropriate.

So does this description remember someone on something?

(And meanwhile I have to invent some solution to have a smaller weewx.conf. 
It is about 64 KB in size now because of a lot of extensions.)

-- 
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/d09f5799-05fd-45e7-aa4b-29051dfebe97n%40googlegroups.com.

[weewx-user] Re: RS485 Pyranometer and Weewx

[Karen K]

I have got another device that uses an RS485 interface. I use an RS485 to 
LAN converter from W&T . It 
depends on the protocol they use, but may be the MQTTSubscribe 
driver/service  can read 
the data into WeeWX.

-- 
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/d2b4a825-cf62-4ba7-a242-f2faabdf91e3n%40googlegroups.com.

[weewx-user] Belchertown skin: Snapshot section layout and customization issues

[Karen K]

I am not sure, if it is possible to recognize new issues within the 
discussion tab at Github. So I put a link here:

Snapshot section layout and customization issues #921 


There I present a proposal to handle layout issues with the Belchertown 
skin on phones and make the snapshots section customizable.

-- 
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/38bcac51-9b4e-45ad-a011-41448f726dd2n%40googlegroups.com.