from:"David"

That's pretty much exactly what I was looking for Mark! Would you happen to 
have insight or a project build you may have followed?

On Monday, September 18, 2023 at 3:08:00 PM UTC-5 Mark Fraser wrote:

> I used an LCD screen and made this 
> https://www.printables.com/model/499066-hanging-case-for-waveshare-8-display
>
> On Mon, 18 Sept 2023, 18:30 Jeremy David,  wrote:
>
>> I moved into a new home a few months ago and have been wanting to build 
>> my own weather station with a RPi and route it wirelessly to display on 
>> another RPi with an LCD or epaper screen of sorts in my kitchen. I believe 
>> I have gotten away from the idea of building my own weather station because 
>> I was wanting to power it with PoE, but it looks like the HAT that gives 
>> that functionality might not work the best in hotter operating temps on my 
>> roof.
>>
>> So I think I have settled on getting either a Tempest or an Ecowitt and 
>> just route the data to Weewx on a RPi or Arduino with a screen attached. 
>> However, and maybe I am just blind, but I can't seem to find a project 
>> build on making a display screen that could project the data, would someone 
>> happen to have any links to one? I swear I found one weeks ago when I was 
>> looking for something else and can't find it again. I have seen ones that 
>> just run Raspbian and have a browser up with Weewx or running an Android 
>> app on an old tablet, but was hoping for something more plug in and start 
>> up for some of the less tech savvy people in my house.
>>
>> I'm thinking this should be possible, but maybe I'm overestimating?
>>
>> Thank you in advance!
>>
>> -- 
>>
> 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/2912c2f5-76ae-41d7-a531-3f6c39cd4011n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/2912c2f5-76ae-41d7-a531-3f6c39cd4011n%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/5fef6862-1e87-4400-820a-0e00f7950a8en%40googlegroups.com.

Re: [weewx-user] Looking for a DIY Screen/Display Solution

That's the article that I had seen that I was referring to that I couldn't
find again, I know that one doesn't use Weewx, but assume it could be done.

On Monday, September 18, 2023 at 2:54:53 PM UTC-5 Dave Webb KB1PVH wrote:

I'm thinking about doing this project.

https://www.hackster.io/lmarzen/esp32-e-paper-weather-display-a2f444

Dave - KB1PVH

Sent from my Galaxy S21

On Mon, Sep 18, 2023, 1:30 PM Jeremy David <> wrote:

I moved into a new home a few months ago and have been wanting to build my
own weather station with a RPi and route it wirelessly to display on
another RPi with an LCD or epaper screen of sorts in my kitchen. I believe
I have gotten away from the idea of building my own weather station because
I was wanting to power it with PoE, but it looks like the HAT that gives
that functionality might not work the best in hotter operating temps on my
roof.

So I think I have settled on getting either a Tempest or an Ecowitt and
just route the data to Weewx on a RPi or Arduino with a screen attached.
However, and maybe I am just blind, but I can't seem to find a project
build on making a display screen that could project the data, would someone
happen to have any links to one? I swear I found one weeks ago when I was
looking for something else and can't find it again. I have seen ones that
just run Raspbian and have a browser up with Weewx or running an Android
app on an old tablet, but was hoping for something more plug in and start
up for some of the less tech savvy people in my house.

I'm thinking this should be possible, but maybe I'm overestimating?

Thank you in advance!

--
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/2912c2f5-76ae-41d7-a531-3f6c39cd4011n%40googlegroups.com

<https://groups.google.com/d/msgid/weewx-user/2912c2f5-76ae-41d7-a531-3f6c39cd4011n%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/0dc7a413-48ba-4bb3-80ff-2025bdd8879bn%40googlegroups.com.

[weewx-user] Re: Looking for a DIY Screen/Display Solution

Correct, display/project, they are synonymous in my mind. I have an old 
Fire that I could use, and might use in testing phase, I just had my mind 
on more of a project build, but definitely keeping that open. I didn't know 
about FullyKioskBrowser, so that's a big help for if I go that route!

On Monday, September 18, 2023 at 2:28:23 PM UTC-5 vince wrote:

I assume you meant "display" the data, not "project" the data there.

I doubt you can get there cheaper than a Kindle Fire 8" or bigger for $40 
or so if you catch a sale, and run FullyKioskBrowser on it to keep the 
display on for any skin/dashboard you want.   If you go a little bigger in 
the display, the Belchertown skin looks 'really' good for weewx on 
something in the 10" size range.

You can run weewx and the Belchertown skin for a really nice looking 
dashboard the Kindle Fire can display for you.  Works great.

-- 
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/3fcde30d-2d6f-4511-b6d9-d36a646aa580n%40googlegroups.com.

[weewx-user] Re: Looking for a DIY Screen/Display Solution

Correct, display/project, they are synonymous in my mind. I have an old 
Fire that I could use, and might use in testing phase, I just had my mind 
on more of a project build, but definitely keeping that open. I didn't know 
about FullyKioskBrowser, so that's a big help for if I go that route!

On Monday, September 18, 2023 at 2:28:23 PM UTC-5 vince wrote:

> I assume you meant "display" the data, not "project" the data there.
>
> I doubt you can get there cheaper than a Kindle Fire 8" or bigger for $40 
> or so if you catch a sale, and run FullyKioskBrowser on it to keep the 
> display on for any skin/dashboard you want.   If you go a little bigger in 
> the display, the Belchertown skin looks 'really' good for weewx on 
> something in the 10" size range.
>
> You can run weewx and the Belchertown skin for a really nice looking 
> dashboard the Kindle Fire can display for you.  Works great.
>
>

-- 
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/ba5fe94c-86cf-49c3-b6a8-e8539135f33fn%40googlegroups.com.

[weewx-user] Looking for a DIY Screen/Display Solution

I'm thinking this should be possible, but maybe I'm overestimating?

Thank you in advance!

--
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/2912c2f5-76ae-41d7-a531-3f6c39cd4011n%40googlegroups.com.

Re: [weewx-user] Trying to configure the logging to be non-privileged

2023-08-28 Thread David Barto


> On Aug 27, 2023, at 3:51 PM, Tom Keffer  wrote:
> 
> Which version of WeeWX? It's possible your version of WeeWX does not have a 
> rotating logger defined for the Mac.
> 
> Try following the instructions in the wiki article Logging to rotating files 
> <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#logging-to-rotating-files>.
>  
> 
> 

Version 4.10.2, and the link you provided works perfectly. Now running and 
logging to non-root directory.

Yet even with the upgrade to 4.10.2 and to macOS Monterey (12.6.7) I’ve still 
got the stupid certificate error for posting to PWSweather and getting 
Forecasts from the NWS and WU:

2023-08-28 10:13:16  weewx[31551] DEBUG weewx.restx: PWSWeather: Failed upload 
attempt 1: 
2023-08-28 10:13:16  weewx[31551] ERROR user.forecast: WUThread: WU: failed 
attempt 1 to download forecast: 
2023-08-28 10:13:16  weewx[31551] DEBUG weewx.restx: StationRegistry: Failed 
upload attempt 1: HTTP Error 429: TOO MANY REQUESTS
2023-08-28 10:13:16  weewx[31551] ERROR user.forecast: NWSThread: NWS: failed 
attempt 1 to download NWS forecast: 
2023-08-28 10:13:16  weewx[31551] ERROR user.forecast: WUThread: WU: failed 
attempt 2 to download forecast: 
2

It doesn’t tell me the certificate that is out of date however.

So two things:

1 - the document http://weewx.com/docs.html/latest/macos.htm needs to be 
updated to redirect the logging information to the wiki article 
https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#logging-to-rotating-files

2 - How would I figure out which certificate is out of date and needs update 
for the forecast and PWS updates?

David

Do the right thing. It will gratify some people and astonish the rest.
--Mark Twain.
David Barto
ba...@kdbarto.org





-- 
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/19587CAD-2FBE-4310-898F-B81D2452F456%40kdbarto.org.

[weewx-user] Trying to reach Rory Gillies

2023-08-27 Thread David Barto

As he mentioned that he had successfully setup the Forecast extension.

If Rory would get in contact *see sig* I’d appreciate it.

David

Every time I think I've hit the bottom of the stupidity well, someone throws me 
a shovel
David Barto
ba...@kdbarto.org


-- 
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/C88283E2-AE71-4587-A6EF-51234EE169FF%40kdbarto.org.

[weewx-user] Trying to configure the logging to be non-privileged

2023-08-27 Thread David Barto

Following the instructions found in http://weewx.com/docs.html/latest/macos.htm 
under Logging, I added (copy/pasted) the alternative to log to 
/var/tmp/weewx.log and get this error when starting up.

Is it not possible to log to an alternative location?

David

Traceback (most recent call last):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 line 565, in configure
handler = self.configure_handler(handlers[name])
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 line 723, in configure_handler
klass = self.resolve(cname)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 line 383, in resolve
name = s.split('.')
AttributeError: 'NoneType' object has no attribute 'split'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/Shared/weewx/bin/weewxd", line 249, in 
main()
  File "/Users/Shared/weewx/bin/weewxd", line 98, in main
weeutil.logger.setup(options.log_label, config_dict)
  File "/Users/Shared/weewx-4.10.2/bin/weeutil/logger.py", line 139, in setup
logging.config.dictConfig(log_dict)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 line 811, in dictConfig
dictConfigClass(config).configure()
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 line 572, in configure
raise ValueError('Unable to configure handler '
ValueError: Unable to configure handler 'rotate'


Never ascribe to malice that which is adequately explained by incompetence
--Napoleon Bonaparte
David Barto
ba...@kdbarto.org


-- 
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/E5347A3B-8C00-488A-A3A6-314148758F7C%40kdbarto.org.

Re: [weewx-user] Re: WDC Skin

2023-08-27 Thread David Bätge

Hi Mau,

yes, the wiki realy includes a lot of information. I guess you are missing 
the base_path setting, 
see 
https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
 
and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras



Mau Hernandez schrieb am Mittwoch, 23. August 2023 um 01:00:26 UTC+2:

> I just found your Wiki! <https://github.com/Daveiano/weewx-wdc/wiki> Will 
> give that a shot! 
>
> On Tuesday, August 22, 2023 at 3:45:36 PM UTC-7 Mau Hernandez wrote:
>
>> Hi David,
>>
>> New user of WeeWx and found this thread with your Skin which Im trying to 
>> install. I saw above that data might be needed so hopefully that explains 
>> why Im getting a blank page but the Menu's are showing.
>>
>> I used the DEB package to do fresh install in a Debian machine. 
>> Everything was setup and accesible at http://IP/weewx/. When I select 
>> any submenu on the skin I see it goes back to root http://IP/about.html so 
>> I probably missed a sym-link during setup? (http://IP/weewx/about.html 
>> should 
>> be the correct? ) 
>>
>> Thanks for your help
>>
>> [image: Screenshot 2023-08-22 at 3.37.53 PM.png]
>> On Friday, August 18, 2023 at 7:17:21 AM UTC-7 David Bätge wrote:
>>
>>> Great, I will include the change in the next release! 
>>>
>>> gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 13:44:22 
>>> UTC+2:
>>>
>>>> Hi David
>>>>
>>>> I was to fast, it seems to work with the new main.ja.
>>>>
>>>> Thanks for that
>>>>
>>>> Gert
>>>>
>>>> On Friday, August 18, 2023 at 12:44:22 PM UTC+2 gert.a...@gmail.com 
>>>> wrote:
>>>>
>>>>> Hi David
>>>>> Unfortunately, the new main.js, did not solve the problem as you can 
>>>>> see. The WindRose seems fine
>>>>>
>>>>> Rgds
>>>>> Gert
>>>>>
>>>>> On Friday, August 18, 2023 at 12:02:36 PM UTC+2 David Bätge wrote:
>>>>>
>>>>>> You can right-click the link and choose "Save as" or open the file in 
>>>>>> the browser and hit "Strg+S" if on Windows or Linux.
>>>>>>
>>>>>> The problem with this menu is that you can not scroll the sidebar. 
>>>>>> The sidebar should be scrollable so you can access all the items, but 
>>>>>> that's not the case. I added 
>>>>>> https://github.com/Daveiano/weewx-wdc/issues/193 for this, will have 
>>>>>> a look soon!
>>>>>>
>>>>>> gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 07:10:37 
>>>>>> UTC+2:
>>>>>>
>>>>>>>
>>>>>>> Hi David
>>>>>>> Thanks for the prompt answer.
>>>>>>>
>>>>>>> The link you provided will just open the file in the browser. so I'm 
>>>>>>> not able to download the file.
>>>>>>>
>>>>>>> Is it possible to move the the Archive and NOAA Reports Menu to the 
>>>>>>> upper Menu line, besides the Year Menu. As you can see from the 
>>>>>>> screenshot, 
>>>>>>> I can't see the last months of the NOAA report and i's not possible to 
>>>>>>> scroll in the left menu.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Gert
>>>>>>> On Friday, August 18, 2023 at 2:26:37 AM UTC+2 David Bätge wrote:
>>>>>>>
>>>>>>>> I just noticed you are using custom ordinate labels - I just tested 
>>>>>>>> this out and noticed that special characters are not handled properly 
>>>>>>>> in 
>>>>>>>> the legend labels.
>>>>>>>>
>>>>>>>> I made a change to the main.js file, you can download the updated 
>>>>>>>> file here: 
>>>>>>>> https://public-images-social.s3.eu-west-1.amazonaws.com/main.js
>>>>>>>> I tried to attach the file here but the messages were deleted...
>>>>>>>>
>>>>>>>> You need to replace the original file at the skins install location 
>>>>>>>> (see 
>>>>>>>> https://weewx.com/docs/latest/usersguide.htm#Where_to_find_things), 
>>>>>

Re: [weewx-user] Just upgraded to 4.10.2 and Python3

2023-08-25 Thread David Barto

Backed off to 9.5.0 and the errors went away, however the png files are still 
not being generated.

The only errors in the log are:

Aug 25 16:20:12 Magrathea2 weewx[2226] ERROR weewx.rest]: PWSWeather: Failed to 
publish record 2023-08-25 16:18:00 PDT (1693005480): Failed upload after 3 tries
Aug 25 16:20:12 Magrathea2 weewx[2226] ERROR weewx.rest]: StationRegistry: 
Failed to publish record 2023-08-25 16:18:00 PDT (1693005480): Failed upload 
after 3 tries
Aug 25 16:20:12 Magrathea2 weewx[2226] ERROR weewx.rest]: Wunderground-PWS: 
Failed to publish record 2023-08-25 16:18:00 PDT (1693005480): Failed upload 
after 3 tries


Which are un-important right now. I’ll fix that in a bit.

Other suggestions?

David

> On Aug 25, 2023, at 3:53 PM, vince  wrote:
> 
> If you google for your error message "AttributeError: type object 'ImageDraw' 
> has no attribute 'textsize' " you'll find an old thread about this
> https://groups.google.com/g/weewx-user/c/4qz0bwgna7g
> 
> 
> 
> On Friday, August 25, 2023 at 2:42:21 PM UTC-7 David Barto wrote:
>> On a new Mac, and I’m getting the following: 
>> 
>> AttributeError: type object 'ImageDraw' has no attribute 'textsize' 
>> Traceback (most recent call last): 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/reportengine.py", line 197, in 
>> run 
>> obj.start() 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/reportengine.py", line 385, in 
>> start 
>> self.run() 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/imagegenerator.py", line 42, in 
>> run 
>> self.gen_images(self.gen_ts) 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/imagegenerator.py", line 114, in 
>> gen_images 
>> image = plot.render() 
>> File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 212, in 
>> render 
>> self._renderBottom(draw) 
>> File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 404, in 
>> _renderBottom 
>> bottom_label_size = draw.textsize(self.bottom_label, font=bottom_label_font) 
>> File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 646, in 
>> textsize 
>> return ImageDraw.ImageDraw.textsize(self, string, **options) 
>> 
>> Highs, lows look fine. 
>> 
>> Loop packets appear OK: 
>> LOOP: 2023-08-25 14:40:56 PDT (1692999656) 'altimeter': '29.931', 'appTemp': 
>> '88.20251678811093', 'bar_reduction': '2', 'barometer': '29.897', 
>> 'cloudbase': '4570.074962495151', 'dateTime': '1692999656', 'dayET': '0.0', 
>> 'dayRain': '0.0', 'dewpoint': '67.0', 'ET': 'None', 'heatindex': '87.0', 
>> 'hourRain': '0.0', 'humidex': '96.5974355268055', 'inDewpoint': 
>> '63.14965844190338', 'inHumidity': '56.0', 'inTemp': '80.3', 'maxSolarRad': 
>> '856.5713445507906', 'outHumidity': '58.0', 'outTemp': '83.6', 'pressure': 
>> '29.023', 'pressure_raw': '29.023', 'rain': '0.0', 'rain15': '0.0', 
>> 'rain24': '0.0', 'rainRate': '0.0', 'stormRain': '0.0', 'trendIcon': '-20', 
>> 'usUnits': '1', 'windchill': '84.0', 'windDir': '296.0', 'windGust': '8.0', 
>> 'windGust10': '11.0', 'windGustDir': '277.0', 'windGustDir10': '270.0', 
>> 'windrun': 'None', 'windSpeed': '3.0', 'windSpeed2': '4.0', 'windSpeed10': 
>> '5.6' 
>> LOOP: 2023-08-25 14:40:58 PDT (1692999658) 'altimeter': '29.931', 'appTemp': 
>> '88.20251678811093', 'bar_reduction': '2', 'barometer': '29.897', 
>> 'cloudbase': '4570.074962495151', 'dateTime': '1692999658', 'dayET': '0.0', 
>> 'dayRain': '0.0', 'dewpoint': '67.0', 'ET': 'None', 'heatindex': '87.0', 
>> 'hourRain': '0.0', 'humidex': '96.5974355268055', 'inDewpoint': 
>> '63.14965844190338', 'in

Re: [weewx-user] Just upgraded to 4.10.2 and Python3

2023-08-25 Thread David Barto

Thanks, My searching the archives didn’t find it.

David

> On Aug 25, 2023, at 3:53 PM, vince  wrote:
> 
> If you google for your error message "AttributeError: type object 'ImageDraw' 
> has no attribute 'textsize' " you'll find an old thread about this
> https://groups.google.com/g/weewx-user/c/4qz0bwgna7g
> 
> 
> 
> On Friday, August 25, 2023 at 2:42:21 PM UTC-7 David Barto wrote:
>> On a new Mac, and I’m getting the following: 
>> 
>> AttributeError: type object 'ImageDraw' has no attribute 'textsize' 
>> Traceback (most recent call last): 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/reportengine.py", line 197, in 
>> run 
>> obj.start() 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/reportengine.py", line 385, in 
>> start 
>> self.run() 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/imagegenerator.py", line 42, in 
>> run 
>> self.gen_images(self.gen_ts) 
>> File "/Users/Shared/weewx-4.10.2/bin/weewx/imagegenerator.py", line 114, in 
>> gen_images 
>> image = plot.render() 
>> File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 212, in 
>> render 
>> self._renderBottom(draw) 
>> File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 404, in 
>> _renderBottom 
>> bottom_label_size = draw.textsize(self.bottom_label, font=bottom_label_font) 
>> File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 646, in 
>> textsize 
>> return ImageDraw.ImageDraw.textsize(self, string, **options) 
>> 
>> Highs, lows look fine. 
>> 
>> Loop packets appear OK: 
>> LOOP: 2023-08-25 14:40:56 PDT (1692999656) 'altimeter': '29.931', 'appTemp': 
>> '88.20251678811093', 'bar_reduction': '2', 'barometer': '29.897', 
>> 'cloudbase': '4570.074962495151', 'dateTime': '1692999656', 'dayET': '0.0', 
>> 'dayRain': '0.0', 'dewpoint': '67.0', 'ET': 'None', 'heatindex': '87.0', 
>> 'hourRain': '0.0', 'humidex': '96.5974355268055', 'inDewpoint': 
>> '63.14965844190338', 'inHumidity': '56.0', 'inTemp': '80.3', 'maxSolarRad': 
>> '856.5713445507906', 'outHumidity': '58.0', 'outTemp': '83.6', 'pressure': 
>> '29.023', 'pressure_raw': '29.023', 'rain': '0.0', 'rain15': '0.0', 
>> 'rain24': '0.0', 'rainRate': '0.0', 'stormRain': '0.0', 'trendIcon': '-20', 
>> 'usUnits': '1', 'windchill': '84.0', 'windDir': '296.0', 'windGust': '8.0', 
>> 'windGust10': '11.0', 'windGustDir': '277.0', 'windGustDir10': '270.0', 
>> 'windrun': 'None', 'windSpeed': '3.0', 'windSpeed2': '4.0', 'windSpeed10': 
>> '5.6' 
>> LOOP: 2023-08-25 14:40:58 PDT (1692999658) 'altimeter': '29.931', 'appTemp': 
>> '88.20251678811093', 'bar_reduction': '2', 'barometer': '29.897', 
>> 'cloudbase': '4570.074962495151', 'dateTime': '1692999658', 'dayET': '0.0', 
>> 'dayRain': '0.0', 'dewpoint': '67.0', 'ET': 'None', 'heatindex': '87.0', 
>> 'hourRain': '0.0', 'humidex': '96.5974355268055', 'inDewpoint': 
>> '63.14965844190338', 'inHumidity': '56.0', 'inTemp': '80.3', 'maxSolarRad': 
>> '856.4989148817249', 'outHumidity': '58.0', 'outTemp': '83.6', 'pressure': 
>> '29.023', 'pressure_raw': '29.023', 'rain': '0.0', 'rain15': '0.0', 
>> 'rain24': '0.0', 'rainRate': '0.0', 'stormRain': '0.0', 'trendIcon': '-20', 
>> 'usUnits': '1', 'windchill': '84.0', 'windDir'

[weewx-user] Just upgraded to 4.10.2 and Python3

2023-08-25 Thread David Barto

On a new Mac, and I’m getting the following:

AttributeError: type object 'ImageDraw' has no attribute 'textsize'
Traceback (most recent call last):
  File "/Users/Shared/weewx-4.10.2/bin/weewx/reportengine.py", line 197, in run
obj.start()
  File "/Users/Shared/weewx-4.10.2/bin/weewx/reportengine.py", line 385, in 
start
self.run()
  File "/Users/Shared/weewx-4.10.2/bin/weewx/imagegenerator.py", line 42, in run
self.gen_images(self.gen_ts)
  File "/Users/Shared/weewx-4.10.2/bin/weewx/imagegenerator.py", line 114, in 
gen_images
image = plot.render()
  File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 212, in render
self._renderBottom(draw)
  File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 404, in 
_renderBottom
bottom_label_size = draw.textsize(self.bottom_label, font=bottom_label_font)
  File "/Users/Shared/weewx-4.10.2/bin/weeplot/genplot.py", line 646, in 
textsize
return ImageDraw.ImageDraw.textsize(self, string, **options)

Highs, lows look fine.

Loop packets appear OK:
LOOP:   2023-08-25 14:40:56 PDT (1692999656) 'altimeter': '29.931', 'appTemp': 
'88.20251678811093', 'bar_reduction': '2', 'barometer': '29.897', 'cloudbase': 
'4570.074962495151', 'dateTime': '1692999656', 'dayET': '0.0', 'dayRain': 
'0.0', 'dewpoint': '67.0', 'ET': 'None', 'heatindex': '87.0', 'hourRain': 
'0.0', 'humidex': '96.5974355268055', 'inDewpoint': '63.14965844190338', 
'inHumidity': '56.0', 'inTemp': '80.3', 'maxSolarRad': '856.5713445507906', 
'outHumidity': '58.0', 'outTemp': '83.6', 'pressure': '29.023', 'pressure_raw': 
'29.023', 'rain': '0.0', 'rain15': '0.0', 'rain24': '0.0', 'rainRate': '0.0', 
'stormRain': '0.0', 'trendIcon': '-20', 'usUnits': '1', 'windchill': '84.0', 
'windDir': '296.0', 'windGust': '8.0', 'windGust10': '11.0', 'windGustDir': 
'277.0', 'windGustDir10': '270.0', 'windrun': 'None', 'windSpeed': '3.0', 
'windSpeed2': '4.0', 'windSpeed10': '5.6'
LOOP:   2023-08-25 14:40:58 PDT (1692999658) 'altimeter': '29.931', 'appTemp': 
'88.20251678811093', 'bar_reduction': '2', 'barometer': '29.897', 'cloudbase': 
'4570.074962495151', 'dateTime': '1692999658', 'dayET': '0.0', 'dayRain': 
'0.0', 'dewpoint': '67.0', 'ET': 'None', 'heatindex': '87.0', 'hourRain': 
'0.0', 'humidex': '96.5974355268055', 'inDewpoint': '63.14965844190338', 
'inHumidity': '56.0', 'inTemp': '80.3', 'maxSolarRad': '856.4989148817249', 
'outHumidity': '58.0', 'outTemp': '83.6', 'pressure': '29.023', 'pressure_raw': 
'29.023', 'rain': '0.0', 'rain15': '0.0', 'rain24': '0.0', 'rainRate': '0.0', 
'stormRain': '0.0', 'trendIcon': '-20', 'usUnits': '1', 'windchill': '84.0', 
'windDir': '296.0', 'windGust': '8.0', 'windGust10': '11.0', 'windGustDir': 
'277.0', 'windGustDir10': '270.0', 'windrun': 'None', 'windSpeed': '3.0', 
'windSpeed2': '4.0', 'windSpeed10': ‘5.6'


So I’m not generating any images.

David


...well over half of the time you spend working on a project (on the order of 
70 percent)
is spent thinking, and no tool, no matter how advanced, can think for you.
Consequently, even if a tool did everything except the thinking for you -- if 
it wrote 100 percent of the code,
wrote 100 percent of the documentation, did 100 percent of the testing, burned 
the CD-ROMs,
put them in boxes, and mailed them to your customers -- the best you could hope 
for would
be a 30 percent improvement in productivity. In order to do better than that, 
you have to
change the way you think.
--Fred Brooks
David Barto
ba...@kdbarto.org


-- 
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/7F93D007-969C-4EFE-8F8B-0A66D270BA06%40kdbarto.org.

Re: [weewx-user] Re: WDC Skin

2023-08-18 Thread David Bätge

Great, I will include the change in the next release! 

gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 13:44:22 UTC+2:

> Hi David
>
> I was to fast, it seems to work with the new main.ja.
>
> Thanks for that
>
> Gert
>
> On Friday, August 18, 2023 at 12:44:22 PM UTC+2 gert.a...@gmail.com wrote:
>
>> Hi David
>> Unfortunately, the new main.js, did not solve the problem as you can see. 
>> The WindRose seems fine
>>
>> Rgds
>> Gert
>>
>> On Friday, August 18, 2023 at 12:02:36 PM UTC+2 David Bätge wrote:
>>
>>> You can right-click the link and choose "Save as" or open the file in 
>>> the browser and hit "Strg+S" if on Windows or Linux.
>>>
>>> The problem with this menu is that you can not scroll the sidebar. The 
>>> sidebar should be scrollable so you can access all the items, but that's 
>>> not the case. I added https://github.com/Daveiano/weewx-wdc/issues/193 
>>> for this, will have a look soon!
>>>
>>> gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 07:10:37 
>>> UTC+2:
>>>
>>>>
>>>> Hi David
>>>> Thanks for the prompt answer.
>>>>
>>>> The link you provided will just open the file in the browser. so I'm 
>>>> not able to download the file.
>>>>
>>>> Is it possible to move the the Archive and NOAA Reports Menu to the 
>>>> upper Menu line, besides the Year Menu. As you can see from the 
>>>> screenshot, 
>>>> I can't see the last months of the NOAA report and i's not possible to 
>>>> scroll in the left menu.
>>>>
>>>> Thanks
>>>> Gert
>>>> On Friday, August 18, 2023 at 2:26:37 AM UTC+2 David Bätge wrote:
>>>>
>>>>> I just noticed you are using custom ordinate labels - I just tested 
>>>>> this out and noticed that special characters are not handled properly in 
>>>>> the legend labels.
>>>>>
>>>>> I made a change to the main.js file, you can download the updated file 
>>>>> here: https://public-images-social.s3.eu-west-1.amazonaws.com/main.js
>>>>> I tried to attach the file here but the messages were deleted...
>>>>>
>>>>> You need to replace the original file at the skins install location 
>>>>> (see https://weewx.com/docs/latest/usersguide.htm#Where_to_find_things), 
>>>>> at eg. /etc/weewx/skins/weewx-wdc/dist/main.js
>>>>>
>>>>> If this fixes the issue, I will include this in the release.
>>>>> David Bätge schrieb am Freitag, 18. August 2023 um 02:06:42 UTC+2:
>>>>>
>>>>>> Ok, I have never seen this behaviour before.
>>>>>>
>>>>>> Could you please set [DisplayOptions]diagram_tile_winddir_ordinal to 
>>>>>> False, and post back what the legend shows?
>>>>>> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 
>>>>>> 22:20:59 UTC+2:
>>>>>>
>>>>>>> Hi
>>>>>>> I'm missing the compass direction where the letter "Ø" is, but only 
>>>>>>> in the first chart . The windrose is ok.
>>>>>>>
>>>>>>> Any ideas how to get the direction in the first chart?
>>>>>>>
>>>>>>> Thanks
>>>>>>> gert
>>>>>>>
>>>>>>> On Thursday, August 17, 2023 at 1:32:43 PM UTC+2 David Bätge wrote:
>>>>>>>
>>>>>>>> Great! 
>>>>>>>>
>>>>>>>> You can run the skin wherever you want, but if it's not in the root 
>>>>>>>> of the webserver, you have to tell the skin, see here: 
>>>>>>>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>>>>>>>>
>>>>>>>> David
>>>>>>>> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 
>>>>>>>> 13:02:56 UTC+2:
>>>>>>>>
>>>>>>>>> Hi David
>>>>>>>>> I copied a database from another system with  4 years of data and 
>>>>>>>>> the that helped. I can now start further testing.
>>>>>>>>>
>>>>>>>>> It seems that I need to run the skin from the webservers root and 
>&g

Re: [weewx-user] Re: WDC Skin

2023-08-18 Thread David Bätge

You can right-click the link and choose "Save as" or open the file in the 
browser and hit "Strg+S" if on Windows or Linux.

The problem with this menu is that you can not scroll the sidebar. The 
sidebar should be scrollable so you can access all the items, but that's 
not the case. I added https://github.com/Daveiano/weewx-wdc/issues/193 for 
this, will have a look soon!

gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 07:10:37 UTC+2:

>
> Hi David
> Thanks for the prompt answer.
>
> The link you provided will just open the file in the browser. so I'm not 
> able to download the file.
>
> Is it possible to move the the Archive and NOAA Reports Menu to the upper 
> Menu line, besides the Year Menu. As you can see from the screenshot, I 
> can't see the last months of the NOAA report and i's not possible to scroll 
> in the left menu.
>
> Thanks
> Gert
> On Friday, August 18, 2023 at 2:26:37 AM UTC+2 David Bätge wrote:
>
>> I just noticed you are using custom ordinate labels - I just tested this 
>> out and noticed that special characters are not handled properly in the 
>> legend labels.
>>
>> I made a change to the main.js file, you can download the updated file 
>> here: https://public-images-social.s3.eu-west-1.amazonaws.com/main.js
>> I tried to attach the file here but the messages were deleted...
>>
>> You need to replace the original file at the skins install location (see 
>> https://weewx.com/docs/latest/usersguide.htm#Where_to_find_things), at 
>> eg. /etc/weewx/skins/weewx-wdc/dist/main.js
>>
>> If this fixes the issue, I will include this in the release.
>> David Bätge schrieb am Freitag, 18. August 2023 um 02:06:42 UTC+2:
>>
>>> Ok, I have never seen this behaviour before.
>>>
>>> Could you please set [DisplayOptions]diagram_tile_winddir_ordinal to 
>>> False, and post back what the legend shows?
>>> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 22:20:59 
>>> UTC+2:
>>>
>>>> Hi
>>>> I'm missing the compass direction where the letter "Ø" is, but only in 
>>>> the first chart . The windrose is ok.
>>>>
>>>> Any ideas how to get the direction in the first chart?
>>>>
>>>> Thanks
>>>> gert
>>>>
>>>> On Thursday, August 17, 2023 at 1:32:43 PM UTC+2 David Bätge wrote:
>>>>
>>>>> Great! 
>>>>>
>>>>> You can run the skin wherever you want, but if it's not in the root of 
>>>>> the webserver, you have to tell the skin, see here: 
>>>>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>>>>>
>>>>> David
>>>>> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 
>>>>> 13:02:56 UTC+2:
>>>>>
>>>>>> Hi David
>>>>>> I copied a database from another system with  4 years of data and the 
>>>>>> that helped. I can now start further testing.
>>>>>>
>>>>>> It seems that I need to run the skin from the webservers root and not 
>>>>>> from a directory under the webservers root. Is that right?
>>>>>>
>>>>>> Gert
>>>>>>
>>>>>> On Thursday, August 17, 2023 at 2:16:15 AM UTC+2 David Bätge wrote:
>>>>>>
>>>>>>> Hi Gert,
>>>>>>>
>>>>>>> I just spotted this the line before where the error was triggered:
>>>>>>>
>>>>>>> # todo: division by zero
>>>>>>>
>>>>>>> If I remember correctly, this could be possible if you have less 
>>>>>>> than 1 day of data in your archive. I assume you are using a new 
>>>>>>> installation with no data? So it "should" work tomorrow, I guess. The 
>>>>>>> error 
>>>>>>> is only triggered from the statistics page and there is no other error?
>>>>>>>
>>>>>>> I think I noticed this while testing, but forgot to fix it... 
>>>>>>> Anyway, I finally added an issue for this: 
>>>>>>> https://github.com/Daveiano/weewx-wdc/issues/192
>>>>>>>
>>>>>>> For the weewx 5 part: I did not get any time to test the skin with 
>>>>>>> the new version, so I am quite happy there are no errors yet ;)
>>>>>>>
>>>>>>>

Re: [weewx-user] Re: WDC Skin

I just noticed you are using custom ordinate labels - I just tested this 
out and noticed that special characters are not handled properly in the 
legend labels.

I made a change to the main.js file, you can download the updated file 
here: https://public-images-social.s3.eu-west-1.amazonaws.com/main.js
I tried to attach the file here but the messages were deleted...

You need to replace the original file at the skins install location (see 
https://weewx.com/docs/latest/usersguide.htm#Where_to_find_things), at eg. 
/etc/weewx/skins/weewx-wdc/dist/main.js

If this fixes the issue, I will include this in the release.
David Bätge schrieb am Freitag, 18. August 2023 um 02:06:42 UTC+2:

> Ok, I have never seen this behaviour before.
>
> Could you please set [DisplayOptions]diagram_tile_winddir_ordinal to False, 
> and post back what the legend shows?
> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 22:20:59 
> UTC+2:
>
>> Hi
>> I'm missing the compass direction where the letter "Ø" is, but only in 
>> the first chart . The windrose is ok.
>>
>> Any ideas how to get the direction in the first chart?
>>
>> Thanks
>> gert
>>
>> On Thursday, August 17, 2023 at 1:32:43 PM UTC+2 David Bätge wrote:
>>
>>> Great! 
>>>
>>> You can run the skin wherever you want, but if it's not in the root of 
>>> the webserver, you have to tell the skin, see here: 
>>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>>>
>>> David
>>> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 13:02:56 
>>> UTC+2:
>>>
>>>> Hi David
>>>> I copied a database from another system with  4 years of data and the 
>>>> that helped. I can now start further testing.
>>>>
>>>> It seems that I need to run the skin from the webservers root and not 
>>>> from a directory under the webservers root. Is that right?
>>>>
>>>> Gert
>>>>
>>>> On Thursday, August 17, 2023 at 2:16:15 AM UTC+2 David Bätge wrote:
>>>>
>>>>> Hi Gert,
>>>>>
>>>>> I just spotted this the line before where the error was triggered:
>>>>>
>>>>> # todo: division by zero
>>>>>
>>>>> If I remember correctly, this could be possible if you have less than 
>>>>> 1 day of data in your archive. I assume you are using a new installation 
>>>>> with no data? So it "should" work tomorrow, I guess. The error is only 
>>>>> triggered from the statistics page and there is no other error?
>>>>>
>>>>> I think I noticed this while testing, but forgot to fix it... Anyway, 
>>>>> I finally added an issue for this: 
>>>>> https://github.com/Daveiano/weewx-wdc/issues/192
>>>>>
>>>>> For the weewx 5 part: I did not get any time to test the skin with the 
>>>>> new version, so I am quite happy there are no errors yet ;)
>>>>>
>>>>> David
>>>>>
>>>>> gert.a...@gmail.com schrieb am Mittwoch, 16. August 2023 um 23:20:46 
>>>>> UTC+2:
>>>>>
>>>>>> Hi
>>>>>> I'm trying to install the template using  WeeWx 5.0.0b10. I copied 
>>>>>> the skin files to the relevant WeeWx directories and created the stanza 
>>>>>> in 
>>>>>> weewx.conf. as you can see from the attached syslog, there were errors.
>>>>>>
>>>>>> I installed WeeWx using pip, so WeeWx is unning in a virtual 
>>>>>> environmrnt
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> Gert
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wednesday, August 16, 2023 at 2:17:52 AM UTC+2 David Bätge wrote:
>>>>>>
>>>>>>> The error indicates that the observation type is unknown, in that 
>>>>>>> case, cloudbase. The skin should not attempt to display data for an 
>>>>>>> observation that has no data - so there seems to be something wrong 
>>>>>>> here.
>>>>>>>
>>>>>>> Could you please remove cloudbase from 
>>>>>>> [DisplayOptions][[diagrams]][[[day]]]observations in 
>>>>>>> skin.conf?
>>>>>>>
>>>>>>> If this does not help, you ca

Re: [weewx-user] Re: WDC Skin

Ok, I have never seen this behaviour before.

Could you please set [DisplayOptions]diagram_tile_winddir_ordinal to False, 
and post back what the legend shows?
gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 22:20:59 
UTC+2:

> Hi
> I'm missing the compass direction where the letter "Ø" is, but only in the 
> first chart . The windrose is ok.
>
> Any ideas how to get the direction in the first chart?
>
> Thanks
> gert
>
> On Thursday, August 17, 2023 at 1:32:43 PM UTC+2 David Bätge wrote:
>
>> Great! 
>>
>> You can run the skin wherever you want, but if it's not in the root of 
>> the webserver, you have to tell the skin, see here: 
>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>>
>> David
>> gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 13:02:56 
>> UTC+2:
>>
>>> Hi David
>>> I copied a database from another system with  4 years of data and the 
>>> that helped. I can now start further testing.
>>>
>>> It seems that I need to run the skin from the webservers root and not 
>>> from a directory under the webservers root. Is that right?
>>>
>>> Gert
>>>
>>> On Thursday, August 17, 2023 at 2:16:15 AM UTC+2 David Bätge wrote:
>>>
>>>> Hi Gert,
>>>>
>>>> I just spotted this the line before where the error was triggered:
>>>>
>>>> # todo: division by zero
>>>>
>>>> If I remember correctly, this could be possible if you have less than 1 
>>>> day of data in your archive. I assume you are using a new installation 
>>>> with 
>>>> no data? So it "should" work tomorrow, I guess. The error is only 
>>>> triggered 
>>>> from the statistics page and there is no other error?
>>>>
>>>> I think I noticed this while testing, but forgot to fix it... Anyway, I 
>>>> finally added an issue for this: 
>>>> https://github.com/Daveiano/weewx-wdc/issues/192
>>>>
>>>> For the weewx 5 part: I did not get any time to test the skin with the 
>>>> new version, so I am quite happy there are no errors yet ;)
>>>>
>>>> David
>>>>
>>>> gert.a...@gmail.com schrieb am Mittwoch, 16. August 2023 um 23:20:46 
>>>> UTC+2:
>>>>
>>>>> Hi
>>>>> I'm trying to install the template using  WeeWx 5.0.0b10. I copied the 
>>>>> skin files to the relevant WeeWx directories and created the stanza in 
>>>>> weewx.conf. as you can see from the attached syslog, there were errors.
>>>>>
>>>>> I installed WeeWx using pip, so WeeWx is unning in a virtual 
>>>>> environmrnt
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Gert
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, August 16, 2023 at 2:17:52 AM UTC+2 David Bätge wrote:
>>>>>
>>>>>> The error indicates that the observation type is unknown, in that 
>>>>>> case, cloudbase. The skin should not attempt to display data for an 
>>>>>> observation that has no data - so there seems to be something wrong here.
>>>>>>
>>>>>> Could you please remove cloudbase from 
>>>>>> [DisplayOptions][[diagrams]][[[day]]]observations in 
>>>>>> skin.conf?
>>>>>>
>>>>>> If this does not help, you can try to remove cloudbase also from 
>>>>>> [DisplayOptions]table_tile_observations and 
>>>>>> [DisplayOptions]stat_tile_observations.
>>>>>>
>>>>>> This error really only appears for the index page?
>>>>>>
>>>>>> Eirik Skorstad schrieb am Dienstag, 15. August 2023 um 17:05:11 UTC+2:
>>>>>>
>>>>>>> 2023-08-15T16:56:50.431510+02:00 odin wee_reports[334303] ERROR 
>>>>>>> weewx.cheetahgenerator:  Ignoring template 
>>>>>>> /home/weewx/skins/weewx-wdc/index.html.tmpl
>>>>>>> 2023-08-15T16:56:50.431625+02:00 odin wee_reports[334303] ERROR 
>>>>>>> weewx.cheetahgenerator:  Reason: 'cloudbase' or 'avg'
>>>>>>> 2023-08-15T16:56:50.434142+02:00 odin wee_reports[334303] ERROR 
>>>>>>> weewx.cheetahgenerator:   Traceback (most recent call last):
>>>>&g

[weewx-user] Re: WDC skin date format

Hi Greg,

you are referring to the heading on the month page "/month.html" and the 
month-archive pages, eg "/month-2021-07.html", right?

These Headings at the top of the page use the same format, both use the 
setting defined in skin.conf [Units][[TimeFormats]]month (see 
https://github.com/Daveiano/weewx-wdc/blob/3.x/skins/weewx-wdc/skin.conf#L636):

[Units]
[[TimeFormats]]
# @see https://weewx.com/docs/customizing.htm#Units_TimeFormats
day= %X
week   = %x
month  = %x
year   = %x
rainyear   = %x
current= %x %X
ephem_day  = %X
ephem_year = %x
stats  = %x %X
daily_archive = %Y-%m-%d

There was a change in the date format in one of the latest releases if I 
remember correctly. There is a chance that your month archive pages use the 
old format. This could be the case since these archive pages do not get 
regenerated after the given archive period (even if templates or configs 
are changed).

To make sure this is not the case, please remove all month archive pages, 
and wait for the next wee_report run or start the run by yourself.

rm -rf /var/www/html/weewx/month*


Greg from Oz schrieb am Donnerstag, 17. August 2023 um 05:01:58 UTC+2:

> Hi,
>
> I have noticed the date format in the headings when I select day, 
> yesterday,week,month,year are correct to how I want them. IE dd/mm/yyy
>
> Like this:
> Monthly Weather Conditions
> 01/08/23 00:00:00 - 31/08/23 23:59:59 
>
> But if I go to the Archive and NOAA sidebar and pick something then the 
> date format changes to the US format mm/dd/yyy
> Like this:
> Monthly Weather Conditions 
> 01/01/2023 12:00:00 AM - 01/31/2023 11:59:59 PM
>
> I have looked through the skin and tmpl files but cannot see anything that 
> I can change.
> I have noticed it looks like it picks up the date formatting from 
> daily_archive 
> = %Y-%m-%d in the skin but if that is so I would have expected the format 
> to be /mm/dd which I would like as it is international ISO standard.
>
> Where is the format for the date set?
>
> Thanks
>
>

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

Re: [weewx-user] Re: WDC Skin

Great! 

You can run the skin wherever you want, but if it's not in the root of the 
webserver, you have to tell the skin, see here: 
https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras

David
gert.a...@gmail.com schrieb am Donnerstag, 17. August 2023 um 13:02:56 
UTC+2:

> Hi David
> I copied a database from another system with  4 years of data and the that 
> helped. I can now start further testing.
>
> It seems that I need to run the skin from the webservers root and not from 
> a directory under the webservers root. Is that right?
>
> Gert
>
> On Thursday, August 17, 2023 at 2:16:15 AM UTC+2 David Bätge wrote:
>
>> Hi Gert,
>>
>> I just spotted this the line before where the error was triggered:
>>
>> # todo: division by zero
>>
>> If I remember correctly, this could be possible if you have less than 1 
>> day of data in your archive. I assume you are using a new installation with 
>> no data? So it "should" work tomorrow, I guess. The error is only triggered 
>> from the statistics page and there is no other error?
>>
>> I think I noticed this while testing, but forgot to fix it... Anyway, I 
>> finally added an issue for this: 
>> https://github.com/Daveiano/weewx-wdc/issues/192
>>
>> For the weewx 5 part: I did not get any time to test the skin with the 
>> new version, so I am quite happy there are no errors yet ;)
>>
>> David
>>
>> gert.a...@gmail.com schrieb am Mittwoch, 16. August 2023 um 23:20:46 
>> UTC+2:
>>
>>> Hi
>>> I'm trying to install the template using  WeeWx 5.0.0b10. I copied the 
>>> skin files to the relevant WeeWx directories and created the stanza in 
>>> weewx.conf. as you can see from the attached syslog, there were errors.
>>>
>>> I installed WeeWx using pip, so WeeWx is unning in a virtual environmrnt
>>>
>>> Any ideas?
>>>
>>> Gert
>>>
>>>
>>>
>>>
>>> On Wednesday, August 16, 2023 at 2:17:52 AM UTC+2 David Bätge wrote:
>>>
>>>> The error indicates that the observation type is unknown, in that case, 
>>>> cloudbase. The skin should not attempt to display data for an observation 
>>>> that has no data - so there seems to be something wrong here.
>>>>
>>>> Could you please remove cloudbase from 
>>>> [DisplayOptions][[diagrams]][[[day]]]observations in skin.conf?
>>>>
>>>> If this does not help, you can try to remove cloudbase also from 
>>>> [DisplayOptions]table_tile_observations and 
>>>> [DisplayOptions]stat_tile_observations.
>>>>
>>>> This error really only appears for the index page?
>>>>
>>>> Eirik Skorstad schrieb am Dienstag, 15. August 2023 um 17:05:11 UTC+2:
>>>>
>>>>> 2023-08-15T16:56:50.431510+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator:  Ignoring template 
>>>>> /home/weewx/skins/weewx-wdc/index.html.tmpl
>>>>> 2023-08-15T16:56:50.431625+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator:  Reason: 'cloudbase' or 'avg'
>>>>> 2023-08-15T16:56:50.434142+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator:   Traceback (most recent call last):
>>>>> 2023-08-15T16:56:50.434253+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator: File 
>>>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
>>>>> 2023-08-15T16:56:50.434352+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator:   unicode_string = 
>>>>> compiled_template.respond()
>>>>> 2023-08-15T16:56:50.434442+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator:    
>>>>> ^^^
>>>>> 2023-08-15T16:56:50.434547+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator: File 
>>>>> "_home_weewx_skins_weewx_wdc_index_html_tmpl.py", line 267, in respond
>>>>> 2023-08-15T16:56:50.434657+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator: File 
>>>>> "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
>>>>> _handleCheetahInclude
>>>>> 2023-08-15T16:56:50.434749+02:00 odin wee_reports[334303] ERROR 
>>>>> weewx.cheetahgenerator:

Re: [weewx-user] Re: WDC Skin

2023-08-16 Thread David Bätge

Hi Gert,

I just spotted this the line before where the error was triggered:

# todo: division by zero

If I remember correctly, this could be possible if you have less than 1 day 
of data in your archive. I assume you are using a new installation with no 
data? So it "should" work tomorrow, I guess. The error is only triggered 
from the statistics page and there is no other error?

I think I noticed this while testing, but forgot to fix it... Anyway, I 
finally added an issue for 
this: https://github.com/Daveiano/weewx-wdc/issues/192

For the weewx 5 part: I did not get any time to test the skin with the new 
version, so I am quite happy there are no errors yet ;)

David

gert.a...@gmail.com schrieb am Mittwoch, 16. August 2023 um 23:20:46 UTC+2:

> Hi
> I'm trying to install the template using  WeeWx 5.0.0b10. I copied the 
> skin files to the relevant WeeWx directories and created the stanza in 
> weewx.conf. as you can see from the attached syslog, there were errors.
>
> I installed WeeWx using pip, so WeeWx is unning in a virtual environmrnt
>
> Any ideas?
>
> Gert
>
>
>
>
> On Wednesday, August 16, 2023 at 2:17:52 AM UTC+2 David Bätge wrote:
>
>> The error indicates that the observation type is unknown, in that case, 
>> cloudbase. The skin should not attempt to display data for an observation 
>> that has no data - so there seems to be something wrong here.
>>
>> Could you please remove cloudbase from 
>> [DisplayOptions][[diagrams]][[[day]]]observations in skin.conf?
>>
>> If this does not help, you can try to remove cloudbase also from 
>> [DisplayOptions]table_tile_observations and 
>> [DisplayOptions]stat_tile_observations.
>>
>> This error really only appears for the index page?
>>
>> Eirik Skorstad schrieb am Dienstag, 15. August 2023 um 17:05:11 UTC+2:
>>
>>> 2023-08-15T16:56:50.431510+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:  Ignoring template 
>>> /home/weewx/skins/weewx-wdc/index.html.tmpl
>>> 2023-08-15T16:56:50.431625+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:  Reason: 'cloudbase' or 'avg'
>>> 2023-08-15T16:56:50.434142+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:   Traceback (most recent call last):
>>> 2023-08-15T16:56:50.434253+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
>>> 2023-08-15T16:56:50.434352+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:   unicode_string = 
>>> compiled_template.respond()
>>> 2023-08-15T16:56:50.434442+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:    
>>> ^^^
>>> 2023-08-15T16:56:50.434547+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "_home_weewx_skins_weewx_wdc_index_html_tmpl.py", line 267, in respond
>>> 2023-08-15T16:56:50.434657+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
>>> _handleCheetahInclude
>>> 2023-08-15T16:56:50.434749+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:  
>>>  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>>> 2023-08-15T16:56:50.434844+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "_home_weewx_skins_weewx_wdc_includes_body_alternative_inc.py", line 326, 
>>> in respond
>>> 2023-08-15T16:56:50.435088+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
>>> _handleCheetahInclude
>>> 2023-08-15T16:56:50.435180+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator:  
>>>  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>>> 2023-08-15T16:56:50.435278+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "_home_weewx_skins_weewx_wdc_includes_diagram_tile_inc.py", line 240, in 
>>> respond
>>> 2023-08-15T16:56:50.435372+02:00 odin wee_reports[334303] ERROR 
>>> weewx.cheetahgenerator: File 
>>> "_home_weewx_skins_weewx_wdc_includes_diagram_tile_inc.py", line 106, in 
>>> __errorCatcher6
>>> 2023-08-15T16:56:50.435499+02:

Re: [weewx-user] Re: WDC Skin

2023-08-15 Thread David Bätge

The error indicates that the observation type is unknown, in that case, 
cloudbase. The skin should not attempt to display data for an observation 
that has no data - so there seems to be something wrong here.

Could you please remove cloudbase from 
[DisplayOptions][[diagrams]][[[day]]]observations in skin.conf?

If this does not help, you can try to remove cloudbase also from 
[DisplayOptions]table_tile_observations and 
[DisplayOptions]stat_tile_observations.

This error really only appears for the index page?

Eirik Skorstad schrieb am Dienstag, 15. August 2023 um 17:05:11 UTC+2:

> 2023-08-15T16:56:50.431510+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:  Ignoring template 
> /home/weewx/skins/weewx-wdc/index.html.tmpl
> 2023-08-15T16:56:50.431625+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:  Reason: 'cloudbase' or 'avg'
> 2023-08-15T16:56:50.434142+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:   Traceback (most recent call last):
> 2023-08-15T16:56:50.434253+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
> 2023-08-15T16:56:50.434352+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:   unicode_string = 
> compiled_template.respond()
> 2023-08-15T16:56:50.434442+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:    
> ^^^
> 2023-08-15T16:56:50.434547+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_weewx_wdc_index_html_tmpl.py", line 267, in respond
> 2023-08-15T16:56:50.434657+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
> _handleCheetahInclude
> 2023-08-15T16:56:50.434749+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:  
>  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
> 2023-08-15T16:56:50.434844+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_weewx_wdc_includes_body_alternative_inc.py", line 326, 
> in respond
> 2023-08-15T16:56:50.435088+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
> _handleCheetahInclude
> 2023-08-15T16:56:50.435180+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:  
>  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
> 2023-08-15T16:56:50.435278+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_weewx_wdc_includes_diagram_tile_inc.py", line 240, in 
> respond
> 2023-08-15T16:56:50.435372+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_weewx_wdc_includes_diagram_tile_inc.py", line 106, in 
> __errorCatcher6
> 2023-08-15T16:56:50.435499+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File "", line 1, in 
> 2023-08-15T16:56:50.435580+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File "/home/weewx/bin/user/weewx_wdc.py", 
> line 1314, in get_diagram_data
> 2023-08-15T16:56:50.435673+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:   obs_start_vt, obs_stop_vt, obs_vt = 
> weewx.xtypes.get_series(
> 2023-08-15T16:56:50.435772+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:  
>  
> 2023-08-15T16:56:50.435867+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator: File "/home/weewx/bin/weewx/xtypes.py", 
> line 116, in get_series
> 2023-08-15T16:56:50.435963+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:   raise weewx.UnknownType(msg)
> 2023-08-15T16:56:50.436057+02:00 odin wee_reports[334303] ERROR 
> weewx.cheetahgenerator:   weewx.UnknownType: 'cloudbase' or 'avg'
>
> tirsdag 15. august 2023 kl. 14:49:45 UTC+2 skrev Eirik Skorstad:
>
>> I think I just answered your post in a private reply to you. Just CC it 
>> in to the post if you like to. 
>>
>> tirsdag 15. august 2023 kl. 03:04:13 UTC+2 skrev David Bätge:
>>
>>> I assume you are using the current version 3.3.0? The error indicates 
>>> that WeeWX can not find 
>>> the search_list_extensions user.weewx_wdc.WdcGeneralUtil. 
>>>
>>> Any chance you are using an old skin.conf file? Please compare with 
>>&

Re: [weewx-user] Re: WDC Skin

2023-08-14 Thread David Bätge

I assume you are using the current version 3.3.0? The error indicates that 
WeeWX can not find 
the search_list_extensions user.weewx_wdc.WdcGeneralUtil. 

Any chance you are using an old skin.conf file? Please compare 
with https://github.com/Daveiano/weewx-wdc/blob/v3.3.0/skins/weewx-wdc/skin.conf
Or, perhaps, have you overwritten the  search_list_extensions  config for 
the skin via weewx.conf?

Would be great if you could post the relevant section from weewx.conf and 
your current skin.conf so I could have a look.

Eirik Skorstad schrieb am Sonntag, 13. August 2023 um 23:04:37 UTC+2:

> Evaluation of template /home/weewx/skins/weewx-wdc/index.html.tmpl failed.
> 2023-08-13T23:00:40.303871+02:00 odin weewx[251007] ERROR 
> weewx.cheetahgenerator:  Ignoring template 
> /home/weewx/skins/weewx-wdc/index.html.tmpl
> 2023-08-13T23:00:40.304352+02:00 odin weewx[251007] ERROR 
> weewx.cheetahgenerator:  Reason: cannot find 'get_windrose_enabled'
> 2023-08-13T23:00:40.304456+02:00 odin weewx[251007] ERROR 
> weewx.cheetahgenerator:  To debug, try inserting '#errorCatcher Echo' 
> at top of template
>
>
> Skin is not generating any of the templates. Why is that? 
> torsdag 8. juni 2023 kl. 11:22:50 UTC+2 skrev Greg from Oz:
>
>> Yes that works.
>> I did a grep of the whole directory and sub directories looking for that 
>> and missed it.
>> But I was looking for get_base_path and not just base_path
>>
>> Thanks again.
>>
>> On Thursday, 8 June 2023 at 19:05:48 UTC+10 David Bätge wrote:
>>
>>> Hi Greg!  Please set the base_path in skin.conf to '/wdc/':
>>>
>>> base_path = /wdc/
>>>
>>> See 
>>> https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
>>>  
>>> and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras. 
>>> This should resolve the problem.
>>> Greg from Oz schrieb am Donnerstag, 8. Juni 2023 um 10:53:53 UTC+2:
>>>
>>>> Hi,
>>>>
>>>> I am testing the wdc skin and have set the html document root to 
>>>> /var/www/html/weather/wdc
>>>> If I go to https://weather.ubeaut.work/wdc/ (because I am testing and 
>>>> want to leave my other webpages) it shows the wdc index.html which is good.
>>>> If I click on any of the menu items eg Today  week month it takes me to 
>>>> my other web page. Yesterday doesn't work because on my other webpage 
>>>> there 
>>>> isn't a yesterday web page.
>>>> I suspect it is because of the $get_base_path which would be 
>>>> https://weather.ubeaut.work in this case.
>>>> How or where can I change this to be https://weather.ubeaut.work/wdc 
>>>> so I can test it out?
>>>>
>>>> Thanks
>>>>
>>>>
>>>> On Monday, 3 April 2023 at 00:31:31 UTC+10 gary@gmail.com wrote:
>>>>
>>>>> Version 3.1.1 has been released and this is now one of the nicest 
>>>>> skins I've used.
>>>>> Clear text, excellent graphs, histograms, live data from MQTT.
>>>>> Scales well to tablets.
>>>>> For my needs, replaced the Belchertown skin.
>>>>> On Friday, August 5, 2022 at 10:43:52 AM UTC-4 Andrea Di Saverio wrote:
>>>>>
>>>>>> Sorry for my late replay.
>>>>>>
>>>>>> Yes, the suggestion solved my problem. I was not installing as root 
>>>>>> user.
>>>>>> Thank you.
>>>>>>
>>>>>> Il giorno giovedì 4 agosto 2022 alle 01:46:26 UTC+2 
>>>>>> david@gmail.com ha scritto:
>>>>>>
>>>>>>> @disaveri Did this solve your problem?
>>>>>>>
>>>>>>> Btw: I released 2.0.1 which resolves the "non-web-root"-issue, the 
>>>>>>> "Pressure diagram with inHg unit"-issue and includes a few other 
>>>>>>> bugfixes: 
>>>>>>> https://github.com/Daveiano/weewx-wdc/releases/tag/v2.0.1
>>>>>>>
>>>>>>> Thanks for your input!
>>>>>>>
>>>>>>> vince schrieb am Dienstag, 2. August 2022 um 00:54:05 UTC+2:
>>>>>>>
>>>>>>>> On Monday, August 1, 2022 at 3:32:23 PM UTC-7 disaveri...@gmail.com 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>  the root cause is possibly something else?
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yes.  The 'root' cause indeed. 
>>>>>>>>
>>>>>>>> See the  FAQ - 
>>>>>>>> https://github.com/weewx/weewx/wiki/faq-permission-denied
>>>>>>>>  
>>>>>>>>
>>>>>>>

-- 
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/db4eac93-de0d-4e36-9155-3b4fd9883564n%40googlegroups.com.

Re: [weewx-user] Certificate Verify failed

2023-08-04 Thread David Barto

This is a MacOS install, apt-get doesn’t exist. 8^(

David

> On Aug 4, 2023, at 2:25 PM, Tom Keffer  wrote:
> 
> Can't speak for the problem with forecast, but for your 
> CERTIFICATE_VERIFY_FAILED error, try refreshing the certificates on your 
> machine:
> 
> sudo apt-get update
> sudo apt-get install --reinstall ca-certificates
> 
> 
> On Fri, Aug 4, 2023 at 2:13 PM David Barto  <mailto:ba...@kdbarto.org>> wrote:
>> But only after I changed my password on the Wunderground.com 
>> <http://wunderground.com/> site because they asked me to. (Bas..rds)
>> 
>> So it went from fine:
>> Aug  1 20:43:15 Magrathea weewx[58335]: manager: Added record 2023-08-01 
>> 20:43:00 PDT (1690947780) to database 'weewx.sdb'
>> Aug  1 20:43:15 Magrathea weewx[58335]: manager: Added record 2023-08-01 
>> 20:43:00 PDT (1690947780) to daily summary in 'weewx.sdb'
>> Aug  1 20:43:15 Magrathea weewx[58335]: restx: CWOP: wait interval (240 < 
>> 600) has not passed for record 2023-08-01 20:43:00 PDT (1690947780)
>> Aug  1 20:43:15 Magrathea weewx[58335]: restx: StationRegistry: wait 
>> interval (85440 < 604800) has not passed for record 2023-08-01 20:43:00 PDT 
>> (1690947780)
>> Aug  1 20:43:16 Magrathea weewx[58335]: forecast: WUThread: WU: failed 
>> attempt 1 to download forecast: HTTP Error 503: Service Unavailable
>> Aug  1 20:43:18 Magrathea weewx[58335]: forecast: WUThread: WU: failed 
>> attempt 2 to download forecast: HTTP Error 503: Service Unavailable
>> Aug  1 20:43:19 Magrathea weewx[58335]: forecast: WUThread: WU: failed 
>> attempt 3 to download forecast: HTTP Error 503: Service Unavailable
>> Aug  1 20:43:19 Magrathea weewx[58335]: forecast: WUThread: WU: failed to 
>> download forecast
>> Aug  1 20:43:19 Magrathea weewx[58335]: forecast: WUThread: WU: no forecast 
>> data for KCAPOWAY187 from http://api.wunderground.com/api
>> 
>> to this:
>> 
>> Aug  4 00:57:18 Magrathea weewx[58335]: manager: Added record 2023-08-04 
>> 00:57:00 PDT (1691135820) to database 'weewx.sdb'
>> Aug  4 00:57:18 Magrathea weewx[58335]: manager: Added record 2023-08-04 
>> 00:57:00 PDT (1691135820) to daily summary in 'weewx.sdb'
>> Aug  4 00:57:18 Magrathea weewx[58335]: restx: StationRegistry: wait 
>> interval (273480 < 604800) has not passed for record 2023-08-04 00:57:00 PDT 
>> (1691135820)
>> Aug  4 00:57:18 Magrathea weewx[58335]: restx: CWOP: wait interval (480 < 
>> 600) has not passed for record 2023-08-04 00:57:00 PDT (1691135820)
>> Aug  4 00:57:19 Magrathea weewx[58335]: restx alert: Wunderground-PWS: 
>> Failed upload attempt 1: > certificate verify failed (_ssl.c:581)>
>> Aug  4 00:57:19 Magrathea weewx[58335]: forecast: WUThread: WU: failed 
>> attempt 1 to download forecast: HTTP Error 503: Service Unavailable
>> Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: failed 
>> attempt 2 to download forecast: HTTP Error 503: Service Unavailable
>> Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: failed 
>> attempt 3 to download forecast: HTTP Error 503: Service Unavailable
>> Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: failed to 
>> download forecast
>> Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: no forecast 
>> data for KCAPOWAY187 from http://api.wunderground.com/api
>> 
>> And I stopped publishing.
>> 
>> Which certificate is it complaining about and how would I find/create a 
>> proper certificate.
>> Note: Version 3.9.2 (yeah, old and my Mac I’m using has a very old python on 
>> it)
>> Local updates are fine: http://www.kdbarto.org/Weather/Current_Plus.htm
>> 
>>  David
>> 
>> 
>> ...well over half of the time you spend working on a project (on the order 
>> of 70 percent)
>> is spent thinking, and no tool, no matter how advanced, can think for you.
>> Consequently, even if a tool did everything except the thinking for you -- 
>> if it wrote 100 percent of the code,
>> wrote 100 percent of the documentation, did 100 percent of the testing, 
>> burned the CD-ROMs,
>> put them in boxes, and mailed them to your customers -- the best you could 
>> hope for would
>> be a 30 percent improvement in productivity. In order to do better than 
>> that, you have to
>> change the way you think.
>> --Fred Brooks
>> David Barto
>> ba...@kdbarto.org <mailto:ba...@kdbarto.org>
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to t

[weewx-user] Certificate Verify failed

2023-08-04 Thread David Barto

But only after I changed my password on the Wunderground.com 
<http://wunderground.com/> site because they asked me to. (Bas..rds)

So it went from fine:
Aug  1 20:43:15 Magrathea weewx[58335]: manager: Added record 2023-08-01 
20:43:00 PDT (1690947780) to database 'weewx.sdb'
Aug  1 20:43:15 Magrathea weewx[58335]: manager: Added record 2023-08-01 
20:43:00 PDT (1690947780) to daily summary in 'weewx.sdb'
Aug  1 20:43:15 Magrathea weewx[58335]: restx: CWOP: wait interval (240 < 600) 
has not passed for record 2023-08-01 20:43:00 PDT (1690947780)
Aug  1 20:43:15 Magrathea weewx[58335]: restx: StationRegistry: wait interval 
(85440 < 604800) has not passed for record 2023-08-01 20:43:00 PDT (1690947780)
Aug  1 20:43:16 Magrathea weewx[58335]: forecast: WUThread: WU: failed attempt 
1 to download forecast: HTTP Error 503: Service Unavailable
Aug  1 20:43:18 Magrathea weewx[58335]: forecast: WUThread: WU: failed attempt 
2 to download forecast: HTTP Error 503: Service Unavailable
Aug  1 20:43:19 Magrathea weewx[58335]: forecast: WUThread: WU: failed attempt 
3 to download forecast: HTTP Error 503: Service Unavailable
Aug  1 20:43:19 Magrathea weewx[58335]: forecast: WUThread: WU: failed to 
download forecast
Aug  1 20:43:19 Magrathea weewx[58335]: forecast: WUThread: WU: no forecast 
data for KCAPOWAY187 from http://api.wunderground.com/api

to this:

Aug  4 00:57:18 Magrathea weewx[58335]: manager: Added record 2023-08-04 
00:57:00 PDT (1691135820) to database 'weewx.sdb'
Aug  4 00:57:18 Magrathea weewx[58335]: manager: Added record 2023-08-04 
00:57:00 PDT (1691135820) to daily summary in 'weewx.sdb'
Aug  4 00:57:18 Magrathea weewx[58335]: restx: StationRegistry: wait interval 
(273480 < 604800) has not passed for record 2023-08-04 00:57:00 PDT (1691135820)
Aug  4 00:57:18 Magrathea weewx[58335]: restx: CWOP: wait interval (480 < 600) 
has not passed for record 2023-08-04 00:57:00 PDT (1691135820)
Aug  4 00:57:19 Magrathea weewx[58335]: restx alert: Wunderground-PWS: Failed 
upload attempt 1: 
Aug  4 00:57:19 Magrathea weewx[58335]: forecast: WUThread: WU: failed attempt 
1 to download forecast: HTTP Error 503: Service Unavailable
Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: failed attempt 
2 to download forecast: HTTP Error 503: Service Unavailable
Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: failed attempt 
3 to download forecast: HTTP Error 503: Service Unavailable
Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: failed to 
download forecast
Aug  4 00:57:20 Magrathea weewx[58335]: forecast: WUThread: WU: no forecast 
data for KCAPOWAY187 from http://api.wunderground.com/api

And I stopped publishing.

Which certificate is it complaining about and how would I find/create a proper 
certificate.
Note: Version 3.9.2 (yeah, old and my Mac I’m using has a very old python on it)
Local updates are fine: http://www.kdbarto.org/Weather/Current_Plus.htm

David


...well over half of the time you spend working on a project (on the order of 
70 percent)
is spent thinking, and no tool, no matter how advanced, can think for you.
Consequently, even if a tool did everything except the thinking for you -- if 
it wrote 100 percent of the code,
wrote 100 percent of the documentation, did 100 percent of the testing, burned 
the CD-ROMs,
put them in boxes, and mailed them to your customers -- the best you could hope 
for would
be a 30 percent improvement in productivity. In order to do better than that, 
you have to
change the way you think.
--Fred Brooks
David Barto
ba...@kdbarto.org


-- 
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/405339E8-0448-477E-9162-719CFCDD90E9%40kdbarto.org.

[weewx-user] weewx and Red Hat 9

2023-07-23 Thread David

 Hi,
Currently there are Red Hat 7 and 8 package releases available for weewx. 
Just wondering if there are any plans to package weewx for Red Hat 9.

Thanks
David

-- 
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/4c6232cf-9244-4d61-9848-fc88d9727d19n%40googlegroups.com.

Re: [weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

2023-06-29 Thread David Bätge

Thanks again to both, this got me an idea about how things are working!

I was asking about testing because my Station/Driver does not provide any 
"extra-fields" which are not saved, just fields included in the schema. I 
should have said that I am the Dave from the weewx-wdc Skin, whom John 
mentioned earlier, so I wanted to test this out when implementing it into 
the skin.

 I had a quick look at the Simulator driver provided by WeeWX. Looks like 
it could be easily modified to emit some extra fields for testing. 
Rainer Lang schrieb am Mittwoch, 28. Juni 2023 um 11:00:49 UTC+2:

> "Where is this data actually stored if not in the database? Is there any 
> way to test this out, besides actually using the said driver?"
>
> The data is not stored on a medium (e.g. disk) but just kept in memory 
> during the runtime of the program - and even there
> only as long as the program logic allows.
>
> Maybe the use of other terms will make it clearer if you are not familiar 
> with the Python programming language and its jargon.
> A dictionary in Python is a defined (potentially complex) data structure 
> of the same or different data types.
> These structures have different names in different programming languages. 
> They exist during the runtime of the program and are used
> to store data during runtime and also use this data during runtime. In 
> older programming languages like COBOL they were just a so-called
> record, a structured description of a memory area  (like a line in a 
> spreadsheet with different columns). 
> On a low level they are (from the point of view of the computer program 
> structured) 
> areas in memory which can be accessed and manipulated by the program code.
>
> If you want to do testing here, whatever are your ideas here and whatever 
> you want to do and for what purpose, you would have to create your
> own Python code which does what you want to do (your "testing"). 
> If you want to see the definition of these structures (Python 
> dictionaries),
> you will have to find the place where they are defined in the weewx 
> coding. 
> As Python is an interpreter language, the program code is available on 
> your computer.
>
> I'm not exactly clear on what you want to "test" here and what for ...
> - certain observations are stored or not stored, depending on what you 
> want and define (e.g. in weewx.conf)
> you want some observation to be stored, do it via the one of the two 
> approaches mentioned earlier,
> some are predefined by the database schema used, for others this would 
> need to be defined
> - you can also define what type of accumulation of this data you want 
> (also in weewx.conf)
> - when displaying the data you can also define (in skin.conf) what type of 
> depiction your want
>
> so much for the technical aspect - storing or not storing (storing here in 
> the sense of archiving into a database)
>
> as for the functional/logical aspect, you have to be clear on what the 
> information you want to archive means
> like in the example of the Ecowitt sensor "signal" observation which is an 
> indicator of successfully received and processed data packages 
> i.e. rather a signal quality indicator but not a signal strength 
> indicator. Even though on an Ecowitt console or app you can see "reception 
> bars",
> they cannot be compared to the signal reception bars of your mobile phone 
> (where they are an indicator of signal strength).
>
> If you want to enter more deeply into how Ecowitt consoles and sensors 
> work, I recommend to read the (whole !) wxforum.net thread
> https://www.wxforum.net/index.php?topic=40730.0
> In the field of battery and signal values there is unfortunately 
> (historically grown) not a consistent logic, especially with the batteries.
> You have to know which values each sensor provides and what they mean
>
> weewx is only using the output from these consoles through whichever 
> driver you are using to do so (Ecowitt Gateway, Interceptor, RTL433).
> It's up to you to make sense of it and what you choose to depict and how 
> to depict.
>
>
>
>
> On 28.06.2023 01:19, David Bätge wrote:
>
> Hi Rainer and Gary, 
>
> thank you both very much for the detailed explanation! I was not aware 
> that the $current tag also provides access to ALL observations of the 
> current record, regardless if they are archived or not. 
>
> Is the $current tag the only tag that provides this access? I assume the 
> $latest tag also does? 
>
> The $span tag would not be able to get values from those fields, since 
> it's an aggregate, right? Just asking because I have added a check for 
> displaying the battery states, like eg. #if $getattr(

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

2023-06-27 Thread David Bätge

Hi Rainer and Gary,

thank you both very much for the detailed explanation! I was not aware that 
the $current tag also provides access to ALL observations of the current 
record, regardless if they are archived or not. 

Is the $current tag the only tag that provides this access? I assume the 
$latest tag also does? 

The $span tag would not be able to get values from those fields, since it's 
an aggregate, right? Just asking because I have added a check for 
displaying the battery states, like eg. #if $getattr($span($day_delta=1, 
boundary='midnight'), 'wh31_ch1_batt').has_data which does not really make 
sense after understanding the internals, it should test against $current.

*[...] weewx includes values from the database and the current values of 
all observations in the current values table, also from those which have 
not been archived but are still available in memory from what has been 
provided from the driver [...]*
Where is this data actually stored if not in the database? Is there any way 
to test this out, besides actually using the said driver?

Sorry for a load of questions, please point me to the right documentation 
if I missed something in the guides. Thanks in advance and thanks again for 
enlighten me about this :) 
gjr80 schrieb am Dienstag, 27. Juni 2023 um 18:21:54 UTC+2:

> David,
>
> Some answers/comments below.
>
> On Tuesday, 27 June 2023 at 01:16:51 UTC+1 david@gmail.com wrote:
>
>
> Signal level observations: All *_sig observations like, wh31_ch1_sig, 
> wh31_ch2_sig, wh32_sig. I don't understand these: What is the signal 
> level here? Values seem to be `0` or `4` in that LOOP packet (looks like 
> battery state fields?). 
>
>  
> Ecowitt gateway signal levels are a pseudo-signal levels at best; the 
> number represents the number of the last four data packets from the sensor 
> that were successfully received/decoded. So most of the time, if the 
> sensors have a reliable connection to the gateway device, you will see a 4, 
> on startup you will see 0 and it will ramp up to 4 if all sensors connect 
> successfully and reliably. The number bears no reference to the sensor 
> signal level received by the gateway device or emitted by the sensor.
>  
>
> So the problem with all these observations is basically (as far as I 
> understand, please correct me if I am wrong): WeeWX does not know about 
> them and does not save them to the database (but you will need this data to 
> show plots of the battery voltages for the last week for example). There 
> should be two ways to overcome this:
>
> 1. Add the fields provided by the GW1000 driver to the database, see 
> http://weewx.com/docs/latest/customizing.htm#Modifying_an_existing_database
> 2. Map the GW1000 fields to WeeWX schema fields (see 
> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py#L16) 
> I assume that was somehow done for a short period of time because e.g. 
> rxCheckPercent or consBaterryVoltage are showing/having data for a few 
> days!?)
>
> @Gary I don't quite understand what you have written about that:
>
> *It is not necessary to do so if only displaying current values (ie values 
> from the current archive record)*
>
>  
> A quick and simplified WeeWX data flow 101. A WeeWX driver gathers data 
> from a station/sensors and emits loop packets on a regular and frequent 
> basis. WeeWX accumulates these loop packets and at the end of an archive 
> period WeeWX synthesises an archive record from the accumulated loop 
> packets, this record is known as the current archive record. WeeWX saves 
> the current archive record to database, but only those fields that are 
> common to the WeeWX database schema and the current archive record. WeeWX 
> then generates reports. Note, there are usually a number of additional 
> WeeWX services that 'do things' (eg quality control, calculate derived 
> values etc) to the loop packets and archive records before they are 
> accumulated/saved to database.
>
> When WeeWX generates reports all fields in the current archive record are 
> available for use in WeeWX generated reports via the $current tag, 
> irrespective of whether the field was saved to database or not. So if you 
> wish to include only the current value of a field in a WeeWX report there 
> is no need to save that field to the database, but if you wish to display 
> any sort of historical data (eg an aggregate in a report or plot historical 
> values) for a field you need to save the field to database. For example, 
> generally folks want to display max/min values of outside temperature or 
> plot outside temperature over some period so outTemp is usually saved to 
> database. However, you may only wish to display the current signal level 
> value for a g

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

2023-06-26 Thread David Bätge

Hi Gary and Jon,

I just got some time to look into this (and also made some notes for 
myself):

First of all, the GW1000 driver provides a lot of sensor information, the 
complete list is:

*Batteries*:
wh31_ch1_batt
wh31_ch2_batt
wh32_batt
wh40_batt
wh41_ch1_batt
wh51_ch1_batt
wh57_batt
ws80_batt
ws90_batt

*Signals*:
wh31_ch1_sig
wh31_ch2_sig
wh32_sig
wh40_sig
wh41_ch1_sig
wh51_ch1_sig
wh57_sig
ws80_sig
ws90_sig


Here is the complete LOOP package with relevant values:
{
   'wh31_ch1_batt': '0',
   'wh31_ch1_sig': '4',
   'wh31_ch2_batt': '0',
   'wh31_ch2_sig': '4',
   'wh32_batt': '0',
   'wh32_sig': '4',
   'wh40_batt': '1.39',
   'wh40_sig': '4',
   'wh41_ch1_batt': '5',
   'wh41_ch1_sig': '4',
   'wh51_ch1_batt': '1.3',
   'wh51_ch1_sig': '4',
   'wh57_batt': '4',
   'wh57_sig': '4',
   'ws80_batt': 'None',
   'ws80_sig': '0',
   'ws90_batt': '2.86',
   'ws90_sig': '4',
}

To be honest, I don't quite understand all of the fields, but I will try to 
give an explanation and how to configure these fields in weewx-wdc:

Observations that show something like "Battery OK" or "Battery LOW" (where 
0 is OK and 1 is LOW): `wh31_ch1_batt, wh31_ch2_batt, wh32_batt`, and 
`wh41_ch1_batt, wh57_batt` (see 
https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states). This 
kind of observation needs to be added to 
[DisplayOptions]sensor_battery_status in skin.conf.

*Note to me:* wh41_ch1_batt, wh57_batt using another representation of 
Battery status, see 
https://github.com/gjr80/weewx-gw1000/blob/master/supplementary/skins/Seasons/sensors.inc
 
and 
https://github.com/gjr80/weewx-gw1000/wiki/Adapting-the-Seasons-skin-to-display-battery-states
 
(There are a few tweaks needed to support these fields)

Signal level observations: All *_sig observations like, wh31_ch1_sig, 
wh31_ch2_sig, wh32_sig. I don't understand these: What is the signal level 
here? Values seem to be `0` or `4` in that LOOP packet (looks like battery 
state fields?). 

Battery Voltages observations: wh40_batt, wh51_ch1_batt, ws80_batt, 
ws90_batt. These should be added to any of 
[DisplayOptions]sensor_stat_tile_observations, 
[DisplayOptions]sensor_diagram_observations or 
[DisplayOptions]sensor_table_observations in skin.conf.

So the problem with all these observations is basically (as far as I 
understand, please correct me if I am wrong): WeeWX does not know about 
them and does not save them to the database (but you will need this data to 
show plots of the battery voltages for the last week for example). There 
should be two ways to overcome this:

1. Add the fields provided by the GW1000 driver to the database, see 
http://weewx.com/docs/latest/customizing.htm#Modifying_an_existing_database
2. Map the GW1000 fields to WeeWX schema fields (see 
https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py#L16) 
I assume that was somehow done for a short period of time because e.g. 
rxCheckPercent or consBaterryVoltage are showing/having data for a few 
days!?)

@Gary I don't quite understand what you have written about that:

*It is not necessary to do so if only displaying current values (ie values 
from the current archive record)*

How would you show fields like wh41_ch1_batt from the current archive 
record when the data is not saved? Am I missing something? 
gjr80 schrieb am Dienstag, 6. Juni 2023 um 13:32:47 UTC+2:

> Jon,
>
> No problems. The console output shows the Ecowitt gateway driver is 
> populating loop packets with sensor status data, eg ws90_sig, wh57_batt 
> etc. I assume the sensor data is complete for all sensors registered with 
> your gateway device (I cannot tell this, only you can). WeeWX is then 
> accumulating this data and it appears in WeeWX generated archive records.
>
> Looking at the weewx-wdc GitHub page it appears to use a similar system to 
> the Seasons skins for displaying sensor status data. The default fields to 
> be displayed are set in sensor-status.html.tmpl and these can be 
> overridden in skin.conf. The default appears to include fields such as 
> rxCheckPercent, consBatteryVoltage, inTempBatteryStatus, rainBatteryStatus 
> etc. None of the Ecowitt sensor state fields are included so I expect you 
> need to override/augment the sensor state fields to be displayed in 
> skin.conf. How you do this (ie which settings to adjust) is best 
> discussed with the skin author.
>
> On thing you will need to consider is whether or not to save the sensor 
> state data to archive. It is not necessary to do so if only displaying 
> current values (ie values from the current archive record), but if you wish 
> to display any aggregates based on historical data you will need to do so. 
> Fortunately it is easy to do, just modify your database schema using 
> wee_database to include the desired fields and WeeWX will take care of 
> the rest. Refer to Modifying an existing database 
>  
> in the Customization Guide.

[weewx-user] Moving to a different server

2023-06-16 Thread David Kozinn

I need to move my instance of weewx running on Ubuntu (20.04) to a 
different Ubuntu server on my local network. I'm planning to do a fresh 
install on the new server then copy over my weewx.conf file and re-install 
the extensions. I don't want to loose my old data, is copying 
/var/lib/weewx.sdb to the new machine sufficient or do I need to do 
anything else? The web server is on a different machine which will not 
change.

Thanks.

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

Re: [weewx-user] Re: WDC Skin

2023-06-08 Thread David Bätge

Hi Greg!  Please set the base_path in skin.conf to '/wdc/':

base_path = /wdc/

See 
https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
 
and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras. This 
should resolve the problem.
Greg from Oz schrieb am Donnerstag, 8. Juni 2023 um 10:53:53 UTC+2:

> Hi,
>
> I am testing the wdc skin and have set the html document root to 
> /var/www/html/weather/wdc
> If I go to https://weather.ubeaut.work/wdc/ (because I am testing and 
> want to leave my other webpages) it shows the wdc index.html which is good.
> If I click on any of the menu items eg Today  week month it takes me to my 
> other web page. Yesterday doesn't work because on my other webpage there 
> isn't a yesterday web page.
> I suspect it is because of the $get_base_path which would be 
> https://weather.ubeaut.work in this case.
> How or where can I change this to be https://weather.ubeaut.work/wdc so I 
> can test it out?
>
> Thanks
>
>
> On Monday, 3 April 2023 at 00:31:31 UTC+10 gary@gmail.com wrote:
>
>> Version 3.1.1 has been released and this is now one of the nicest skins 
>> I've used.
>> Clear text, excellent graphs, histograms, live data from MQTT.
>> Scales well to tablets.
>> For my needs, replaced the Belchertown skin.
>> On Friday, August 5, 2022 at 10:43:52 AM UTC-4 Andrea Di Saverio wrote:
>>
>>> Sorry for my late replay.
>>>
>>> Yes, the suggestion solved my problem. I was not installing as root user.
>>> Thank you.
>>>
>>> Il giorno giovedì 4 agosto 2022 alle 01:46:26 UTC+2 david@gmail.com 
>>> ha scritto:
>>>
>>>> @disaveri Did this solve your problem?
>>>>
>>>> Btw: I released 2.0.1 which resolves the "non-web-root"-issue, the 
>>>> "Pressure diagram with inHg unit"-issue and includes a few other bugfixes: 
>>>> https://github.com/Daveiano/weewx-wdc/releases/tag/v2.0.1
>>>>
>>>> Thanks for your input!
>>>>
>>>> vince schrieb am Dienstag, 2. August 2022 um 00:54:05 UTC+2:
>>>>
>>>>> On Monday, August 1, 2022 at 3:32:23 PM UTC-7 disaveri...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>>  the root cause is possibly something else?
>>>>>>
>>>>>
>>>>> Yes.  The 'root' cause indeed. 
>>>>>
>>>>> See the  FAQ - 
>>>>> https://github.com/weewx/weewx/wiki/faq-permission-denied
>>>>>  
>>>>>
>>>>

-- 
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/211b9bac-f1ce-4ea3-9aae-0cc91af870a8n%40googlegroups.com.

Re: [weewx-user] Raspberry Pi ... What's happening?

2023-03-29 Thread David Lang

when covid hit, the Pi foundation made the mistake of thinking that demand would 
drop, and so they reduced their fab orders (and then the fabs had outages, 
causing the chip shortages)


Instead, demand spiked, and they have spent the last couple of years scrambling 
to re-establish volume production. They opted to prioritize business bulk 
purchases over retail use, and even then were in the odd position of trying to 
sell as few to each buisiness as they could (to be able to provide a steady 
supply to all their corporate buyers).


The supply has started to recover, and they expect full recovery in the last 
half of 2023 (and have put off any Pi5 development until 2024)


As for what you want to use, if the Pi 2 1G was happy running it, it's still 
supported with software updates, so there's not a big reason to replace it. But 
if you want to replace it, anything new with similar specs will do the job.


David Lang

 On Wed, 29 Mar 2023, Yves Martin wrote:


Date: Wed, 29 Mar 2023 07:24:44 -0700 (PDT)
From: Yves Martin 
Reply-To: weewx-user@googlegroups.com
To: weewx-user 
Subject: [weewx-user] Raspberry Pi ... What's happening?

Hi,

I've ordered 6 months ago 2 Raspberry Pi 4B 8GB, and they are still BO, and
the price triple since! It looks like, it becomes very difficult to get
this board now at a reasonable price.

What model of motherboard with how much memory on it, do you suggest for
weewx? I have here an old version (Raspberry Pi 2B 1GB) and it works well
but the board is 4-5 years old. It is time to upgrade. What is your
suggestion?

Ref : https://ymartin.com/meteo/about.html

*PS: I'm using an old version of weewx (v3.9.2), and I want to add a
AirQuality device to it, so I need to upgrade... *

Regards,

YMartin.com/meteo




--
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/6nr07s12-4nn1-s360-7r88-rn9s3313480n%40ynat.uz.

[weewx-user] Re: weewx-wdc Skin v3.0.0 available

2023-03-09 Thread David Bätge

That's indeed a big ask and I am afraid to say that this is out of scope of 
my spare free time, I am sorry about that.

At first, I thought there should be some extension already to pull in the 
Australian BOM data, but it seems there is none yet. What I found is 
this: 
https://github.com/weewx/weewx/wiki/Raspberry-Pi-weather-station-with-i2C-sensors#australian-weather-forecast-added-to-belchertown-skin
 

A Post about integrating the data into the Belchertown skin - I have not 
had a look over the files, sorry, but this could be a potential starting 
point. If anyone has the time/need for that, I would be happy to support 
that in some way (Wiki Posts, PR's).

Greg from Oz schrieb am Donnerstag, 9. März 2023 um 22:58:00 UTC+1:

> Thanks for looking at the caching issue.
> Also would it be possible to have Australian official forecast from the 
> Bureau of Meteorology (BOM)?
> I can get a json file from here:
> https://api.weather.bom.gov.au/v1/locations/r7hgdpk/forecasts/daily
>
> The forecast looks like this:
> https://weather.bom.gov.au/location/r67rt9q-moonbi
>
> I know that this would be a big ask but it would be great if it was 
> available.
> If I knew enough about how the programming worked I would do it myself.
>
>
> On Thursday, 9 March 2023 at 22:49:05 UTC+11 David Bätge wrote:
>
>> @greg 
>>
>> Thank you for all the feedback!
>>
>> So the time of the last rain is not yet displayed, but I have noted this, 
>> and will add it in a future release :)
>>
>> Yes, I think I found the reason why your radar image is not refreshing 
>> (cached) - that's a bug with the service worker of the skin. I will have a 
>> look at it and release a small bugfix update by the end of the week, there 
>> were some more bugs with 3.0.0 which need to be resolved.
>>
>> Greg from Oz schrieb am Donnerstag, 9. März 2023 um 10:30:43 UTC+1:
>>
>>> Also another observation is the radar graphic doesn't change in the 
>>> weather web page until I press F5 refresh.
>>> If I click the today link it reverts back to the wrong image.
>>> If I open a new browser tab and use this:
>>> https://weather.ubeaut.work/WEBCAM/radar.jpg?
>>> I get the correct radar image.
>>> Very strange.
>>>
>>> On Thursday, 9 March 2023 at 19:33:07 UTC+11 Greg from Oz wrote:
>>>
>>>> Hi,
>>>>
>>>> Is there a way to add the date and time for example to the radar html 
>>>> code?
>>>> The reason I ask is because the image is being cached but if the name 
>>>> changes I should get the latest image.
>>>>
>>>> This is what I meanbut it doesn't work.
>>>>     radar_html = 'https://weather.ubeaut.work/WEBCAM/radar.jpg?""$current.dateTime";>'
>>>>
>>>> My web site is here:
>>>> https://weather.ubeaut.work/index.html
>>>>
>>>> Thanks
>>>>
>>>>
>>>> On Thursday, 9 March 2023 at 00:06:03 UTC+11 Claudio wrote:
>>>>
>>>>> Well done! you did a good job
>>>>>
>>>>> Il giorno lunedì 6 marzo 2023 alle 20:22:15 UTC+1 David Bätge ha 
>>>>> scritto:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>>
>>>>>> I just wanted to inform you that a new version is available for the 
>>>>>> weewx-wdc 
>>>>>> skin <https://github.com/Daveiano/weewx-wdc> for download 
>>>>>> <https://github.com/Daveiano/weewx-wdc/releases/download/v3.0.0/weewx-wdc-v3.0.0.zip>
>>>>>> .
>>>>>>
>>>>>>
>>>>>> This release includes some big updates and refactoring:
>>>>>>
>>>>>>- Several Bugfixes and enhancements for weewx-forecast
>>>>>>- Show weather data for a specific day - Daily archive
>>>>>>- Make diagrams configurable per context (per period) / Refactor 
>>>>>>diagrams configuration. Diagrams can now be configured per context, 
>>>>>> eg. 
>>>>>>day, week or month. Per default, the day and week pages do not 
>>>>>> include the 
>>>>>>outTemp min/max/avg diagram anymore.
>>>>>>- Make show_min, show_max, show_sum configurable for stat tiles 
>>>>>>- Support for custom data_bindings
>>>>>>- Configurable Icons
>>>>>>- Configurable unit for diagrams
>>>>

[weewx-user] Re: weewx-wdc Skin v3.0.0 available

2023-03-09 Thread David Bätge

@greg 

Thank you for all the feedback!

So the time of the last rain is not yet displayed, but I have noted this, 
and will add it in a future release :)

Yes, I think I found the reason why your radar image is not refreshing 
(cached) - that's a bug with the service worker of the skin. I will have a 
look at it and release a small bugfix update by the end of the week, there 
were some more bugs with 3.0.0 which need to be resolved.

Greg from Oz schrieb am Donnerstag, 9. März 2023 um 10:30:43 UTC+1:

> Also another observation is the radar graphic doesn't change in the 
> weather web page until I press F5 refresh.
> If I click the today link it reverts back to the wrong image.
> If I open a new browser tab and use this:
> https://weather.ubeaut.work/WEBCAM/radar.jpg?
> I get the correct radar image.
> Very strange.
>
> On Thursday, 9 March 2023 at 19:33:07 UTC+11 Greg from Oz wrote:
>
>> Hi,
>>
>> Is there a way to add the date and time for example to the radar html 
>> code?
>> The reason I ask is because the image is being cached but if the name 
>> changes I should get the latest image.
>>
>> This is what I meanbut it doesn't work.
>> radar_html = 'https://weather.ubeaut.work/WEBCAM/radar.jpg
>> ?""$current.dateTime">'
>>
>> My web site is here:
>> https://weather.ubeaut.work/index.html
>>
>> Thanks
>>
>>
>> On Thursday, 9 March 2023 at 00:06:03 UTC+11 Claudio wrote:
>>
>>> Well done! you did a good job
>>>
>>> Il giorno lunedì 6 marzo 2023 alle 20:22:15 UTC+1 David Bätge ha scritto:
>>>
>>>> Hi all,
>>>>
>>>>
>>>> I just wanted to inform you that a new version is available for the 
>>>> weewx-wdc 
>>>> skin <https://github.com/Daveiano/weewx-wdc> for download 
>>>> <https://github.com/Daveiano/weewx-wdc/releases/download/v3.0.0/weewx-wdc-v3.0.0.zip>
>>>> .
>>>>
>>>>
>>>> This release includes some big updates and refactoring:
>>>>
>>>>- Several Bugfixes and enhancements for weewx-forecast
>>>>- Show weather data for a specific day - Daily archive
>>>>- Make diagrams configurable per context (per period) / Refactor 
>>>>diagrams configuration. Diagrams can now be configured per context, eg. 
>>>>day, week or month. Per default, the day and week pages do not include 
>>>> the 
>>>>outTemp min/max/avg diagram anymore.
>>>>- Make show_min, show_max, show_sum configurable for stat tiles 
>>>>- Support for custom data_bindings
>>>>- Configurable Icons
>>>>- Configurable unit for diagrams
>>>>- Configurable Rounding
>>>>- Configurable markers for diagrams
>>>>- Automatic Refresh (via http-equiv="refresh")
>>>>- Added new climatogram (combined chart consisting of rain as bar 
>>>>and temp as line) for statistics and yearly statistics pages
>>>>- Update radar_img to allow for raw HTML (for using eg. iFrames as 
>>>>radar maps)
>>>>
>>>>
>>>> Also included is "Support for combining different diagram types" (eg. 
>>>> line and bar). I added an own implementation of chart rendering based 
>>>> directly on D3.js <https://d3js.org/>, which will replace the current nivo 
>>>> library <https://nivo.rocks/> in a future release. The direct usage of 
>>>> D3 allows for really custom implementations, so I am very open to new 
>>>> ideas 
>>>> of visualizations.
>>>>
>>>>
>>>> Please see 
>>>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#ENABLE_D3_DIAGRAMS
>>>>  for 
>>>> more information if you want to test this out in v3.0.0.
>>>>
>>>>
>>>> Since this release includes a near rewrite of the skin.conf, you likely 
>>>> have to make some changes to it, if you had the skin very heavily 
>>>> customized in a previous version.
>>>>
>>>>
>>>> The wiki <https://github.com/Daveiano/weewx-wdc/wiki> was updated to 
>>>> include information about all the new features and configurations. If you 
>>>> encounter any problem or bug, just let me know!
>>>>
>>>>
>>>> Thank you all for your feedback/contributions to the skin!
>>>>
>>>>
>>>> Changelog/Download: 
>>>> https://github.com/Daveiano/weewx-wdc/releases/tag/v3.0.0
>>>>
>>>

-- 
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/46166dda-e6ad-4634-9159-2ea41cdbd235n%40googlegroups.com.

[weewx-user] weewx-wdc Skin v3.0.0 available

2023-03-06 Thread David Bätge

Hi all,

I just wanted to inform you that a new version is available for the weewx-wdc
skin for download

This release includes some big updates and refactoring:

- Several Bugfixes and enhancements for weewx-forecast
- Show weather data for a specific day - Daily archive
- Make diagrams configurable per context (per period) / Refactor
diagrams configuration. Diagrams can now be configured per context, eg.
day, week or month. Per default, the day and week pages do not include the
outTemp min/max/avg diagram anymore.
- Make show_min, show_max, show_sum configurable for stat tiles
- Support for custom data_bindings
- Configurable Icons
- Configurable unit for diagrams
- Configurable Rounding
- Configurable markers for diagrams
- Automatic Refresh (via http-equiv="refresh")
- Added new climatogram (combined chart consisting of rain as bar and
temp as line) for statistics and yearly statistics pages
- Update radar_img to allow for raw HTML (for using eg. iFrames as radar
maps)

Also included is "Support for combining different diagram types" (eg. line
and bar). I added an own implementation of chart rendering based directly
on D3.js , which will replace the current nivo library
in a future release. The direct usage of D3 allows
for really custom implementations, so I am very open to new ideas of
visualizations.

Please see
https://github.com/Daveiano/weewx-wdc/wiki/Configuration#ENABLE_D3_DIAGRAMS for
more information if you want to test this out in v3.0.0.

Since this release includes a near rewrite of the skin.conf, you likely
have to make some changes to it, if you had the skin very heavily
customized in a previous version.

The wiki was updated to
include information about all the new features and configurations. If you
encounter any problem or bug, just let me know!

Thank you all for your feedback/contributions to the skin!

Changelog/Download:
https://github.com/Daveiano/weewx-wdc/releases/tag/v3.0.0

--
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/a8759291-390e-4335-bbca-4f847c8b57e3n%40googlegroups.com.

Re: [weewx-user] Why are the Weather intervals (week, month, year) all off by one day?

2023-02-28 Thread David Bätge

*Now I recognize that when one is running a report that works in units of 
days, not instants of time, you might want to represent the end of the 
month as being 31-Jan-2010 (no time) and not 1-Feb-2010 00:00. *

*Thinking out loud here, we could create tags such as:*

*$week.last_day*
*$month.last_day*
*$year.last_day*


Yes, that's exactly how this question was born. The weewx-wdc skin 
generates a page for each period (week, month, year), for example, the month's 
page  has a heading like:

Monthly Weather Conditions
03/01/23 - 04/01/23

03/01/23 - 04/01/23 is the output from $month.start - $month.end.

*If you're really stuck, you can always custom format the end of the month 
like this:*

*#from time import strftime, localtime*
*Month ends at $strftime("%d-%b-%Y", $localtime($month.end.raw - 1))*


*Note the "- 1". That shoves the time into the previous day. The results 
will be 31-Jan-2010. *

That's a good solution to the actual problem, I was not sure about the 
internals of period handling but the explanations of Tom and Karen are 
making perfect sense, thank you. After understanding this, I think I will 
implement the small change :)
michael.k...@gmx.at schrieb am Dienstag, 28. Februar 2023 um 21:29:45 UTC+1:

> Ah! Ok! Nevermind. I probably never really get warm with google groups... 
> :^)
>
> Tom Keffer schrieb am Dienstag, 28. Februar 2023 um 20:43:57 UTC+1:
>
>> My comment was in response to Karen's comment.
>>
>> On Tue, Feb 28, 2023 at 10:58 AM michael.k...@gmx.at  
>> wrote:
>>
>>> Yes, I agree, but I am thinking a little bit out of the standard weewx 
>>> box. A calculated average month observation, computed by weewx, using the 
>>> local timezone, uploading to a static website will be lead to a common user 
>>> experience, regardless where it is viewed from. On the other hand, when you 
>>> compare https://www.kainzbauer.net/weather/Rif/en/ with 
>>> https://www.kainzbauer.net/weather/Rif/en/day.html you will probably 
>>> recognize that the live charts are in your browser time zone, the static 
>>> images in the stations local time zone. eCharts doesn't support setting a 
>>> time zone independently from the browsers (systems?) time zone. If I would 
>>> compute monthly average values in the front end, there would be a 
>>> difference, depending on the time zone settings of the viewer's system.
>>>
>>> Tom Keffer schrieb am Dienstag, 28. Februar 2023 um 19:43:34 UTC+1:
>>>
 If you regard a day as ending precisely at midnight, the convention is 
 the same for both archive intervals and for a day: exclusive on the left, 
 inclusive on the right. 

 A five-minute archive interval timestamped 11:35 includes all data from 
 just after 11:30 to precisely 11:35. In a similar manner, a day 
 timestamped 
 1-Feb-2010 includes all data from just after 31-Jan 00:00 to precisely 
 1-Feb 00:00.

 On Tue, Feb 28, 2023 at 9:53 AM Karen K  wrote:

> May be it worth mentioning the background that the archive interval is 
> open at the left end (start time) and closed at the right end (end time). 
> That is not uncommon. It is a widely used design. That is because it is 
> the 
> only way to combine values that summarize the archive interval with 
> actual 
> readings. Unfortunately the day is counted the other way round: It starts 
> at 00:00 and ends right before 00:00 the next day.
>
> Tom Keffer schrieb am Dienstag, 28. Februar 2023 um 18:02:30 UTC+1:
>
>> I assume you are referring to the tags $month.start and $month.end, 
>> the start and stop of the interval $month. See 
>> http://www.weewx.com/docs/customizing.htm#Start,_end,_and_dateTime
>>
>> Using the example from the Customizing Guide, if $month.end returned 
>> 31-Jan-2010, what time should it be? It can't be 00:00: we would be 
>> missing 
>> the whole day 31-Jan-2010. It also can't be 24:00: no such time exists. 
>>
>> So, it must be 1-Feb-2010 at midnight. The month runs right up to the 
>> instant the clock turns over into February.
>>
>> Now I recognize that when one is running a report that works in units 
>> of days, not instants of time, you might want to represent the end of 
>> the 
>> month as being 31-Jan-2010 (no time) and not 1-Feb-2010 00:00. 
>>
>> Thinking out loud here, we could create tags such as:
>>
>> $week.last_day
>> $month.last_day
>> $year.last_day
>>
>> but I'm not sure what they would return. While the tag $month.end 
>> returns a ValueHelper that holds a unix epoch time internally, 
>> that's not going to work for $month.last_day, because it will print 
>> 31-Jan-2010 00:00 --- not what we want. The user would have to always 
>> remember to custom format it to show only days --- no time. Something 
>> like 
>> $month.last_day.format("%d-%b-%Y"). That feels wrong.

[weewx-user] Re: WDC skin v2.3.3

2023-02-28 Thread David Bätge

Yes that's because of a change in how weewx handles delta times, see 
here: 
http://www.weewx.com/docs/upgrading.htm#Breaking_changes_for_skins_that_use_delta_times

I added a short question/answer in the skins wiki about 
that: https://github.com/Daveiano/weewx-wdc/wiki#faq
Jim Munro schrieb am Dienstag, 28. Februar 2023 um 18:49:07 UTC+1:

> There are some other implications see thread 
> https://groups.google.com/g/weewx-user/c/J0aF5mzxcrE/m/CrR36ww3AgAJ
>
> On Tuesday, February 28, 2023 at 12:31:56 a.m. UTC-5 Jim Munro wrote:
>
>> Looks like in foot.inc
>> that you need 
>> $gettext("WeeWX uptime"): $station.uptime
>> $gettext("Server uptime"): $station.os_uptime
>> if weewx is version <4.10.0
>> On Monday, February 27, 2023 at 10:17:28 p.m. UTC-5 Jim Munro wrote:
>>
>>> Its been a while.  But I have just reinstalled 2.3.3 in a vbox docker 
>>> image.  The problem with the header and side bar seem to be gone but the 
>>> footer uptime doesn't seem right.  Please see attached.  The vbox image has 
>>> only been running approx 30 min.
>>>   
>>>
>>> On Monday, February 27, 2023 at 8:12:52 p.m. UTC-5 David Bätge wrote:
>>>
>>>> Hi Jim, sorry for the late response. I am the author of the skin, do 
>>>> you have still problems with running v2.3.3? I could have a look at why 
>>>> the 
>>>> page header and left sidebar are missing.
>>>>
>>>> Jim Munro schrieb am Freitag, 3. Februar 2023 um 01:46:56 UTC+1:
>>>>
>>>>> After downloading and installing the WDC skin with  "wget -O 
>>>>> "/tmp/weewx-wdc.zip" 
>>>>> https://github.com/Daveiano/weewx-wdc/releases/download/v2.3.3/weewx-wdc-v2.3.3.zip";
>>>>>  
>>>>> and installing it per instructions,  the index.html page header and left 
>>>>> hand side bar would disappear (readings and charts seemed ok) after an 
>>>>> archive update.  No error message in the log.  I did see the header and 
>>>>> side bar for a short time but it soon disappeared.
>>>>> Removing v2.3.3 and installing v2.3.2 seemed to fix the problem.  
>>>>> Weewx 4.9.1 was running
>>>>> as a container on a docker host.
>>>>>
>>>>

-- 
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/5743879b-1ec1-4371-bc6e-cef166e33ce0n%40googlegroups.com.

[weewx-user] Re: WDC skin v2.3.3

2023-02-27 Thread David Bätge

Hi Jim, sorry for the late response. I am the author of the skin, do you 
have still problems with running v2.3.3? I could have a look at why the 
page header and left sidebar are missing.

Jim Munro schrieb am Freitag, 3. Februar 2023 um 01:46:56 UTC+1:

> After downloading and installing the WDC skin with  "wget -O 
> "/tmp/weewx-wdc.zip" 
> https://github.com/Daveiano/weewx-wdc/releases/download/v2.3.3/weewx-wdc-v2.3.3.zip";
>  
> and installing it per instructions,  the index.html page header and left 
> hand side bar would disappear (readings and charts seemed ok) after an 
> archive update.  No error message in the log.  I did see the header and 
> side bar for a short time but it soon disappeared.
> Removing v2.3.3 and installing v2.3.2 seemed to fix the problem.  Weewx 
> 4.9.1 was running
> as a container on a docker host.
>

-- 
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/eac4ef23-8a50-4f07-9438-dad9e99a06f6n%40googlegroups.com.

[weewx-user] Re: Weather Forecast

2023-02-03 Thread David Schulz

Thanks for the work and the great plugin. I will update and test today.

kk44...@gmail.com schrieb am Donnerstag, 2. Februar 2023 um 16:11:42 UTC+1:

> Thanks to Open-Meteo  and Hoetzgit 
>  the WeeWX extension weewx-DWD 
>  is not 
> restricted to Germany any more. You can now create weather forecasts for 
> every place of the world and include them in your skin by the #include 
> directive. Additionally, Belchertown users can directly replace the Aeris 
> forecast by the forecast of other big weather services including DWD, 
> MeteoFrance, and NOAA.
>
> Weekday names and compass directions are actually available in german, 
> English, french, italian, and czech.
>
> The publicly available readings of the DWD (Germany) and ZAMG (Austria) 
> weather stations can be included into the WeeWX archive record for display 
> and saving.
>
> See the Readme 
>  (for 
> german speaking users Readme-de ) and 
> the Wiki  for more details.
>
> (Remark: Using data provided by Open-Meteo requires linking to their 
> website. And the weather services have their own terms and conditions, too. 
> Please observe them when displaying their data in public.)
>

-- 
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/25aff743-2f22-4d12-941e-f8c1b49ce0d3n%40googlegroups.com.

[weewx-user] Re: Missing Raindata after import

thx

David Schulz schrieb am Sonntag, 15. Januar 2023 um 00:23:42 UTC+1:

> Jepp. Got it...
>
> decimal = ','
>
> gjr80 schrieb am Sonntag, 15. Januar 2023 um 00:18:03 UTC+1:
>
>> If your import rainfall data is a per row value and not a cumulative 
>> total then this is correct.
>>
>> Gary
>> On Sunday, 15 January 2023 at 09:14:27 UTC+10 schulz@gmail.com wrote:
>> I changed the config to...
>>
>> rain = discrete
>>
>

-- 
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/8a5fe65d-faf0-4a10-b998-6c7fc25677c3n%40googlegroups.com.

[weewx-user] Re: Missing Raindata after import

Jepp. Got it...

decimal = ','

gjr80 schrieb am Sonntag, 15. Januar 2023 um 00:18:03 UTC+1:

> If your import rainfall data is a per row value and not a cumulative total 
> then this is correct.
>
> Gary
> On Sunday, 15 January 2023 at 09:14:27 UTC+10 schulz@gmail.com wrote:
> I changed the config to...
>
> rain = discrete
>

-- 
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/043ee4b4-6c01-4104-b705-fcdfd800de51n%40googlegroups.com.

[weewx-user] Re: Missing Raindata after import

I changed the config to...

rain = discrete

gjr80 schrieb am Sonntag, 15. Januar 2023 um 00:06:43 UTC+1:

> Your import config file is telling wee_import the input rainfall field 
> contains cumulative data, so wee_import uses the difference between the 
> current row rainfall data and the previous row rainfall data to calculate 
> the WeeWX field rain. For the first row there is no previous row so rain 
> is set to None (also note that the 1January 2019 00:00 rain value is 
> considered by WeeWX as containing 2018 data (ie data covering the period 
> from 23:59:00 to 23:59:59 + 1 second on 31 December 2018). The second row 
> is is the first record containing 2019 data. It should calculate the rain 
> field as being 0.2 - 0.2 = 0.0, though from your database extract it 
> appears to have been set to None. This could be a corner case involving 
> the change of year, but as far as I know wee_import should handle change 
> of year without problem. I will need to look further at the wee_import 
> code. The third row will calculate rain as 0 - 0.2 = -0.2 which of course 
> is a nonsense and I believe wee_import would assume there has been a 
> counter overflow and set rain to 0.0. For the fourth row rain is calculated 
> as 0 - 0 = 0.0 which is what you see. 
>
> So other than the minor discrepancy at row two (for rain 0 and None are 
> essentially treated the same in WeeWX output) I think wee_import is 
> working as expected given the import data and import config settings. 
> Analysis of a larger sample of data involving non-zero rainfall data may 
> throw up more information.
>
> Gary
>
> On Sunday, 15 January 2023 at 08:40:05 UTC+10 schulz@gmail.com wrote:
>
>> I think I should add a period to all values, not a comma.
>>
>> David Schulz schrieb am Samstag, 14. Januar 2023 um 23:35:21 UTC+1:
>>
>>> There should actually be values in there.
>>>
>>> echo "SELECT dateTime, rain FROM archive" | sqlite3 
>>> /var/lib/weewx/weewx.sdb
>>> 1546297200|
>>> 1546297260|
>>> 1546297320|0.0
>>> 1546297380|0.0
>>>
>>> DatumZeit;Temp;Feuchte;Luftdruck;Regen;Wind;Richtung;Windboeen
>>> 01.01.2019 00:00;6,9;97;1026,6;0,2;4,7;242;9,7
>>> 01.01.2019 00:01;6,9;97;1026,6;0,2;4,7;251;7,9
>>> 01.01.2019 00:02;6,9;97;1026,6;0;4,7;250;7,9
>>> 01.01.2019 00:03;6,9;97;1026,6;0;4,7;245;4,7
>>>
>>>
>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:19:12 UTC+1:
>>>
>>>> OK. Let's go straight to the horses head, what happens when you 
>>>> manually query the database archive table for the period concerned. Do 
>>>> each 
>>>> of the rows show the correct rainfall data or is it missing?
>>>>
>>>> Gary
>>>>
>>>> On Sunday, 15 January 2023 at 08:06:20 UTC+10 schulz@gmail.com 
>>>> wrote:
>>>>
>>>>> Thanks for the info. But for testing I delete every time the whole DB 
>>>>> and the NOAA reports. I have a Weewx test environment specifically for 
>>>>> this.
>>>>>
>>>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:03:41 UTC+1:
>>>>>
>>>>>> You need to be very careful when using the NOAA format reports to 
>>>>>> verify the import of historical data, this is because only the current 
>>>>>> month and current year reports are updated each report cycle. Historical 
>>>>>> reports are not updated so will not reflect and changes to earlier data. 
>>>>>> The sample data you provided is from January 2019 so I am guessing you 
>>>>>> did 
>>>>>> not import into the current month and year on your system. Try deleting 
>>>>>> all 
>>>>>> of your NOAA format reports from your WeeWX system, they will all be 
>>>>>> re-generated on the next report cycle based on the current database data.
>>>>>>
>>>>>> Gary 
>>>>>>
>>>>>> On Sunday, 15 January 2023 at 07:06:08 UTC+10 schulz@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> [image: 2023-01-14 22_05_47-Blub.png]
>>>>>>>
>>>>>>> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:
>>>>>>>
>>>>>>>> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
>>>>>>>> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils 
>>>>>>>> package is deprec

[weewx-user] Re: Missing Raindata after import

...Dots instead of comma...



David Schulz schrieb am Samstag, 14. Januar 2023 um 23:58:07 UTC+1:

> I think so, because now the graphs are also generated better. But feel 
> free to test.
>
> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:50:58 UTC+1:
>
>> No, commas are fine. If the commas were the problem wee_import would be 
>> failing hard. Let me finish working through your data.
>>
>> Gary
>> On Sunday, 15 January 2023 at 08:40:05 UTC+10 schulz@gmail.com wrote:
>>
>>> I think I should add a period to all values, not a comma.
>>>
>>> David Schulz schrieb am Samstag, 14. Januar 2023 um 23:35:21 UTC+1:
>>>
>>>> There should actually be values in there.
>>>>
>>>> echo "SELECT dateTime, rain FROM archive" | sqlite3 
>>>> /var/lib/weewx/weewx.sdb
>>>> 1546297200|
>>>> 1546297260|
>>>> 1546297320|0.0
>>>> 1546297380|0.0
>>>>
>>>> DatumZeit;Temp;Feuchte;Luftdruck;Regen;Wind;Richtung;Windboeen
>>>> 01.01.2019 00:00;6,9;97;1026,6;0,2;4,7;242;9,7
>>>> 01.01.2019 00:01;6,9;97;1026,6;0,2;4,7;251;7,9
>>>> 01.01.2019 00:02;6,9;97;1026,6;0;4,7;250;7,9
>>>> 01.01.2019 00:03;6,9;97;1026,6;0;4,7;245;4,7
>>>>
>>>>
>>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:19:12 UTC+1:
>>>>
>>>>> OK. Let's go straight to the horses head, what happens when you 
>>>>> manually query the database archive table for the period concerned. Do 
>>>>> each 
>>>>> of the rows show the correct rainfall data or is it missing?
>>>>>
>>>>> Gary
>>>>>
>>>>> On Sunday, 15 January 2023 at 08:06:20 UTC+10 schulz@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Thanks for the info. But for testing I delete every time the whole DB 
>>>>>> and the NOAA reports. I have a Weewx test environment specifically for 
>>>>>> this.
>>>>>>
>>>>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:03:41 UTC+1:
>>>>>>
>>>>>>> You need to be very careful when using the NOAA format reports to 
>>>>>>> verify the import of historical data, this is because only the current 
>>>>>>> month and current year reports are updated each report cycle. 
>>>>>>> Historical 
>>>>>>> reports are not updated so will not reflect and changes to earlier 
>>>>>>> data. 
>>>>>>> The sample data you provided is from January 2019 so I am guessing you 
>>>>>>> did 
>>>>>>> not import into the current month and year on your system. Try deleting 
>>>>>>> all 
>>>>>>> of your NOAA format reports from your WeeWX system, they will all be 
>>>>>>> re-generated on the next report cycle based on the current database 
>>>>>>> data.
>>>>>>>
>>>>>>> Gary 
>>>>>>>
>>>>>>> On Sunday, 15 January 2023 at 07:06:08 UTC+10 schulz@gmail.com 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> [image: 2023-01-14 22_05_47-Blub.png]
>>>>>>>>
>>>>>>>> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:
>>>>>>>>
>>>>>>>>> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
>>>>>>>>> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils 
>>>>>>>>> package is deprecated and slated for removal in Python 3.12. Use 
>>>>>>>>> setuptools 
>>>>>>>>> or check PEP 632 for potential alternatives
>>>>>>>>>   from distutils.version import StrictVersion
>>>>>>>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>>>>>>>> Starting wee_import...
>>>>>>>>> A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' 
>>>>>>>>> has been requested.
>>>>>>>>> The following options will be used:
>>>>>>>>>  config=/etc/weewx/weewx.conf, 
>>>>>>>>> import-config=/etc/weewx/import/csv.conf
>>>>>>>>>  source=/etc/weewx/import/EXP201901A.CSV, from=None, to=Non

[weewx-user] Re: Missing Raindata after import

I think so, because now the graphs are also generated better. But feel free 
to test.

gjr80 schrieb am Samstag, 14. Januar 2023 um 23:50:58 UTC+1:

> No, commas are fine. If the commas were the problem wee_import would be 
> failing hard. Let me finish working through your data.
>
> Gary
> On Sunday, 15 January 2023 at 08:40:05 UTC+10 schulz@gmail.com wrote:
>
>> I think I should add a period to all values, not a comma.
>>
>> David Schulz schrieb am Samstag, 14. Januar 2023 um 23:35:21 UTC+1:
>>
>>> There should actually be values in there.
>>>
>>> echo "SELECT dateTime, rain FROM archive" | sqlite3 
>>> /var/lib/weewx/weewx.sdb
>>> 1546297200|
>>> 1546297260|
>>> 1546297320|0.0
>>> 1546297380|0.0
>>>
>>> DatumZeit;Temp;Feuchte;Luftdruck;Regen;Wind;Richtung;Windboeen
>>> 01.01.2019 00:00;6,9;97;1026,6;0,2;4,7;242;9,7
>>> 01.01.2019 00:01;6,9;97;1026,6;0,2;4,7;251;7,9
>>> 01.01.2019 00:02;6,9;97;1026,6;0;4,7;250;7,9
>>> 01.01.2019 00:03;6,9;97;1026,6;0;4,7;245;4,7
>>>
>>>
>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:19:12 UTC+1:
>>>
>>>> OK. Let's go straight to the horses head, what happens when you 
>>>> manually query the database archive table for the period concerned. Do 
>>>> each 
>>>> of the rows show the correct rainfall data or is it missing?
>>>>
>>>> Gary
>>>>
>>>> On Sunday, 15 January 2023 at 08:06:20 UTC+10 schulz@gmail.com 
>>>> wrote:
>>>>
>>>>> Thanks for the info. But for testing I delete every time the whole DB 
>>>>> and the NOAA reports. I have a Weewx test environment specifically for 
>>>>> this.
>>>>>
>>>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:03:41 UTC+1:
>>>>>
>>>>>> You need to be very careful when using the NOAA format reports to 
>>>>>> verify the import of historical data, this is because only the current 
>>>>>> month and current year reports are updated each report cycle. Historical 
>>>>>> reports are not updated so will not reflect and changes to earlier data. 
>>>>>> The sample data you provided is from January 2019 so I am guessing you 
>>>>>> did 
>>>>>> not import into the current month and year on your system. Try deleting 
>>>>>> all 
>>>>>> of your NOAA format reports from your WeeWX system, they will all be 
>>>>>> re-generated on the next report cycle based on the current database data.
>>>>>>
>>>>>> Gary 
>>>>>>
>>>>>> On Sunday, 15 January 2023 at 07:06:08 UTC+10 schulz@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> [image: 2023-01-14 22_05_47-Blub.png]
>>>>>>>
>>>>>>> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:
>>>>>>>
>>>>>>>> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
>>>>>>>> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils 
>>>>>>>> package is deprecated and slated for removal in Python 3.12. Use 
>>>>>>>> setuptools 
>>>>>>>> or check PEP 632 for potential alternatives
>>>>>>>>   from distutils.version import StrictVersion
>>>>>>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>>>>>>> Starting wee_import...
>>>>>>>> A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' 
>>>>>>>> has been requested.
>>>>>>>> The following options will be used:
>>>>>>>>  config=/etc/weewx/weewx.conf, 
>>>>>>>> import-config=/etc/weewx/import/csv.conf
>>>>>>>>  source=/etc/weewx/import/EXP201901A.CSV, from=None, to=None
>>>>>>>>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>>>>>>>>  tranche=1000, interval=derive, 
>>>>>>>> date/time_string_format=%d.%m.%Y %H:%M
>>>>>>>>  delimiter=';', rain=cumulative, wind_direction=[-360.0, 360.0]
>>>>>>>>  UV=False, radiation=False
>>>>>>>> Using database binding 'wx_binding', which is bound to database 
&g

[weewx-user] Re: Missing Raindata after import

I think I should add a period to all values, not a comma.

David Schulz schrieb am Samstag, 14. Januar 2023 um 23:35:21 UTC+1:

> There should actually be values in there.
>
> echo "SELECT dateTime, rain FROM archive" | sqlite3 
> /var/lib/weewx/weewx.sdb
> 1546297200|
> 1546297260|
> 1546297320|0.0
> 1546297380|0.0
>
> DatumZeit;Temp;Feuchte;Luftdruck;Regen;Wind;Richtung;Windboeen
> 01.01.2019 00:00;6,9;97;1026,6;0,2;4,7;242;9,7
> 01.01.2019 00:01;6,9;97;1026,6;0,2;4,7;251;7,9
> 01.01.2019 00:02;6,9;97;1026,6;0;4,7;250;7,9
> 01.01.2019 00:03;6,9;97;1026,6;0;4,7;245;4,7
>
>
> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:19:12 UTC+1:
>
>> OK. Let's go straight to the horses head, what happens when you manually 
>> query the database archive table for the period concerned. Do each of the 
>> rows show the correct rainfall data or is it missing?
>>
>> Gary
>>
>> On Sunday, 15 January 2023 at 08:06:20 UTC+10 schulz@gmail.com wrote:
>>
>>> Thanks for the info. But for testing I delete every time the whole DB 
>>> and the NOAA reports. I have a Weewx test environment specifically for this.
>>>
>>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:03:41 UTC+1:
>>>
>>>> You need to be very careful when using the NOAA format reports to 
>>>> verify the import of historical data, this is because only the current 
>>>> month and current year reports are updated each report cycle. Historical 
>>>> reports are not updated so will not reflect and changes to earlier data. 
>>>> The sample data you provided is from January 2019 so I am guessing you did 
>>>> not import into the current month and year on your system. Try deleting 
>>>> all 
>>>> of your NOAA format reports from your WeeWX system, they will all be 
>>>> re-generated on the next report cycle based on the current database data.
>>>>
>>>> Gary 
>>>>
>>>> On Sunday, 15 January 2023 at 07:06:08 UTC+10 schulz@gmail.com 
>>>> wrote:
>>>>
>>>>> [image: 2023-01-14 22_05_47-Blub.png]
>>>>>
>>>>> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:
>>>>>
>>>>>> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
>>>>>> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils 
>>>>>> package is deprecated and slated for removal in Python 3.12. Use 
>>>>>> setuptools 
>>>>>> or check PEP 632 for potential alternatives
>>>>>>   from distutils.version import StrictVersion
>>>>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>>>>> Starting wee_import...
>>>>>> A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' has 
>>>>>> been requested.
>>>>>> The following options will be used:
>>>>>>  config=/etc/weewx/weewx.conf, 
>>>>>> import-config=/etc/weewx/import/csv.conf
>>>>>>  source=/etc/weewx/import/EXP201901A.CSV, from=None, to=None
>>>>>>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>>>>>>  tranche=1000, interval=derive, date/time_string_format=%d.%m.%Y 
>>>>>> %H:%M
>>>>>>  delimiter=';', rain=cumulative, wind_direction=[-360.0, 360.0]
>>>>>>  UV=False, radiation=False
>>>>>> Using database binding 'wx_binding', which is bound to database 
>>>>>> 'weewx.sdb'
>>>>>> Destination table 'archive' unit system is '0x01' (US).
>>>>>> Missing derived observations will be calculated.
>>>>>> All WeeWX UV fields will be set to None.
>>>>>> All WeeWX radiation fields will be set to None.
>>>>>> Starting import ...
>>>>>> Obtaining raw import data for period 1 ...
>>>>>> The following imported field-to-WeeWX field map will be used:
>>>>>>  source field 'DatumZeit' in units 'unix_epoch' --> WeeWX field 
>>>>>> 'dateTime'
>>>>>>  source field 'Temp' in units 'degree_C' --> WeeWX field 'outTemp'
>>>>>>  source field 'Feuchte' in units 'percent' --> WeeWX field 
>>>>>> 'outHumidity'
>>>>>>  source field 'Lu

[weewx-user] Re: Missing Raindata after import

There should actually be values in there.

echo "SELECT dateTime, rain FROM archive" | sqlite3 /var/lib/weewx/weewx.sdb
1546297200|
1546297260|
1546297320|0.0
1546297380|0.0

DatumZeit;Temp;Feuchte;Luftdruck;Regen;Wind;Richtung;Windboeen
01.01.2019 00:00;6,9;97;1026,6;0,2;4,7;242;9,7
01.01.2019 00:01;6,9;97;1026,6;0,2;4,7;251;7,9
01.01.2019 00:02;6,9;97;1026,6;0;4,7;250;7,9
01.01.2019 00:03;6,9;97;1026,6;0;4,7;245;4,7


gjr80 schrieb am Samstag, 14. Januar 2023 um 23:19:12 UTC+1:

> OK. Let's go straight to the horses head, what happens when you manually 
> query the database archive table for the period concerned. Do each of the 
> rows show the correct rainfall data or is it missing?
>
> Gary
>
> On Sunday, 15 January 2023 at 08:06:20 UTC+10 schulz@gmail.com wrote:
>
>> Thanks for the info. But for testing I delete every time the whole DB and 
>> the NOAA reports. I have a Weewx test environment specifically for this.
>>
>> gjr80 schrieb am Samstag, 14. Januar 2023 um 23:03:41 UTC+1:
>>
>>> You need to be very careful when using the NOAA format reports to verify 
>>> the import of historical data, this is because only the current month and 
>>> current year reports are updated each report cycle. Historical reports are 
>>> not updated so will not reflect and changes to earlier data. The sample 
>>> data you provided is from January 2019 so I am guessing you did not import 
>>> into the current month and year on your system. Try deleting all of your 
>>> NOAA format reports from your WeeWX system, they will all be re-generated 
>>> on the next report cycle based on the current database data.
>>>
>>> Gary 
>>>
>>> On Sunday, 15 January 2023 at 07:06:08 UTC+10 schulz@gmail.com 
>>> wrote:
>>>
>>>> [image: 2023-01-14 22_05_47-Blub.png]
>>>>
>>>> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:
>>>>
>>>>> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
>>>>> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils 
>>>>> package is deprecated and slated for removal in Python 3.12. Use 
>>>>> setuptools 
>>>>> or check PEP 632 for potential alternatives
>>>>>   from distutils.version import StrictVersion
>>>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>>>> Starting wee_import...
>>>>> A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' has 
>>>>> been requested.
>>>>> The following options will be used:
>>>>>  config=/etc/weewx/weewx.conf, 
>>>>> import-config=/etc/weewx/import/csv.conf
>>>>>  source=/etc/weewx/import/EXP201901A.CSV, from=None, to=None
>>>>>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>>>>>  tranche=1000, interval=derive, date/time_string_format=%d.%m.%Y 
>>>>> %H:%M
>>>>>  delimiter=';', rain=cumulative, wind_direction=[-360.0, 360.0]
>>>>>  UV=False, radiation=False
>>>>> Using database binding 'wx_binding', which is bound to database 
>>>>> 'weewx.sdb'
>>>>> Destination table 'archive' unit system is '0x01' (US).
>>>>> Missing derived observations will be calculated.
>>>>> All WeeWX UV fields will be set to None.
>>>>> All WeeWX radiation fields will be set to None.
>>>>> Starting import ...
>>>>> Obtaining raw import data for period 1 ...
>>>>> The following imported field-to-WeeWX field map will be used:
>>>>>  source field 'DatumZeit' in units 'unix_epoch' --> WeeWX field 
>>>>> 'dateTime'
>>>>>  source field 'Temp' in units 'degree_C' --> WeeWX field 'outTemp'
>>>>>  source field 'Feuchte' in units 'percent' --> WeeWX field 
>>>>> 'outHumidity'
>>>>>  source field 'Luftdruck' in units 'hPa' --> WeeWX field 
>>>>> 'barometer'
>>>>>  source field 'Regen' in units 'mm' --> WeeWX field 'rain'
>>>>>  source field 'Wind' in units 'km_per_hour' --> WeeWX field 
>>>>> 'windSpeed'
>>>>>  source field 'Richtung' in units 'degree_compass' --> WeeWX field 
>>&

[weewx-user] Re: Missing Raindata after import

Thanks for the info. But for testing I delete every time the whole DB and 
the NOAA reports. I have a Weewx test environment specifically for this.

gjr80 schrieb am Samstag, 14. Januar 2023 um 23:03:41 UTC+1:

> You need to be very careful when using the NOAA format reports to verify 
> the import of historical data, this is because only the current month and 
> current year reports are updated each report cycle. Historical reports are 
> not updated so will not reflect and changes to earlier data. The sample 
> data you provided is from January 2019 so I am guessing you did not import 
> into the current month and year on your system. Try deleting all of your 
> NOAA format reports from your WeeWX system, they will all be re-generated 
> on the next report cycle based on the current database data.
>
> Gary 
>
> On Sunday, 15 January 2023 at 07:06:08 UTC+10 schulz@gmail.com wrote:
>
>> [image: 2023-01-14 22_05_47-Blub.png]
>>
>> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:
>>
>>> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
>>> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils 
>>> package is deprecated and slated for removal in Python 3.12. Use setuptools 
>>> or check PEP 632 for potential alternatives
>>>   from distutils.version import StrictVersion
>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>> Starting wee_import...
>>> A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' has 
>>> been requested.
>>> The following options will be used:
>>>  config=/etc/weewx/weewx.conf, 
>>> import-config=/etc/weewx/import/csv.conf
>>>  source=/etc/weewx/import/EXP201901A.CSV, from=None, to=None
>>>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>>>  tranche=1000, interval=derive, date/time_string_format=%d.%m.%Y 
>>> %H:%M
>>>  delimiter=';', rain=cumulative, wind_direction=[-360.0, 360.0]
>>>  UV=False, radiation=False
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'weewx.sdb'
>>> Destination table 'archive' unit system is '0x01' (US).
>>> Missing derived observations will be calculated.
>>> All WeeWX UV fields will be set to None.
>>> All WeeWX radiation fields will be set to None.
>>> Starting import ...
>>> Obtaining raw import data for period 1 ...
>>> The following imported field-to-WeeWX field map will be used:
>>>  source field 'DatumZeit' in units 'unix_epoch' --> WeeWX field 
>>> 'dateTime'
>>>  source field 'Temp' in units 'degree_C' --> WeeWX field 'outTemp'
>>>  source field 'Feuchte' in units 'percent' --> WeeWX field 
>>> 'outHumidity'
>>>  source field 'Luftdruck' in units 'hPa' --> WeeWX field 'barometer'
>>>  source field 'Regen' in units 'mm' --> WeeWX field 'rain'
>>>  source field 'Wind' in units 'km_per_hour' --> WeeWX field 
>>> 'windSpeed'
>>>  source field 'Richtung' in units 'degree_compass' --> WeeWX field 
>>> 'windDir'
>>>  source field 'Windboeen' in units 'km_per_hour' --> WeeWX field 
>>> 'windGust'
>>> Raw import data read successfully for period 1.
>>> Mapping raw import data for period 1 ...
>>> Mapped 1440 records.
>>> Raw import data mapped successfully for period 1.
>>> Saving mapped data to archive for period 1 ...
>>> 1440 records identified for import.
>>> Proceeding will save all imported records in the WeeWX archive.
>>> Are you sure you want to proceed (y/n)? y
>>> Unique records processed: 1440; Last timestamp: 2019-01-01 23:59:00 CET 
>>> (1546383540)
>>> Mapped data saved to archive successfully ""for period 1.
>>> Calculating missing derived observations ...
>>> Processing record: 1440; Last record: 2019-01-02 00:00:00 CET 
>>> (1546383600)
>>> Recalculating daily summaries...
>>> Records processed: 1000; time: 2019-01-01 16:39:00 CET (1546357140)
>>> Finished recalculating daily summaries
>>> Finished calculating missing derived observations
>>> Finished import
>>> 1440 records were processed and 1440 unique records imported in 40.49 
>>> seconds.
>

[weewx-user] Re: Missing Raindata after import

[image: 2023-01-14 22_05_47-Blub.png]

David Schulz schrieb am Samstag, 14. Januar 2023 um 22:04:28 UTC+1:

> wee_import --verbose --import-config=/etc/weewx/import/csv.conf
> /usr/share/weewx/wee_import:719: DeprecationWarning: The distutils package 
> is deprecated and slated for removal in Python 3.12. Use setuptools or 
> check PEP 632 for potential alternatives
>   from distutils.version import StrictVersion
> Using WeeWX configuration file /etc/weewx/weewx.conf
> Starting wee_import...
> A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' has been 
> requested.
> The following options will be used:
>  config=/etc/weewx/weewx.conf, import-config=/etc/weewx/import/csv.conf
>  source=/etc/weewx/import/EXP201901A.CSV, from=None, to=None
>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>  tranche=1000, interval=derive, date/time_string_format=%d.%m.%Y %H:%M
>  delimiter=';', rain=cumulative, wind_direction=[-360.0, 360.0]
>  UV=False, radiation=False
> Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Missing derived observations will be calculated.
> All WeeWX UV fields will be set to None.
> All WeeWX radiation fields will be set to None.
> Starting import ...
> Obtaining raw import data for period 1 ...
> The following imported field-to-WeeWX field map will be used:
>  source field 'DatumZeit' in units 'unix_epoch' --> WeeWX field 
> 'dateTime'
>  source field 'Temp' in units 'degree_C' --> WeeWX field 'outTemp'
>  source field 'Feuchte' in units 'percent' --> WeeWX field 
> 'outHumidity'
>  source field 'Luftdruck' in units 'hPa' --> WeeWX field 'barometer'
>  source field 'Regen' in units 'mm' --> WeeWX field 'rain'
>  source field 'Wind' in units 'km_per_hour' --> WeeWX field 'windSpeed'
>  source field 'Richtung' in units 'degree_compass' --> WeeWX field 
> 'windDir'
>  source field 'Windboeen' in units 'km_per_hour' --> WeeWX field 
> 'windGust'
> Raw import data read successfully for period 1.
> Mapping raw import data for period 1 ...
> Mapped 1440 records.
> Raw import data mapped successfully for period 1.
> Saving mapped data to archive for period 1 ...
> 1440 records identified for import.
> Proceeding will save all imported records in the WeeWX archive.
> Are you sure you want to proceed (y/n)? y
> Unique records processed: 1440; Last timestamp: 2019-01-01 23:59:00 CET 
> (1546383540)
> Mapped data saved to archive successfully ""for period 1.
> Calculating missing derived observations ...
> Processing record: 1440; Last record: 2019-01-02 00:00:00 CET (1546383600)
> Recalculating daily summaries...
> Records processed: 1000; time: 2019-01-01 16:39:00 CET (1546357140)
> Finished recalculating daily summaries
> Finished calculating missing derived observations
> Finished import
> 1440 records were processed and 1440 unique records imported in 40.49 
> seconds.
> Those records with a timestamp already in the archive will not have been
> imported. Confirm successful import in the WeeWX log file.
>
> David Schulz schrieb am Samstag, 14. Januar 2023 um 22:03:34 UTC+1:
>
>> Hi,
>>
>> i want to import some old weatherdata via csv file, but after the import, 
>> the raindata is missing. i tried the import with "rain = cumulative / 
>> discrete".
>>
>> Here my config:
>>
>> source = CSV
>> ###
>> [CSV]
>> file = /etc/weewx/import/EXP201901A.CSV
>> delimiter = ;
>> interval = derive
>> qc = True
>> calc_missing = True
>> ignore_invalid_data = True
>> tranche = 1000
>> UV_sensor = False
>> solar_sensor = False
>> raw_datetime_format = %d.%m.%Y %H:%M
>> # rain = (discrete | cumulative)
>> rain = cumulative
>> wind_direction = -360,360
>> [[FieldMap]]
>> dateTime= DatumZeit, unix_epoch
>> outTemp = Temp, degree_C
>> outHumidity = Feuchte, percent
>> barometer   = Luftdruck, hPa
>> rain= Regen, mm
>> windSpeed   = Wind, km_per_hour
>> windDir = Richtung, degree_compass
>> windGust= Windboeen, km_per_hour
>>
>> And here some sample data.
>

[weewx-user] Re: Missing Raindata after import

wee_import --verbose --import-config=/etc/weewx/import/csv.conf
/usr/share/weewx/wee_import:719: DeprecationWarning: The distutils package 
is deprecated and slated for removal in Python 3.12. Use setuptools or 
check PEP 632 for potential alternatives
  from distutils.version import StrictVersion
Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
A CSV import from source file '/etc/weewx/import/EXP201901A.CSV' has been 
requested.
The following options will be used:
 config=/etc/weewx/weewx.conf, import-config=/etc/weewx/import/csv.conf
 source=/etc/weewx/import/EXP201901A.CSV, from=None, to=None
 dry-run=None, calc_missing=True, ignore_invalid_data=True
 tranche=1000, interval=derive, date/time_string_format=%d.%m.%Y %H:%M
 delimiter=';', rain=cumulative, wind_direction=[-360.0, 360.0]
 UV=False, radiation=False
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
All WeeWX UV fields will be set to None.
All WeeWX radiation fields will be set to None.
Starting import ...
Obtaining raw import data for period 1 ...
The following imported field-to-WeeWX field map will be used:
 source field 'DatumZeit' in units 'unix_epoch' --> WeeWX field 
'dateTime'
 source field 'Temp' in units 'degree_C' --> WeeWX field 'outTemp'
 source field 'Feuchte' in units 'percent' --> WeeWX field 'outHumidity'
 source field 'Luftdruck' in units 'hPa' --> WeeWX field 'barometer'
 source field 'Regen' in units 'mm' --> WeeWX field 'rain'
 source field 'Wind' in units 'km_per_hour' --> WeeWX field 'windSpeed'
 source field 'Richtung' in units 'degree_compass' --> WeeWX field 
'windDir'
 source field 'Windboeen' in units 'km_per_hour' --> WeeWX field 
'windGust'
Raw import data read successfully for period 1.
Mapping raw import data for period 1 ...
Mapped 1440 records.
Raw import data mapped successfully for period 1.
Saving mapped data to archive for period 1 ...
1440 records identified for import.
Proceeding will save all imported records in the WeeWX archive.
Are you sure you want to proceed (y/n)? y
Unique records processed: 1440; Last timestamp: 2019-01-01 23:59:00 CET 
(1546383540)
Mapped data saved to archive successfully ""for period 1.
Calculating missing derived observations ...
Processing record: 1440; Last record: 2019-01-02 00:00:00 CET (1546383600)
Recalculating daily summaries...
Records processed: 1000; time: 2019-01-01 16:39:00 CET (1546357140)
Finished recalculating daily summaries
Finished calculating missing derived observations
Finished import
1440 records were processed and 1440 unique records imported in 40.49 
seconds.
Those records with a timestamp already in the archive will not have been
imported. Confirm successful import in the WeeWX log file.

David Schulz schrieb am Samstag, 14. Januar 2023 um 22:03:34 UTC+1:

> Hi,
>
> i want to import some old weatherdata via csv file, but after the import, 
> the raindata is missing. i tried the import with "rain = cumulative / 
> discrete".
>
> Here my config:
>
> source = CSV
> ###
> [CSV]
> file = /etc/weewx/import/EXP201901A.CSV
> delimiter = ;
> interval = derive
> qc = True
> calc_missing = True
> ignore_invalid_data = True
> tranche = 1000
> UV_sensor = False
> solar_sensor = False
> raw_datetime_format = %d.%m.%Y %H:%M
> # rain = (discrete | cumulative)
> rain = cumulative
> wind_direction = -360,360
> [[FieldMap]]
> dateTime= DatumZeit, unix_epoch
> outTemp = Temp, degree_C
> outHumidity = Feuchte, percent
> barometer   = Luftdruck, hPa
> rain= Regen, mm
> windSpeed   = Wind, km_per_hour
> windDir = Richtung, degree_compass
> windGust= Windboeen, km_per_hour
>
> And here some sample data.
>
> DatumZeit;Temp;Feuchte;Luftdruck;Regen;Wind;Richtung;Windboeen
> 01.01.2019 00:00;6,9;97;1026,6;0,2;4,7;242;9,7
> 01.01.2019 00:01;6,9;97;1026,6;0,2;4,7;251;7,9
> 01.01.2019 00:02;6,9;97;1026,6;0,2;4,7;250;7,9
> 01.01.2019 00:03;6,9;97;1026,6;0,2;4,7;245;4,7
> 01.01.2019 00:04;6,9;97;1026,6;0;4,7;250;7,9
> 01.01.2019 00:05;6,9;97;1026,5;0;4,7;234;7,9
> 01.01.2019 00:06;6,9;97;1026,5;0;4,7;232;11,2
> 01.01.2019 00:07;7;97;1026,5;0;4,7;234;4,7
> 01.01.2019 00:08;7;97;1026,5;0;4,7;241;7,9
> 01.01.2019 00:09;7;97;1026,5;0;4,7;240;6,5
>

-- 
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/103cc457-012f-4d35-b606-3063563c40cen%40googlegroups.com.

[weewx-user] Missing Raindata after import