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 l
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 (an
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
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 optio
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 optio
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 optio
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
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:
>
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 $d
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]]
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 t
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 progres
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
pa
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.
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:
>
>> Thi
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 direct
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 st
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 m
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
whi
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:
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
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 t
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
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 some
The last time weather365 was able to receive data from me was exactly
9:30pm est July 26th. At the same time I noticed the same issue with
meteo-services.com - and at the same exact time (same corporate owner?).
Both of their websites appear to be offline as well...
On Thursday, July 27, 2023 a
I feed data to numerous places via weewx, but since yesterday my attempts
to send weewx data to weather365 - and meteroservices.com - are no longer
working. The last transmission I was able to make - to both of them - was
at exactly 9:30pm EST July 26, 2023 (does the same corporatre entity own
I confirm that from a moment when I changed False to True, log are not
filled anymore. I have only these lines:
[Logging]
version = 1
disable_existing_loggers = True
# Root logger
[[root]]
level = ERROR
handlers = syslog,
So probably I found Holy Grail.
czwartek, 27
27 matches
Mail list logo
