If clearing the browser cache works, as you imply it does, the problem
would appear to be that, somewhere in the chain between you and the site,
an assumption is being propagated that the data is stable (for more than
the relatively short periods for which you want it to be). Have you tried
e original installation, but that was over 3 years ago and I
don't remember. Is there a way of identifying the original install method?
Thanks again,
Peter T.
On Friday, April 12, 2024 at 11:05:18 AM UTC+10 Tom Keffer wrote:
> You can accomplish the same thing by using the old v4 utilities
> <ht
uot; I'm running old software -
Weewx 4.5.1 under Raspbian 10. But maybe it's "broke" - do I need to
update to access weectl device?
Thanks,
Peter T.
On Friday, April 12, 2024 at 1:35:19 AM UTC+10 Tom Keffer wrote:
> Odds are it's a problem with corrupted memory
>
. The system updates every 10 minutes and you can see two cycles
of that at the end of the log. That same pattern continues indefinitely,
but the FTP upload is always of the same old data from a couple of days ago.
I'll be most grateful for any advice.
Thanks,
Peter T.
--
You received
matthew wall wrote:
> On Wednesday, February 21, 2024 at 6:50:52 PM UTC-5 Peter Fletcher wrote:
>
> There were essentially no issues with the 4.x->5.x update. What I wasn't
> prepared for was an update *from 5.01 to 5.02* clobbering everything *that
> was previously working in 5.
I'm not ignoring you, but today has been a bit busy! I will try to write
something up and post it later today or tomorrow.
On Wednesday, February 21, 2024 at 7:13:08 PM UTC-5 matthew wall wrote:
> On Wednesday, February 21, 2024 at 6:50:52 PM UTC-5 Peter Fletcher wrote:
>
> T
ur old version basically forever if
> you were so inclined.
>
> But to reply
>
> On Wednesday, February 21, 2024 at 2:18:49 PM UTC-8 Peter Fletcher wrote:
>
> That was one of the *many* permissions-related problems caused by the
> update! Changing the registered user o
, 2024 at 4:02:39 PM UTC-5 matthew wall wrote:
> On Wednesday, February 21, 2024 at 3:54:31 PM UTC-5 Peter Fletcher wrote:
>
> It turns out that there were some other privilege problems, resulting from
> the 5.02 update, but I managed to get journalctl to show me the detailed
> er
and
they allowed me to identify and fix the rest. I think that everything is
now really sorted, but a nominally minor utility update, liable to be
included in a routine apt full-upgrade, should not create this big a mess!
On Wednesday, February 21, 2024 at 1:47:30 PM UTC-5 Peter Fletcher wrote
the permissions error and logged it.
>
>
>
> On Tue, Feb 20, 2024 at 7:21 PM 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> That is the entire log from shortly before the update. I am guessing that
>> the known bug in crt.py results in t
20:30:00 was downloaded from the logger
> at 20:32:22. I would expect the next record to be processed at 20:35:16 or
> so. Did you terminate the program? Is there something later in the log?
>
> On Tue, Feb 20, 2024 at 5:41 PM 'Peter Fletcher' via weewx-user <
> weewx...@googleg
oblem, we will need to see more of the log.
>
> On Tue, Feb 20, 2024 at 4:14 PM 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I have had weewx 4.x (apt installed) running happily on my Pi 3b for
>> years. A month ago, since 5.0 seemed to be
I have had weewx 4.x (apt installed) running happily on my Pi 3b for years.
A month ago, since 5.0 seemed to be stable, I allowed the upgrade to the
then current release of 5.0. Since there had been a few concerns raised
about it, I did a complete image backup of the Pi before allowing the
It is very unlikely to be the Pi power supply if the Pi itself is not
flagging up power problems.
On Friday, February 2, 2024 at 9:23:04 PM UTC-5 Joe wrote:
> Its a standard PI4. No external USB devices are connected except for the
> Vantage data logger.
> There are coils on both ends of the
I use the SolarEdge cloud API to download and save my PV production data on
my Raspberry Pi, though I actually save it to a dedicated sqlite database
rather than incorporating it into weewx's records. I haven't had any
problems with it and download data every 5 minutes during the solar day
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
Hello, I thought people here might be interested in a review of the
serial-to-Ethernet adaptor I recently added to our Weewx configuration.
We started with a Davis Vantage Pro+ in 2003, and upgraded to Vantage Pro2+
in 2013. We've been using Weewx since 2013 with the Davis serial
interface,
gregations:
> https://github.com/weewx/weewx/wiki/xtypes#calculating-aggregates
>
>
> On Sat, Jun 3, 2023 at 4:39 PM 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> For reasons discussed elsewhere, I have a user service which saves nulls.
>>
html/weewx folder content
>
> (for a /home/weewx installation the command would be:
> sudo chmod -R 755 /home/weewx/public_html )
> On 18.05.2023 23:48, Peter Hurn wrote:
>
> Hello,
>
> I am trying to install Weewx fresh on a Raspberry PI, running Debian
> Bullseye,
> I wo
olving the issue,
any thoughts?
Kind regards,
Peter.
--
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 weewx-user+unsubscr...@googlegroups.com.
To view
t
> completely without problems - there are issues (I think) with server-side
> caching, but, in general, it works ok.
>
> Hth
>
> Geoff
>
> On Thursday, 6 April 2023 at 01:28:25 UTC+1 Tom Keffer wrote:
>
>> Are you using secure_ftp?
>>
>> On Wed, Apr 5
Hi! I've been using weewx on a raspberrypi for many years including
uploading reports to an account on a cloud provider (1and1.com) to post
standard reports on my personal webpage.About 2 weeks ago I started
having problems with getting the reports uploaded to the cloud via the
weewx
I would endorse the 'if it aint broke, don't replace it' approach. I have a
1 GB 3B running the latest version of weewx and a number of other services
for home control, and there would still be plenty of spare capacity if I
could think of something else I wanted to do with it. An 8GB 4B would
I would endorse the 'if it aint broke, don't replace it' approach. I have a
1 GB 2B running the latest version of weewx and a number of other services
for home control, and there would still be plenty of spare capacity if I
could think of something else I wanted to do with it. An 8GB 4B would
Thanks Gary. I did have it there but as I said it was something I had done.
I have been creating backups of the config as I have been altering things
and used the incorrect file. Looks like its showing a bit of data now so I
will keep watching.
Many thanks
On Thursday, March 23, 2023 at
ne option is
>>> not covered in the readme, but it is identical to running the driver
>>> directly with the --test-driver command line option you just need to
>>> substitute the --live-data command line option. You can also use the
>>> --help command line optio
cwop page after I went home it
>> shows no rain either and that gets fed from Weewx. The wunderground page
>> that gets fed directly from the GW2000 shows the rain.
>>
>> I am happy to post any logs etc if that helps or look at anything if you
>> can point me in that direc
And a link to the Weewx webpages hosted on a different server uploaded via
ftp https://weewx.secs.net.au/index.html
On Thursday, March 23, 2023 at 6:40:27 AM UTC+11 Peter Peter wrote:
> Hey again Garry. I am trying to work out if this is a weewx or weather34
> issue. I can see as men
that gets fed directly from the GW2000 shows the rain.
I am happy to post any logs etc if that helps or look at anything if you
can point me in that direction.
On Wednesday, March 22, 2023 at 12:17:58 PM UTC+11 Peter Peter wrote:
> Thanks Gary. I was trying to beat you back here but ala
just noticed
that https://www.pwsweather.com/station/pws/goulbnswgrs isnt showing the
rain. That gets updated from Weewx. Wunderground gets updated from the
gw2000 and it shows the rain.. I fully expect its something I have done
On Wednesday, March 22, 2023 at 6:52:52 PM UTC+11 Peter Peter
my iPad.
>
> On 22 Mar 2023, at 02:10, Peter Peter wrote:
>
> As a side note I also miss the solar radiation reading as well (but get
> the UV) so I am thinking as per the reading of other conversations that it
> has something to do with real time files
>
>
>
> On
As a side note I also miss the solar radiation reading as well (but get the
UV) so I am thinking as per the reading of other conversations that it has
something to do with real time files
On Wednesday, March 22, 2023 at 1:08:36 PM UTC+11 Peter Peter wrote:
> First question: Is this the corr
First question: Is this the correct place/forum/group for Weather34?
if yes see next
Ok all and thanks to Garry we seem to be collecting data via Weewx
including rain butits not showing up in the Weather34 skin. I have been
searching around in the weewx conf file etc and looked at various
Thanks Gary. I was trying to beat you back here but alas I didnt. I did a
search on the gw2000 and found some posts and like you suggested here ran
Weewx directly and can see both the rain in the loop and rec so that parts
seems ok. I will do a bit more research and see what I can find. I have
Hey all.
I have been running Weewx together with my Ecowitt and using the GW1000
setup. My base unit is actually a GW2000C_V2.2.3C
When I initially set it up I ran it in simulator mode and all seemed ok
I have been waiting for rain and we have some today but it appears Weewx
isnt picking up
ssages in quarantine, so I'm not sure
>> what I can do.
>>
>> Were you posting from email, or directly to the weewx-development website?
>>
>> On Sat, Mar 11, 2023 at 5:59 AM 'Peter Fletcher' via weewx-user <
>> weewx...@googlegroups.com> wrote:
&g
The last message in that group is from February 22, and I submitted two
messages to it a couple of days ago, which have not appeared. I was not a
member of that group until shortly before I submitted the first message,
but I would not have expected this long a moderation delay.
--
You
I'm not 100% clear what you are trying to do here. I don't think that you
can actually add data to the loop packet 'on the fly'. I am also not sure
why you would want to do *anything* with tide height every loop. It is
self-evidently a rather slow-changing datum, and could easily be dealt with
I'm not 100% clear what you are trying to do here. I don't think that you
can actually add data to the loop packet 'on the fly'. What you can
certainly do is write a service that is triggered every time a loop packet
is received and processed which either gets data from somewhere (?MQTT) and
No, I'm aware of that. Given that I've got the site working in a very
non-purist way, I shall let if get on with it for the time being as I've
got other things which are higher priority at the moment. When I come back
to tackle it again, I shall certainly provide much more info.
On Wednesday,
I'm interested in this topic.
I've tried and tried to get Weewx to write files to my server, firstly via
FTP, with no success, (Ionos helpdesk said, after a few calls that FTP had
been disabled on my server - it came back with an error 550 - but different
guys said slightly conflicting things,
the
problem.
On Tuesday, December 20, 2022 at 6:48:54 PM UTC-5 tke...@gmail.com wrote:
> This is set by the environment variable LANG. Double check your's.
>
> echo $LANG
>
> If you're in the US, it should read something like "en_US.UTF-8".
>
> On Tue, Dec 20, 2022 at 2:4
I have, for some years, used the Seasons skin as a base for two of the
skins I employ for my weewx setup. I have just noticed that the date part
of the datestamp at the top left of the main page is in (what I think of
as) British format - DD/MM/. I am sure that it has always been that way
Hi Gary,
Thanks for the quick response. Your answer makes complete sense, but
unfortunately it doesn't seem to work. Even after I have set the rainRate
fields to NULL, wee_database --calc-missing just seems to refill the
rainRate with 0.0.
I've checked that I have definitely set the rain
I recently (25/08/2022) had to delete a 6 hour section of data from my
database as the rain accumulation data contained in the LOOP packets from
that period were incorrect. I refilled the database using the correct rain
accumulation data from ARCHIVE packets over that 6 hours, and everything
It sounds as if your weewx/solar Pi installation was one or (probably) two
versions behind the current ('Bullseye') version of the Pi's Debian-based
OS. While it may be possible to upgrade the OS 'around' the existing
installed programs, it would take a lot more Linux knowledge than I am
, or rename columns.
On Monday, July 18, 2022 at 10:35:03 AM UTC-4 jterr...@gmail.com wrote:
> @Peter : if one want to update the database using wee_database, the new
> updated schema with the new field is needed. Otherwise, in case of a
> manual update of the database structure, the n
FWIW, weewx does work fine with a Vantage Pro 2 and a Meteo-Pi under
bullseye.
On Thursday, July 7, 2022 at 10:43:40 AM UTC-4 taroka...@gmail.com wrote:
> Thank you Peter and Vince,
>
> An update: We got it to work!
>
> I did three things differently:
> 1) since I am using
@Jacques: I initially had the same error (or a very similar one) as Jon B
and had to comment out that last line. I had already manually added the
sunshine_time field (as well as some others, previously) to my weewx
database, so it didn't seem to be necessary or useful. My installation also
did
for the archive values automatically corrects for 'short' archive
intervals, and I would handle longer interruptions (if there were any) by
running my update code on the database after the interruption.
On Saturday, July 16, 2022 at 11:34:07 AM UTC-4 jterr...@gmail.com wrote:
> Peter,
>
&
ot; % (mod.__name__, part,
> module_class))
> Jul 16 17:05:15 Wetter weewx[3755]: AttributeError: Module
> 'user.radiationhours' has no attribute 'RadiationHours' when searching for
> 'user.radiationhours.RadiationHours'
> Jul 16 17:05:15 Wetter weewx[3755]: Exiti
data logger?
> Can you use it to fill up past values? So e.g. from the year 2019 or
> something?
>
> Best regards
> Stefan
>
> Peter Fletcher schrieb am Freitag, 1. Juli 2022 um 19:37:54 UTC+2:
>
>> I'm sure you are right about the triggering circumstances. The
, C++ as well as Linux and
networking
And thanks again for your help
Peter
On Wed, 13 Jul 2022, 8:36 am Rainer Lang, wrote:
> Now, this depends on various factors:
> a) what does "modestly priced" mean for you ? (price range - upper limit)
> b) what do you mean exactl
, more modern, setups
that permit this would be welcome.
Peter
On Wed, 13 Jul 2022, 07:37 Rainer Lang, wrote:
> This looks like a clone of the old Fine Offset WH1080 weather station
> which is no longer sold by Ecowitt due to old technology.
> Console connectivity is USB only
Certainly looks like it might be but would appreciate confirmation.
Full skinny here:
rds are not automatically regenerated. Did you
> delete everything before running wee_reports?
>
> On Sat, Jul 2, 2022 at 2:46 PM 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I have recently added a 'Sunshine minutes/hours' field to weewx's
>&
Thanks!
On Saturday, July 2, 2022 at 5:38:23 PM UTC-4 matthew wall wrote:
> On Saturday, July 2, 2022 at 4:14:37 PM UTC-4 Peter Fletcher wrote:
>
>> The installation instructions add 'http://weewx.com/apt/python3 *buster*
>> InRelease' to apt's list of sources f
I have recently added a 'Sunshine minutes/hours' field to weewx's database
- calculated on the fly from measured solar radiation. Since I have
radiation records going back a couple of years, I wanted to backfill the
sunshine time records to display on longer term reports. After a couple of
The installation instructions add 'http://weewx.com/apt/python3 *buster*
InRelease' to apt's list of sources for Debian installs, and this works.
However, Debian and Raspbian have been up to bullseye for long enough that
I have recently upgraded my main Pi (!) and weewx appears to run perfectly
as just below zero and that the measured
> radiation was just higher than 20 W/m2
>
> Le 1 juil. 2022 à 16:19, 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> a écrit :
>
> Something like that is obviously needed. I don't know how my copy of the
> code omit
son) * cos((pi /
> 180) * angle_horaire)) * (180 / pi)
> If hauteur_soleil > 0:
>
> seuil = (0.73 + 0.06 * cos((pi / 180) * 360 * dayofyear / 365)) * 1080
> * pow(
> (sin(pi / 180) * hauteur_soleil), 1.25) * coeff
> else :
> seuil = 0
> return seuil
>
&
to try to understand.
>
>
>
> Le 30 juin 2022 à 19:51, 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> a écrit :
>
> It did as it seems you predicted - passed 1592614800 and stopped at
> 1632611100. You obviously have a clue as to what is going on. Please
t;SELECT
> dateTime, Radiation from archive where dateTime <> 1592614500", will the
> script stop at 1592614800 ( the next dateTime) or will it continue and stop
> at 1632611100 ?
>
> Le 30 juin 2022 à 14:34, 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.co
the error ?
>
>
>
> Le mercredi 29 juin 2022 à 23:23:16 UTC+2, Peter Fletcher a écrit :
>
>> Have you had any odd weewx errors or crashes related to the sunshine
>> calculations? I ask because I hadn't, but I decided to try to 'backfill' my
>> database with sunshine tim
h
> loop packet, the total CPU utilization of python3 is about 0.75%
> With mqtt and without calculation of sunshine threshold : 0.5% of total
> CPU.
>
> So one can estimate that 0.25 % of total CPU is needed for the calculation
> of the threshold value for each LOOP packet.
ate a service, one of the parameters is the engine
> instance:
>
> def __init__(self, engine, config_dict):
>
> The archive interval used by the engine can be obtained from it as
>
> engine.console.archive_interval
>
> -tk
>
>
>
> On Fri, Jun 10, 2022 at 11:07 AM
f the VP2 compared
> to the LOOP interval, I decided to round up the sunshine duration to full
> minutes
>
> Le 10 juin 2022 à 15:52, 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> a écrit :
>
> Thanks to all! Granted that you are most likely to need to know the
Thanks to all! Granted that you are most likely to need to know the archive
interval in the context of an archive interrupt service, where it is easily
available and the returned value is reliable, it would be nice if the
actual working value (rather than just the value from weewx.conf) were
on hardware supports data logging then the archive
> interval
> # will be downloaded from the station. Otherwise, specify it (in
> seconds).
> archive_interval = 300 #example
>
> Am 09.06.2022 um 21:40 schrieb 'Peter Fletcher' via weewx-user:
>
> This may seem like a ve
Approaching the search from a different angle, I have now found that,
within an archive event handler (which is where I needed it), you can get
it from the event record as ['interval'], but is there another and/or more
general way?
On Thursday, June 9, 2022 at 3:40:03 PM UTC-4 Peter Fletcher
values of the LOOP packet are the same for at least 50 seconds.!
>
> Le 5 juin 2022 à 18:02, 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> a écrit :
>
> I chose to average the LOOP radiation readings and only to do the
> threshold calculation and make the su
This may seem like a very stupid question, but I have not been able to
google an answer. Is there a method or parameter that is accessible from
within (e.g.) a user extension which gives the current archive interval?
--
You received this message because you are subscribed to the Google Groups
nyway the solar
> radiation values of the LOOP packet are the same for at least 50 seconds.!
>
> Le 5 juin 2022 à 18:02, 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> a écrit :
>
> I chose to average the LOOP radiation readings and only to do the
> thr
e archive period.
> Le vendredi 3 juin 2022 à 21:59:36 UTC+2, Peter Fletcher a écrit :
>
>> That makes some sense when you are getting data from an 'external'
>> sensor, though there are (IMHO) simpler ways of doing it. weewx already has
>> access to the LOOP radiation d
se option 'unit' in skin.conf.
>
> [ImageGenerator]
> ...
> [[week_images]]
> ...
> [[[week_sunshine]]]
> unit = hour
> sunshine
>
> All documented in the Customizing Guide
> <http://www.weewx.com/docs/customizing.htm>.
>
> On
As noted in a different thread, I am working on a small extension to
calculate and store sunshine time (time when the sun is out, rather than
covered by clouds). I am saving the number of *minutes* of sunshine during
the archive period in each archive record. Sunshine minutes are fine for
That makes some sense when you are getting data from an 'external' sensor,
though there are (IMHO) simpler ways of doing it. weewx already has access
to the LOOP radiation data from the VP2, so handling the processing and
data storage within weewx makes more sense to me in this case.
On
sunshine is only recorded every 10 minutes. Not
> everything in between. If the solar value is then high enough at the
> measuring point, the full 10 minutes are registered as sunshine. With a
> minute interval, this could be obtained even more precisely
>
> Thank you for your feedback
>
>
han the default average). Then at the end of the
> archive interval, multiply the sum by the loop interval. The result will be
> the amount of time the sensor returned 1 during the archive interval, which
> should be the amount of time the sun was out.
>
>
>
> On Thu, Jun 2,
I think that this is a sensor issue. If the sensor returns only a binary
(sun/no sun) value, which appears to be the case for this computed
'sensor', then sampling it every 10 minutes will give results with a
granularity of 10 minutes, as the OP describes; if the sensor returns the
minutes (or
ater leak, soil humidity,
> temperature, lightning, etc.
> And I like to add some to my web page.
>
> sreda, 1. junij 2022 ob 22:00:29 UTC+2 je oseba Peter Fletcher napisala:
>
>> I handle the public/private page issue by having an additional skin
>> enabled with
I handle the public/private page issue by having an additional skin enabled
with the sensors I want to be publicly visible pointing at a local
directory and then using weewx's FTP pseudo-report option to upload the
contents of that directory to a folder on (and linked to) my public
website. I
is already very old and there is no support from
>> the manufacturer, but I can tap the harvest data via serial interface.
>> Let's see which solution brings me the faster success.
>>
>> kk44...@gmail.com schrieb am Freitag, 7. Januar 2022 um 15:56:14 UTC+1:
>>
>
You have at least two options. One is to keep your detailed solar records
separately and pull the data items you want to display into either new
fields or 'spare' fields in the weewx database. The other, of course, is to
add all the fields you need to the weewx database. AFAIK, there is no
Highly unlikely! Even if the weewx code and its associated libraries do not
use Python functionalities that MicroPython doesn't support, and you can
deal with the interfacing, there probably isn't enough memory space to fit
the interpreter and all the code and libraries on the device,
Dear group, once again I put my hope to your competence and willingness to
help.
I want to publish my weather data to my web page in the Seasons skin format
using the FTP transfer method in weewx.conf. This seems to work only with
skin=FTP which of course give the FTP skin look at the webpage.
Thanks a lot Gary! The header part worked perfectly. I´ll try the plots
tomorrow
On Tuesday, May 4, 2021 at 10:44:10 PM UTC+2 gjr80 wrote:
> Hi,
>
> There are a few ways to handle the date-time in the header. Basically the
> options come down to changing the format used by the tag used to
This should be a simple config question but I have failed. How can I change
the date and time format from something like 05/04/2021 09:15:00 PM to
2021-05-04 21:15 in the header of the Seasons skin as well as in the day
plots?
Thanks for any support to solve this minor but irritating issue.
h another
> weewx "driver", before I spent a lot of time on it.
>
> Thanks for the pointer to service vs. driver configuration!
> I'll read through it.
> On Tuesday, May 4, 2021 at 11:33:07 AM UTC-5 Greg Troxel wrote:
>
>>
>> Eric Koester writes:
>>
>&
Check this: https://github.com/bellrichm/WeeWX-MQTTSubscribe
On Tuesday, May 4, 2021 at 12:31:55 AM UTC+2 eric.k...@gmail.com wrote:
> I'm currently reading data into weewx using an Acurite Atlas, an RTL-SDR,
> rtl_433, and weewx-sdr.
>
> I'd like to import barometric pressure sensor data into
to replace the weather station; the hardware outside is fine, but the
the convoluted way it reports to WU and CWOP are a headache I don't want,
especially if it's turning into a monthly circus.
On Friday, April 23, 2021 at 11:24:24 PM UTC-4 Peter Dougherty wrote:
> Last month (Mar. 22
Last month (Mar. 22) I was experiencing upload problems to CWOP. Today a
similar (worse) problem. Nothing was done to the Pi since the end of last
month's troubles. It just stopped uploading to both CWOP and WU about an
hour ago.
I've tried unplugging the console, restarting the process,
I have used a variety of loggers with my Davis VP 2+ - for many years
directly connected to Windows systems; subsequently (but also for 2-3 years
now) to a Raspberry Pi. I can say without doubt that the Meteo-Pi, once set
up, has given me fewer problems than the Davis alternatives. It also
Yes, that is what I did with the more extensively modified version of
Seasons I use for my public site, but the version I use locally just had
some minor tweaks, so I didn't change the name, and apt appears to be
handling it as I would wish and as mwall describes (though I have never
touched
), and I don't see anything else.
On Friday, April 2, 2021 at 4:59:46 PM UTC-4 tke...@gmail.com wrote:
> Peter: are you using a Debian or Redhat system?
>
> Do you have the output from the session?
>
> On Fri, Apr 2, 2021 at 11:56 AM 'Peter Fletcher' via weewx-user <
> weewx...@go
What has changed in the Seasons skin? When I apt upgraded my Pi today, I
got the usual "What do you want to do about weewx.conf?" prompt (which I
answered, as usual, by opting to keep my existing version), but I also got
a similar prompt for the Seasons skin.conf. I have made some minor
://www.findu.com/cgi-bin/raw.cgi?call=W2IRT
On Mar 22, 2021, at 7:03 PM, Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:
Sorry to be so daft, but I honestly could not understand this. I’m a
“set-it-and-forget-it” user so I’m not up on all the terminology, I’m afraid. I
last did an
cycle.
-tk
On Mon, Mar 22, 2021 at 6:54 PM Peter Dougherty mailto:pjdoughe...@gmail.com> > wrote:
I did use the - - dump command. But (a) I don’t know where it put the data,
(b) how to recover it, or (c) does it need to even be recovered now?
- pjd
From: weewx-user@googlegrou
I did use the - - dump command. But (a) I don’t know where it put the data,
(b) how to recover it, or (c) does it need to even be recovered now?
- pjd
From: weewx-user@googlegroups.com On Behalf Of
Tom Keffer
Sent: Monday, March 22, 2021 9:30 PM
To: weewx-user
Subject: Re:
So…a tiny bit of progress (maybe??)
I stopped the Vantage console for a few minutes and pulled out the batteries.
Restarted it, then unplugged the RPi and reconnected it. It seems to have
started adding the missing data and I’m seeing “restx” messages again, but
after 10 minutes, nothing seems
1 - 100 of 264 matches
Mail list logo
