run the command as user weewx on the weewx box, i hasten to clarify
⊣GE⊢
> On 24 May 2024, at 10:39 PM, Graham Eddy wrote:
>
> on source box running weewx, run $ ssh websvr hostname (where websvr is rsync
> target host)
--
You received this message because you are subscribed t
verify that ssh passwordless login is actually working:
on source box running weewx, run $ ssh websvr hostname (where websvr is rsync
target host)
and you should see it print websvr’s hostname
but it might prompt you interactively to update known_hosts, if they are new
keys...
⊣GE⊢
> On 24 May
this says weewx box is broadcasting query for any gw1000 devices to respond
with their MAC address but no answer → make sure weewx box and gw1000 device on
same lan
⊣GE⊢
> On 11 May 2024, at 8:10 PM, Mitchell Tuckness wrote:
>
> May 10 08:23:17 weewx-pi weewx[1657] ERROR user.gw1000: Failed
ltiple
> processes that you can ssh into isn't a container, it's a virtual machine.
>
> On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:
>> i suggest testing before publishing..
>> that won’t work without the permissions towards end of my lxc/105.conf file
>>
i suggest testing before publishing..
that won’t work without the permissions towards end of my lxc/105.conf file
⊣GE⊢
> On 8 May 2024, at 9:25 PM, G7LTT wrote:
>
> Updated to add USB device to the container.
--
You received this message because you are subscribed to the Google Groups
1157485956
Swap: 7807 5167291
graham@ballina:~$ uptime
14:04:35 up 78 days, 14:26, 1 user, load average: 0.00, 0.04, 0.10
cheers
⊣GE⊢
> On 8 May 2024, at 1:30 PM, Graham Eddy wrote:
>
> as the doc hinted, putting proxmox itself a
as the doc hinted, putting proxmox itself aside, install/run weewx in LXC
unprivileged container is the same as running it outside a container, with the
benefit of it not being able to trample on rest of host
the tricky parts are where the container walls are visible, the two principal
cases
i replaced my then-18yo cracked & peeling solar panel with a nice new one -
just required plugging panel’s lead into ISS
⊣GE⊢
> On 23 Apr 2024, at 2:00 AM, vince wrote:
>
> perhaps a solar panel ($55) will handle the data problems, but I'd suggest
> doing just the battery first to see.
--
i interpreted the suggestion as making it the default that logging is turned on.
this is self-correcting: when the user has learnt enough to turn logging off,
they can.
place the instruction how in the documentation that they should have read but
did not (or did not understand at the time).
i
this sounds great.
for the record, eliminating the davis console and its need for a serial/usb
port also eliminates what it provides: various indoor sensors (including
barometer i think) and -crucially- the hardware data logger
⊣GE⊢
> On 25 Mar 2024, at 3:46 AM, vince wrote:
>
> Short answer
i wrapped paho mqtt a few years ago, but not implementing whole interface.
i wote a bunch of apps on top of my wrapper, one being my own weewx mqtt
service/driver, other apps are various mqtt producers and consumers
thanks for the heads-up on the mqtt interface change.
it prompted me to polish
oops, python syntax would be: expr if ops_tye in globals() else None
⊣GE⊢
> On 9 Mar 2024, at 10:31 am, Graham Eddy wrote:
>
> i think ' if obs_type in globals() then expr else None ' would work
> ⊣GE⊢
>
>> On 9 Mar 2024, at 9:13 am, 'michael.k...@gmx.at' via weewx-user
i think ' if obs_type in globals() then expr else None ' would work
⊣GE⊢
> On 9 Mar 2024, at 9:13 am, 'michael.k...@gmx.at' via weewx-user
> wrote:
>
> I think I remember that this has been asked before, how to check with an
> expression in Corrections, if an obs_type is present?
>
> --
>
Jsonpath is good for plucking specific values on the subscribe/inward side, but
it doesn’t help with the publish/outward side (or at least i couldn’t think of
one). i am still using the eval(expr, weewx-packet or json-message) approach in
my mqtt implementation
⊣GE⊢
> On 7 Mar 2024, at 11:05
your archive interval is set to 10 mins, and the log is truncated just where it
started getting interesting. collect log data for two complete cycles at least,
in your case 20 mins
⊣GE⊢
> On 5 Mar 2024, at 8:03 pm, Francis Greaves wrote:
>
> Thanks Tom for the suggestions.
> I upgraded to
“month” is a fuzzy measure, not precise. it is not surprising that arithmetic
with fuzzy numbers produces fuzzy numbers.
what *is* surprising is that people find the above surprising
same as network distributed time - given the variable time it takes to transfer
a “time” to another place, we
i tried proxmox on RPi 4 briefly but it was too unstable for a reliable weather
station - proxmox (pimox) is not supported on RPi and known to have problems
and limitations (don’t get me started on overlay driver!)
proxmox 8 runs extremely well on bookworm on my mac mini. i pass through a
why are you writing into files outside weewx’s area? weewx user is unlikely to
have perms to do that
⊣GE⊢
> On 11 Feb 2024, at 1:59 am, Ton Karsten wrote:
>
> feb 10 15:10:15 raspberrypi weewxd[4548]: ERROR weewx.reportengine:
> File "/usr/lib/python3.11/shutil.py", line 258,
vantage device is on LAN. wireless interface normally not ready until long
after weewx tries to start, unusual (but not impossible) for ethernet interface
to be so late. try the ‘loop-on-init = 1’ in weewx.conf, or insert a delay in
the startup file
⊣GE⊢
> On 6 Feb 2024, at 8:08 am, Neil B
it is worth noting and perhaps documenting that python builtin functions can be
used in StdCalibrate expressions
⊣GE⊢
> On 22 Jan 2024, at 4:19 am, Tom Keffer wrote:
>
> Yes, of course. Just substitute "**" for "^" so it's a Python expression. Or,
> use the math function pow().
>
> On Sun,
i found putting the db into a RAM disk for the duration helps in these
situations (i had to do that for a weewx migration some time ago)
⊣GE⊢
> On 19 Jan 2024, at 3:36 pm, 'michael.k...@gmx.at' via weewx-user
> wrote:
>
> Or, to speed things up, do the "calc-missing" on another machine with a
maybe a bit short?
⊣GE⊢
> On 18 Jan 2024, at 11:55 am, Michael Sanphillipo
> wrote:
>
> archive_interval = 120
--
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
many plaudits to tom, matt and gary for V5, navigating the shifting decks
of python and linux while preserving the long stability of weewx for
another milestone release.
the software engineers amongst us understand and appreciate the difficulty,
attention to detail and sheer volume of work -
reasonable questions: yes to both, the ‘(venv)’ in the prompt is the clue to
the first. i showed content of ~weewx/bin because i was asked for it; i knew it
did not exist, and what was really being asked was for ~weewx/{venv}/bin and
~weewx/{station}/bin, so i showed those as well
actually
;
> Also, what is in /home/weewx/bin?
>
> I'm reluctant to put too much energy in debugging b16, because a lot of how
> WEEWX_ROOT is handled has changed since then. If you're still having
> problems, upgrade to the current rc3.
>
> -tk
>
> On Mon, Jan 8, 2024 at 4:31 AM
running weewx 5.0.0b16 in production quite happily for weeks - it works fine.
i needed to delete a bad barometer reading from station called ‘vantage’, so i
stopped unit weewx@vantage, set the value to None, then tried to rebuild the
daily database → following error:
(venv) weewx@wx:~$ weectl
maybe check the font_path in skins.conf, ensure the image generator fonts
include the simplified chinese symbols
⊣GE⊢
> On 6 Jan 2024, at 2:21 pm, Kranz Liang wrote:
>
> I have translated the language files in weewx, converting Traditional Chinese
> into Simplified Chinese and also adjusted
the vantage IP device seems to accept a connection, work for a while, then stop
responding, then connection is reset → sounds like on device side it seizes up
and the ip protocol times out; establishing new connection just repeats the
cycle. the device apparently has been working for years and
suggestions:
(1) maybe the weekly graph is only being calculated in your 0-5 daily hour
interval → really failing all the time. try hourly or daily graph to verify it
works during those & other hours
(2) maybe another deeper exception is happening which happens to be percolated
up as sqlError
microwave:
i have the wide beam aligned up/downstream to mitigate its width.
my readings are always larger, not smaller, than they should be. successive
readings that should be nearly identical can be more than 20% different, and i
notice a general daily oscillation of about 50% but i could not
river level sensors:
* my dragino lorawan ultrasonic sensor has been fine, though it has
condensation problems (to be fair, it is mounted under a bridge a couple metres
above normal river level)
* my dragino lorawan microwave radar has been a failure. i get neither
accurate nor consistent
just looking at the intention of the code without having read the thread
[always dangerous!]
i cannot quote the original python text here because unfortunately it was
reported using a screenshot [please don’t do that]
but note that if extraHumid1 is undefined (not present in packet, as opposed
i posted details of my implementation of lorawan river level sensors reporting
via weewx on this forum about a year (or two?) ago. they are anxiously watched
by community when we have severe rain events in the region (we flood fairly
often - you learn to deal with weather extremes)
ditto re
for the record, a reminder:
conf syntax is driven by the [..[ ]..] sections, not by indent.
putting ‘username’ after ‘[[tls]]’ means username is inside [[tls]] section,
not in parent section (indenting irrelevant)
⊣GE⊢
> On 5 Nov 2023, at 2:34 am, Fjordey wrote:
>
> #2 That told me right there
>
> On Fri, Sep 29, 2023 at 3:41 PM Graham Eddy <mailto:g...@geddy.au>> wrote:
>> try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo tail
>> -50 /var/log/mosquitto/* if it puts them there instead)
>> ⊣GE⊢
>>
>>> On 29
try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo tail
-50 /var/log/mosquitto/* if it puts them there instead)
⊣GE⊢
> On 29 Sep 2023, at 11:35 pm, Stefan Gliessmann
> wrote:
>
> I am trying to get my weather station web presence secure with https://
> Therefore, I also
an item timestamped 21:10:05 belongs to the reporting period after 21:10 - it
doesn’t matter when the report is actually generated
⊣GE⊢
> On 14 Sep 2023, at 11:35 am, kufuu wrote:
>
> I reboot the pi zero-w and seen it didnt add the files to database till it
> ran the second payload
>
>
>
perhaps it was generating all reports, as from a clean slate, and in future it
could just be incremental and less of an issue
⊣GE⊢
> On 4 Sep 2023, at 12:10 pm, Greg from Oz wrote:
>
> I guess it was wdc:
> Sep 3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: Generated
> 11
in V5 i am assuming a single station can be created but separate weewx.conf’s
used, as in V4 weewx-multi config, with the downside that they share same
extensions.py i.e. not utilising V5’s design change
in my case, i want same codebase and python modules available to all weewx
instances but
my experiments with multiple instances and topologies have been very smooth
with pip install - that is quite elegant.
i tried the documented github install and fell on my face, even after working
out to select V5 to clone. i’m not github-savvy (but i look at the source code
a lot) so ‘here be
for the forum search record, you can do a lot of stuff (especially using
services) within one instance of weewx. you only *must* use separate instances
when you need multiple drivers, or services conflict with each other. you *may*
separate instances for operational or scalability purposes
⊣GE⊢
not quite what is being asked re ‘extract data for the last 5 minutes’…
given weewx usually generates data reports each 5 mins, presumably you just
want a file generated with the data you specifically want.
i create a json file with basic wx info each 5 mins as a javascript-friendly
api - it is
use ‘python3 -m venv ~/venv’ to create the environment in ~/venv.
then in your shell run ’source ~/venv/bin/activate’ to set up the shell
environment (initialised python bindary, PYTHONPATH etc). i put this in my
~/.bashrc
a key trick is that running the initialised python binary
i have been polling a SolarEdge HDWave inverter for a few years.
my inverter has the LED, so it is not the latest version, and doesn’t have
direct API, so i use the API to the (yuck) vendor cloud API (and not happy
about it). vendor API throttles to about 1 call/15 mins.
i have a simple daemon
read up on python ‘virtual environment’ (venv) to get your libraries etc in
place.
running it while not logged in - best way depends upon your o/s (eg user mode
of systemd)
⊣GE⊢
> On 10 Aug 2023, at 2:06 am, Matthew Fields wrote:
>
> Might seem like an odd request, but I'm trying to find some
swap vantage to ecowitt and you lose the data logger (stored in local hardware)
→ one day you lose critical data
ecowitt already have a ‘regularly call home' to china built in that adds no
value to customer, only a dependency on ecowitt company. if ecowitt turn off
their ‘ok’ response,
have a look at LoRaWAN (and run your own Network Server, several are available
to install). their whole point in open communications to sensors (mqtt). the
price points are higher than Ecowitt, but nowhere near as expensive as Davis
⊣GE⊢
> On 9 Aug 2023, at 9:30 am, Greg from Oz wrote:
>
> It
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:
>
ould mqtt_websockets_topic look like? e.g. =
> weather/inTemp_degree_C/loop?
>
> TIA,
> Stefan
>
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>> referenced topic not listed in the topics of published messages
>> ⊣GE⊢
>&
referenced topic not listed in the topics of published messages
⊣GE⊢
> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann
> wrote:
>
> mqtt_websockets_topic = weather/loop
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe
i meant ‘mosquito_sub -v -t “#" -h brokerhost’ on weewx host, plus
authentication if any
⊣GE⊢
> On 25 Jul 2023, at 11:47 am, Graham Eddy wrote:
>
> try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** being
> published
> ⊣GE⊢
>
>> On 25 Jul 2
try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** being
published
⊣GE⊢
> On 25 Jul 2023, at 5:08 am, vince wrote:
>
> I think you have a mismatch in what you are publishing vs. what you are
> trying to subscribe to.
--
You received this message because you are
windoze xp was my last - i bet it hasn’t improved since
⊣GE⊢
> On 24 Jul 2023, at 7:06 am, vince wrote:
>
> I can't speak to using Windows as I haven't needed to do so in well over two
> years
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
values like rain - and, in my own case, energy created by solar panel inverter
- need to be summed not averaged over the archive interval.
the default accumulator for a data_type is averaging, so you need to specify
your new data_type explicitly as summed - in my case, ‘’weewx.conf'' has:
> Laptop can ping PI
> Pi cannot ping laptop
> PI cannot ping 192.168.1.248 the GW1000
>
> i can SSH into both PI's
>
>
>
>
>
> On Sunday, 23 July 2023 at 13:22:51 UTC+1 Graham Eddy wrote:
>> laptop can ping gw1000.
>> pi cannot ping gw1000.
>&g
laptop can ping gw1000.
pi cannot ping gw1000.
can laptop ping pi? and pi ping laptop?
⊣GE⊢
> On 23 Jul 2023, at 9:56 pm, zasp...@gmail.com wrote:
>
> i have pinged other IP address on my net work and the PI gets response its
> only the GW1000 its have an issue with
>
> On Sunday, 23 July
2023 at 15:03:26 UTC+10 Greg Reive wrote:
>> What do you mean rain year date?
>>
>>
>> On Sat, 24 June 2023, 14:50 Graham Eddy, > wrote:
>>> rainyear date?
>>> ⊣GE⊢
>>>
>>>> On 24 Jun 2023, at 2:27 pm, Greg from Oz &g
rainyear date?
⊣GE⊢
> On 24 Jun 2023, at 2:27 pm, Greg from Oz wrote:
>
> I have made a graph to show the cumulative rainfall and it seems to show the
> correct values on the graphs for day, week and month. They tally up with the
> figures that weewx has calculated but the year total is way
someone could develop a ‘filter’ service that could hold state (either in
memory or private database) of successive readings.
conceptually an extension of StdQC
⊣GE⊢
> On 24 Jun 2023, at 6:22 am, gjr80 wrote:
>
> Hi Steve,
>
> Unfortunately you are correct; StdQC does a simple check that an
does this indicate the same MQTT service is being loaded twice? that might
confuse the driver
⊣GE⊢
> On 22 Jun 2023, at 8:42 am, jose riaño wrote:
>
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Loading service
> user.mqtt.MQTT
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT:
assuming you rolled everything back, then rolled forward one step at a time
until it started to fail, what was the last step causing it to fail?
⊣GE⊢
> On 14 Jun 2023, at 1:09 am, Mark Fraser wrote:
>
> I can't think of anything I've changed that would cause this
--
You received this
disable everythng back to bare bones, then add them back again one at a time
⊣GE⊢
> On 12 Jun 2023, at 12:22 am, Mark Fraser wrote:
>
> Any ideas how to debug this?
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
-gw1000[807215] DEBUG user.gw1000: #GE before
s.close
May 31 20:46:41 ironbark weewx-gw1000[807215] DEBUG user.gw1000: Failed attempt
1 to send command 'CMD_GW1000_LIVEDATA': [Errno 113] No route to host
cheers
⊣GE⊢
> On 28 May 2023, at 10:08 pm, Graham Eddy wrote:
>
> nope, adding s
nope, adding s.shutdown() call didn’t help, still timing out
now i’ll try increasing [GW1000]socket_timeout to 59s to see if it blows even
that long a period
⊣GE⊢
> On 28 May 2023, at 8:10 pm, Graham Eddy wrote:
>
> the greater detail shows it is timing out on the s.connect() ca
3/library/socket.html#socket.socket.shutdown> before
close() <https://docs.python.org/3/library/socket.html#socket.close>.
so i have experimentally inserted a s.shutdown() call just before the
s.connect() call. we’ll see if it makes any difference...
⊣GE⊢
> On 28 May 2023, at 5:30 p
i should also have mentioned that this same weewx server also hosts another
instance of weewx, using serial vantage driver, that is having no such problems
⊣GE⊢
> On 28 May 2023, at 5:28 pm, Graham Eddy wrote:
>
> v0.5.0b5 is in place and i continue to get timeouts and restarts.
&
v0.5.0b5 is in place and i continue to get timeouts and restarts.
(logging issue is resolved; i am preferring to continue in this thread for
situational continuity e.g. logs are all relevant)
in brief, at intermittent times (less than an hour apart to several days
apart), i get three
May 2023, at 5:57 pm, gjr80 wrote:
>
> You might want to upgrade your driver, support for the GW2000 was introduced
> in v0.5.0.
>
> Gary
>
> On Friday, 26 May 2023 at 16:29:03 UTC+10 Graham Eddy wrote:
> May 26 15:33:31 ironbark weewx-gw1000[350663] INFO user.gw1000:
for a couple of weeks i have been getting gw1000 driver rebooting after three
no-responses. old gw1000 unit seems otherwise fine; tried different power
source, tried rebooting everything occasionally; still failed, sometimes after
few mins, sometimes 2 hours, 5 hours, sometimes a couple of
tom did not say that 4.10.2 removed [Logging], he did ask you to remove that
section temporarily, to get it to use default, in case your own content of that
section was wrong. tom said that you were using a specific item (i think it was
‘rotate’) that was removed in 4.10.2 and thus causing your
try subscribe (-v) to topic ‘#’ to examine all messages (in case topic
mis-named)
⊣GE⊢
> On 9 May 2023, at 9:09 am, Kevin Crivelli wrote:
>
> So I am definitely getting records published from MQTT however I still have
> the same problem where the local address is showing connected waiting for
;
>>>> http://livefreeorpi.com <http://livefreeorpi.com/>
>>>>
>>>> On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
>>>>> I remember such behavior when a spider let the remains of her meals drop
>>>>> into the rain bucket.
>
is the outlet from rain bucket partially blocked?
⊣GE⊢
> On 29 Apr 2023, at 11:48 pm, Steve C wrote:
>
> Important distinction! I meant to mention that. Yes, the software seems
> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it
> accordingly. Being a hardware issue I
looks like to separate problems
(1) something in interceptor driver - might be benign (ignorable), or might be
serious
(2) logging misconfigured. check the syslog interface mechanism for your
specific o/s
⊣GE⊢
> On 27 Apr 2023, at 11:00 am, Marcin Metter wrote:
>
> I've been seeing the
i continue to run my old pressure river level sensor with my new ultrasound
river level sensor.
i found the cable from pressure sensor (at river bottom) to prioprietary
transmitter (above flood level) very inconvenient, whereas ultrasound
sensor/transmitter are together (above flood level),
i put a detailed description of lorawan river level/temp sensors under weewx in
this forum not long ago. a search will find it. cheers
⊣GE⊢
> On 17 Apr 2023, at 9:38 am, Tim Tuck wrote:
>
> Just wondering if anyone has network attached water tank level meters ?
>
> Also wondering if anyone
congratulations to gary for a brilliant diagnosis
⊣GE⊢
> On 9 Apr 2023, at 12:44 pm, Mike wrote:
>
> i have found the excluded fields option for rain in weewx.conf, I have added
> all the lightning fields and it has sorted the issue.
--
You received this message because you are subscribed to
suppose you look at a given weekly plot of some observation e.g. outside
temperature.
suppose further that you can scroll left or right to see earlier or later
weekly plots - much easier to see trends going over months e.g. how the
temperature is varying over several months.
(in my case looking
a DaySummaryManager
instance for its database?
⊣GE⊢
> On 12 Mar 2023, at 8:45 pm, Graham Eddy wrote:
>
> i have updated the NOAA reports to include fields from another weewx database
> (using $data_binding in tags). these external fields all work fine for
> min,mintime,max,ma
i have updated the NOAA reports to include fields from another weewx database
(using $data_binding in tags). these external fields all work fine for
min,mintime,max,maxtime,avg,count but not for meanmax,meanmin. weewx v4.10.2
the period tags are $day,$month,$year (all at least one day) so i
isn’t this parsed as a list?
⊣GE⊢
> On 12 Mar 2023, at 12:28 pm, gjr80 wrote:
>
> delimiter = ,
--
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
looks like wrongly set unit label (not unit name)
⊣GE⊢
> On 3 Mar 2023, at 12:44 pm, lloyd...@gmail.com wrote:
>
> it shows on the skin (whatever the default is) RTD Temperature 20% and
> TMP117 temperature 18% for temperatures of 20.46 and 18.09 respectively
--
You received this message
sounds like XON/XOFF problem (slow receiving side hardware/driver)
⊣GE⊢
> On 20 Feb 2023, at 4:15 am, Brian Waligorski / N6RZR
> wrote:
>
> I tried each successive slower rate until I arrived at 1200 baud and it's
> been now a month with no problem.
>
--
You received this message because
rain in LOOP packet (inches) equals rain in wsview app (mm)
⊣GE⊢
> On 7 Feb 2023, at 11:15 pm, Christian H. wrote:
>
> LOOP: 2023-02-07 13:10:50 CET (1675771850) 'dateTime': '1675771850',
> 'daymaxwind': '6.0', 'dummyTemp': '96.3', 'inHumidity': '38', 'inTemp':
> '64.22', 'luminosity':
untested: put in Corrections section of weewx.conf something like
PRIMARY_V = PRIMARY_V if PRIMARY_V in locals() else BACKUP_V
(weewx packet is used as local bindings in python eval)
⊣GE⊢
> On 1 Feb 2023, at 5:18 pm, p q wrote:
>
> Yes, but by modifying the driver code, which is not the
i posted some time ago about my trusty old river level monitor. i am still
receiving occasional enquiries about it - yes, unfortunately that product i
used is no longer available. whilst it is still working for me, i have now
deployed a new river level monitor in parallel, some details below
; wrote:
>>>
>>> You're not doing something dumb. None values always mark line breaks.
>>>
>>> On Wed, Jan 18, 2023 at 6:30 AM Graham Eddy >> <mailto:g...@geddy.au>> wrote:
>>>
>>
>>
>> --
>> You received this
to love the ‘mark’ not the ‘line'.
thanks
⊣GE⊢
> On 19 Jan 2023, at 2:49 am, Tom Keffer wrote:
>
> You're not doing something dumb. None values always mark line breaks.
>
> On Wed, Jan 18, 2023 at 6:30 AM Graham Eddy <mailto:g...@geddy.au>> wrote:
>
--
You receiv
i am getting a sequence of points plotted rather than a line showing.
line_type = solid
line_gap_fraction = 0.3
the points are 20 mins apart. 20min/24hrs = 0.013 so i expect the points to be
joined.
i have tried line_gap_fraction 0.9 and - just to be thorough - 1.0 and (being
silly) 10.0 - with
It is much more likely your power supply being the problem. Get a ups to smooth the spikes (dunno if rpi hat does that)⊣ GE ⊢ phone➔brevityOn 6 Jan 2023 12:46 pm, "iams...@gmail.com" wrote:"What happens if you 'pull the plug' on your VP2? Does it keep running? Perhaps the batteries are
i was travelling when it flooded back home (se oz) 6 weeks ago. lots of folk
watch my river depth graph so as the value unexpectedly went off the top of
graph, i updated the y-scale to compensate a few times. someone asked me to
stop increasing it because i was dragging the river level up :-)
perhaps consider the provided ‘fileparse’ driver - see
~weewx/examples/fileparse/readme.txt
> On 29 Aug 2022, at 7:43 pm, Stein Arne Storslett wrote:
>
> Is there a way to only run the weewx database with data through "wee_import"
> without connecting a weather station?
> I.e. just producing
15 years of data, running happily on RPi 4B:
graham@paperbark:/home/weewx/archive $ ls -l weewx.sdb
-rw-r--r-- 1 weewx weewx 175935488 Jul 11 00:55 weewx.sdb
> On 11 Jul 2022, at 12:43 am, Fische Namenlos wrote:
>
> my station is using sqlite database (weewx.sdb) for nearly 5 years, and now -
as tom noted, you need to configure the vp2 console device to 300 secs to get
reports each 5 mins (or change weewx.conf file to 1800 secs if every 30 mins
sufficient)
this would not cause the read errors on the vp2, so is off-topic, but worth
pointing out.
cheers
> On 18 Jun 2022, at 2:23 pm,
not the reported problem, but config error needs to be fixed nonetheless
> On 18 Jun 2022, at 1:14 am, mup...@gmail.com wrote:
>
> Jun 17 08:09:38 weewx-RPi weewx[83743] ERROR weewx.engine: The archive
> interval in the configuration file (300) does not match the station hardware
> interval
s, including batteries, waiting for 10-20 seconds for any capacitance
> to discharge and then power up again. Don't know I would put the batteries in
> reverse though.
>
> Gary
>
> On Wednesday, 25 May 2022 at 21:05:36 UTC+10 Graham Eddy wrote:
> i can power down, pull it apart, pu
>
> Gary
>
> On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:
> data logger is in an envoy
>
>
>> On 25 May 2022, at 7:25 pm, gjr80 > > wrote:
>>
>
>> Can't you set transmitter IDs manually via the console?
>>
&g
data logger is in an envoy
> On 25 May 2022, at 7:25 pm, gjr80 wrote:
>
> Can't you set transmitter IDs manually via the console?
>
> Gary
>
> On Wednesday, 25 May 2022 at 18:18:36 UTC+10 Graham Eddy wrote:
> QC is filtering out the bad values, but weewx server is curr
under [StdQC].
>
> On Wed, 25 May 2022 at 17:45, Graham Eddy <mailto:g...@geddy.au>> wrote:
> my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1)
> has carked it (crushed in tree fall). it exists no more; it is not
> transmitting. my vp2 data logger is
my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1)
has carked it (crushed in tree fall). it exists no more; it is not
transmitting. my vp2 data logger is faithfully reporting a phantom value of
about 150 C (not bad for a river!) every few seconds, how do i disable
1 - 100 of 391 matches
Mail list logo
