Thanks Gary - I mean things like the following that I use in the about page
on my site
$station.hardware
$station.os_uptime
$station.uptime
$station.version
$belchertown_version
I want to add to this current observations from my Netatmo station as a
snapshot, these are the ones available, there m
OK. At the moment my best guess is that when weectl import calculates
missing derived obs one of the GTS derived obs is not being calculated
cleanly/causing a process to remain in memory. Over time the overall memory
use increases until the system hangs/crashes due to lack of free memory. A
res
Hey, attached is an excerpt from journalctl.
Greetings Sebastian
gjr80 schrieb am Dienstag, 23. Juli 2024 um 10:41:51 UTC+2:
> OK. At the moment my best guess is that when weectl import calculates
> missing derived obs one of the GTS derived obs is not being calculated
> cleanly/causing a pro
If - as Gary suggests - GTS is the reason, you could try and comment out
user.GTS.GTSService in weewx.conf and try again. If that makes a
difference, this would be a path to look further.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubs
Was there anything after the last two lines? The 'calculate missing' part
of the log is where there may be a clue. The 'UNIQUE constraint failed'
error messages are expected and can be ignored; once WeeWX has written a
given record to archive any attempt to write the same record again will
resu
Hi,
Also noticed the same. Did you ever get anywhere with this?
Am thinking about changing the console to use WU format, and changing
interceptor to use wu-client. But haven't got that far yet
RRB.
On Wednesday 17 July 2024 at 16:14:36 UTC+1 Jeff Burricelli wrote:
> Is anyone using the ECOWIT
Unfortunately without success
Karen K schrieb am Dienstag, 23. Juli 2024 um 12:02:41 UTC+2:
> If - as Gary suggests - GTS is the reason, you could try and comment out
> user.GTS.GTSService in weewx.conf and try again. If that makes a
> difference, this would be a path to look further.
--
You
Sebastian E schrieb am Dienstag, 23. Juli 2024 um 13:41:03 UTC+2:
Here is a longer excerpt from journalctl
What I get from that log is, that weectl starts report generation after
importing data. And I see, the Belchertown skin is involved. So there is a
possibility that this problem is involve
Does anyone know if just a Davis 6410 anemometer works with Weewx by just
connecting it with the RJ-11 cable?
--
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 wee
It's possible the so called 'Belchertown v5 issue' is involved but a few
things suggest it is not, or if it is it's effect is insignificant:
- weewx.conf indicates the user is using the wview_extended schema
- the Belchertown issue raises it's head when a report is run and missing
derived obs ar
I'm trying to track the water level of a lake so I added a new column to
the database (lakeSurfaceLevel), created a service to populate the data,
and modified my skin to display it. All of that works great, however when I
try to import data for that new observation using weectl, I get a error
"
Thanks, can you post the complete and exact output to the console when weectl
import is run. Also, what does the weectl log show?
Gary
On Wednesday 24 July 2024 at 06:40:53 UTC+10 Zach wrote:
> I'm trying to track the water level of a lake so I added a new column to
> the database (lakeSurfaceL
Sorry, I should have clicked reply all. ;)
Here is the output
Using configuration file */Users/zach/weewx-data/weewx.conf*
This is a dry run. Nothing will actually be done.
Starting weectl import...
A CSV import from source file '/Users/zach/Downloads/Untitled.csv' has been
requested.
The fo
One thing to check is that while weewx.conf might say it's using the
wview_extended schema, that is only positively true if the db was created
at weewx v4 or later. Suggest the original poster check their actual db
files to see what the database is actually using. You should probably
check a
OK, I suspect the problem is when you added field lakeSurfaceLevel to WeeWX
you didn't tell WeeWX what unit group the field belongs to. Consequently,
when you attempt to import data into lakeSurfaceLevel weectl import
conducts some checks to see if any source field unit conversion is
required.
I have that line in my custom service for pulling the data from an API.
Should I also put it in the extension.py?
On Tuesday, July 23, 2024 at 4:17:36 PM UTC-5 gjr80 wrote:
> OK, I suspect the problem is when you added field lakeSurfaceLevel to
> WeeWX you didn't tell WeeWX what unit group the
Does anyone know of a testing program that could simulate the WLL sending
data over the WiFi network. That might be a helpful tool.
On Monday, July 22, 2024 at 8:53:55 PM UTC-4 vince wrote:
> No, weewx supports all kinds of interfaces including network depending on
> which gear you have.
>
> To
I looked on google groups to see if there is a help group for Campbell
Scientific questions, and found nothing so far.
I have generously been given a copy of the CR Basic and weewx driver
developed by a user here and am adapting it to my datalogger and sensors
from the ones he programmed.
M
The problem is weectl import is a standalone utility run independent of
WeeWX and as such does not load the WeeWX services specified in the WeeWX
config file (well it actually does cause some of the services to be loaded,
but later on after the import has occurred when missing obs are/may be
ca
True, but I suspect Belchertown is not playing a significant role here, the
log extract shows Belchertown completes in less than 10 seconds. My
understanding tis that the v5 Belchertown issue is characterised by
excessively long Belchertown report generation times.
Gary
On Wednesday 24 July 20
Unfortunately, adding it to extensions.py did not work. I'll sit tight
until a fix is completed. But no hurry!
Thanks Gary!
On Tuesday, July 23, 2024 at 5:48:01 PM UTC-5 gjr80 wrote:
> The problem is weectl import is a standalone utility run independent of
> WeeWX and as such does not load the
OK. Thanks.
Gary
On Wednesday 24 July 2024 at 08:53:39 UTC+10 Zach wrote:
> Unfortunately, adding it to extensions.py did not work. I'll sit tight
> until a fix is completed. But no hurry!
>
> Thanks Gary!
>
> On Tuesday, July 23, 2024 at 5:48:01 PM UTC-5 gjr80 wrote:
>
>> The problem is weectl
I looked at all the wll implementation you mentioned in your former post
Vince, and https://github.com/michael-slx/weewx-weatherlink-live looks like
the most recently updated. It also uses the new weectl function.
I have not done much python programming. During my career days I programmed
mostl
There are 31 registered sites using that driver, so personally I'd trust it
works and save yourself the work :-)
On Tuesday, July 23, 2024 at 3:58:35 PM UTC-7 Barton Phillips wrote:
> I looked at all the wll implementation you mentioned in your former post
> Vince, and https://github.com/michae
Agree, but it eliminates some possibilities. They also have a secondary
db which might be where the issue is. Quick thing to try to pin down the
cause...
On Tuesday, July 23, 2024 at 3:53:00 PM UTC-7 gjr80 wrote:
> True, but I suspect Belchertown is not playing a significant role here,
> t
wxforum.net would be the go-to place for just about any question you can
think up, but you'll have to figure out which board there to post to...
perhaps https://www.wxforum.net/index.php?board=70.0
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group
Probably enough chefs in the kitchen already…. But I can’t help myself.
Did this work at one time and now doesn’t? If so, can you remember what you
changed?
If it never ‘worked’ or you can’t remember what you changed, I’d step back
and ‘disable’ all non core WeeWX extensions. A quick scan o
Bob,
Thanks for letting us know that you are up and running. I greatly
appreciate knowing when a suggestion has worked (as I bet future google
searchers do too). A couple of comments.
The key option you add is `expires_after = None`. This enables
MQTTSubscribeService’s cache. The `contains_total
Zach,
Did you by chance copy and paste those two lines from my earlier post into
extensions.py? If so if you look closely I had a typo, lakeSurfaceLevel was
incorrectly capitalised. I've just run weectl import with your data and
import config file with the correct two lines in extensions.py and
That was it! Thank you so much for your help!!!
On Tuesday, July 23, 2024 at 7:33:10 PM UTC-5 gjr80 wrote:
> Zach,
>
> Did you by chance copy and paste those two lines from my earlier post into
> extensions.py? If so if you look closely I had a typo, lakeSurfaceLevel
> was incorrectly capitalis
maybe report interval aggregation, to (mostly) eliminate NULLs
⊣GE⊢
> On 24 Jul 2024, at 9:56 AM, bell...@gmail.com wrote:
>
> Stating differently, it works when a complete archive record is not in the DB
> but not for missing values in an archive record. So in your case, no setting
> of `line
i.e. add new field to the schema, as well as just add column in database
⊣GE⊢
> On 24 Jul 2024, at 7:17 AM, gjr80 wrote:
>
> OK, I suspect the problem is when you added field lakeSurfaceLevel to WeeWX
> you didn't tell WeeWX what unit group the field belongs to.
--
You received this message
I thought the schema is only used during database creation. Did I min-read
that?
On Tuesday, July 23, 2024 at 8:27:14 PM UTC-5 Graham Eddy wrote:
> i.e. add new field to the schema, as well as just add column in database
> *⊣GE⊢*
>
> On 24 Jul 2024, at 7:17 AM, gjr80 wrote:
>
> OK, I suspect th
i meant it in broader context of the defining the types
re the schema columns table in extensions.py, i have seen tom several times say
it is used only on creation but i have encountered it being used at different
times while fiddling
⊣GE⊢
> On 24 Jul 2024, at 12:59 PM, Zach wrote:
>
> I thou
34 matches
Mail list logo
