date:20230727

[weewx-user] Re: Understanding Weewx new method of logging

2023-07-27 Thread Tomasz Lewicki

Thank you. I'm using log2ram so I think it has the same effect. But I think 
that some mechanism to completely turn off logging does/should exist. I can 
always turn it on if needed.

 I don't know if it is good approach but I've used 
"disable_existing_loggers = True" directive in weewx.conf and log aren't 
generated - or I can't find them :)

środa, 26 lipca 2023 o 17:50:53 UTC+2 vince napisał(a):

> I just log to tmpfs (essentially ramdisk) and it is not an issue for me.
>
> Add this to your /etc/fstab and reboot
>
> # put logs and tmp dirs in ramdisk ---
> tmpfs   /tmptmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> tmpfs   /var/logtmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> tmpfs   /var/tmptmpfs   
> defaults,nosuid,mode=0755,nodev,noatime   0   0
> #-
>
> Note that the result here is that you will lose 'all' logs when you 
> reboot, but the upside is it never writes to SD card.  In this 
> configuration your pi SD is close to read-only.
>
>
> On Wednesday, July 26, 2023 at 2:40:26 AM UTC-7 Tomasz Lewicki wrote:
>
>> Hi WX users.
>>
>> I'd like to ask about logging in Weewx (I'm using version 4.10.2). To 
>> make a long story short, I'd like to completely turn off logging by Weewx - 
>> because I'm using Raspberry Pi with SD card and want to minimize write 
>> operations as much as possible. 
>>
>> I've read article on wiki (
>> https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging) but do not 
>> clearly understand new way of control logging. I'd like to have simple 
>> switch in weewx.conf, for example "completely_disable_logging = True" or 
>> something similar. Is there some switch in [Logging] block as I see it in 
>> wiki? If I change "disable_existing_loggers = False" to 
>> "disable_existing_loggers = True", will I get the expected effect?
>>
>

-- 
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/9812f2ab-5ffb-4e64-bd97-80358501cf5bn%40googlegroups.com.

Re: [weewx-user] Re: Understanding Weewx new method of logging

2023-07-27 Thread 'Rainer Lang' via weewx-user

you are free to do whatever you want...
You can even disable the rsyslog service completely and have no logging
at all.
However, turning off logging is not a very smart approach, and thinking
you can turn logging on again "when it's needed" is imho rather naive
thinking. When an application (and it may even fail to restart) fails,
you may no longer be able to find out what has caused the issue without
logs.
You can use RAM (temporary file system) as suggested by @vince, you can
move the logs to a remote server (e.g. NAS) etc., but switching off
logging completely is nothing a professional IT person would recommend

you could also use a SSD disk instead of a microSD with your RPi or a
SLC microSD card if you want to avoid wear out of your SD card ...
I'm using both approaches for years now with my RPi's - and have my logs
available in case they are needed 😎

On 27.07.2023 12:18, Tomasz Lewicki wrote:
Thank you. I'm using log2ram so I think it has the same effect. But I
think that some mechanism to completely turn off logging does/should
exist. I can always turn it on if needed.

I don't know if it is good approach but I've used
"disable_existing_loggers = True" directive in weewx.conf and log
aren't generated - or I can't find them :)

środa, 26 lipca 2023 o 17:50:53 UTC+2 vince napisał(a):

I just log to tmpfs (essentially ramdisk) and it is not an issue
for me.

Add this to your /etc/fstab and reboot

# put logs and tmp dirs in ramdisk ---
tmpfs /tmp tmpfs
defaults,nosuid,mode=0755,nodev,noatime 0 0
tmpfs /var/log tmpfs
defaults,nosuid,mode=0755,nodev,noatime 0 0
tmpfs /var/tmp tmpfs
defaults,nosuid,mode=0755,nodev,noatime 0 0
#-

Note that the result here is that you will lose 'all' logs when
you reboot, but the upside is it never writes to SD card. In this
configuration your pi SD is close to read-only.

On Wednesday, July 26, 2023 at 2:40:26 AM UTC-7 Tomasz Lewicki wrote:

Hi WX users.

I'd like to ask about logging in Weewx (I'm using version
4.10.2). To make a long story short, I'd like to completely
turn off logging by Weewx - because I'm using Raspberry Pi
with SD card and want to minimize write operations as much as
possible.

I've read article on wiki
(https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging) but
do not clearly understand new way of control logging. I'd like
to have simple switch in weewx.conf, for example
"completely_disable_logging = True" or something similar. Is
there some switch in [Logging] block as I see it in wiki? If I
change "disable_existing_loggers = False" to
"disable_existing_loggers = True", will I get the expected effect?

--
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/9812f2ab-5ffb-4e64-bd97-80358501cf5bn%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/938b704c-2597-c822-d901-086b40b030db%40gmail.com.

Re: [weewx-user] current doesnt work with xargs function but with day it does

2023-07-27 Thread enu...@gmail.com

no, it's from a solution you gave me here. An extension of historical_avg 
to the hour level, the query is on the first message, but that's not what's 
important. The bottom line is that if I use $day.historical_hour_avg it 
works with the time 0:00 but if I use $current to get the current time it 
doesn't.

El jueves, 27 de julio de 2023 a las 1:46:20 UTC+2, Tom Keffer escribió:

> I'm confused. The key "historical_hour_avg" is not in weewx-xaggs. It can 
> only do full days, not hours.
>
> Is this something you wrote?
>
> On Wed, Jul 26, 2023 at 6:15 AM enu...@gmail.com  wrote:
>
>> I have in xagss thanks to Tom Keller who was the one who did the 
>> following:
>>
>>  'historical_hour_avg': "SELECT avg({obs_type}) FROM {table} "
>>"WHERE STRFTIME('%m-%d-%H', datetime, 
>> 'unixepoch', 'localtime') "
>> "= 
>> '{month:02d}-{day:02d}-{hour:02d}'",
>>
>> to calculate the average historical temperature of that day at that time.
>> If I use day.outTemp.historical_hour_avg the hour it uses is 0:00 which 
>> is not what I want.
>> If I use current.outTemp.historical_hour_avg it does nothing. It doesn't 
>> show an error or give any results.
>> How can I pass the current time to xagss and why doesn't it work with 
>> $current?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/8ab23a4c-d49b-4a0e-9570-6fd2f6212f4bn%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/4e2ce931-0f72-439c-8bef-8ff34c8d0d41n%40googlegroups.com.

Re: [weewx-user] Re: Graph with the days at more than a certain temperature in the month or in the year in Belchertown

2023-07-27 Thread enu...@gmail.com

Thank you it works with season but it still doesn't work with belchertown 
and i don't understand why.
I have modified belchertown.py by changing all calls to xtypes.get_series 
to have **option_dict but it still doesn't work and still gives the same 
"no such column" error. I understand that option_dict is a global variable 
accessible from all modules

El miércoles, 26 de julio de 2023 a las 21:35:15 UTC+2, Tom Keffer escribió:

> Fixed in commit 52db478 
> 
> .
>
> The fix is in the file weewx/xtypes.py 
> . 
> You can simply swap out your old version for the new one, if you are 
> comfortable doing that. 
>
> Otherwise, wait for V5.
>
> On Wed, Jul 26, 2023 at 7:01 AM Tom Keffer  wrote:
>
>> Thanks.
>>
>> Turns out there is a bug in how aggregates are calculated that prevents 
>> this. I've created issue #881 
>> .
>>
>> I'll fix it, but not until Version 5.0.
>>
>> -tk
>>
>> On Wed, Jul 26, 2023 at 5:56 AM enu...@gmail.com  
>> wrote:
>>
>>> I try with the Seasson skin and i get the same error "no such column: 
>>> None". Doesn't work.
>>>
>>> El miércoles, 26 de julio de 2023 a las 13:30:58 UTC+2, enu...@gmail.com 
>>> escribió:
>>>
 Thank you very much. but it don't works in belchertown. It gives this 
 error:
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine: 
 Caught unrecoverable exception in generator 
 'user.belchertown.HighchartsJsonGenerator'
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Error trying to use database binding wx_binding to graph 
 observation outTemp. Error was: no such column: None.
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Traceback (most recent call last):
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weedb/sqlite.py", line 39, in 
 guarded_fn
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return fn(*args, **kwargs)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weedb/sqlite.py", line 233, in execute
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return sqlite3.Cursor.execute(self, *args, **kwargs)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     sqlite3.OperationalError: no such column: None
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     During handling of the above exception, another exception 
 occurred:
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Traceback (most recent call last):
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/user/belchertown.py", line 3790, in 
 get_observation_data
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     (time_start_vt, time_stop_vt, obs_vt) = 
 weewx.xtypes.get_series(
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 100, in 
 get_series
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return xtype.get_series(obs_type, timespan, db_manager, 
 aggregate_type,
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 167, in 
 get_series
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     agg_vt = get_aggregate(obs_type, stamp, do_aggregate, 
 db_manager)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 127, in 
 get_aggregate
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return xtype.get_aggregate(obs_type, timespan, 
 aggregate_type, db_manager,
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 551, in 
 get_aggregate
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     row = 
 db_manager.getSql(DailySummaries.agg_sql_dict[aggregate_type] % inter_dict)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:

Re: [weewx-user] Re: Graph with the days at more than a certain temperature in the month or in the year in Belchertown

2023-07-27 Thread enu...@gmail.com

Thank you it works with season but it still doesn't work with belchertown 
and i don't understand why.
I have modified belchertown.py by changing all calls to xtypes.get_series 
to have **option_dict but it still doesn't work and still gives the same 
"no such column" error. I understand that option_dict is a global variable 
accessible from all modules but i see that option_dictisempty

Responder a todos
Responder al autor
Reenviar


El miércoles, 26 de julio de 2023 a las 21:35:15 UTC+2, Tom Keffer escribió:

> Fixed in commit 52db478 
> 
> .
>
> The fix is in the file weewx/xtypes.py 
> . 
> You can simply swap out your old version for the new one, if you are 
> comfortable doing that. 
>
> Otherwise, wait for V5.
>
> On Wed, Jul 26, 2023 at 7:01 AM Tom Keffer  wrote:
>
>> Thanks.
>>
>> Turns out there is a bug in how aggregates are calculated that prevents 
>> this. I've created issue #881 
>> .
>>
>> I'll fix it, but not until Version 5.0.
>>
>> -tk
>>
>> On Wed, Jul 26, 2023 at 5:56 AM enu...@gmail.com  
>> wrote:
>>
>>> I try with the Seasson skin and i get the same error "no such column: 
>>> None". Doesn't work.
>>>
>>> El miércoles, 26 de julio de 2023 a las 13:30:58 UTC+2, enu...@gmail.com 
>>> escribió:
>>>
 Thank you very much. but it don't works in belchertown. It gives this 
 error:
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine: 
 Caught unrecoverable exception in generator 
 'user.belchertown.HighchartsJsonGenerator'
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Error trying to use database binding wx_binding to graph 
 observation outTemp. Error was: no such column: None.
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Traceback (most recent call last):
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weedb/sqlite.py", line 39, in 
 guarded_fn
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return fn(*args, **kwargs)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weedb/sqlite.py", line 233, in execute
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return sqlite3.Cursor.execute(self, *args, **kwargs)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     sqlite3.OperationalError: no such column: None
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     During handling of the above exception, another exception 
 occurred:
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Traceback (most recent call last):
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/user/belchertown.py", line 3790, in 
 get_observation_data
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     (time_start_vt, time_stop_vt, obs_vt) = 
 weewx.xtypes.get_series(
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 100, in 
 get_series
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return xtype.get_series(obs_type, timespan, db_manager, 
 aggregate_type,
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 167, in 
 get_series
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     agg_vt = get_aggregate(obs_type, stamp, do_aggregate, 
 db_manager)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 127, in 
 get_aggregate
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return xtype.get_aggregate(obs_type, timespan, 
 aggregate_type, db_manager,
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 551, in 
 get_aggregate
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     row = 
 db_manager.getSql(DailySummaries.agg_sql_dict[aggregate_type] % inter_dict)
>>

Re: [weewx-user] Re: Graph with the days at more than a certain temperature in the month or in the year in Belchertown

2023-07-27 Thread enu...@gmail.com

Thank you it works with season but it still doesn't work with belchertown 
and i don't understand why.
I have modified belchertown.py by changing all calls to xtypes.get_series 
to have **option_dict but it still doesn't work and still gives the same 
"no such column" error. I understand that option_dict is a global variable 
accessible from all modules but i see that option_dict is empty

El miércoles, 26 de julio de 2023 a las 21:35:15 UTC+2, Tom Keffer escribió:

> Fixed in commit 52db478 
> 
> .
>
> The fix is in the file weewx/xtypes.py 
> . 
> You can simply swap out your old version for the new one, if you are 
> comfortable doing that. 
>
> Otherwise, wait for V5.
>
> On Wed, Jul 26, 2023 at 7:01 AM Tom Keffer  wrote:
>
>> Thanks.
>>
>> Turns out there is a bug in how aggregates are calculated that prevents 
>> this. I've created issue #881 
>> .
>>
>> I'll fix it, but not until Version 5.0.
>>
>> -tk
>>
>> On Wed, Jul 26, 2023 at 5:56 AM enu...@gmail.com  
>> wrote:
>>
>>> I try with the Seasson skin and i get the same error "no such column: 
>>> None". Doesn't work.
>>>
>>> El miércoles, 26 de julio de 2023 a las 13:30:58 UTC+2, enu...@gmail.com 
>>> escribió:
>>>
 Thank you very much. but it don't works in belchertown. It gives this 
 error:
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine: 
 Caught unrecoverable exception in generator 
 'user.belchertown.HighchartsJsonGenerator'
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Error trying to use database binding wx_binding to graph 
 observation outTemp. Error was: no such column: None.
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Traceback (most recent call last):
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weedb/sqlite.py", line 39, in 
 guarded_fn
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return fn(*args, **kwargs)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weedb/sqlite.py", line 233, in execute
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return sqlite3.Cursor.execute(self, *args, **kwargs)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     sqlite3.OperationalError: no such column: None
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     During handling of the above exception, another exception 
 occurred:
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     Traceback (most recent call last):
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/user/belchertown.py", line 3790, in 
 get_observation_data
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     (time_start_vt, time_stop_vt, obs_vt) = 
 weewx.xtypes.get_series(
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 100, in 
 get_series
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return xtype.get_series(obs_type, timespan, db_manager, 
 aggregate_type,
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 167, in 
 get_series
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     agg_vt = get_aggregate(obs_type, stamp, do_aggregate, 
 db_manager)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 127, in 
 get_aggregate
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     return xtype.get_aggregate(obs_type, timespan, 
 aggregate_type, db_manager,
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
   File "/usr/share/weewx/weewx/xtypes.py", line 551, in 
 get_aggregate
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERROR weewx.reportengine:   
     row = 
 db_manager.getSql(DailySummaries.agg_sql_dict[aggregate_type] % inter_dict)
 Jul 26 13:25:32 raspberrypi weewx[1189454] ERRO

Re: [weewx-user] Re: Understanding Weewx new method of logging

2023-07-27 Thread Tomasz Lewicki

Thank you for advice but external SSD/USB is not an option. Unfortunately I 
can't send logs to other machine because I will install the station in 
remote place where web access is limited and I have limits for LTE transfer 
(transfer rate and volume of data). UPS supply is out of the question too. 
I got RPi outside and have to limit potential points of failure as much as 
possible.

I worked in IT for some time and of course I know that log tell you the 
truth (even if you don't want to know it). But I also think that 
it's entirely up to the user if he/she wants some service enabled/disabled 
or log created or not. With all pros and cons of this approach of course.

czwartek, 27 lipca 2023 o 12:33:17 UTC+2 Rainer Lang napisał(a):

> you are free to do whatever you want...
> You can even disable the rsyslog service completely and have no logging at 
> all.
> However, turning off logging is not a very smart approach, and thinking 
> you can turn logging on again "when it's needed" is imho rather naive 
> thinking. When an application (and it may even fail to restart) fails, you 
> may no longer be able to find out what has caused the issue without logs.
> You can use RAM (temporary file system) as suggested by @vince, you can 
> move the logs to a remote server (e.g. NAS) etc., but switching off logging 
> completely is nothing a professional IT person would recommend
>
> you could also use a SSD disk instead of a microSD with your RPi or a SLC 
> microSD card if you want to avoid wear out of your SD card ...
> I'm using both approaches for years now with my RPi's - and have my logs 
> available in case they are needed 😎
> On 27.07.2023 12:18, Tomasz Lewicki wrote:
>
> Thank you. I'm using log2ram so I think it has the same effect. But I 
> think that some mechanism to completely turn off logging does/should exist. 
> I can always turn it on if needed. 
>
>  I don't know if it is good approach but I've used 
> "disable_existing_loggers = True" directive in weewx.conf and log aren't 
> generated - or I can't find them :)
>
> środa, 26 lipca 2023 o 17:50:53 UTC+2 vince napisał(a):
>
>> I just log to tmpfs (essentially ramdisk) and it is not an issue for me. 
>>
>> Add this to your /etc/fstab and reboot
>>
>> # put logs and tmp dirs in ramdisk ---
>> tmpfs   /tmptmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> tmpfs   /var/logtmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> tmpfs   /var/tmptmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> #-
>>
>> Note that the result here is that you will lose 'all' logs when you 
>> reboot, but the upside is it never writes to SD card.  In this 
>> configuration your pi SD is close to read-only.
>>
>>
>> On Wednesday, July 26, 2023 at 2:40:26 AM UTC-7 Tomasz Lewicki wrote:
>>
>>> Hi WX users.
>>>
>>> I'd like to ask about logging in Weewx (I'm using version 4.10.2). To 
>>> make a long story short, I'd like to completely turn off logging by Weewx - 
>>> because I'm using Raspberry Pi with SD card and want to minimize write 
>>> operations as much as possible. 
>>>
>>> I've read article on wiki (
>>> https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging) but do not 
>>> clearly understand new way of control logging. I'd like to have simple 
>>> switch in weewx.conf, for example "completely_disable_logging = True" or 
>>> something similar. Is there some switch in [Logging] block as I see it in 
>>> wiki? If I change "disable_existing_loggers = False" to 
>>> "disable_existing_loggers = True", will I get the expected effect?
>>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/9812f2ab-5ffb-4e64-bd97-80358501cf5bn%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/f32ced07-ea6b-4c58-9448-67aabaef3134n%40googlegroups.com.

Re: [weewx-user] Understanding Weewx new method of logging

2023-07-27 Thread Graham Eddy

see https://docs.python.org/3/library/logging.config.html - weewx logging uses 
this yaml (translated into ini syntax).
perhaps your best option is to set logging level at ‘error’, which is not 
verbose unless you really really need it
⊣GE⊢

> On 27 Jul 2023, at 11:08 pm, Tomasz Lewicki  wrote:
> 
>> But I think that some mechanism to completely turn off logging does/should 
>> exist. I can always turn it on if needed.
>> 
>>  I don't know if it is good approach but I've used "disable_existing_loggers 
>> = True" directive in weewx.conf and log aren't generated - or I can't find 
>> them :)

-- 
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/FFBBF8FF-3141-4F2B-A49D-37B177AF355A%40geddy.au.

Re: [weewx-user] current doesnt work with xargs function but with day it does

2023-07-27 Thread Tom Keffer

If you say so. I don't remember this.

On Thu, Jul 27, 2023 at 5:25 AM enu...@gmail.com  wrote:

> no, it's from a solution you gave me here. An extension of historical_avg
> to the hour level, the query is on the first message, but that's not what's
> important. The bottom line is that if I use $day.historical_hour_avg it
> works with the time 0:00 but if I use $current to get the current time it
> doesn't.
>
> El jueves, 27 de julio de 2023 a las 1:46:20 UTC+2, Tom Keffer escribió:
>
>> I'm confused. The key "historical_hour_avg" is not in weewx-xaggs. It can
>> only do full days, not hours.
>>
>> Is this something you wrote?
>>
>> On Wed, Jul 26, 2023 at 6:15 AM enu...@gmail.com 
>> wrote:
>>
>>> I have in xagss thanks to Tom Keller who was the one who did the
>>> following:
>>>
>>>  'historical_hour_avg': "SELECT avg({obs_type}) FROM {table} "
>>>"WHERE STRFTIME('%m-%d-%H', datetime,
>>> 'unixepoch', 'localtime') "
>>> "=
>>> '{month:02d}-{day:02d}-{hour:02d}'",
>>>
>>> to calculate the average historical temperature of that day at that time.
>>> If I use day.outTemp.historical_hour_avg the hour it uses is 0:00 which
>>> is not what I want.
>>> If I use current.outTemp.historical_hour_avg it does nothing. It doesn't
>>> show an error or give any results.
>>> How can I pass the current time to xagss and why doesn't it work with
>>> $current?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/8ab23a4c-d49b-4a0e-9570-6fd2f6212f4bn%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/4e2ce931-0f72-439c-8bef-8ff34c8d0d41n%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/CAPq0zEAVu_dt6-tpiLOBiWAidJVVjKG%2Bum_D_AJRgnjFj7xX9g%40mail.gmail.com.

Re: [weewx-user] Understanding Weewx new method of logging

2023-07-27 Thread vince

This worked for me in debian12 using a v5 beta.

It's probably not 'off' completely but there are zero syslog lines from 
weewx starting/running/stopping other than a line or two that systemd 
writes.

[Logging]
version = 1
disable_existing_loggers = True

# Root logger
[[root]]
  level = CRITICAL


-- 
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/5e5d16d8-48e6-4491-808d-cc60771e01a7n%40googlegroups.com.

Re: [weewx-user] Understanding Weewx new method of logging

2023-07-27 Thread Tom Keffer

Geez, if that works, it should be mentioned in the Logging wiki.

On Thu, Jul 27, 2023 at 9:22 AM vince  wrote:

> This worked for me in debian12 using a v5 beta.
>
> It's probably not 'off' completely but there are zero syslog lines from
> weewx starting/running/stopping other than a line or two that systemd
> writes.
>
> [Logging]
> version = 1
> disable_existing_loggers = True
>
> # Root logger
> [[root]]
>   level = CRITICAL
>
>
> --
> 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/5e5d16d8-48e6-4491-808d-cc60771e01a7n%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/CAPq0zEAqQBk%2BfoHWrA5-CB%3DJSzebq%2Bd0L8Lp2C-q%2BKLJKvEVfw%40mail.gmail.com.

[weewx-user] Getting 4.5.1 to upload plots from ImageGenerator to my web page

2023-07-27 Thread DR

I have had 4.5.1 running on a Rasp Pi 4 for over a half a year. Not a
glitch.

I wanted to add to the Seasons Skin an additional plot. The stock
package gives me the bar graph of the rain each hour.

I wanted to also have the more traditional accumulation line graph
showing the upward progression of rain (all theoretical lately with our
drought), so I copied the one that was working, then modified it a
little to produce the graph.

Despite having done this, whenever I either go to index.html in the
/var/... directory, or look at the page that WeeWx is FTPing to my web
server, I don't see the new graph.

When I look at the .png plots that are ein the directory, the correctly
named one is there, it has the (flat) graph, and the bottom listing show
the right date, time and all, so I am pretty sure it is changing because
I check at various times through the day, and it agrees with the .png
plots that are being uploaded.

Having produced the plot from ImageGenerator, is there some other action
I need to take to tell WeeWx to actually upload the plot to my webserver?

If I modify the original rain plot with bar graphs to some slight
cosmetic change, THAT does go to my web page, so I assume there must be,
somewhere, a list of .pngs to upload?

Can someone give me a hint? Dale

--
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/582ecd1a-8f2d-5d34-9d19-8a918f536218%40gmail.com.

Re: [weewx-user] Getting 4.5.1 to upload plots from ImageGenerator to my web page

2023-07-27 Thread 'Rainer Lang' via weewx-user

You probably gave your new plot a new different name - and have
forgotten to display it also in index.html.tmpl 😎

On 27.07.2023 20:13, DR wrote:
I have had 4.5.1 running on a Rasp Pi 4 for over a half a year. Not a
glitch.

I wanted to add to the Seasons Skin an additional plot. The stock
package gives me the bar graph of the rain each hour.

I wanted to also have the more traditional accumulation line graph
showing the upward progression of rain (all theoretical lately with
our drought), so I copied the one that was working, then modified it a
little to produce the graph.

Despite having done this, whenever I either go to index.html in the
/var/... directory, or look at the page that WeeWx is FTPing to my web
server, I don't see the new graph.

When I look at the .png plots that are ein the directory, the
correctly named one is there, it has the (flat) graph, and the bottom
listing show the right date, time and all, so I am pretty sure it is
changing because I check at various times through the day, and it
agrees with the .png plots that are being uploaded.

Having produced the plot from ImageGenerator, is there some other
action I need to take to tell WeeWx to actually upload the plot to my
webserver?

If I modify the original rain plot with bar graphs to some slight
cosmetic change, THAT does go to my web page, so I assume there must
be, somewhere, a list of .pngs to upload?

Can someone give me a hint? Dale

--
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/8774-1f66-44f8-036c-0477b5ecad61%40gmail.com.

Re: [weewx-user] Getting 4.5.1 to upload plots from ImageGenerator to my web page

2023-07-27 Thread DR

I sure did NOT put anything in the index.html.tmpl file!

I am off to try that, and hope it is that simple of a fix. Thx. Dale

On 7/27/2023 1:19 PM, 'Rainer Lang' via weewx-user wrote:

You probably gave your new plot a new different name - and have
forgotten to display it also in index.html.tmpl 😎

On 27.07.2023 20:13, DR wrote:
I have had 4.5.1 running on a Rasp Pi 4 for over a half a year. Not a
glitch.

I wanted to add to the Seasons Skin an additional plot. The stock
package gives me the bar graph of the rain each hour.

I wanted to also have the more traditional accumulation line graph
showing the upward progression of rain (all theoretical lately with
our drought), so I copied the one that was working, then modified it
a little to produce the graph.

Despite having done this, whenever I either go to index.html in the
/var/... directory, or look at the page that WeeWx is FTPing to my
web server, I don't see the new graph.

When I look at the .png plots that are ein the directory, the
correctly named one is there, it has the (flat) graph, and the bottom
listing show the right date, time and all, so I am pretty sure it is
changing because I check at various times through the day, and it
agrees with the .png plots that are being uploaded.

Having produced the plot from ImageGenerator, is there some other
action I need to take to tell WeeWx to actually upload the plot to my
webserver?

If I modify the original rain plot with bar graphs to some slight
cosmetic change, THAT does go to my web page, so I assume there must
be, somewhere, a list of .pngs to upload?

Can someone give me a hint? Dale

--
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/abe4c912-f4e5-521f-a7cc-ee2059277745%40gmail.com.

Re: [weewx-user] Understanding Weewx new method of logging

2023-07-27 Thread vince

I'd appreciate it if others try to verify it and let me know via email 
please and I'd be happy to do so.

On Thursday, July 27, 2023 at 11:13:17 AM UTC-7 Tom Keffer wrote:

> Geez, if that works, it should be mentioned in the Logging wiki.
>
> On Thu, Jul 27, 2023 at 9:22 AM vince  wrote:
>
>> This worked for me in debian12 using a v5 beta.
>>
>> It's probably not 'off' completely but there are zero syslog lines from 
>> weewx starting/running/stopping other than a line or two that systemd 
>> writes.
>>
>> [Logging]
>> version = 1
>> disable_existing_loggers = True
>>
>> # Root logger
>> [[root]]
>>   level = CRITICAL
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/5e5d16d8-48e6-4491-808d-cc60771e01a7n%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/a6350d32-fc43-479e-bc02-c90c99d07589n%40googlegroups.com.

[weewx-user] WeeWx to Web

2023-07-27 Thread Sideshow Raheem

Hello all,

I've been enjoying tinkering with my new weather station lately. I've got 
it setup perfectly on my raspberry pi at home and it displays exactly how 
I'd like using WeeWx and the Belchertown skin.

Now I want to securely get it accessible via the web. At first I thought 
that the directions here would work well for me - 
https://www.cougar.eu.com/useful-guides/weewx-guides/publish-weewx-to-s3/index.html
 
and it seemed like it was. But using CloudFront and this setup I'm just 
getting a static site that doesnt update, and all of the pictures are broke 
as well.

Now I'm wondering if I either A) setup something incorrectly, or B) am 
taking the wrong approach.

Would I be better off hosting the WeeWx server itself in AWS instead of my 
Raspberry Pi? And then just harden the ec2 instance in AWS? I liked the 
appeal of the s3 hosted site but just cant seem to get it to load correctly.

Thanks,
www.duluthweather.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/695692c2-0f0a-4c94-aa24-fd554ec54998n%40googlegroups.com.

[weewx-user] Re: WeeWx to Web

2023-07-27 Thread michael.k...@gmx.at

Hi,

why isn't FTP'ing from the Pi to any simple webspace an option? For MQTT 
features you'll probably get along with flespi.io

Or did I miss something?



Sideshow Raheem schrieb am Donnerstag, 27. Juli 2023 um 21:31:34 UTC+2:

> Hello all,
>
> I've been enjoying tinkering with my new weather station lately. I've got 
> it setup perfectly on my raspberry pi at home and it displays exactly how 
> I'd like using WeeWx and the Belchertown skin.
>
> Now I want to securely get it accessible via the web. At first I thought 
> that the directions here would work well for me - 
> https://www.cougar.eu.com/useful-guides/weewx-guides/publish-weewx-to-s3/index.html
>  
> and it seemed like it was. But using CloudFront and this setup I'm just 
> getting a static site that doesnt update, and all of the pictures are broke 
> as well.
>
> Now I'm wondering if I either A) setup something incorrectly, or B) am 
> taking the wrong approach.
>
> Would I be better off hosting the WeeWx server itself in AWS instead of my 
> Raspberry Pi? And then just harden the ec2 instance in AWS? I liked the 
> appeal of the s3 hosted site but just cant seem to get it to load correctly.
>
> Thanks,
> www.duluthweather.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/bab791d6-474d-4cab-bf51-d6a60039cc74n%40googlegroups.com.

[weewx-user] Re: WeeWx to Web

2023-07-27 Thread Sideshow Raheem

You know how when youre a hammer everything looks like a nail?

I use AWS at work, though not CloudFront as I'm not a web guy, and just 
jumped in head first that way for some reason. I think youre right though, 
MQTT is probably a better way to go.

On Thursday, July 27, 2023 at 2:39:49 PM UTC-5 michael.k...@gmx.at wrote:

> Hi,
>
> why isn't FTP'ing from the Pi to any simple webspace an option? For MQTT 
> features you'll probably get along with flespi.io
>
> Or did I miss something?
>
>
>
> Sideshow Raheem schrieb am Donnerstag, 27. Juli 2023 um 21:31:34 UTC+2:
>
>> Hello all,
>>
>> I've been enjoying tinkering with my new weather station lately. I've got 
>> it setup perfectly on my raspberry pi at home and it displays exactly how 
>> I'd like using WeeWx and the Belchertown skin.
>>
>> Now I want to securely get it accessible via the web. At first I thought 
>> that the directions here would work well for me - 
>> https://www.cougar.eu.com/useful-guides/weewx-guides/publish-weewx-to-s3/index.html
>>  
>> and it seemed like it was. But using CloudFront and this setup I'm just 
>> getting a static site that doesnt update, and all of the pictures are broke 
>> as well.
>>
>> Now I'm wondering if I either A) setup something incorrectly, or B) am 
>> taking the wrong approach.
>>
>> Would I be better off hosting the WeeWx server itself in AWS instead of 
>> my Raspberry Pi? And then just harden the ec2 instance in AWS? I liked the 
>> appeal of the s3 hosted site but just cant seem to get it to load correctly.
>>
>> Thanks,
>> www.duluthweather.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/2d0b4220-194f-4455-bab5-06fb1cc6e455n%40googlegroups.com.

[weewx-user] Re: WeeWx to Web

2023-07-27 Thread vince

AWS Lightsail is $3.50 per month so just spin up a 'minimal' nginx only 
site, stick it behind LetsEncrypt or CloudFlare, and go wild.   Use the 
weewx rsync uploader and you're done.  All you'd need to do for maintenance 
is periodically ssh in from home and apply updates and reboot once in a 
while.

On Thursday, July 27, 2023 at 12:56:19 PM UTC-7 Sideshow Raheem wrote:

> You know how when youre a hammer everything looks like a nail?
>
> I use AWS at work, though not CloudFront as I'm not a web guy, and just 
> jumped in head first that way for some reason. I think youre right though, 
> MQTT is probably a better way to go.
>
> On Thursday, July 27, 2023 at 2:39:49 PM UTC-5 michael.k...@gmx.at wrote:
>
>> Hi,
>>
>> why isn't FTP'ing from the Pi to any simple webspace an option? For MQTT 
>> features you'll probably get along with flespi.io
>>
>> Or did I miss something?
>>
>>
>>
>> Sideshow Raheem schrieb am Donnerstag, 27. Juli 2023 um 21:31:34 UTC+2:
>>
>>> Hello all,
>>>
>>> I've been enjoying tinkering with my new weather station lately. I've 
>>> got it setup perfectly on my raspberry pi at home and it displays exactly 
>>> how I'd like using WeeWx and the Belchertown skin.
>>>
>>> Now I want to securely get it accessible via the web. At first I thought 
>>> that the directions here would work well for me - 
>>> https://www.cougar.eu.com/useful-guides/weewx-guides/publish-weewx-to-s3/index.html
>>>  
>>> and it seemed like it was. But using CloudFront and this setup I'm just 
>>> getting a static site that doesnt update, and all of the pictures are broke 
>>> as well.
>>>
>>> Now I'm wondering if I either A) setup something incorrectly, or B) am 
>>> taking the wrong approach.
>>>
>>> Would I be better off hosting the WeeWx server itself in AWS instead of 
>>> my Raspberry Pi? And then just harden the ec2 instance in AWS? I liked the 
>>> appeal of the s3 hosted site but just cant seem to get it to load correctly.
>>>
>>> Thanks,
>>> www.duluthweather.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/cba6217b-f611-4d9d-8cbb-cdd71e23b504n%40googlegroups.com.

[weewx-user] Weewx stopped

2023-07-27 Thread jon...@gmail.com

 

Hello, since the 24th at 22:30 weewx has stopped. It does not even update 
the log.

I have updated to version 4.10.2 (I had 4.6 before but nothing changed).

Weewx works on a 3B raspi.


generated with: sudo wee_report:


Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

Caught unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 '>' not supported between instances of 'NoneType' and 'float'

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 Traceback (most recent call last):

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/reportengine.py", line 197, in run

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 obj.start()

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/reportengine.py", line 385, in start

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 self.run()

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in 
generate

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 ngen += self.generate(section[subsection], subsection, gen_ts)

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in 
generate

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 ngen += self.generate(section[subsection], subsection, gen_ts)

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 325, in 
generate

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 _filename))

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in 
_getSearchList

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 search_list += obj.get_extension_list(timespan, db_lookup)

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/user/highchartssearchlist.py", line 1243, in 
get_extension_list

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 period)

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 File "/usr/share/weewx/user/highchartssearchlist.py", line 961, in 
calc_windrose

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 max_speed = max(speed_vec_vt.value)

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 TypeError: '>' not supported between instances of 'NoneType' and 
'float'

Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine: 

 Generator terminated.


excuse me for this English., I'm Catalan and I translated with Im Translator

-- 
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/e947f11e-e21a-4e23-b65f-bc8d8056ca0en%40googlegroups.com.

Re: [weewx-user] WeeWx to Web

2023-07-27 Thread William Reading

You can also always set up cloudfront to hit the Pi running a webserver as the 
origin. Personally, I just run nginx as a reverse proxy to the pi (and skip 
paying for CF), which I think is generally good enough as long as you're 
comfortable setting up something like let's encrypt and dns pointed at it.

S3 static sites are nice in that you don't have to run an EC2 instance or 
configure that, but I've found that they have a bit of a learning curve because 
you need to make sure that stuff is shared publicly in the bucket and working 
there before you can point cloudfront at it. I think cloudfront also does have 
a mode where you skip the S3 static site altogether and just serve files out of 
S3, but I haven't tried that approach before.

--Bill

> On Jul 27, 2023, at 15:56, Sideshow Raheem  wrote:
> 
> You know how when youre a hammer everything looks like a nail?
> 
> I use AWS at work, though not CloudFront as I'm not a web guy, and just 
> jumped in head first that way for some reason. I think youre right though, 
> MQTT is probably a better way to go.
> 
> On Thursday, July 27, 2023 at 2:39:49 PM UTC-5 michael.k...@gmx.at 
>  wrote:
>> Hi,
>> 
>> why isn't FTP'ing from the Pi to any simple webspace an option? For MQTT 
>> features you'll probably get along with flespi.io 
>> 
>> Or did I miss something?
>> 
>> 
>> 
>> Sideshow Raheem schrieb am Donnerstag, 27. Juli 2023 um 21:31:34 UTC+2:
>>> Hello all,
>>> 
>>> I've been enjoying tinkering with my new weather station lately. I've got 
>>> it setup perfectly on my raspberry pi at home and it displays exactly how 
>>> I'd like using WeeWx and the Belchertown skin.
>>> 
>>> Now I want to securely get it accessible via the web. At first I thought 
>>> that the directions here would work well for me - 
>>> https://www.cougar.eu.com/useful-guides/weewx-guides/publish-weewx-to-s3/index.html
>>>  and it seemed like it was. But using CloudFront and this setup I'm just 
>>> getting a static site that doesnt update, and all of the pictures are broke 
>>> as well.
>>> 
>>> Now I'm wondering if I either A) setup something incorrectly, or B) am 
>>> taking the wrong approach.
>>> 
>>> Would I be better off hosting the WeeWx server itself in AWS instead of my 
>>> Raspberry Pi? And then just harden the ec2 instance in AWS? I liked the 
>>> appeal of the s3 hosted site but just cant seem to get it to load correctly.
>>> 
>>> Thanks,
>>> www.duluthweather.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/2d0b4220-194f-4455-bab5-06fb1cc6e455n%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/71C6712E-93DB-49E5-BB0B-4958A13C8192%40anmt.net.

[weewx-user] Is weather365 now defunct?

2023-07-27 Thread Kruse Ludington

I feed data to numerous places via weewx, but since yesterday my attempts 
to send weewx data to weather365 are no longer working. In the weewx wiki I 
don't see weather365 (not sure if it used to be there, I thought it was) - 
and now I am unable to get to the weather365 web site. Anybody notice this? 
Is this just an outage they are having, or is it gone for good? Was there 
any kind of an announcement that went out?

-- 
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/c2ff633d-aabc-4302-b0b0-994a13069ddbn%40googlegroups.com.

Re: [weewx-user] Weewx stopped

2023-07-27 Thread Tom Keffer

See https://github.com/gjr80/weewx-highcharts/issues/10


On Thu, Jul 27, 2023 at 1:34 PM jon...@gmail.com  wrote:

> Hello, since the 24th at 22:30 weewx has stopped. It does not even update
> the log.
>
> I have updated to version 4.10.2 (I had 4.6 before but nothing changed).
>
> Weewx works on a 3B raspi.
>
>
> generated with: sudo wee_report:
>
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
> Caught unrecoverable exception in generator
> 'weewx.cheetahgenerator.CheetahGenerator'
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  '>' not supported between instances of 'NoneType' and 'float'
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  Traceback (most recent call last):
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  obj.start()
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  self.run()
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  ngen = self.generate(gen_dict[section_name], section_name,
> self.gen_ts)
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in
> generate
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  ngen += self.generate(section[subsection], subsection, gen_ts)
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in
> generate
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  ngen += self.generate(section[subsection], subsection, gen_ts)
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 325, in
> generate
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  _filename))
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in
> _getSearchList
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  search_list += obj.get_extension_list(timespan, db_lookup)
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/user/highchartssearchlist.py", line 1243, in
> get_extension_list
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  period)
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  File "/usr/share/weewx/user/highchartssearchlist.py", line 961, in
> calc_windrose
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  max_speed = max(speed_vec_vt.value)
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  TypeError: '>' not supported between instances of 'NoneType' and
> 'float'
>
> Jul 27 22:08:26 raspberrypi wee_reports[20850] ERROR weewx.reportengine:
>
>  Generator terminated.
>
>
> excuse me for this English., I'm Catalan and I translated with Im
> Translator
>
> --
> 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/e947f11e-e21a-4e23-b65f-bc8d8056ca0en%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/CAPq0zEDOG7See1tU-w7xZzoHN1S0J3DFx8x5MKOt3nfqTY2Uzg%40mail.gmail.com.

Re: [weewx-user] Getting 4.5.1 to upload plots from ImageGenerator to my web page

2023-07-27 Thread DR

That did it, and it was much easier than I thought!

Thanks for the hint as to what to look at to include that plot in the
template. I hadn't gone back that far, only reading about the plot
generator and what to do for the various configurations and control over
the plot, and if there was something there in that flow of instructions
that said to go to the template to add it (if it were not a modification
of an existing plot), I missed it entirely.

Thanks again. I appreciate the hand holding and kind supoort. Dale