Just started experimenting with weewx - and using the simulator with
lighttpd serving up the data to a great looking web page on my rPi.
While I don't have a weather station yet, I've been trying to incorporate
data from an mqtt service and have had partial success. I am using the
MQTTSubscribe
Where do those 2 formatting statements go?
Also, why, in current.inc, is the line
#set $observations =
$to_list($DisplayOptions.get('observations_current', ['outTemp',
'barometer']))
containing only outTemp and barometer? Where are the rest of the items
displayed in Current Conditions? Sorry I'm ju
For WeeWX to save data to the database two conditions must be met (1) the
data must be present in a field in a WeeWX generated archive record (lines
starting with REC: when running WeeWX directly) and (2) the same field must
exist in the database. If these conditions are not met then data for th
Also should I have mentioned my newly added LakeElev column in the
database is not a member of any "group"? i.e. not group_altitude. Not
sure where I would group it; I do remember that in my 3.9.1 I edited
"units.py" and added group Lake and added new things like "foot2" and
"inch2" and someone pol
Your condition 2) is, of course, an absolute requirement. Your condition 1)
isn't, strictly speaking. It is perfectly possible (and fairly common) for
a Service triggered by the Archive record event to add (e.g.) a calculated
value to the archive record being processed, which is then inserted in
Sorry. I had assumed you were still using your v3.9.1 Seasons skin. If
that's the case, the tag $current.barometer is in the file
Seasons/current.inc.
Incidentally, there's no reason not to continue using your old skin.
But, if you are actually using a V4 skin, then to answer your questions:
1.
Hmm, '*the data must be present in a field in a WeeWX generated archive
record (lines starting with REC: when running WeeWX directly)*', that
includes any calculated/derived/added fields by any WeeWX service last time
I checked. I stand by my previous post.
Gary
On Sunday, 16 July 2023 at 13:5
I'm confused (again).
You mention that you CAN use an older version of a skin even in a newer
version of WeeWx.
I have a WeeWx 4.5.1 running with a Seasons skin that I like. Somewhere
along the evolution the way that the newer versions handle the plots and
the summaries was changed, and I a
You're probably overthinking.
WeeWX doesn't care what version of a skin you use, be it older, newer, or
totally custom written by you or a third party.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop rece
On Sunday, July 16, 2023 at 12:17:47 AM UTC-7 IceNov wrote:
I can see the mqtt data when running weewxd from the command line - it is
one of the fields showing up in the terminal output - but it's not being
added to the database.
I've also tried importing a csv file with timestamp and value - w
You do need to be careful with the parameterised Seasons skin introduced in
v4.6.0, there are a couple of features that require WeeWX v4.6.0 or later.
But in the main the shipped skins don't care about WeeWX version, the
shipped skins tend to use WeeWX features/tags that have existed since very
Thank you for those answers. I will continue to experiment. Dale
On 7/16/2023 12:13 PM, vince wrote:
You're probably overthinking.
WeeWX doesn't care what version of a skin you use, be it older, newer,
or totally custom written by you or a third party.
--
You received this message because
re: "3. I'm not following your question about "LakeElev". I don't know
what that is."
I have a ultrasonic range sensor (MaxBotix) which uses ttyS0 on the pi
which some python code (which has been working very well for several
years and still is) which writes a single line of text containing two
val
The answer is that you're confusing units (such as "inHg") with observation
types (such as "LakeElev").
The StringFormats section uses *units* as keys, not observation
types. If LakeElev is measured in meters, it will use whatever formatting
has been specified for meters.
I suspect that y
Before I read your reply I edited units.py and added LakeElev to
group_altitude at the bottom of the ...Dicts whatever-that-is, gave it
some time, had a bourbon, and lo and behold it is now printing out
lake elevation as ""LakeElev 594.75 feet" instead of 594.75
But I'm going to read your secti
I followed that guidance, removed my hack to units.py, placed the
entries in user/lakedata.py, and it's great.
to wit:
LakeElev 594.74 ftMSL
Yeah.
Thank you again. This is probably what I should've done way back in
the 3.9 days.
Phil
On Sun, Jul 16, 2023 at 11:00 PM Messy Potamia wrote:
>
> Befo
Glad it's working for you.
Single-malt Scotch works best for me.
On Sun, Jul 16, 2023 at 2:23 PM Messy Potamia
wrote:
> I followed that guidance, removed my hack to units.py, placed the
> entries in user/lakedata.py, and it's great.
> to wit:
> LakeElev 594.74 ftMSL
>
> Yeah.
> Thank you again.
Noted that. I might drop off one bottle, when I'm in Hood River next time.
Tom Keffer schrieb am Montag, 17. Juli 2023 um 00:50:40 UTC+2:
> Glad it's working for you.
>
> Single-malt Scotch works best for me.
>
> On Sun, Jul 16, 2023 at 2:23 PM Messy Potamia wrote:
>
>> I followed that guidance
18 matches
Mail list logo
