Re: [weewx-user] Missing xstats module

[Paul Bartholdi]

Dear Thomas,

I moved this morning from 4.1.0 to 4.1.1 and discovered the error (in 
/var/log/syslog):
Module 'user.xstats' has no attribute 'XStatsService' when searching ...

In fact it was already there in 4.1.0, but I didn't noticed, as it had no 
apparent effects.

I tries to figure out what/where is wrong, but no success. Then I found you 
answer, implemented it and the result is catastrophic. Weewx stops 
working.  
Running  "wee_extension --uninstall "  is not better.  (Error: No module 
named 'user.xstats', seems normal, but I don;t know where to go.
May be I should better reinstall weewx.

Running python 3, on a Debian 10.4 X64 / DEBUG is ON.

This is the extract from syslog:

   Module 'user.xstats' has no attribute 'XStatsService' when searching 
for 'user.xstats.XStatsService'
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   Traceback 
(most recent call last):
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1098, in get_object
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   mod = 
getattr(mod, part)
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   
AttributeError: module 'user.xstats' has no attribute 'XStatsService'
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   During 
handling of the above exception, another exception occurred:
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   Traceback 
(most recent call last):
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 148, in main
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   engine 
= weewx.engine.StdEngine(config_dict)
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 75, in __init__
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   
self.loadServices(config_dict)
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   obj = 
weeutil.weeutil.get_object(svc)(self,config_dict)
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1102, in get_object
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   
"Module '%s' has no attribute '%s' when searching for '%s'" % 
(mod.__name__, part, module_class))
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   
AttributeError: Module 'user.xstats' has no attribute 'XStatsService' when 
searching for 'user.xstats.XStatsService'
Jun  2 23:04:57 aragorn weewx[4012] CRITICAL __main__:   Exiting.

Any help will be welcome, but no hurry! It is time to sleep form me...

Best regards and thanks, Paul


Le jeudi 18 janvier 2018 00:33:55 UTC+1, Thomas Keffer a écrit :
>
> While xstats is included in the weeWX distribution as an example of an 
> extension, it is not part of the code base. If you want to use it, you 
> would have to install it first.
>
> It's location depends on the install method you used 
> , 
> typically either /usr/share/doc/weewx/examples/xstats or 
> /home/weewx/examples/xstats.
>
> Installation instructions are included in the accompanying readme.txt 
> file, located in the subdirectory.
>
> -tk
>
>
> On Wed, Jan 17, 2018 at 3:56 PM, ON9CB > 
> wrote:
>
>> Hi All,
>>
>> Really struggling to make sense of this one.  Just completed a fresh 
>> install of 3.8.0 on a fresh install of Raspbian Stretch on a Pi3B after a 
>> replacement SD card - failed after only a week in service!  
>>
>> Copied the backup weewx.conf, skins, and DB's and all looked good until I 
>> got the xstats module missing error, followed by 'launch of report thread 
>> aborted...'.  The aborted thread errors started after I upgraded to 3.8.0.  
>> The xstats errors started today.  Debug report is attached.
>>
>> Also, the graphs are all updating nicely, but apparently no index page is 
>> being generated. 
>>
>> Thanks in advance for any assistance!!
>>
>> Craig
>>
>>
>>
>> >>>
>>
>> Jan 17 23:09:12 Weewx weewx[1828]: manager: Added record 2018-01-17 
>> 23:09:00 CET (1516226940) to database 'weewx.sdb'
>> Jan 17 23:09:12 Weewx weewx[1828]: manager: Added record 2018-01-17 
>> 23:09:00 CET (1516226940) to daily summary in 'weewx.sdb'
>> Jan 17 23:10:10 Weewx weewx[1828]: manager: Added record 2018-01-17 
>> 23:10:11 CET (1516227011) to database 'cmon.sdb'
>> Jan 17 23:10:10 Weewx weewx[1828]: manager: Added record 2018-01-17 
>> 23:10:11 CET (1516227011) to daily summary in 'cmon.sdb'
>> Jan 17 23:10:12 Weewx weewx[1828]: manager: Added record 2018-01-17 
>> 

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.

Re: [weewx-user] Problem in TE923 driver with Weewx 4.0.0 on Python 3.7

[Paul Bartholdi]

I had the same problem, and this new version sovles it. THANK YOU !  
Paul
(By the way, I started 60 years ago with FORTRAN I...)

Le vendredi 1 mai 2020 16:38:34 UTC+2, Michael a écrit :
>
> ;)
>
> this version looks good. No more Errors. Thank you very much for the fast 
> support.
>
> Michael
>

-- 
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/caa78b6f-00ec-4413-89df-3ba7f08cdc11%40googlegroups.com.

[weewx-user] Re: Weewx 3.9.2 Upgrade

[Paul Bartholdi]

Same for me with an IROX Pro X and many local adaptations. No problem at 
all. Thanks!

Le mercredi 17 juillet 2019 14:08:56 UTC+2, HoracioDos a écrit :
>
> For those who might be interested to upgrade weewx. I didn't find any 
> problems yet with a fine offset weather station on buster.
>
>

-- 
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/59850135-17e7-4625-84e1-a2a8d2f979a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Stupid question / solved !

[Paul Bartholdi]

I thought it was simple, sorry.

sudo wee_database /etc/weewx/weewx.conf --drop-daily
sudo wee_database /etc/weewx/weewx.conf --rebuild-daily

I still don't understand how I got there.

What a wunderful system, where ther is always a solution not that far.

Thanks again, Paul

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Stupid question

[Paul Bartholdi]

I did some thing stupid and wrong but what, probably typing to fast...
Sorry,  what to do after this error produced when I want to restart the
service weewx (ubuntu). Paul

manager: Starting backfill of daily summaries
engine: Caught unrecoverable exception in engine:
  lastUpdate(2019-04-09 22:25:00 CEST (1554841500)) >
lastRecord(2019-04-09 22:20:00 CEST (1554841200))
  Traceback (most recent call last):
File "/usr/share/weewx/weewx/engine.py", line 884, in main
  engine = engine_class(config_dict)
File "/usr/share/weewx/weewx/engine.py", line 78, in __init__
  self.loadServices(config_dict)
File "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
  self.service_obj.append(weeutil.weeutil._get_object(svc)(self,
config_dict))
File "/usr/share/weewx/weewx/engine.py", line 500, in __init__
***  self.setup_database(config_dict)
File "/usr/share/weewx/weewx/engine.py", line 617, in setup_database
  _nrecs, _ndays = dbmanager.backfill_day_summary() #
@UnusedVariable
File "/usr/share/weewx/weewx/manager.py", line 1447, in
backfill_day_summary
  timestamp_to_string(lastRecord)))
  ViolatedPrecondition: lastUpdate(2019-04-09 22:25:00 CEST
(1554841500)) > lastRecord(2019-04-09 22:20:00 CEST (1554841200))

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] problems with graphics/label/accented characters

[Paul Bartholdi]

Hello,

I did some clean-up of various files, and have a few problems related with 
graphics.
I am using version 3.9.1(p2). Station is an IROX PRO X (te923).  'interval' 
is 5 minutes.
All accented characters are given in "html-entities".
Every thing works perfectly, no problem except:

1 I have been able to use accented characters in tables and graphics, 
except in the top labels. No encoding works.

2 I am using 'filepile' to get the instant power produced by the solar 
panels. The data are put in column 'radiation'. It works very nicely. Is is 
a simple and very effective solution.
  For week/month/year 'power' has no meaning, I want 'energy', the 
'sum/integral' over a given interval (1d, 1w, 1m...).

For the tables, I found the following solution (in week.html.tmpl) :

   
  $week.radiation.max le 
$week.radiation.maxtime.format("%d/%m  %H:%M")
  $("%0.3f kWh" % (0.08333*$week.radiation.sum.raw)) 


Is there a better way to do it?   adding a new column (as rainrate)?

Using the following code in skin.conf, I get the right graph, but the 
y-scale is wrong by a factor of 12 (12 measurements per hour).

[[[weekradiation]]]
yscale = None, None, 1
plot_type = bar
radiation
aggregate_type = sum
aggregate_interval = 86400
label = Energie PV

How, where can I produce the right scaling?

In general, what is the best place to do these kind of adaptations?

Thanks for any help/suggestion.   Yours, Paul

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Adding a new object in the ephem database

[Paul Bartholdi]

>
> Dear Thomas, 
>

Just a line to say that now everything is perfect (see 
http://shire-bdi.gotdns.com/weewx ). ! Thank for all your help.Paul

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Adding a new object in the ephem database

[Paul Bartholdi]

Dear Thommas,

Once more you impressed me a lot, such quick and well formed answer. Thanks.

Now I am afraid to say that there is still a buf, probably a typo or some
thing like that. I checked "my" additions in "extensions.py" and
"almanac.py" (and of course in "index.html.tmpl"), and believe they were
correctly done.
Just a question: where can I find the generated file
"cheetah__etc_weewx_skins_Standard_index_html_tmpl_1548001524_26_16364.py" ?

Here is the .log of the error:

reportengine: Found configuration file /etc/weewx/skins/Standard/skin.conf
for report StandardReport
cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac',
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
'weewx.cheetahgenerator.Extras']
manager: Daily summary version is 2.0
cheetahgenerator: Generate failed with exception ''
cheetahgenerator:  Ignoring template
/etc/weewx/skins/Standard/index.html.tmpl
cheetahgenerator:  Reason: 'ephem.EllipticalBody' object is not callable
  Traceback (most recent call last):
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in
generate
  print >> _file, compiled_template
File "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line
1005, in __str__
  rc = getattr(self, mainMethName)()
File
"cheetah__etc_weewx_skins_Standard_index_html_tmpl_1548001524_26_16364.py",
line 2545, in respond
File
"cheetah__etc_weewx_skins_Standard_index_html_tmpl_1548001524_26_16364.py",
line 1155, in __errorCatcher156
File "", line 1, in 
File "/usr/share/weewx/weewx/almanac.py", line 355, in __getattr__
  ephem_body = _get_ephem_body(self.heavenly_body)
File "/usr/share/weewx/weewx/almanac.py", line 424, in
_get_ephem_body
  ephem_body = getattr(ephem, cap_name)()
  TypeError: 'ephem.EllipticalBody' object is not callable
cheetahgenerator: Generated 13 files for report StandardReport in 0.56
seconds
manager: Daily summary version is 2.0

Best regards, Paul


Le dim. 20 janv. 2019 à 01:28, Thomas Keffer  a écrit :

> This is a good question, and it took me a while to figure out how to work
> around the limitations of pyephem. Try this:
>
> 1. Put the following in user/extensions.py:
>
> import ephem
> eros = ephem.readdb("433
> Eros,e,10.8276,304.3222,178.8165,1.457940,0.5598795,0.22258902,71.2803,09/04.0/2017,2000,H11.16,0.46")
> ephem.Eros = eros
>
> 2. Modify the WeeWX module weewx/almanac.py so that the function
> _get_ephem_body() looks like this:
>
> def _get_ephem_body(heavenly_body):
> # The library 'ephem' refers to heavenly bodies using a capitalized
> # name. For example, the module used for 'mars' is 'ephem.Mars'.
> cap_name = heavenly_body.capitalize()
>
> # If the heavenly body is a star, or if the body does not exist, then
> an
> # exception will be raised. Be prepared to catch it.
> try:
> ephem_body = getattr(ephem, cap_name)()
> except AttributeError:
> # That didn't work. Try a star. If this doesn't work either,
> # then a KeyError exception will be raised.
> ephem_body = ephem.star(cap_name)
> except TypeError:
> ephem_body = getattr(ephem, cap_name)
>
> return ephem_body
>
> You are adding the two highlighted lines.
>
> 3. Then use this in your template:
>
> $almanac.eros.rise
>
> for when it rises, etc. (treat it just like any other planet).
>
> Double check the answer. I'm not 100% confident this will work. If it
> does, I'll add the changes for weewx/almanac.py to the code base.
>
> -tk
>
> On Sat, Jan 19, 2019 at 10:20 AM Paul Bartholdi 
> wrote:
>
>> Hi,
>>
>> I nodified a few years ago the "Standard/index.html.tmpl" to print the
>> main solar systems objects (sun, moon, Jupiter...).
>> Now I want to pint the same informations but for the minor planet Eros
>> that pass very (very relative!) the earth in the few next days.
>> This implies adding the python line:
>>
>>  eros = ephem.readdb("433
>> Eros,e,10.8276,304.3222,178.8165,1.457940,0.5598795,0.22258902,71.2803,09/04.0/2017,2000,H11.16,0.46")
>>
>> and then (in index.html.tmp) :
>>
>>
>>   Rise  :
>>   $almanac.eros.rise
>> 
>>
>> Where should I add the " eros = ephem.readdb(...) line ?   (
>> index.html.tmpl ?  almanac.py ? elsewhere ?).
>>
>> Thanks for any help/advice! Paul
>>
>>
>> --
>> You received this message b

[weewx-user] Adding a new object in the ephem database

[Paul Bartholdi]

Hi,

I nodified a few years ago the "Standard/index.html.tmpl" to print the main 
solar systems objects (sun, moon, Jupiter...).
Now I want to pint the same informations but for the minor planet Eros that 
pass very (very relative!) the earth in the few next days.
This implies adding the python line:

 eros = ephem.readdb("433 
Eros,e,10.8276,304.3222,178.8165,1.457940,0.5598795,0.22258902,71.2803,09/04.0/2017,2000,H11.16,0.46")

and then (in index.html.tmp) :

   
  Rise  :
  $almanac.eros.rise


Where should I add the " eros = ephem.readdb(...) line ?   ( 
index.html.tmpl ?  almanac.py ? elsewhere ?).

Thanks for any help/advice! Paul


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Metric v US databases

[Paul Bartholdi]

I fully support the change to metric units. 
- the international metric system is more than 200 years old. At the 
origin, all countries agreed to adopt the Greenwich (British/american) 
meridian as a reference, and, in exchange, the metric unit system first 
developed in France. After 200 years, the non British/American have long 
ago adopted the Greenwich meridian, but the "imperial" unit system is still 
in use; The move to metric is well advanced in England. I thought that is 
was mandatory according to the laws in the US...
- the mixed use of metric/imperial units has costed hundreds millions 
dollar to the US, when they lost at least 2 satellites (to Mars) because 
NASA and GPL didn't used the same units system;
- the metric is much simpler to use, in particular when the scale is 
different. What is the force on a square foot when the pressure is given in 
psi...
- ...
On the other side, I would NOT support a fork. There is enough work still 
to be done for new stations, new skins etc. Let's keep ONE weewx, is it 
such a powerful and useful tool!

Le samedi 12 janvier 2019 04:23:06 UTC+1, Andrew Milner a écrit :
>
> Having read for the umpteenth time recently comments implying that there 
> is no need to change the database units from US to Metric I thought it was 
> time to give my pennyworth.  IMHO there is every reason in the world to 
> change the units if one is living in the rest of the world outside the US.  
> When (not if) one has to look at the database to resolve an issue using 
> sqlite3 or MySQL there is nothing worse than being faced with a load of 
> data which is unrecognizable and means nothing since the units are such 
> they are never seen during daily life.  pressures of 30. mean nothing 
> when daily pressures are in mbar and temperatures are meaningless when in 
> farenheit and daily weather temperatures are in Celsius.  IMHO if you live 
> outside the US your database should be Metric or Metricwx so that the data 
> becomes meaningful when viewed directly.
>
> I agree that for the purposes of weewx this is not necessary as all 
> conversions will happen automatically.
>
> One final thing which I have done to my MySQL database is to redefine the 
> columns to limit the number of decimal places to 2 in most cases.  This 
> makes viewing with MySQL directly much much more readable and gets rid of 
> the totally unnecessary additional decimal places with little (if any) 
> effect on weewx.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Paul Bartholdi]

The problem you see :

  *DatabaseError: (1055, "Expression #2 of SELECT list is not in GROUP 
BY clause and contains nonaggregated column 
'weewx.archive_day_rain.dateTime' which is not functionally dependent on 
columns in GROUP BY clause; this is incompatible with 
sql_mode=only_full_group_by")*

is related to MySQL* :* Earlier versions were not to strict and accepted 
expressions that are correct for usual logic but incorrect according to SQL 
standard. They are now rejected by default, this is the reason of your 
error.
You can change this behavior by adding the (MySQL) command *" SET 
@@sql_mode=""; " * before the offending " SELECT " or simply at the 
beginning of you SQL code. In any case you have to repeat it whenever you 
reuse MySQL.

Note that this is NOT a MySQL error, the rejection of your command is 
correct according to the SQL standard.

The better solution is to correct the statement, that is adding " DateTime 
" in the " GROUP BY " list.  But to do it I need to dig further into weewx 
code.

An other solution is to change the defaults of MySQL from 
"*sql_mode=only_full_group_by" 
*to* "**sql_mode="" ", *making MySQL non standard for all as* it *was in 
earlier version. I would not do it!


*Paul*
 



Le dimanche 26 août 2018 21:01:10 UTC+2, David Hathaway a écrit :
>
> I'm having a different error, I believe.  Any ideas on how to sort it out?
>
> My weewx is quite old indeed.  Ubuntu 18.04LTS and MySQL.
>
> I downloaded the version the day you posted it first, so it is v0.1?  
> Would the later revisions solve the issue?  I think not, since this appears 
> to be a SQL issue.
>
>
> 13:56:15 localhost weewx[23412]: restx: Wunderground-PWS: Published record 
> 2018-08-26 13:56:00 CDT (1535309760)
> Aug 26 13:56:16 localhost weewx[23412]: cheetahgenerator: Generated 14 
> files for report StandardReport in 0.78 seconds
> Aug 26 13:56:16 localhost weewx[23412]: imagegenerator: Generated 16 
> images for StandardReport in 0.76 seconds
> Aug 26 13:56:16 localhost weewx[23412]: reportengine: Caught unrecoverable 
> exception in generator weewx.cheetahgenerator.CheetahGenerator
> Aug 26 13:56:16 localhost weewx[23412]:*   (1055, "Expression 
> #2 of SELECT list is not in GROUP BY clause and contains nonaggregated 
> column 'weewx.archive_day_rain.dateTime' which is not functionally 
> dependent on columns in GROUP BY clause; this is incompatible with 
> sql_mode=only_full_group_by")*
> Aug 26 13:56:16 localhost weewx[23412]:   Traceback (most 
> recent call last):
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Aug 26 13:56:16 localhost weewx[23412]:   obj.start()
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Aug 26 13:56:16 localhost weewx[23412]:   self.run()
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
> Aug 26 13:56:16 localhost weewx[23412]:   ngen = 
> self.generate(gen_dict[section_name], self.gen_ts)
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
> Aug 26 13:56:16 localhost weewx[23412]:   default_binding)
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
> Aug 26 13:56:16 localhost weewx[23412]:   searchList += 
> obj.get_extension_list(timespan, db_lookup)
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/user/belchertown.py", line 82, in get_extension_list
> Aug 26 13:56:16 localhost weewx[23412]:   
> at_rainiest_month = wx_manager.getSql( at_rainiest_month_sql )
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weewx/manager.py", line 394, in getSql
> Aug 26 13:56:16 localhost weewx[23412]:   
> _cursor.execute(sql, sqlargs)
> Aug 26 13:56:16 localhost weewx[23412]: File 
> "/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
> Aug 26 13:56:16 localhost weewx[23412]:   raise klass(e)
> Aug 26 13:56:16 localhost weewx[23412]:   *DatabaseError: 
> (1055, "Expression #2 of SELECT list is not in GROUP BY clause and contains 
> 

[weewx-user] Re: Looking for a Weewx running script

[Paul Bartholdi]

Hello,

Having you station on Internet could be an other root of yourr problem: 
hackers interfering/disrupting your connections. Most stations I know have 
little, if any, protection against hackers. So check your firewall. You can 
also install a spy, using wireshark for example, recording all in/out 
coming data to your weather station.

Good luck! Paul

On Thursday, May 24, 2018 at 8:42:18 AM UTC+2, Mike wrote:
>
> Hi guys,
>
> my Weewx is crashing time by time.
>
> I am looking for a script which is checking the status of Weewx every 
> hour. In case Weewx was crashing the script is starting Weewx.
>
> My Linux knowledge is not the best at all. Looking like something: It does 
> not work.
>
> #!/bin/bash
> #weewx check
> if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx >/dev/null
> then
> echo "weewx  ok"
> else
> echo ""
> date >> /etc/weewx/weewx.fail
> echo "weewx crashed ... restarting now" >> /usr/local/
> sleep 1
> /etc/init.d/weewx start
> fi
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Distance on the sky between planets

[Paul Bartholdi]

Thank you very much Thomas, as usual it works immediately!
Will the "new" alamanac.py be part of the next version?
Regards,Paul

On 23 January 2018 at 20:14, Thomas Keffer <tkef...@gmail.com> wrote:

> ​Separation is not supported in v3.8, but it would not be hard to add. Try
> the attached version of almanac.py
>
> -tk​
>
> On Tue, Jan 23, 2018 at 11:26 AM, Paul Bartholdi <paul.bartho...@gmail.com
> > wrote:
>
>> Hello,
>>
>> I would like to add in the "almanac" part of the main weewx page the
>> distance on the sky between planets, as between Mars and Jupiter these
>> days. I know how to use "IF...THEN" to select only the interesting ones.
>>
>> I know more or less how to play with almanac and ephem (see my page "
>> http://shire-bdi.gotdns.com/weewx;), though I have very little
>> experience with python.
>> I am aware in ephem of the "separation" on the sky between two celestial
>> bodies, but have not been able to got anything working.
>>
>> I tried something like
>>
>>#set $dvm = $almanac.separation(($almanac.venus.alt,$almanac.venus.az),
>> ($almanac.mars.alt,$almanac.mars.az))
>>
>> but all attempts have been rejected because it uses 3 (!) parameters
>> which is not supported.
>>
>> Most probably I started in the wrong direction. Could you put me back on
>> the right rails?
>>
>> Thank you very much in advance,   Paul
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/_G26k2zKxuM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Distance on the sky between planets

[Paul Bartholdi]

Hello,

I would like to add in the "almanac" part of the main weewx page the 
distance on the sky between planets, as between Mars and Jupiter these 
days. I know how to use "IF...THEN" to select only the interesting ones.

I know more or less how to play with almanac and ephem (see my page 
"http://shire-bdi.gotdns.com/weewx;), though I have very little experience 
with python.  
I am aware in ephem of the "separation" on the sky between two celestial 
bodies, but have not been able to got anything working.

I tried something like

   #set $dvm = $almanac.separation(($almanac.venus.alt,$almanac.venus.az), 
($almanac.mars.alt,$almanac.mars.az))

but all attempts have been rejected because it uses 3 (!) parameters which 
is not supported.

Most probably I started in the wrong direction. Could you put me back on 
the right rails?

Thank you very much in advance,   Paul

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Transit alt error after moving from 3.7.1 to 3.8.0

[Paul Bartholdi]

Happy new year !Great weewx,   great help.
Thank you a lot!   It works 100% OK.
It was effectively working, as I has already put in place the "new"
almanac.py which was replaced by the older one when I installed the new
package (or could it be an other package?)
Paul

On 21 January 2018 at 00:09, Thomas Keffer <tkef...@gmail.com> wrote:

> I doubt this ever worked: this is a known bug that was fixed on 29
> December 2017
> <https://github.com/weewx/weewx/commit/202f25d7e069aeebdb66fd9a604cdb7862739f73>,
> a month *after* V3.8.0 was released.
>
> To patch, replace your version of almanac.py with this version
> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/almanac.py>.
> The following commands should accomplish this:
>
> cd /usr/share/weewx/weewx
> sudo mv almanac.py almanac.py.backup
> sudo wget https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/
> almanac.py
>
>
> Then restart weewx.
>
> -tk
>
>
>
> On Sat, Jan 20, 2018 at 3:30 PM, Paul Bartholdi <paul.bartho...@gmail.com>
> wrote:
>
>> Hello,
>>
>> I just updated today from 3.7.1 to 3.8.0 using .deb package.
>>
>> Every ting is instantly OK except for the following line, printing the
>> altitude of the sun at transit.
>>
>>  Hauteur au transit :
>>  $("%.1f" % $almanac($almanac_time=$almana
>> c.sun.transit.raw).sun.alt)
>>
>> Now it returns the current altitude.
>> I had a look at all discussions, but could not find a hint for my
>> problem.
>> There is neither any warning or error on the log (debug=1) file.
>>
>> Thanks for this beautiful software, and for your help!
>> Paul
>>
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/pXJjGHTVXYw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Transit alt error after moving from 3.7.1 to 3.8.0

[Paul Bartholdi]

Hello,

I just updated today from 3.7.1 to 3.8.0 using .deb package.

Every ting is instantly OK except for the following line, printing the 
altitude of the sun at transit.

 Hauteur au transit :
 $("%.1f" % 
$almanac($almanac_time=$almanac.sun.transit.raw).sun.alt)
   
Now it returns the current altitude.
I had a look at all discussions, but could not find a hint for my problem. 
There is neither any warning or error on the log (debug=1) file.

Thanks for this beautiful software, and for your help!
Paul


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Simplest Way to Read Current Data

[Paul Bartholdi]

Hello,

I like the SQL access because it gives you the widest possibilities to get 
any already recorded data, be it just now or any older ones.
I suppose that the problem you had is sqlite vs sqlite3. Weewx uses 
sqlite3, so you should use sqlite3 to interrogate the dB.

So :   sqlite3 /var/lib/weewx/weewx.sdb( not sqlite /var/... )

I assume you are using some sort of linux OS.  You can check that weewx.sdb 
is for sqlitte3 with the command  :
$ file /var/lib/weewx/weewx.sdb

In my case I get :

$ file PAS-weewx-20171203.sdb
PAS-weewx-20171203.sdb: SQLite 3.x database, last written using SQLite 
version 3008010

I hope this helps you.

Happy New Year ! Paul


On Sunday, January 7, 2018 at 1:56:17 PM UTC+1, Allan Ortile wrote:
>
> Hi, I've been looking through a bunch of documentation and group threads 
> on how to get the current data as simple as possible. Right now im thinking 
> of these approaches: 
>
> 1.) Using the RSS feed of Weewx, read the current data which is enclosed 
> in CDATA. 
>
> I tried this one and throught to myself, how hard can it be? Then I tried 
> beautifulsoup to read/parse the rss, tried some other libraries but ended 
> up wasting an hour not getting anywhere. 
>
> 2.) Maybe I can just run wee_device --current and just parse the data 
> there 
>
> It works for a time, til I get the annoying "weewx.WeeWxIOError: [Errno 
> 16] Resource busy" errors. Dont get me wrong, the device is still polling 
> and is still updating the HTTP website with fresh data its just that 
> wee_device is so unreliable that i'd even consider this as an option
>
> 3.) Directly pull the latest data from the SQLite database 
>
> Well, i tried the command sqlite /var/lib/weewx/weewx.sdb and got the 
> error Unable to open database "/var/lib/weewx/weewx.sdb": file is encrypted 
> or is not a database 
>
> Man this gets weirder and weirder. 
>
> 4.) Use the weewx python library 
>
> I saw some guys use the weewx python via import, but theres no reference 
> libraries i can turn to. 
>
> 5.) Curl an endpoint? 
>
> Is there an endpoint i can curl to just get raw data from the sensor? 
>
> 
>
> I honestly just want the current values from weewx. Is it too much to ask? 
> :( 
>
> My end goal would be to write a simple python aggregator to get my sensor 
> data from weewx + some other sensor data directly connected to the pi 
> (soil, uv, etc) then send it via an http request to my server which stores 
> it on a database and processes everything collectively (this wont be just 
> one weather station, we will deploy many). 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Adding data from homemade wireless sensors to weewx

[Paul Bartholdi]

Hello,

It could be good to have a look at "http://www.yoctopuce.com;. The company 
is based in Geneva, Switzerland, but send products worldwide, with typical 
Swiss high quality. They have extremely low power hubs usb --> Ethernet, 
gsm or WiFi, which can put all the boards asleep and wake up only on 
command from central PC. Boards include barometer, temperature(s), 
humidity, light and many other possibilities not so much related to weather 
station. Software exists for most high level languages (C, C++, Java, 
Python, shell (bash) etc.).
MQTT looks very interesting, but I had no time yet to play with it.  To 
interface other programs with weewx data, I simply interrogate the database 
(mysql).
Hope this helps. Paul

On Tuesday, June 13, 2017 at 3:53:48 PM UTC+2, Craig Thom wrote:
>
> tl;dr What's the best way of getting home brew wireless sensor data into 
> weewx?
>
> I plan to build a soil moisture (and temperature) sensor for my garden 
> bed.  I'll likely build another for leaf wetness and UV index, because the 
> sensors are cheap and it will be fun.
>
> The question is how best to get this data to weewx.  I am already using 
> the SDR driver for my Acurite 5-in-1 and additional sensors.
>
> I could use a 433MHz transmitter.  I think, though, I'd have to decide on 
> how to make a packet, then modify rtl_433 to recognize that packet, then 
> modify SDR.py to use that new rtl_433 packet.  This seems pretty 
> complicated.
>
> Or, since these sensors will be within range of wifi, I could use an 
> ESP2866.  This is attractive because the microcontroller for reading the 
> sensor and processing the data is in the same package.  I really like this 
> idea.
>
> But how do I get the data to weewx?
>
> Because the sensor will be running on batteries (and maybe solar cells for 
> the UV/leaf wetness one), I do not want to turn on the wifi radio except 
> when absolutely necessary, so weewx will not be able to initiate contact.
>
> My first thought was to use ftp, so the sensor connects to an FTP server 
> on my network, probably on the RPi running weewx, and dumps a file.  Then I 
> could write a service within weewx to check for that file, read it, and add 
> the data to the LOOP packet.
>
> But I was reading through old discussions here, and I found one using MQTT 
> as a source for weewx.  There was no resolution reached, other than some 
> references to weeRT that I didn't really understand (and weeRT is a lot 
> harder to Google than weewx).  
>
> MQTT is attractive because it's a standard, and other things could 
> subscribe to the sensor data (like a home automation program, or something 
> that will turn on the water to the garden bed).
>
> I'd rather not start from scratch with the regular sensors; I'd like to 
> keep using the sdr driver.
>
> Is there some really obvious solution that I'm missing?  Is there code 
> someone for producing Acurite-like radio packets so my sensors could just 
> pretend to be a tower sensor or something?
>
> (I was concerned about getting accurate numbers from a soil moisture 
> sensor, because all my reading says it depends on soil type, and it needs 
> to be calibrated, etc., but Davis doesn't do any of that calibration, and 
> if just using relative moisture is good enough for them, it's good enough 
> for me.)
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: MySQL server has gone away

[Paul Bartholdi]

Hello,  I faced the same problem once or twice in the past, even with both 
weewx and mysql on the same host. In all cases I could point to the culprit 
on me.  I had updated mysql or restarted altogether the host just at the 
time weewx wanted to insert new records. In both cases I had to stop and 
restart weewx, with no data lost.
Paul


On Wednesday, May 31, 2017 at 4:22:16 AM UTC+2, Louis De Lange wrote:
>
> While there seem to be great excitement for the new meteotemplate 
> uploader, I previously wrote a service that updates my meteotemplate 
> database directly without an intermediate php script.  In the service i use 
> a ."getSql("INSERT INTO" statement.  This works really well and I even 
> resolved the dayrain issue that is now being discussed on another thread.
>
> There is one annoying bug and I dont know how to solve it.  My 
> meteotemplate install is located on a different server than weewx.  It can 
> sometimes happen that the meteotemplate server is temporarily unavailable. 
>  To overcome this scenario I use a "try" statement when inserting SQL data, 
> so that it will just skip the upload attempt if the MySQL server is not 
> available.  The bug is that the mysql insert command continue to fail after 
> the meteotemplate server becomes available again, and the only way to 
> correct it is to restart weewx. 
>
> The fail message is "Error (2006, 'MySQL server has gone away')" and it 
> continues to be displayed after the meteotemplate server is back on line.
>
> Any ideas how to resolve this will be appreciated.
>
> Louis
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: How would I get Sunrise and Sunset into mysql

[Paul Bartholdi]

Hello,

I think I had similar ideas, that is adding sunrise/sunset etc. on the main 
weewx page.  I found the solution in editing (that is really addig new 
lines) in the "index.html.tmpl" file.  That was quite easy though my 
knowledge on python is rather small. The necessary informations came from 
"pyephem.doc".  

To get an idea of the result (sorry, it's all in French, but the command 
themself are in English so you should have no problem in getting all in 
English), look at  
"http:shire-bdi.gotdns.com/weewx"
You can get the modified file at:
"http://shire-bdi.gotdns.com/weewx/Extra/index.html.tmpl;
NB: This file should go in "/etc/weewx/skins/Standard/". By default, it is 
not overwritten when weewx is updated, at least when using the ".deb" 
package.

If you have any problem in using it, don't hesitate to contact me through 
the list or directly; and if you improve it (surely many places can be 
improved!), send it back to me. Thanks.
Good luck, Paul

On Sunday, April 23, 2017 at 10:21:55 PM UTC+2, mark2326L wrote:
>
> I have been running weewx for a week now. I'm making  a custom php 
> webpage, everything is going good, but I have no idea how to get the 
> almanac data into my php page.
> I'm completely new to python, that adds to my struggle.
> I also realize having the sunrise, sunset in the database is a waste of 
> space, but it's the only way I can think of. 
> I was thinking of adding 2 tables or changing 2 that I most likely will 
> never use in the archive table.
> The problem is I don't know how or where to put the python code to enter 
> it.
> Any ideas?
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Air quality sensors?

[Paul Bartholdi]

Hello,   if this is still open, you may be interested with the "Yoctopuce" 
modules. " http://www.yoctopuce.com/EN/ ". They include CO_2 and volatile 
air sensors in very tiny boards interconnected via USB. They are produced 
in Geneva/Switzerland, supposed of high quality, but at a rather reasonable 
price. One module includes barometer, temperature and humidity for < 75 
US$... on a board of 20x60mm, including connector.
Hope this helps! Paul

On Tuesday, April 4, 2017 at 11:44:40 PM UTC+2, Yves Martin wrote:
>
> Hi,
>
> Just a simple question about "air quality", because it is nowadays an 
> important health factor in the cities. I'm using a Vantage Pro since 10 
> years now, and this station is a rock... it never failed and gives accurate 
> information.
>
> Is there a kind of project that could be used with "weewx" for this kind 
> of information? This is the kind of air quality sensor I found on eBay: 
> http://www.ebay.ca/itm/132141883335?_trksid=p2060353.m1438.l2649=STRK%3AMEBIDX%3AIT
>  
> (2017 AirMaster2 AM7 master air CO2 laser pm2.5 formaldehyde air quality 
> testing). Is there a way to integrate this with weewx?
>
> Yves,
> YMartin.com/meteo
> CANADA
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: (old) Irox usb station support

[Paul Bartholdi]

Hello,  I have also an Irox Pro X station, probably 4-5 years old (not the 
more modern X2) and use without any difficulty the TE923 driver. Previous 
versions (before 3.5 as I remember had some troubles with his driver, but 
it seems they have been solved. 3days ago I updated to 3.7.1 (.deb package) 
without any hi-cup. Nice !  
Have a good time, Paul

On Wednesday, April 5, 2017 at 9:14:48 PM UTC+2, David Broster wrote:
>
> Hi, I'm completely new to Weewx
> . so I first quickly looked at the list of supported stations - no 
> obvious support.
>
> Does anyone have any ideas on how I could interface to my old USB Irox 
> station
>
> (Originally set-up years ago to use WDisplay32 & WDLive, but now time to 
> move on shut down WindowsHomeServer and shift to RaspberryPi)
>
> Thanks for some hints ..  David
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Te923 driver is not starting anymore.

[Paul Bartholdi]

Concerning "te923", I had "te923.py-0.18r6", which I assumed to be the 
latest "te923.py-0.18". It was 100 % OK with Ubuntu 14.04 LTS.
When I installed U 16.04 LTS however, weewx started to work very 
erratically and soon stopped completely.
Then I realised that the "r6" version was just temporary and is now 
replaced with "te923.py-0.18", I installed the latest and now weewx runs 
perfectly, better than ever!

Is there a way to be informed when a new version of such a sensible driver 
comes out?

Thanks of all! Paul

On Thursday, 8 September 2016 23:53:22 UTC+2, mwall wrote:
>
> On Thursday, September 8, 2016 at 5:47:49 PM UTC-4, Andy Harrold wrote:
>>
>> I'm needing to update the te923 driver to the latest version 0.18
>> Where is this file located so I can update it ?
>> I have the latest version from 
>> https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/te923.py
>> How do I instal it? (Newbie on Raspbian!)
>> Thanks
>>
>
>
> assuming a setup.py installation, it looks something like this:
>
> 1) stop weewx
>
> sudo /etc/init.d/weewx stop
>
> 2) move the old driver aside
>
> sudo mv /home/weewx/bin/weewx/drivers/te923.py 
> /home/weewx/bin/weewx/drivers/te923-0.17.py
>
> 3) put the new driver in place
>
> sudo cp ~/Downloads/te923.py /home/weewx/bin/weewx/drivers/te923.py
>
> 4) start weewx
>
> sudo /etc/init.d/weewx start
>  
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.