s Guide pointer is (here)
> <http://weewx.com/docs/usersguide.htm#Nothing_in_the_log_file> and there
> are a variety of other places logging is mentioned.
>
> Re: operating systems being confusing - that is not a weewx problem. Each
> os does things differently. You have
NOT "custom logs". I turned on `debug=1` -- if that's customization, ok.
Paul Anderson nailed it.
I knew nothing about systemd logging. Now I do.
As a person with some significant background in computing (yet new to this
environment), I suspect the following might be confusing to more than a
My weewx was running reasonably well for a year.
In Feb we left on a trip.
I returned, and learned weewx stopped working back on Feb 22
Here's the strange part: NOTHING is being logged.
/var/log/weewx.log has been empty since the end of January.
I run systemctl start weewx and it blows up early
Oh, the nice thing about using REST for catchup is it can request all
missing data. The local hub only sends what *it thinks is needed*, as there
can be no requests.
Power outages aren't the only things that cause data gaps ;)
On Monday, January 2, 2023 at 10:20:44 AM UTC-7 MrPete wrote
Interesting on the "calculated" data... my Tempest needs serious
recalibration of the raw rain data. Collected a whole season last year;
will soon submit it to them.
I'm wondering if "modified" rain data from REST includes recalibrated rain,
while UDP rain is uncalibrated?
On Friday, December
THANKS!
I now understand more. that yes, it's a fork to add REST support (so it can
catch up... and because WeatherFlow highly recommends making use of REST
instead of UDP whenever possible ;) ).
I connected with WeatherFlow support. Turns out, accessing the Hub in the
REST API simply is not
My Weewx now crashes continually, due to a new problem in the link from
WeatherFlowUDP to the WeatherFlow REST API:
* I'm getting crashes due to a 500 error returning from the API
* Turns out the Weewx driver is attempting to retrieve observations from
all "devices" in the station... but the
OK, if not a bug, then let's define the default for users who live above
5,000 ft. :)
I think it's far more reasonable to set defaults so that under ANY normal
conditions, users will not see an error. YES, let them tune the default to
a narrower range if they want.
On Thursday, March 3, 2022
I may have something quite basic wrong, but need some hints to even get
going...
As noted above, my logs show lots of mqtt publishing just fine for archive,
but user.mqtt loop publish fails every time.
I set debug=1 in weewx.conf but that doesn't appear to add any debug info.
Is there a way
s file that you can tweak.
>
> On Thu, Jul 14, 2022 at 3:47 PM MrPete wrote:
>
>> I've browsed the User Guide, the Customization Guide, the Wiki, the
>> *.conf files, and some code for my preferred skin (BelcherTown)
>>
>> Two seemingly obvious elements remain
I've browsed the User Guide, the Customization Guide, the Wiki, the *.conf
files, and some code for my preferred skin (BelcherTown)
Two seemingly obvious elements remain invisible to me:
CONTEXT: My site, at least for mobile users, uses clearly-too-large fonts.
(They are BIG, and wordwrap
Hi all,
Experienced tech (HW, SW, FW and more), brand new to WeeWX. Have had my
WeatherFlow Tempest running for a couple of months.
On initial setup, I just discovered that weewx thinks my barometric
pressure is out of range! I thought that was interesting.
I consider this a bug:
- The
12 matches
Mail list logo
