Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Paul Bartholdi]

Hello,

The move from python2 to python3 is a mess because of the way python is 
designed and the many incompatibilities between them.
I think what was done by the weewx developer was the right one, even the 
necessary one. But user need to be careful that just installing python3 
does not mean that all libraries/package are updated at the same time.
pyephem is a python package, but not part of the python package. It must be 
installed independently. 
I had to install (I use mysql/mariadb not sqlite3 as support dB):
 sudo apt install python-mysqldb
 sudo apt install python3-mysqldb
Hope this helps.
Thanks again to the installers!  Paul


Le lundi 4 mai 2020 23:31:15 UTC+2, Tom Keffer a écrit :
>
> The current pyephem broke the extended almanac, and I've held back that 
>> python 2.7 package. 
>>
>
> Sorry. I don't understand what you mean by "broke the extended almanac."
>
>> I'm having an issue with the annual "High Wind" speed value. Although the 
>> direction and time are there, the speed is the max speed for the current 
>> month (less than the earlier max wind speed event).
>>
>
> How about some details? Do you mean $year.wind.max gives a smaller value 
> than $month.wind.max? Something else? 
>
> What do you mean by "earlier max wind speed event? What was generated by 
> earlier versions of weewx? Something else?
>

-- 
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/cd9d71b1-b1f8-426b-b02e-495c53b8ca11%40googlegroups.com.

[weewx-user] CWOP: Exception

[Cat22]

weewx 4.0.0 on linux
I saw this in my weewx.log file while i had debug enabled:

DEBUG weewx.restx: CWOP: Exception  (timed out) 
when looking for response to tnc packet

Checking an previous log i see its fairly frequent.
I suspect its behind the missing Temperature and Dew Point graph data at 
CWOP

See here: http://www.findu.com/cgi-bin/wxpage.cgi?call=DW0249&last=12

Any idea whats causing it?
TIA

-- 
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/1fa19b13-e80e-4b8a-a127-ac82f826d129%40googlegroups.com.

Re: [weewx-user] Re: Forecast from UKMO no longer working after upgrade to V4 of weewx

[Phil Owers]

Just leave it. P

On Mon, 4 May 2020, 16:39 Ian Flipp,  wrote:

> Thank you,
>
> That's sorted it :-) Everything now working as expected.
>
> Is there a way of closing the thread or do I just leave it hanging?
>
> Cheers,
> Ian
>
> --
> 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/809e0555-7111-463b-b5f1-13748fa27597%40googlegroups.com
> .
>

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

[weewx-user] Re: Version 4.0 is (finally) here!

[Keimpe Bleeker]

Hi Tom, All,

>From December I had Weewx V3 with Belchertown running on the Simulator 
without any problems. Because of the import of the Wunderground history I 
have been waiting for the transition from WeatherDisplay & WordPerss to 
Weewx to V4.

I've been fiddling for days now to get things going; tried upgrading from 
V3 (/etc/weewx/ ...) to V4, of course with all the Python prerequisites and 
the setup.py method but without success. I cleaned up the RPi from A to Z 
and tried the standard installation without any changes in the Setup.cfg 
but no success. 

Today I made a fresh start with a clean RPi and Weewx installed by default 
in /home/weewx/. Weewx seems to run well -basic skin, without Belchertown-, 
but now the utilities don't work: 'sudo / home / weewx / bin / wee_debug 
verbosity = 1' results in 'sudo: wee_debug: command not found'. This 
applies to all utillities. I only have one thing left for Weewx: HELP!

One problem with Belchertown is that Cheetah can't find the 
/home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's right, 
the file is not there. So also here: HELP!

Thanks in advance for any suggestion.

Regards, Keimpe


After running since Decemwaiting for V4 

Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:
>
> After months of waiting, Version 4 has finally arrived! The major new 
> feature is that WeeWX will not run under either Python 2 or Python 3.
>
> It took a long time to get the packaging right but now, thanks to Matthew 
> Wall, WeeWX is easier than ever to install. Be sure to read the 
> installation instructions for your specific operating system 
> . As always, a setup.py install method is 
> also supported.
>
> Generally, the package installers will use Python 3, if its available. On 
> older systems, the installers will use Python 2.
>
>
> CHANGE LOG
> Ported to Python 3. WeeWX should now run under Python 3.5 and greater, as 
> well
> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>
> New facility for creating new user-defined derived types. See the Wiki 
> article
> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>
> WeeWX now uses the Python 'logging' facility. This means log, formats, and 
> other
> things can now be customized. Fixes issue #353.
>
> Strings appearing in the data stream no longer cause a TypeError if they 
> can be
> converted to a number.
>
> Strings can now be accumulated and extracted in the accumulators, making it
> possible to include them in the database schemas.
>
> The utility wee_reports now loads services, allowing it to use 
> user-supplied
> extensions. Fixes issue #95.
>
> New default schema ("wview_extended") that offers many new types. The old 
> schema
> is still supported. Fixes issue #115.
>
> Optional, more flexible, way of specifying schemas for the daily 
> summaries. The
> old way is still supported.
>
> The install process now offers to register a user's station with weewx.com
> .
>
> The package MySQL-python, which we used previously, is not always 
> available on
> Python 3. Ported the MySQL code to use the package mysqlclient as an
> alternative.
>
> The default for WOW no longer throttles posting frequency (the default 
> used to
> be no more than once every 15 minutes).
>
> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>
> Unit group group_distance is now a first-class group.
>
> Added new tag $python_version.
>
> Ported to Python2-PyMySQL package on OpenSUSE.
>
> Added new aggregation types 'first' (similar to 'last'), 'diff' (the 
> difference
> between last and first value in the aggregation interval), and 'tderiv' 
> (the
> difference divided by the time difference).
>
> Created new unit group 'group_energy2', defined as watt-seconds. Useful 
> for high
> resolution energy monitors.
>
> An observation type known to the system, but not in a record, will now 
> return a
> proper ValueTuple, rather than UnknownType.
>
> Type "stormStart" was added to the unit system. Fixes issue #380.
>
> Added new aggregation type 'growdeg'. Similar to 'heatdeg', or 'cooldeg', 
> it
> measures growing degree-days. Basically, cooldeg, but with a different 
> base.
> Fixes issue #367. Thanks to user Clay Jackson for guidance!
>
> Ported OS uptime to OpenBSD. Fixes issue #428. Thanks to user Jeff Ross!
>
> Catch SSL certificate errors in uploaders. Retry after an hour. Fixes issue
> #413.
>
> Wunderfixer has been ported to the new WU API. This API requires an API 
> key,
> which you can get from the WU. Put it in weewx.conf. Added option 
> --upload-only.
> Thanks to user Leon Shaner! Fixes issues #414 and #445.
>
> Wee_import can now import Weather Display monthly log files.
>
> Fixed problem where sub-sections DegreeDays and Trend were located under 
> the
> wrong weewx.conf section. Fixes issue #432. Thanks to user mph for spotting
> this!
>
> Added new parameters to the Weather Underground uploader. Fixes issue #435.
>
> Added new 

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Tom Keffer]

Keimpe

Trying to clarify what you tried. You said you tried 'sudo / home / weewx /
bin / wee_debug verbosity = 1'  Is that a typo, or did you literally type
that? There should not be spaces in there. I should be something like

/home/weewx/bin/wee_debug --verbosity=1

Or, maybe it was just a typo. Let us know.



On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker  wrote:

> Hi Tom, All,
>
> From December I had Weewx V3 with Belchertown running on the Simulator
> without any problems. Because of the import of the Wunderground history I
> have been waiting for the transition from WeatherDisplay & WordPerss to
> Weewx to V4.
>
> I've been fiddling for days now to get things going; tried upgrading from
> V3 (/etc/weewx/ ...) to V4, of course with all the Python prerequisites and
> the setup.py method but without success. I cleaned up the RPi from A to Z
> and tried the standard installation without any changes in the Setup.cfg
> but no success.
>
> Today I made a fresh start with a clean RPi and Weewx installed by default
> in /home/weewx/. Weewx seems to run well -basic skin, without Belchertown-,
> but now the utilities don't work: 'sudo / home / weewx / bin / wee_debug
> verbosity = 1' results in 'sudo: wee_debug: command not found'. This
> applies to all utillities. I only have one thing left for Weewx: HELP!
>
> One problem with Belchertown is that Cheetah can't find the
> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's right,
> the file is not there. So also here: HELP!
>
> Thanks in advance for any suggestion.
>
> Regards, Keimpe
>
>
> After running since Decemwaiting for V4
>
> Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:
>>
>> After months of waiting, Version 4 has finally arrived! The major new
>> feature is that WeeWX will not run under either Python 2 or Python 3.
>>
>> It took a long time to get the packaging right but now, thanks to Matthew
>> Wall, WeeWX is easier than ever to install. Be sure to read the
>> installation instructions for your specific operating system
>> . As always, a setup.py install method is
>> also supported.
>>
>> Generally, the package installers will use Python 3, if its available. On
>> older systems, the installers will use Python 2.
>>
>>
>> CHANGE LOG
>> Ported to Python 3. WeeWX should now run under Python 3.5 and greater, as
>> well
>> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>>
>> New facility for creating new user-defined derived types. See the Wiki
>> article
>> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>>
>> WeeWX now uses the Python 'logging' facility. This means log, formats,
>> and other
>> things can now be customized. Fixes issue #353.
>>
>> Strings appearing in the data stream no longer cause a TypeError if they
>> can be
>> converted to a number.
>>
>> Strings can now be accumulated and extracted in the accumulators, making
>> it
>> possible to include them in the database schemas.
>>
>> The utility wee_reports now loads services, allowing it to use
>> user-supplied
>> extensions. Fixes issue #95.
>>
>> New default schema ("wview_extended") that offers many new types. The old
>> schema
>> is still supported. Fixes issue #115.
>>
>> Optional, more flexible, way of specifying schemas for the daily
>> summaries. The
>> old way is still supported.
>>
>> The install process now offers to register a user's station with
>> weewx.com.
>>
>> The package MySQL-python, which we used previously, is not always
>> available on
>> Python 3. Ported the MySQL code to use the package mysqlclient as an
>> alternative.
>>
>> The default for WOW no longer throttles posting frequency (the default
>> used to
>> be no more than once every 15 minutes).
>>
>> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>>
>> Unit group group_distance is now a first-class group.
>>
>> Added new tag $python_version.
>>
>> Ported to Python2-PyMySQL package on OpenSUSE.
>>
>> Added new aggregation types 'first' (similar to 'last'), 'diff' (the
>> difference
>> between last and first value in the aggregation interval), and 'tderiv'
>> (the
>> difference divided by the time difference).
>>
>> Created new unit group 'group_energy2', defined as watt-seconds. Useful
>> for high
>> resolution energy monitors.
>>
>> An observation type known to the system, but not in a record, will now
>> return a
>> proper ValueTuple, rather than UnknownType.
>>
>> Type "stormStart" was added to the unit system. Fixes issue #380.
>>
>> Added new aggregation type 'growdeg'. Similar to 'heatdeg', or 'cooldeg',
>> it
>> measures growing degree-days. Basically, cooldeg, but with a different
>> base.
>> Fixes issue #367. Thanks to user Clay Jackson for guidance!
>>
>> Ported OS uptime to OpenBSD. Fixes issue #428. Thanks to user Jeff Ross!
>>
>> Catch SSL certificate errors in uploaders. Retry after an hour. Fixes
>> issue
>> #413.
>>
>> Wunderfixer has been ported to the new WU API. This API requires an

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Keimpe Bleeker]

Sorry, typo... use the command exactly as you mentioned. 
 

Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>
> Keimpe
>
> Trying to clarify what you tried. You said you tried 'sudo / home / weewx 
> / bin / wee_debug verbosity = 1'  Is that a typo, or did you literally type 
> that? There should not be spaces in there. I should be something like
>
> /home/weewx/bin/wee_debug --verbosity=1
>
> Or, maybe it was just a typo. Let us know.
>
>
>
> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker  > wrote:
>
>> Hi Tom, All,
>>
>> From December I had Weewx V3 with Belchertown running on the Simulator 
>> without any problems. Because of the import of the Wunderground history I 
>> have been waiting for the transition from WeatherDisplay & WordPerss to 
>> Weewx to V4.
>>
>> I've been fiddling for days now to get things going; tried upgrading from 
>> V3 (/etc/weewx/ ...) to V4, of course with all the Python prerequisites and 
>> the setup.py method but without success. I cleaned up the RPi from A to Z 
>> and tried the standard installation without any changes in the Setup.cfg 
>> but no success. 
>>
>> Today I made a fresh start with a clean RPi and Weewx installed by 
>> default in /home/weewx/. Weewx seems to run well -basic skin, without 
>> Belchertown-, but now the utilities don't work: 'sudo / home / weewx / bin 
>> / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not found'. 
>> This applies to all utillities. I only have one thing left for Weewx: HELP!
>>
>> One problem with Belchertown is that Cheetah can't find the 
>> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's right, 
>> the file is not there. So also here: HELP!
>>
>> Thanks in advance for any suggestion.
>>
>> Regards, Keimpe
>>
>>
>> After running since Decemwaiting for V4 
>>
>> Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:
>>>
>>> After months of waiting, Version 4 has finally arrived! The major new 
>>> feature is that WeeWX will not run under either Python 2 or Python 3.
>>>
>>> It took a long time to get the packaging right but now, thanks to 
>>> Matthew Wall, WeeWX is easier than ever to install. Be sure to read the 
>>> installation instructions for your specific operating system 
>>> . As always, a setup.py install method is 
>>> also supported.
>>>
>>> Generally, the package installers will use Python 3, if its available. 
>>> On older systems, the installers will use Python 2.
>>>
>>>
>>> CHANGE LOG
>>> Ported to Python 3. WeeWX should now run under Python 3.5 and greater, 
>>> as well
>>> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>>>
>>> New facility for creating new user-defined derived types. See the Wiki 
>>> article
>>> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>>>
>>> WeeWX now uses the Python 'logging' facility. This means log, formats, 
>>> and other
>>> things can now be customized. Fixes issue #353.
>>>
>>> Strings appearing in the data stream no longer cause a TypeError if they 
>>> can be
>>> converted to a number.
>>>
>>> Strings can now be accumulated and extracted in the accumulators, making 
>>> it
>>> possible to include them in the database schemas.
>>>
>>> The utility wee_reports now loads services, allowing it to use 
>>> user-supplied
>>> extensions. Fixes issue #95.
>>>
>>> New default schema ("wview_extended") that offers many new types. The 
>>> old schema
>>> is still supported. Fixes issue #115.
>>>
>>> Optional, more flexible, way of specifying schemas for the daily 
>>> summaries. The
>>> old way is still supported.
>>>
>>> The install process now offers to register a user's station with 
>>> weewx.com.
>>>
>>> The package MySQL-python, which we used previously, is not always 
>>> available on
>>> Python 3. Ported the MySQL code to use the package mysqlclient as an
>>> alternative.
>>>
>>> The default for WOW no longer throttles posting frequency (the default 
>>> used to
>>> be no more than once every 15 minutes).
>>>
>>> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>>>
>>> Unit group group_distance is now a first-class group.
>>>
>>> Added new tag $python_version.
>>>
>>> Ported to Python2-PyMySQL package on OpenSUSE.
>>>
>>> Added new aggregation types 'first' (similar to 'last'), 'diff' (the 
>>> difference
>>> between last and first value in the aggregation interval), and 'tderiv' 
>>> (the
>>> difference divided by the time difference).
>>>
>>> Created new unit group 'group_energy2', defined as watt-seconds. Useful 
>>> for high
>>> resolution energy monitors.
>>>
>>> An observation type known to the system, but not in a record, will now 
>>> return a
>>> proper ValueTuple, rather than UnknownType.
>>>
>>> Type "stormStart" was added to the unit system. Fixes issue #380.
>>>
>>> Added new aggregation type 'growdeg'. Similar to 'heatdeg', or 
>>> 'cooldeg', it
>>> measures growing degree-days. Basically, cooldeg, but with a different 
>>> base.
>>> Fixe

Re: [weewx-user] CWOP: Exception

[Tom Keffer]

We've been seeing a lot of that recently. There's a recent weewx-user thread

about it.

One user says that he's found cwop2.mesowest.org to be more reliable.

On Tue, May 5, 2020 at 1:46 AM Cat22  wrote:

> weewx 4.0.0 on linux
> I saw this in my weewx.log file while i had debug enabled:
>
> DEBUG weewx.restx: CWOP: Exception  (timed out)
> when looking for response to tnc packet
>
> Checking an previous log i see its fairly frequent.
> I suspect its behind the missing Temperature and Dew Point graph data at
> CWOP
>
> See here: http://www.findu.com/cgi-bin/wxpage.cgi?call=DW0249&last=12
>
> Any idea whats causing it?
> TIA
>
> --
> 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/1fa19b13-e80e-4b8a-a127-ac82f826d129%40googlegroups.com
> 
> .
>

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

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Tom Keffer]

So, what is in /home/weewx/bin?

On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker  wrote:

> Sorry, typo... use the command exactly as you mentioned.
>
>
> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>>
>> Keimpe
>>
>> Trying to clarify what you tried. You said you tried 'sudo / home /
>> weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you
>> literally type that? There should not be spaces in there. I should be
>> something like
>>
>> /home/weewx/bin/wee_debug --verbosity=1
>>
>> Or, maybe it was just a typo. Let us know.
>>
>>
>>
>> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker  wrote:
>>
>>> Hi Tom, All,
>>>
>>> From December I had Weewx V3 with Belchertown running on the Simulator
>>> without any problems. Because of the import of the Wunderground history I
>>> have been waiting for the transition from WeatherDisplay & WordPerss to
>>> Weewx to V4.
>>>
>>> I've been fiddling for days now to get things going; tried upgrading
>>> from V3 (/etc/weewx/ ...) to V4, of course with all the Python
>>> prerequisites and the setup.py method but without success. I cleaned up the
>>> RPi from A to Z and tried the standard installation without any changes in
>>> the Setup.cfg but no success.
>>>
>>> Today I made a fresh start with a clean RPi and Weewx installed by
>>> default in /home/weewx/. Weewx seems to run well -basic skin, without
>>> Belchertown-, but now the utilities don't work: 'sudo / home / weewx / bin
>>> / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not found'.
>>> This applies to all utillities. I only have one thing left for Weewx: HELP!
>>>
>>> One problem with Belchertown is that Cheetah can't find the
>>> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's right,
>>> the file is not there. So also here: HELP!
>>>
>>> Thanks in advance for any suggestion.
>>>
>>> Regards, Keimpe
>>>
>>>
>>> After running since Decemwaiting for V4
>>>
>>> Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:

 After months of waiting, Version 4 has finally arrived! The major new
 feature is that WeeWX will not run under either Python 2 or Python 3.

 It took a long time to get the packaging right but now, thanks to
 Matthew Wall, WeeWX is easier than ever to install. Be sure to read the
 installation instructions for your specific operating system
 . As always, a setup.py install method is
 also supported.

 Generally, the package installers will use Python 3, if its available.
 On older systems, the installers will use Python 2.


 CHANGE LOG
 Ported to Python 3. WeeWX should now run under Python 3.5 and greater,
 as well
 as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.

 New facility for creating new user-defined derived types. See the Wiki
 article
 https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types

 WeeWX now uses the Python 'logging' facility. This means log, formats,
 and other
 things can now be customized. Fixes issue #353.

 Strings appearing in the data stream no longer cause a TypeError if
 they can be
 converted to a number.

 Strings can now be accumulated and extracted in the accumulators,
 making it
 possible to include them in the database schemas.

 The utility wee_reports now loads services, allowing it to use
 user-supplied
 extensions. Fixes issue #95.

 New default schema ("wview_extended") that offers many new types. The
 old schema
 is still supported. Fixes issue #115.

 Optional, more flexible, way of specifying schemas for the daily
 summaries. The
 old way is still supported.

 The install process now offers to register a user's station with
 weewx.com.

 The package MySQL-python, which we used previously, is not always
 available on
 Python 3. Ported the MySQL code to use the package mysqlclient as an
 alternative.

 The default for WOW no longer throttles posting frequency (the default
 used to
 be no more than once every 15 minutes).

 Added new aggregate types minsum, minsumtime, sum_le. PR #382.

 Unit group group_distance is now a first-class group.

 Added new tag $python_version.

 Ported to Python2-PyMySQL package on OpenSUSE.

 Added new aggregation types 'first' (similar to 'last'), 'diff' (the
 difference
 between last and first value in the aggregation interval), and 'tderiv'
 (the
 difference divided by the time difference).

 Created new unit group 'group_energy2', defined as watt-seconds. Useful
 for high
 resolution energy monitors.

 An observation type known to the system, but not in a record, will now
 return a
 proper ValueTuple, rather than UnknownType.

 Type "stormStart" was added to the unit system. Fixes issue #380.
>

[weewx-user] Re: wee_import Weather Underground HTTP Error 401: Unauthorized

[Clint Parrish]

Gary,

I was able to import all of the nearly 10 years worth of records. I did six 
month intervals at a time with no issue.  Something on WU’s end was giving me 
grief.  I consider this matter to be resolved.

Thanks again and thanks to the many people who put months of work into ver 4.

Clint

-- 
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/f99a62c4-e7ac-4ba7-bac1-19c4d2688040%40googlegroups.com.

[weewx-user] Re: Pressure data - SDR - Ecowitt GW1000/Froggit DP1500

[Andy]

 [[sensor_map]]
   inTemp = temperature.152.FOWH25Packet
   inHumidity = humidity.152.FOWH25Packet
   pressure = pressure.152.FOWH25Packet
   inTempBatteryStatus = battery.152.FOWH25Packet

On Monday, May 4, 2020 at 4:19:34 PM UTC-7, Richard Horobin wrote:
>
> I have a WH25 that does temperature, humidity and pressure (raw) that I 
> bought from Misol via ali-express. It emits RF at 433.9MHz, perfect for 
> SDR.  (Now I've forgotten how to add the sensor, which I will ask about 
> separately.)
> Richard.
>
> On Saturday, 28 December 2019 07:36:36 UTC+11, galfert wrote:
>>
>>
>>

-- 
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/65b8c5a8-858a-4a0d-81e5-8ebd4eeeca39%40googlegroups.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Keimpe Bleeker]

See attached screenshot, all the necessary files and folders, as it appears.


Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
>
> So, what is in /home/weewx/bin?
>
> On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker  > wrote:
>
>> Sorry, typo... use the command exactly as you mentioned. 
>>  
>>
>> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>>>
>>> Keimpe
>>>
>>> Trying to clarify what you tried. You said you tried 'sudo / home / 
>>> weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you 
>>> literally type that? There should not be spaces in there. I should be 
>>> something like
>>>
>>> /home/weewx/bin/wee_debug --verbosity=1
>>>
>>> Or, maybe it was just a typo. Let us know.
>>>
>>>
>>>
>>> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker  wrote:
>>>
 Hi Tom, All,

 From December I had Weewx V3 with Belchertown running on the Simulator 
 without any problems. Because of the import of the Wunderground history I 
 have been waiting for the transition from WeatherDisplay & WordPerss to 
 Weewx to V4.

 I've been fiddling for days now to get things going; tried upgrading 
 from V3 (/etc/weewx/ ...) to V4, of course with all the Python 
 prerequisites and the setup.py method but without success. I cleaned up 
 the 
 RPi from A to Z and tried the standard installation without any changes in 
 the Setup.cfg but no success. 

 Today I made a fresh start with a clean RPi and Weewx installed by 
 default in /home/weewx/. Weewx seems to run well -basic skin, without 
 Belchertown-, but now the utilities don't work: 'sudo / home / weewx / bin 
 / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not 
 found'. 
 This applies to all utillities. I only have one thing left for Weewx: HELP!

 One problem with Belchertown is that Cheetah can't find the 
 /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's 
 right, 
 the file is not there. So also here: HELP!

 Thanks in advance for any suggestion.

 Regards, Keimpe


 After running since Decemwaiting for V4 

 Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:
>
> After months of waiting, Version 4 has finally arrived! The major new 
> feature is that WeeWX will not run under either Python 2 or Python 3.
>
> It took a long time to get the packaging right but now, thanks to 
> Matthew Wall, WeeWX is easier than ever to install. Be sure to read the 
> installation instructions for your specific operating system 
> . As always, a setup.py install method is 
> also supported.
>
> Generally, the package installers will use Python 3, if its available. 
> On older systems, the installers will use Python 2.
>
>
> CHANGE LOG
> Ported to Python 3. WeeWX should now run under Python 3.5 and greater, 
> as well
> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>
> New facility for creating new user-defined derived types. See the Wiki 
> article
> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>
> WeeWX now uses the Python 'logging' facility. This means log, formats, 
> and other
> things can now be customized. Fixes issue #353.
>
> Strings appearing in the data stream no longer cause a TypeError if 
> they can be
> converted to a number.
>
> Strings can now be accumulated and extracted in the accumulators, 
> making it
> possible to include them in the database schemas.
>
> The utility wee_reports now loads services, allowing it to use 
> user-supplied
> extensions. Fixes issue #95.
>
> New default schema ("wview_extended") that offers many new types. The 
> old schema
> is still supported. Fixes issue #115.
>
> Optional, more flexible, way of specifying schemas for the daily 
> summaries. The
> old way is still supported.
>
> The install process now offers to register a user's station with 
> weewx.com.
>
> The package MySQL-python, which we used previously, is not always 
> available on
> Python 3. Ported the MySQL code to use the package mysqlclient as an
> alternative.
>
> The default for WOW no longer throttles posting frequency (the default 
> used to
> be no more than once every 15 minutes).
>
> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>
> Unit group group_distance is now a first-class group.
>
> Added new tag $python_version.
>
> Ported to Python2-PyMySQL package on OpenSUSE.
>
> Added new aggregation types 'first' (similar to 'last'), 'diff' (the 
> difference
> between last and first value in the aggregation interval), and 
> 'tderiv' (the
> difference divided by the time difference).
>
> Created new

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Tom Keffer]

OK. So, you're telling me that running a program /home/weewx/bin/wee_debug,
that clearly exists in a directory listing, results in an error "wee_debug
not found". That doesn't make sense.

I'd like to see the actual console output. Run the command, then copy and
paste from the console output into your post. DO NOT TAKE A SCREENSHOT.
Just highlight the resultant text, right click, select "Copy", then paste
into your post.

-tk

On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker  wrote:

> See attached screenshot, all the necessary files and folders, as it
> appears.
>
>
> Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
>>
>> So, what is in /home/weewx/bin?
>>
>> On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker  wrote:
>>
>>> Sorry, typo... use the command exactly as you mentioned.
>>>
>>>
>>> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:

 Keimpe

 Trying to clarify what you tried. You said you tried 'sudo / home /
 weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you
 literally type that? There should not be spaces in there. I should be
 something like

 /home/weewx/bin/wee_debug --verbosity=1

 Or, maybe it was just a typo. Let us know.



 On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker 
 wrote:

> Hi Tom, All,
>
> From December I had Weewx V3 with Belchertown running on the Simulator
> without any problems. Because of the import of the Wunderground history I
> have been waiting for the transition from WeatherDisplay & WordPerss to
> Weewx to V4.
>
> I've been fiddling for days now to get things going; tried upgrading
> from V3 (/etc/weewx/ ...) to V4, of course with all the Python
> prerequisites and the setup.py method but without success. I cleaned up 
> the
> RPi from A to Z and tried the standard installation without any changes in
> the Setup.cfg but no success.
>
> Today I made a fresh start with a clean RPi and Weewx installed by
> default in /home/weewx/. Weewx seems to run well -basic skin, without
> Belchertown-, but now the utilities don't work: 'sudo / home / weewx / bin
> / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not 
> found'.
> This applies to all utillities. I only have one thing left for Weewx: 
> HELP!
>
> One problem with Belchertown is that Cheetah can't find the
> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's 
> right,
> the file is not there. So also here: HELP!
>
> Thanks in advance for any suggestion.
>
> Regards, Keimpe
>
>
> After running since Decemwaiting for V4
>
> Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:
>>
>> After months of waiting, Version 4 has finally arrived! The major new
>> feature is that WeeWX will not run under either Python 2 or Python 3.
>>
>> It took a long time to get the packaging right but now, thanks to
>> Matthew Wall, WeeWX is easier than ever to install. Be sure to read the
>> installation instructions for your specific operating system
>> . As always, a setup.py install method
>> is also supported.
>>
>> Generally, the package installers will use Python 3, if its
>> available. On older systems, the installers will use Python 2.
>>
>>
>> CHANGE LOG
>> Ported to Python 3. WeeWX should now run under Python 3.5 and
>> greater, as well
>> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>>
>> New facility for creating new user-defined derived types. See the
>> Wiki article
>> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>>
>> WeeWX now uses the Python 'logging' facility. This means log,
>> formats, and other
>> things can now be customized. Fixes issue #353.
>>
>> Strings appearing in the data stream no longer cause a TypeError if
>> they can be
>> converted to a number.
>>
>> Strings can now be accumulated and extracted in the accumulators,
>> making it
>> possible to include them in the database schemas.
>>
>> The utility wee_reports now loads services, allowing it to use
>> user-supplied
>> extensions. Fixes issue #95.
>>
>> New default schema ("wview_extended") that offers many new types. The
>> old schema
>> is still supported. Fixes issue #115.
>>
>> Optional, more flexible, way of specifying schemas for the daily
>> summaries. The
>> old way is still supported.
>>
>> The install process now offers to register a user's station with
>> weewx.com.
>>
>> The package MySQL-python, which we used previously, is not always
>> available on
>> Python 3. Ported the MySQL code to use the package mysqlclient as an
>> alternative.
>>
>> The default for WOW no longer throttles posting frequen

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Keimpe Bleeker]

Wee_debug --verbostity=1 results in help-info:

pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1
Usage: wee_debug --help
   wee_debug --info
[CONFIG_FILE|--config=CONFIG_FILE]
[--output|--output DEBUG_PATH]
[--verbosity=0|1|2]
   wee_debug --version

Description:

Generate a standard suite of system/weewx information to aid in remote
debugging. The wee_debug output consists of two parts, the first part 
containing
a snapshot of relevant system/weewx information and the second part a 
parsed and
obfuscated copy of weewx.conf. This output can be redirected to file and 
posted
when seeking assistance via forums or email.

Actions:

--info   Generate a debug report.

Options:
  -h, --helpshow this help message and exit
  --config=CONFIG_FILE  Use configuration file CONFIG_FILE.
  --infoGenerate weewx debug output.
  --output  Write wee_debug output to DEBUG_PATH. DEBUG_PATH
includes path and file name. Default is
/var/tmp/weewx.debug.
  --verbosity=N How much detail to display, 0-2, default=1.
  --version Display wee_debug version number.

wee_debug will attempt to obfuscate obvious personal/private information in
weewx.conf such as user names, passwords and API keys; however, the user
should thoroughly check the generated output for personal/private 
information
before posting the information publicly.
pi@Pi4Weewx:/home/weewx $

Or for wee_config ends in:
 
pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $ 
bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet
pi@Pi4Weewx:/home/weewx $ 

NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)

 
Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:
>
> OK. So, you're telling me that running a program 
> /home/weewx/bin/wee_debug, that clearly exists in a directory listing, 
> results in an error "wee_debug not found". That doesn't make sense.
>
> I'd like to see the actual console output. Run the command, then copy and 
> paste from the console output into your post. DO NOT TAKE A SCREENSHOT. 
> Just highlight the resultant text, right click, select "Copy", then paste 
> into your post.
>
> -tk
>
> On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker  > wrote:
>
>> See attached screenshot, all the necessary files and folders, as it 
>> appears.
>>
>>
>> Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
>>>
>>> So, what is in /home/weewx/bin?
>>>
>>> On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker  wrote:
>>>
 Sorry, typo... use the command exactly as you mentioned. 
  

 Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>
> Keimpe
>
> Trying to clarify what you tried. You said you tried 'sudo / home / 
> weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you 
> literally type that? There should not be spaces in there. I should be 
> something like
>
> /home/weewx/bin/wee_debug --verbosity=1
>
> Or, maybe it was just a typo. Let us know.
>
>
>
> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker  
> wrote:
>
>> Hi Tom, All,
>>
>> From December I had Weewx V3 with Belchertown running on the 
>> Simulator without any problems. Because of the import of the 
>> Wunderground 
>> history I have been waiting for the transition from WeatherDisplay & 
>> WordPerss to Weewx to V4.
>>
>> I've been fiddling for days now to get things going; tried upgrading 
>> from V3 (/etc/weewx/ ...) to V4, of course with all the Python 
>> prerequisites and the setup.py method but without success. I cleaned up 
>> the 
>> RPi from A to Z and tried the standard installation without any changes 
>> in 
>> the Setup.cfg but no success. 
>>
>> Today I made a fresh start with a clean RPi and Weewx installed by 
>> default in /home/weewx/. Weewx seems to run well -basic skin, without 
>> Belchertown-, but now the utilities don't work: 'sudo / home / weewx / 
>> bin 
>> / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not 
>> found'. 
>> This applies to all utillities. I only have one thing left for Weewx: 
>> HELP!
>>
>> One problem with Belchertown is that Cheetah can't find the 
>> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's 
>> right, 
>> the file is not there. So also here: HELP!
>>
>> Thanks in advance for any suggestion.
>>
>> Regards, Keimpe
>>
>>
>> After running since Decemwaiting for V4 
>>
>> Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:
>>>
>>> After months of waiting, Version 4 has finally arrived! The major 
>>> new feature is that WeeWX will not run under either Python 2 or Python 
>>> 3.
>>>
>>> It took a long time to get the packaging right but now, than

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[John Kline]

You are missing the “—info” flag (as shown in the Usage message printed).

Try /home/weewx/bin/wee_debug —info --verbosity=1

> On May 5, 2020, at 8:29 AM, Keimpe Bleeker  wrote:
> 
> 
> Wee_debug --verbostity=1 results in help-info:
> 
> pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1
> Usage: wee_debug --help
>wee_debug --info
> [CONFIG_FILE|--config=CONFIG_FILE]
> [--output|--output DEBUG_PATH]
> [--verbosity=0|1|2]
>wee_debug --version
> 
> Description:
> 
> Generate a standard suite of system/weewx information to aid in remote
> debugging. The wee_debug output consists of two parts, the first part 
> containing
> a snapshot of relevant system/weewx information and the second part a parsed 
> and
> obfuscated copy of weewx.conf. This output can be redirected to file and 
> posted
> when seeking assistance via forums or email.
> 
> Actions:
> 
> --info   Generate a debug report.
> 
> Options:
>   -h, --helpshow this help message and exit
>   --config=CONFIG_FILE  Use configuration file CONFIG_FILE.
>   --infoGenerate weewx debug output.
>   --output  Write wee_debug output to DEBUG_PATH. DEBUG_PATH
> includes path and file name. Default is
> /var/tmp/weewx.debug.
>   --verbosity=N How much detail to display, 0-2, default=1.
>   --version Display wee_debug version number.
> 
> wee_debug will attempt to obfuscate obvious personal/private information in
> weewx.conf such as user names, passwords and API keys; however, the user
> should thoroughly check the generated output for personal/private information
> before posting the information publicly.
> pi@Pi4Weewx:/home/weewx $
> 
> Or for wee_config ends in:
>  
> pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $ 
> bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet
> pi@Pi4Weewx:/home/weewx $ 
> 
> NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)
> 
>  
> Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:
>> 
>> OK. So, you're telling me that running a program /home/weewx/bin/wee_debug, 
>> that clearly exists in a directory listing, results in an error "wee_debug 
>> not found". That doesn't make sense.
>> 
>> I'd like to see the actual console output. Run the command, then copy and 
>> paste from the console output into your post. DO NOT TAKE A SCREENSHOT. Just 
>> highlight the resultant text, right click, select "Copy", then paste into 
>> your post.
>> 
>> -tk
>> 
>> On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker  wrote:
>>> See attached screenshot, all the necessary files and folders, as it appears.
>>> 
>>> 
>>> Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
 
 So, what is in /home/weewx/bin?
 
 On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker  wrote:
> Sorry, typo... use the command exactly as you mentioned. 
>  
> 
> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>> 
>> Keimpe
>> 
>> Trying to clarify what you tried. You said you tried 'sudo / home / 
>> weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you 
>> literally type that? There should not be spaces in there. I should be 
>> something like
>> 
>> /home/weewx/bin/wee_debug --verbosity=1
>> 
>> Or, maybe it was just a typo. Let us know.
>> 
>> 
>> 
>> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker  wrote:
>>> Hi Tom, All,
>>> 
>>> From December I had Weewx V3 with Belchertown running on the Simulator 
>>> without any problems. Because of the import of the Wunderground history 
>>> I have been waiting for the transition from WeatherDisplay & WordPerss 
>>> to Weewx to V4.
>>> 
>>> I've been fiddling for days now to get things going; tried upgrading 
>>> from V3 (/etc/weewx/ ...) to V4, of course with all the Python 
>>> prerequisites and the setup.py method but without success. I cleaned up 
>>> the RPi from A to Z and tried the standard installation without any 
>>> changes in the Setup.cfg but no success. 
>>> 
>>> Today I made a fresh start with a clean RPi and Weewx installed by 
>>> default in /home/weewx/. Weewx seems to run well -basic skin, without 
>>> Belchertown-, but now the utilities don't work: 'sudo / home / weewx / 
>>> bin / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not 
>>> found'. This applies to all utillities. I only have one thing left for 
>>> Weewx: HELP!
>>> 
>>> One problem with Belchertown is that Cheetah can't find the 
>>> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's 
>>> right, the file is not there. So also here: HELP!
>>> 
>>> Thanks in advance for any suggestion.
>>> 
>>> Regards, Keimpe
>>> 
>>> 
>>> After running since Decemwaiting for V4 
>>> 
>>> O

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Tom Keffer]

OK. That looks normal.  There is no "wee_debug not found" error.

You have to give it something to do. You probably want a --info flag

/home/weewx/bin/wee_debug --verbosity=1 --info

Be sure to read the manual
!



On Tue, May 5, 2020 at 8:29 AM Keimpe Bleeker  wrote:

> Wee_debug --verbostity=1 results in help-info:
>
> pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1
> Usage: wee_debug --help
>wee_debug --info
> [CONFIG_FILE|--config=CONFIG_FILE]
> [--output|--output DEBUG_PATH]
> [--verbosity=0|1|2]
>wee_debug --version
>
> Description:
>
> Generate a standard suite of system/weewx information to aid in remote
> debugging. The wee_debug output consists of two parts, the first part
> containing
> a snapshot of relevant system/weewx information and the second part a
> parsed and
> obfuscated copy of weewx.conf. This output can be redirected to file and
> posted
> when seeking assistance via forums or email.
>
> Actions:
>
> --info   Generate a debug report.
>
> Options:
>   -h, --helpshow this help message and exit
>   --config=CONFIG_FILE  Use configuration file CONFIG_FILE.
>   --infoGenerate weewx debug output.
>   --output  Write wee_debug output to DEBUG_PATH. DEBUG_PATH
> includes path and file name. Default is
> /var/tmp/weewx.debug.
>   --verbosity=N How much detail to display, 0-2, default=1.
>   --version Display wee_debug version number.
>
> wee_debug will attempt to obfuscate obvious personal/private information in
> weewx.conf such as user names, passwords and API keys; however, the user
> should thoroughly check the generated output for personal/private
> information
> before posting the information publicly.
> pi@Pi4Weewx:/home/weewx $
>
> Or for wee_config ends in:
>
> pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $
> bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet
> pi@Pi4Weewx:/home/weewx $
>
> NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)
>
>
> Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:
>>
>> OK. So, you're telling me that running a program
>> /home/weewx/bin/wee_debug, that clearly exists in a directory listing,
>> results in an error "wee_debug not found". That doesn't make sense.
>>
>> I'd like to see the actual console output. Run the command, then copy and
>> paste from the console output into your post. DO NOT TAKE A SCREENSHOT.
>> Just highlight the resultant text, right click, select "Copy", then paste
>> into your post.
>>
>> -tk
>>
>> On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker  wrote:
>>
>>> See attached screenshot, all the necessary files and folders, as it
>>> appears.
>>>
>>>
>>> Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:

 So, what is in /home/weewx/bin?

 On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker 
 wrote:

> Sorry, typo... use the command exactly as you mentioned.
>
>
> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>>
>> Keimpe
>>
>> Trying to clarify what you tried. You said you tried 'sudo / home /
>> weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you
>> literally type that? There should not be spaces in there. I should be
>> something like
>>
>> /home/weewx/bin/wee_debug --verbosity=1
>>
>> Or, maybe it was just a typo. Let us know.
>>
>>
>>
>> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker 
>> wrote:
>>
>>> Hi Tom, All,
>>>
>>> From December I had Weewx V3 with Belchertown running on the
>>> Simulator without any problems. Because of the import of the 
>>> Wunderground
>>> history I have been waiting for the transition from WeatherDisplay &
>>> WordPerss to Weewx to V4.
>>>
>>> I've been fiddling for days now to get things going; tried upgrading
>>> from V3 (/etc/weewx/ ...) to V4, of course with all the Python
>>> prerequisites and the setup.py method but without success. I cleaned up 
>>> the
>>> RPi from A to Z and tried the standard installation without any changes 
>>> in
>>> the Setup.cfg but no success.
>>>
>>> Today I made a fresh start with a clean RPi and Weewx installed by
>>> default in /home/weewx/. Weewx seems to run well -basic skin, without
>>> Belchertown-, but now the utilities don't work: 'sudo / home / weewx / 
>>> bin
>>> / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not 
>>> found'.
>>> This applies to all utillities. I only have one thing left for Weewx: 
>>> HELP!
>>>
>>> One problem with Belchertown is that Cheetah can't find the
>>> /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's 
>>> right,
>>> the file is not there. So also here: HELP!
>>

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Tom Keffer]

Oh, one other thing: you said this applies to "all utilities." Example?

-tk

On Tue, May 5, 2020 at 8:39 AM Tom Keffer  wrote:

> OK. That looks normal.  There is no "wee_debug not found" error.
>
> You have to give it something to do. You probably want a --info flag
>
> /home/weewx/bin/wee_debug --verbosity=1 --info
>
> Be sure to read the manual
> !
>
>
>
> On Tue, May 5, 2020 at 8:29 AM Keimpe Bleeker  wrote:
>
>> Wee_debug --verbostity=1 results in help-info:
>>
>> pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1
>> Usage: wee_debug --help
>>wee_debug --info
>> [CONFIG_FILE|--config=CONFIG_FILE]
>> [--output|--output DEBUG_PATH]
>> [--verbosity=0|1|2]
>>wee_debug --version
>>
>> Description:
>>
>> Generate a standard suite of system/weewx information to aid in remote
>> debugging. The wee_debug output consists of two parts, the first part
>> containing
>> a snapshot of relevant system/weewx information and the second part a
>> parsed and
>> obfuscated copy of weewx.conf. This output can be redirected to file and
>> posted
>> when seeking assistance via forums or email.
>>
>> Actions:
>>
>> --info   Generate a debug report.
>>
>> Options:
>>   -h, --helpshow this help message and exit
>>   --config=CONFIG_FILE  Use configuration file CONFIG_FILE.
>>   --infoGenerate weewx debug output.
>>   --output  Write wee_debug output to DEBUG_PATH. DEBUG_PATH
>> includes path and file name. Default is
>> /var/tmp/weewx.debug.
>>   --verbosity=N How much detail to display, 0-2, default=1.
>>   --version Display wee_debug version number.
>>
>> wee_debug will attempt to obfuscate obvious personal/private information
>> in
>> weewx.conf such as user names, passwords and API keys; however, the user
>> should thoroughly check the generated output for personal/private
>> information
>> before posting the information publicly.
>> pi@Pi4Weewx:/home/weewx $
>>
>> Or for wee_config ends in:
>>
>> pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $
>> bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet
>> pi@Pi4Weewx:/home/weewx $
>>
>> NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)
>>
>>
>> Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:
>>>
>>> OK. So, you're telling me that running a program
>>> /home/weewx/bin/wee_debug, that clearly exists in a directory listing,
>>> results in an error "wee_debug not found". That doesn't make sense.
>>>
>>> I'd like to see the actual console output. Run the command, then copy
>>> and paste from the console output into your post. DO NOT TAKE A SCREENSHOT.
>>> Just highlight the resultant text, right click, select "Copy", then paste
>>> into your post.
>>>
>>> -tk
>>>
>>> On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker  wrote:
>>>
 See attached screenshot, all the necessary files and folders, as it
 appears.


 Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
>
> So, what is in /home/weewx/bin?
>
> On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker 
> wrote:
>
>> Sorry, typo... use the command exactly as you mentioned.
>>
>>
>> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>>>
>>> Keimpe
>>>
>>> Trying to clarify what you tried. You said you tried 'sudo / home /
>>> weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you
>>> literally type that? There should not be spaces in there. I should be
>>> something like
>>>
>>> /home/weewx/bin/wee_debug --verbosity=1
>>>
>>> Or, maybe it was just a typo. Let us know.
>>>
>>>
>>>
>>> On Tue, May 5, 2020 at 4:47 AM Keimpe Bleeker 
>>> wrote:
>>>
 Hi Tom, All,

 From December I had Weewx V3 with Belchertown running on the
 Simulator without any problems. Because of the import of the 
 Wunderground
 history I have been waiting for the transition from WeatherDisplay &
 WordPerss to Weewx to V4.

 I've been fiddling for days now to get things going; tried
 upgrading from V3 (/etc/weewx/ ...) to V4, of course with all the 
 Python
 prerequisites and the setup.py method but without success. I cleaned 
 up the
 RPi from A to Z and tried the standard installation without any 
 changes in
 the Setup.cfg but no success.

 Today I made a fresh start with a clean RPi and Weewx installed by
 default in /home/weewx/. Weewx seems to run well -basic skin, without
 Belchertown-, but now the utilities don't work: 'sudo / home / weewx / 
 bin
 / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not 
 found'.
 This applies to all utillitie

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Keimpe Bleeker]

Thanks, wee_debug is working!

pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --info --verbosity=1
Using verbosity=1, displaying most info

wee_debug output will be sent to stdout(console)

Using configuration file /home/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'

System info
  Platform:   Linux-4.19.97-v7l+-armv7l-with-debian-10.3
  Python Version: 3.7.3

Load Information
  1 minute load average:  0.01
  5 minute load average:  0.02
  15 minute load average: 0.00

General Weewx info
  Weewx version 4.0.0 detected.

Station info
  Station type: Simulator
  Driver:   weewx.drivers.simulator

Driver info
[Simulator]
# This section is for the weewx weather station simulator
   . 

But the important wee_config, to change from Simulator to Vantage still 
says:

pi@Pi4Weewx:/home/weewx $ wee_config --config=/home/weewx/weewx.conf
bash: wee_config: opdracht niet gevonden
pi@Pi4Weewx:/home/weewx $ 





Op dinsdag 5 mei 2020 17:41:44 UTC+2 schreef Tom Keffer:
>
> Oh, one other thing: you said this applies to "all utilities." Example?
>
> -tk
>
> On Tue, May 5, 2020 at 8:39 AM Tom Keffer > 
> wrote:
>
>> OK. That looks normal.  There is no "wee_debug not found" error.
>>
>> You have to give it something to do. You probably want a --info flag
>>
>> /home/weewx/bin/wee_debug --verbosity=1 --info
>>
>> Be sure to read the manual 
>> !
>>
>>
>>
>> On Tue, May 5, 2020 at 8:29 AM Keimpe Bleeker > > wrote:
>>
>>> Wee_debug --verbostity=1 results in help-info:
>>>
>>> pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1
>>> Usage: wee_debug --help
>>>wee_debug --info
>>> [CONFIG_FILE|--config=CONFIG_FILE]
>>> [--output|--output DEBUG_PATH]
>>> [--verbosity=0|1|2]
>>>wee_debug --version
>>>
>>> Description:
>>>
>>> Generate a standard suite of system/weewx information to aid in remote
>>> debugging. The wee_debug output consists of two parts, the first part 
>>> containing
>>> a snapshot of relevant system/weewx information and the second part a 
>>> parsed and
>>> obfuscated copy of weewx.conf. This output can be redirected to file and 
>>> posted
>>> when seeking assistance via forums or email.
>>>
>>> Actions:
>>>
>>> --info   Generate a debug report.
>>>
>>> Options:
>>>   -h, --helpshow this help message and exit
>>>   --config=CONFIG_FILE  Use configuration file CONFIG_FILE.
>>>   --infoGenerate weewx debug output.
>>>   --output  Write wee_debug output to DEBUG_PATH. DEBUG_PATH
>>> includes path and file name. Default is
>>> /var/tmp/weewx.debug.
>>>   --verbosity=N How much detail to display, 0-2, default=1.
>>>   --version Display wee_debug version number.
>>>
>>> wee_debug will attempt to obfuscate obvious personal/private information 
>>> in
>>> weewx.conf such as user names, passwords and API keys; however, the user
>>> should thoroughly check the generated output for personal/private 
>>> information
>>> before posting the information publicly.
>>> pi@Pi4Weewx:/home/weewx $
>>>
>>> Or for wee_config ends in:
>>>  
>>> pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $ 
>>> bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet
>>> pi@Pi4Weewx:/home/weewx $ 
>>>
>>> NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)
>>>
>>>  
>>> Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:

 OK. So, you're telling me that running a program 
 /home/weewx/bin/wee_debug, that clearly exists in a directory listing, 
 results in an error "wee_debug not found". That doesn't make sense.

 I'd like to see the actual console output. Run the command, then copy 
 and paste from the console output into your post. DO NOT TAKE A 
 SCREENSHOT. 
 Just highlight the resultant text, right click, select "Copy", then paste 
 into your post.

 -tk

 On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker  
 wrote:

> See attached screenshot, all the necessary files and folders, as it 
> appears.
>
>
> Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
>>
>> So, what is in /home/weewx/bin?
>>
>> On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker  
>> wrote:
>>
>>> Sorry, typo... use the command exactly as you mentioned. 
>>>  
>>>
>>> Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:

 Keimpe

 Trying to clarify what you tried. You said you tried 'sudo / home 
 / weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you 
 literally type that? There should not be spaces in there. I should be 
 something like

 /home/weewx/bin/wee_debug --verbosity=1

 Or, maybe it was just a typo. Let us

[weewx-user] rPI SD Card - IMG backup, cloning, transfer to larger/smaller (Windows)

[Xant]

My experience with rPI SD cards. The following refers to Windows/PC with a 
SD card slot or with a USB SD card reader/writer.

*1) Backup, Image or Cloning *- to equal or larger SD card

*Win32DiskImager* - https://sourceforge.net/projects/win32diskimager/

Win32DiskImager is the "to-go" option for rPI SD cards disk imaging, backup 
or cloning. It creates a 'perfect' image as it copies 'bit-by-bit' data 
clusters to an IMG file. Thus, it creates a file as big as the Card size 
itself as it even 'copies empty cluster data'.

But bigger, not always better.
As SD storage size prices keeps following, its easy to get tempted to slide 
a very large SD card into rPI, and I took this bait when upgrading to 
rPI-4. I placed a 64Gb SD Card, but turned out that only used a small 
fraction of the card storage (~7%, for WeeWx, MQTT, wx-database, 
Belchertown skin, InfluxDB, Grafana, etc).
On the other side, it takes long to Backup and creates very large IMG files.

Thus, Win32DiskImager can transfer IMG to same or larger SD card, where the 
extra space would be "unallocated" and needs to be expanded (raspi-config).


*2) Transfer to Smaller SD Card*

Transfer to a Smaller SD Card is possible and there are different 
approaches pending OS, Software or more than 1 SD card slot.
The easiest (and free) way I found was through '*Paragon Backup & Recovery*' 
- https://www.paragon-software.com/us/free/br-free/#
Paragon creates a 'recovery-point file' that saves only the actual data 
from SD card that can be transferred back to "any size" SD card, 
same/smaller/larger (data usage considered).

This worked perfect in my case, and now have a better size-fit SD card 
running on rPI=4 for WeeWX.

Xant

-- 
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/71ea00fc-de53-43fa-89e4-90dd7b101611%40googlegroups.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[gjr80]

With a setup.py install you need to include the path to the utilities unless 
you happen to be in the /home/weewx/bin directory (which in this case you are 
not). wee_debug worked because you included the path, with wee_device you did 
not. Use /home/weewx/bin/wee_device and it will work.

Gary

-- 
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/4eb1d14e-f3eb-4447-9285-5d8a0af6cdca%40googlegroups.com.

Re: [weewx-user] Weatherdata (rain) from own Weatherstation (Arduino)

[Johann Schneider]

Hello everybody!
Thank you for your answers.
Sorry for my difficult to understand question.
So my weather station sends the measured values every 15 seconds.
If it sends rain, I get the hourly rain value and the rain value for the 
whole day. The rain value for the whole day is cumulative and is set to 0 
at 00:00. The hourly rain value at the beginning of the rain is always 
calculated for one hour.
I thought I could simply import the data into weewx with "fileparser". This 
also works with the other data. Just not with the rain values.
John Kline's suggestion sounds great. That's how I would have imagined it.
How can I implement something for the rain value?

kind regards

Johnny

Am Dienstag, 5. Mai 2020 03:19:43 UTC+2 schrieb John Kline:
>
> Hi Tom,
>
> Apologies in advance if I have misunderstood the question and have made 
> you read what I believe you already know.
>
> If the question is can a driver be written to make use of rain emitted 
> every 15 seconds and resetting every hour, I believe such a driver can 
> easily be written.
>
> The RainWise CC3000 reports total rain and resets once a day.
>
> The delta is calculated with the following call in the cc3000 driver:
> return weewx.wxformulas.calculate_rain(rain_total, last_rain)
>
> If the the rain total is less than the last rain total recorded, it is 
> assumed that the counter reset.  On the CC3000, the reset is at midnight; 
> but this would work just fine if the reset occurs every hour.
>
> I suspect other drivers do the same in this regard (convert total rain to 
> incremental).
>
> On May 4, 2020, at 3:58 PM, Tom Keffer > 
> wrote:
>
> 
> Hello Johnny,
>
> Unfortunately, the data is summed up every few minutes and the values no 
>> longer fit.
>> For example, I have 0.15mm of rain in the last hour, then the value after 
>> each loop adds up until the hour is over.
>
>
> If I understand you correctly, your software emits the total rain measured 
> so far in an hour, which then gets reset at the end of the hour.
>
> If that that is the case, then, no, that would not work well with weewx. 
> In weewx, observation type 'rain' is the total amount of rain measured *for 
> that packet*, and only for that packet. Typically, it is a very small 
> number. This is explained in a little more detail in the section 
> genLoopPackets  
> in the Customizing Guide.
>
> Or, maybe I am misunderstanding your problem.
>
> -tk
>
> On Mon, May 4, 2020 at 2:02 PM Johann Schneider  > wrote:
>
>> Hello everybody!
>> I have a little problem. Sorry for my very bad english. I come from 
>> Germany and my English is not the best. My experience with weewx is also 
>> very limited. I built a weather station 3 years ago. It consists of an 
>> Arduino Mega and several sensors.
>> Among other things, a rain sensor that reports 0.16mm of rain per seesaw
>> The values ​​are pushed to iobroker (similar to openhab) every 15 
>> seconds. Here is an excerpt from my Arduino codes:
>> /*
>> Auswertung Regenmengensensor mit Regenwippe
>> - Counter kann durch reed-Kontakt oder Hallsensor erfolgen
>> - i2c eeprom AT24C256
>> - i2c Adresse EEPROM (default: 0x50)
>> */
>> #include 
>> //#include 
>> #//include 
>> //
>> /*PIN-Section   */
>> /*  Hier Sensor-Pins definieren */
>> //
>> //#define RAIN_COUNT_PIN 7
>> #define RAIN_COUNT_PIN 30
>> //
>> /*   Variablen-Section  */
>> //
>> long lastSecond; // Original - The millis counter to see when a second 
>> rolls by
>> unsigned int minutesSinceLastReset; //Used to reset variables after 24 
>> hours. Imp should tell us when it's midnight, this is backup.
>> byte secondsRain; //When it hits 60, increase the current minute
>> byte minutesRain; //Keeps track of where we are in various arrays of data
>>
>> volatile float rainHour[60]; //60 floating numbers to keep track of 60 
>> minutes of rain
>> volatile unsigned long raintime, rainlast, raininterval, rain;
>> volatile unsigned long last_micros1;
>> long debouncing_time1 = 3; // in millis -> eleminiert evtl 
>> REED-Kontakt-Prellen
>> boolean RainTimeReset = false;
>>
>> //struct Configuration
>> //{
>> //  float regenTag;
>> //  float regenStunde;
>> //}eepconfig EEMEM;
>>
>> //AT24C256<0x50> eep; // Das EEProm auf der china üblichen RTC3231 
>>
>> //
>> /* Interrupt-Section*/
>> //
>> void rainIRQ(unsigned long now){
>>   if((long)(micros() - last_micros1) >= debouncing_time1 * 1000) {
>> rainToday += 0.1618; // Each dump is 0.1618mm of water
>> rainHour[minutesRain] += 0.1618; // Increase this minute's amount of 
>> rain
>>   last_micros1 = micros();
>>   }
>> }
>>
>> /***

[weewx-user] Re: Bresser 6in1

[Bob Atchley]

Hi Remy and Sebastien

I have a Youshiko YC9388 Weather station that I believe is identical to the 
Bresser 6 in 1 with usb connection to a PC.

I found it was incompatible with the existing weewx weather station 
drivers.  However I have been able to reverse engineer the usb protocol and 
have written a driver that should work.

I have uploaded the new driver for the 6 in 1 weather stations with PC 
connected consoles:

Youshiko YC9388

Bresser PC 6 in 1

Garni 935PC

Ventus W835

If you go to the weewx wiki  and 
search for the ws6in1 driver and follow the link hopefully the readme.txt 
will give you enough information to get going.

Good luck

Bob

-- 
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/42a55d3d-6e19-485b-902a-124b2b11f83f%40googlegroups.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

[Tom Keffer]

Keimpe, please see the Wiki article *Understanding paths
*.

On Tue, May 5, 2020 at 9:00 AM Keimpe Bleeker  wrote:

> Thanks, wee_debug is working!
>
> pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --info --verbosity=1
> Using verbosity=1, displaying most info
>
> wee_debug output will be sent to stdout(console)
>
> Using configuration file /home/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database
> 'archive_sqlite'
>
> System info
>   Platform:   Linux-4.19.97-v7l+-armv7l-with-debian-10.3
>   Python Version: 3.7.3
>
> Load Information
>   1 minute load average:  0.01
>   5 minute load average:  0.02
>   15 minute load average: 0.00
>
> General Weewx info
>   Weewx version 4.0.0 detected.
>
> Station info
>   Station type: Simulator
>   Driver:   weewx.drivers.simulator
>
> Driver info
> [Simulator]
> # This section is for the weewx weather station simulator
>.
>
> But the important wee_config, to change from Simulator to Vantage still
> says:
>
> pi@Pi4Weewx:/home/weewx $ wee_config --config=/home/weewx/weewx.conf
> bash: wee_config: opdracht niet gevonden
> pi@Pi4Weewx:/home/weewx $
>
>
>
>
>
> Op dinsdag 5 mei 2020 17:41:44 UTC+2 schreef Tom Keffer:
>>
>> Oh, one other thing: you said this applies to "all utilities." Example?
>>
>> -tk
>>
>> On Tue, May 5, 2020 at 8:39 AM Tom Keffer  wrote:
>>
>>> OK. That looks normal.  There is no "wee_debug not found" error.
>>>
>>> You have to give it something to do. You probably want a --info flag
>>>
>>> /home/weewx/bin/wee_debug --verbosity=1 --info
>>>
>>> Be sure to read the manual
>>> !
>>>
>>>
>>>
>>> On Tue, May 5, 2020 at 8:29 AM Keimpe Bleeker  wrote:
>>>
 Wee_debug --verbostity=1 results in help-info:

 pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1
 Usage: wee_debug --help
wee_debug --info
 [CONFIG_FILE|--config=CONFIG_FILE]
 [--output|--output DEBUG_PATH]
 [--verbosity=0|1|2]
wee_debug --version

 Description:

 Generate a standard suite of system/weewx information to aid in remote
 debugging. The wee_debug output consists of two parts, the first part
 containing
 a snapshot of relevant system/weewx information and the second part a
 parsed and
 obfuscated copy of weewx.conf. This output can be redirected to file
 and posted
 when seeking assistance via forums or email.

 Actions:

 --info   Generate a debug report.

 Options:
   -h, --helpshow this help message and exit
   --config=CONFIG_FILE  Use configuration file CONFIG_FILE.
   --infoGenerate weewx debug output.
   --output  Write wee_debug output to DEBUG_PATH. DEBUG_PATH
 includes path and file name. Default is
 /var/tmp/weewx.debug.
   --verbosity=N How much detail to display, 0-2, default=1.
   --version Display wee_debug version number.

 wee_debug will attempt to obfuscate obvious personal/private
 information in
 weewx.conf such as user names, passwords and API keys; however, the user
 should thoroughly check the generated output for personal/private
 information
 before posting the information publicly.
 pi@Pi4Weewx:/home/weewx $

 Or for wee_config ends in:

 pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $
 bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet
 pi@Pi4Weewx:/home/weewx $

 NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)


 Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:
>
> OK. So, you're telling me that running a program
> /home/weewx/bin/wee_debug, that clearly exists in a directory listing,
> results in an error "wee_debug not found". That doesn't make sense.
>
> I'd like to see the actual console output. Run the command, then copy
> and paste from the console output into your post. DO NOT TAKE A 
> SCREENSHOT.
> Just highlight the resultant text, right click, select "Copy", then paste
> into your post.
>
> -tk
>
> On Tue, May 5, 2020 at 7:41 AM Keimpe Bleeker 
> wrote:
>
>> See attached screenshot, all the necessary files and folders, as it
>> appears.
>>
>>
>> Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:
>>>
>>> So, what is in /home/weewx/bin?
>>>
>>> On Tue, May 5, 2020 at 5:10 AM Keimpe Bleeker 
>>> wrote:
>>>
 Sorry, typo... use the command exactly as you mentioned.


 Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:
>
> Keimpe
>
> Trying to clarify what you tried. You said

Re: [weewx-user] rPI SD Card - IMG backup, cloning, transfer to larger/smaller (Windows)

[Tom Keffer]

I just use the Unix utility "dd". For example


*dd if=/dev/sdc of=/dev/sdd bs=8M*

The disks should not be in use. That is, they should not be mounted.

-tk

On Tue, May 5, 2020 at 12:59 PM Xant  wrote:

>
> My experience with rPI SD cards. The following refers to Windows/PC with a
> SD card slot or with a USB SD card reader/writer.
>
> *1) Backup, Image or Cloning *- to equal or larger SD card
>
> *Win32DiskImager* - https://sourceforge.net/projects/win32diskimager/
>
> Win32DiskImager is the "to-go" option for rPI SD cards disk imaging,
> backup or cloning. It creates a 'perfect' image as it copies 'bit-by-bit'
> data clusters to an IMG file. Thus, it creates a file as big as the Card
> size itself as it even 'copies empty cluster data'.
>
> But bigger, not always better.
> As SD storage size prices keeps following, its easy to get tempted to
> slide a very large SD card into rPI, and I took this bait when upgrading to
> rPI-4. I placed a 64Gb SD Card, but turned out that only used a small
> fraction of the card storage (~7%, for WeeWx, MQTT, wx-database,
> Belchertown skin, InfluxDB, Grafana, etc).
> On the other side, it takes long to Backup and creates very large IMG
> files.
>
> Thus, Win32DiskImager can transfer IMG to same or larger SD card, where
> the extra space would be "unallocated" and needs to be expanded
> (raspi-config).
>
>
> *2) Transfer to Smaller SD Card*
>
> Transfer to a Smaller SD Card is possible and there are different
> approaches pending OS, Software or more than 1 SD card slot.
> The easiest (and free) way I found was through '*Paragon Backup &
> Recovery*' - https://www.paragon-software.com/us/free/br-free/#
> Paragon creates a 'recovery-point file' that saves only the actual data
> from SD card that can be transferred back to "any size" SD card,
> same/smaller/larger (data usage considered).
>
> This worked perfect in my case, and now have a better size-fit SD card
> running on rPI=4 for WeeWX.
>
> Xant
>
> --
> 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/71ea00fc-de53-43fa-89e4-90dd7b101611%40googlegroups.com
> 
> .
>

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

Re: [weewx-user] Weatherdata (rain) from own Weatherstation (Arduino)

[John Kline]

If you have some experience programming, you might consider writing a driver 
for your weather station (as opposed to hacking something just for rain).

See:
http://www.weewx.com/docs/customizing.htm#porting

> On May 5, 2020, at 1:56 PM, Johann Schneider  
> wrote:
> 
> 
> Hello everybody!
> Thank you for your answers.
> Sorry for my difficult to understand question.
> So my weather station sends the measured values every 15 seconds.
> If it sends rain, I get the hourly rain value and the rain value for the 
> whole day. The rain value for the whole day is cumulative and is set to 0 at 
> 00:00. The hourly rain value at the beginning of the rain is always 
> calculated for one hour.
> I thought I could simply import the data into weewx with "fileparser". This 
> also works with the other data. Just not with the rain values.
> John Kline's suggestion sounds great. That's how I would have imagined it.
> How can I implement something for the rain value?
> 
> kind regards
> 
> Johnny
> 
> Am Dienstag, 5. Mai 2020 03:19:43 UTC+2 schrieb John Kline:
>> 
>> Hi Tom,
>> 
>> Apologies in advance if I have misunderstood the question and have made you 
>> read what I believe you already know.
>> 
>> If the question is can a driver be written to make use of rain emitted every 
>> 15 seconds and resetting every hour, I believe such a driver can easily be 
>> written.
>> 
>> The RainWise CC3000 reports total rain and resets once a day.
>> 
>> The delta is calculated with the following call in the cc3000 driver:
>> return weewx.wxformulas.calculate_rain(rain_total, last_rain)
>> 
>> If the the rain total is less than the last rain total recorded, it is 
>> assumed that the counter reset.  On the CC3000, the reset is at midnight; 
>> but this would work just fine if the reset occurs every hour.
>> 
>> I suspect other drivers do the same in this regard (convert total rain to 
>> incremental).
>> 
 On May 4, 2020, at 3:58 PM, Tom Keffer  wrote:
 
>>> 
>>> Hello Johnny,
>>> 
 Unfortunately, the data is summed up every few minutes and the values no 
 longer fit.
 For example, I have 0.15mm of rain in the last hour, then the value after 
 each loop adds up until the hour is over.
>>> 
>>> If I understand you correctly, your software emits the total rain measured 
>>> so far in an hour, which then gets reset at the end of the hour.
>>> 
>>> If that that is the case, then, no, that would not work well with weewx. In 
>>> weewx, observation type 'rain' is the total amount of rain measured for 
>>> that packet, and only for that packet. Typically, it is a very small 
>>> number. This is explained in a little more detail in the section 
>>> genLoopPackets in the Customizing Guide.
>>> 
>>> Or, maybe I am misunderstanding your problem.
>>> 
>>> -tk
>>> 
 On Mon, May 4, 2020 at 2:02 PM Johann Schneider  
 wrote:
 Hello everybody!
 I have a little problem. Sorry for my very bad english. I come from 
 Germany and my English is not the best. My experience with weewx is also 
 very limited. I built a weather station 3 years ago. It consists of an 
 Arduino Mega and several sensors.
 Among other things, a rain sensor that reports 0.16mm of rain per seesaw
 The values ​​are pushed to iobroker (similar to openhab) every 15 seconds. 
 Here is an excerpt from my Arduino codes:
 /*
 Auswertung Regenmengensensor mit Regenwippe
 - Counter kann durch reed-Kontakt oder Hallsensor erfolgen
 - i2c eeprom AT24C256
 - i2c Adresse EEPROM (default: 0x50)
 */
 #include 
 //#include 
 #//include 
 //
 /*PIN-Section   */
 /*  Hier Sensor-Pins definieren */
 //
 //#define RAIN_COUNT_PIN 7
 #define RAIN_COUNT_PIN 30
 //
 /*   Variablen-Section  */
 //
 long lastSecond; // Original - The millis counter to see when a second 
 rolls by
 unsigned int minutesSinceLastReset; //Used to reset variables after 24 
 hours. Imp should tell us when it's midnight, this is backup.
 byte secondsRain; //When it hits 60, increase the current minute
 byte minutesRain; //Keeps track of where we are in various arrays of data
 
 volatile float rainHour[60]; //60 floating numbers to keep track of 60 
 minutes of rain
 volatile unsigned long raintime, rainlast, raininterval, rain;
 volatile unsigned long last_micros1;
 long debouncing_time1 = 3; // in millis -> eleminiert evtl 
 REED-Kontakt-Prellen
 boolean RainTimeReset = false;
 
 //struct Configuration
 //{
 //  float regenTag;
 //  float regenStunde;
 //}eepconfig EEMEM;
 
 //AT24C256<0x50> eep; // Das EEProm auf der china üblichen RTC3231 
 
 /

[weewx-user] Re: [weewx-development] Feature Request : Add calculate method standard OMM on daily database

[Graham Eddy]

i don’t know what the OMM standard is either, but australian BOM (govt weather 
bureau) uses 9am-9am as its rainfall reporting period. i have been meaning to 
get around to writing an extension to support this duration this since i first 
read the weex customisation documentation…

> On 6 May 2020, at 7:37 am, Tom Keffer  wrote:
> 
> Sorry. Can you give us more details? I do not know what the OMM standard is. 
> And, I don't know what you mean by "Weewx calculate each 00AM to 00PM"
> 
> On Tue, May 5, 2020 at 9:07 AM Florentin Prevost  > wrote:
> Hi,
> 
> I would like to know if it possible in futur to add in database values from 
> OMM standard. At the moment, Weewx calculate each 00AM to 00PM. 

-- 
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/6DE8EB42-4CAC-4B61-9922-40CBB77E5583%40gmail.com.

[weewx-user] Feeding weewx from Meteobridge

[Ryan Stasel]

Hi All,

I'd really like to feed weewx from my Meteobridge Nano SD. Looks like I 
could do this with the fileparse driver into weewx, just uploaded once a 
minute to weewx box, or possibly I could get Meteobridge to push data 
directly into the weewx archive DB (I saw a couple year old thread about 
that here: https://groups.google.com/forum/#!topic/weewx-user/1A8z8VUY98c). 
To answer the "why?" I like the format of Weewx's data archives, NOAA 
reports, graphs, etc. Would love to actually pump all my archive into weewx 
as well (over 10 years). 

Anyone have any input on how to do this? Anyone doing this? It should be 
super doable... but admittedly hacky as heck. =)

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/930b652a-844e-4e07-abc8-3e1694b5%40googlegroups.com.

Re: [weewx-user] Python versions

[Colin Larsen]

Still going ..

Installed the new mqtt and now get this error

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: Caught
unrecoverable exception:

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   No
module named 'paho'

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   Traceback
(most recent call last):

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weewxd", line 148, in main

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   engine
= weewx.engine.StdEngine(config_dict)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
self.loadServices(config_dict)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   obj
= weeutil.weeutil.get_object(svc)(self,config_dict)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   mod
= __import__(module)

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
"/usr/share/weewx/user/mqtt.py", line 94, in 

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   import
paho.mqtt.client as mqtt

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
ImportError:
No module named 'paho'

May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
Exiting.


Tried to install Paho and I get  ...


*pi@raspberrypi*:*/etc/default $* sudo pip install paho-mqtt

Requirement already satisfied: paho-mqtt in
/usr/local/lib/python2.7/dist-packages


So how do I install it for python3 please :)



Cheers

Colin

On Tue, 5 May 2020 at 00:18, Graham Eddy  wrote:

> this (ujson instead of python-cjson, then install mqtt extension) seems to
> have worked up to point that weewx.log reports its mqtt client is
> successfully publishing loop data
>
> sudo python3.7 -m pip install ujson
>
>
> On 4 May 2020, at 8:58 pm, Graham Eddy  wrote:
>
> i have only just become interested in mqtt (to make my custom weewx gauges
> near realtime).
> the link to the MQTT weewx extension mentioned below lists two
> prerequisites: paho-mqtt, python-cjson.
> paho-mqtt installed fine.
> python-cjson fails.
>
>
> --
> 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/296D8321-100E-45B1-A47A-2657960A2942%40gmail.com
> 
> .
>

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

Re: [weewx-user] Python versions

[Colin Larsen]

Fixed that one with; sudo python3 -m pip install paho-mqtt

Now I have an error that looks like it is Open Wetaher map?

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: Caught
unrecoverable exception:

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   invalid
syntax (owm.py, line 84)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   Traceback
(most recent call last):

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weewxd", line 148, in main

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   engine
= weewx.engine.StdEngine(config_dict)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
self.loadServices(config_dict)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   obj
= weeutil.weeutil.get_object(svc)(self,config_dict)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   mod
= __import__(module)

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: File
"/usr/share/weewx/user/owm.py", line 84

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__:   except
KeyError, e:

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
^

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
SyntaxError:
invalid syntax

May  6 14:29:07 raspberrypi weewx[6896] CRITICAL __main__: 
Exiting.

On Wed, 6 May 2020 at 14:19, Colin Larsen  wrote:

> Still going ..
>
> Installed the new mqtt and now get this error
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: Caught
> unrecoverable exception:
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   No
> module named 'paho'
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   Traceback
> (most recent call last):
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weewxd", line 148, in main
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
> engine
> = weewx.engine.StdEngine(config_dict)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
> self.loadServices(config_dict)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   obj
> = weeutil.weeutil.get_object(svc)(self,config_dict)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   mod
> = __import__(module)
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: File
> "/usr/share/weewx/user/mqtt.py", line 94, in 
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
> import
> paho.mqtt.client as mqtt
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__:   
> ImportError:
> No module named 'paho'
>
> May  6 14:16:47 raspberrypi weewx[6432] CRITICAL __main__: 
> Exiting.
>
>
> Tried to install Paho and I get  ...
>
>
> *pi@raspberrypi*:*/etc/default $* sudo pip install paho-mqtt
>
> Requirement already satisfied: paho-mqtt in
> /usr/local/lib/python2.7/dist-packages
>
>
> So how do I install it for python3 please :)
>
>
>
> Cheers
>
> Colin
>
> On Tue, 5 May 2020 at 00:18, Graham Eddy  wrote:
>
>> this (ujson instead of python-cjson, then install mqtt extension) seems
>> to have worked up to point that weewx.log reports its mqtt client is
>> successfully publishing loop data
>>
>> sudo python3.7 -m pip install ujson
>>
>>
>> On 4 May 2020, at 8:58 pm, Graham Eddy  wrote:
>>
>> i have only just become interested in mqtt (to make my custom weewx
>> gauges near realtime).
>> the link to the MQTT weewx extension mentioned below lists two
>> prerequisites: paho-mqtt, python-cjson.
>> paho-mqtt installed fine.
>> python-cjson fails.
>>
>>
>> --
>> 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/296D8321-100E-45B1-A47A-2

Re: [weewx-user] Feeding weewx from Meteobridge

[Mike Harold Chan]

Im a meteobridge use, as far I know theres no yet available Interceptor yet
available for weewx - meteobridge, I tried to research for that too long
but so far theres none for meteobridge Interceptor

On Wed, May 6, 2020 at 9:53 AM Ryan Stasel  wrote:

> Hi All,
>
> I'd really like to feed weewx from my Meteobridge Nano SD. Looks like I
> could do this with the fileparse driver into weewx, just uploaded once a
> minute to weewx box, or possibly I could get Meteobridge to push data
> directly into the weewx archive DB (I saw a couple year old thread about
> that here: https://groups.google.com/forum/#!topic/weewx-user/1A8z8VUY98c).
> To answer the "why?" I like the format of Weewx's data archives, NOAA
> reports, graphs, etc. Would love to actually pump all my archive into weewx
> as well (over 10 years).
>
> Anyone have any input on how to do this? Anyone doing this? It should be
> super doable... but admittedly hacky as heck. =)
>
> 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/930b652a-844e-4e07-abc8-3e1694b5%40googlegroups.com
> 
> .
>

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

[weewx-user] Re: [weewx-development] Feature Request : Add calculate method standard OMM on daily database

[John Smith]

On Wednesday, 6 May 2020 10:20:04 UTC+10, Graham Eddy wrote:
>
> i don’t know what the OMM standard is either, but australian BOM (govt 
> weather bureau) uses 9am-9am as its rainfall reporting period. i have been 
> meaning to get around to writing an extension to support this duration this 
> since i first read the weex customisation documentation…
>

Gary already has:

https://github.com/weewx/weewx/issues/91 

-- 
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/b9bc4c3a-57f8-4c5c-a6d3-8fa6c551e77d%40googlegroups.com.

Re: [weewx-user] Feeding weewx from Meteobridge

[Ryan Stasel]

I mean. I could just have it use loop, as at least the nano will support doing 
that. But I’m trying to get away from handing off control to another system 
(I’m moving away from weathercat because of this). 

Fileparse may be the easiest. Will need to poke at it. 

> On May 5, 2020, at 20:29, Mike Harold Chan  wrote:
> 
> 
> Im a meteobridge use, as far I know theres no yet available Interceptor yet 
> available for weewx - meteobridge, I tried to research for that too long but 
> so far theres none for meteobridge Interceptor 
> 
>> On Wed, May 6, 2020 at 9:53 AM Ryan Stasel  wrote:
>> Hi All,
>> 
>> I'd really like to feed weewx from my Meteobridge Nano SD. Looks like I 
>> could do this with the fileparse driver into weewx, just uploaded once a 
>> minute to weewx box, or possibly I could get Meteobridge to push data 
>> directly into the weewx archive DB (I saw a couple year old thread about 
>> that here: https://groups.google.com/forum/#!topic/weewx-user/1A8z8VUY98c). 
>> To answer the "why?" I like the format of Weewx's data archives, NOAA 
>> reports, graphs, etc. Would love to actually pump all my archive into weewx 
>> as well (over 10 years). 
>> 
>> Anyone have any input on how to do this? Anyone doing this? It should be 
>> super doable... but admittedly hacky as heck. =)
>> 
>> 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/930b652a-844e-4e07-abc8-3e1694b5%40googlegroups.com.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/4FETwWj0OfA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAKjfRK%3Dyt%3Dazm%3D45uk9mvRoyfqFxp96vG2qBNpvKZsfhhrEChg%40mail.gmail.com.

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

Re: [weewx-user] Re: [weewx-development] Feature Request : Add calculate method standard OMM on daily database

[Graham Eddy]

“seek, and ye shall find” :-)

anything out there for 9am-9am the *previous* day? (or even since 9am yesterday 
so i can subtract since 9am today)

> On 6 May 2020, at 2:07 pm, John Smith  wrote:
> 
> 
> 
> On Wednesday, 6 May 2020 10:20:04 UTC+10, Graham Eddy wrote:
> i don’t know what the OMM standard is either, but australian BOM (govt 
> weather bureau) uses 9am-9am as its rainfall reporting period. i have been 
> meaning to get around to writing an extension to support this duration this 
> since i first read the weex customisation documentation…
> 
> Gary already has:
> 
> https://github.com/weewx/weewx/issues/91 
>  
> 
> -- 
> 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/b9bc4c3a-57f8-4c5c-a6d3-8fa6c551e77d%40googlegroups.com
>  
> .

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

Re: [weewx-user] Re: [weewx-development] Feature Request : Add calculate method standard OMM on daily database

[John Smith]

On Wednesday, 6 May 2020 15:01:20 UTC+10, Graham Eddy wrote:
>
> “seek, and ye shall find” :-)
>
> anything out there for 9am-9am the *previous* day? (or even since 9am 
> yesterday so i can subtract since 9am today)
>
>
$since($hour=9,$today=False).rain.sum.formatted 

-- 
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/06df511b-8481-4b81-b215-72d255f45804%40googlegroups.com.