>>
>> Sep 27 16:38:25 machine-name weewx[503476] ERROR weeutil.rsyncupload:
>> rsync error: some files/attrs were not transferred (see previous
>> errors) (code 23) at main.c(1338) [sender=3.2.7]
>>
>> So I guess that it might be. How is the "last up
7]
So I guess that it might be. How is the "last updated" banner generated by
Belchertown?
The website is here:
https://empslocal.ex.ac.uk/uoeweather/
On Wednesday, 23 August 2023 at 18:25:24 UTC+1 Jon B wrote:
> Thanks for the reply. I've just copied the correct key across t
SSH key has
> obviously changed, and currently in .ssh/authorized_keys you probably have
> the old key.
>
> Be sure to copy the correct user's key depending on who's running weewx on
> your system.
> On Tuesday, August 22, 2023 at 7:34:09 PM UTC+2 Jon B wrote:
>
>&g
I recently updated the operating system on which I'm running weewx to
Ubuntu 22.04 and now Rsync to my web server is no longer working. I'm
pretty sure it's because the version of ssh in Ubuntu 22.04 is newer than
the previous version and I've tried various fixes but haven't been able to
solve
Does anyone have any ideas for this? I guess one way may be to read from
the previous day's archive_day entries in the database e.g.
archive_day_rain, although I'm not sure how easy/practical this would be
On Saturday, 7 January 2023 at 02:33:15 UTC Jon B wrote:
> Is it possibl
, Max wind gust:
35 mph, Total rainfall: 12.2 mm
I have it working so that it only tweets once a day at 10am, but giving
instantaneous values is a bit pointless at that tweet frequency
On Saturday, 7 January 2023 at 02:24:33 UTC Jon B wrote:
> I managed this by modifying Axelle's
5 mph, Total rainfall: 12.2 mm
I have it working so that it only tweets once a day at 10am, but giving
instantaneous values is a bit pointless at that tweet frequency
On Saturday, 7 January 2023 at 02:24:33 UTC Jon B wrote:
> I managed this by modifying Axelle's code above in process_rec
I managed this by modifying Axelle's code above in process_record():
ts = time.localtime()
if ts.tm_hour not in (0,6,12,18) or ts.tm_min != 0:
logdbg("This is not hour to tweet: %d" % ts.tm_hour)
return
That should tweet at 00:00, 06:00, 12:00 and 18:00. I'm not sure if this
I didn't and that's done the trick, thanks!
On Friday, 22 July 2022 at 17:12:35 UTC+1 jterr...@gmail.com wrote:
> Did you try to add group_interval = hour in
> the [[Defaults]] [[[Units]]] Groups section of weewx.conf ?
>
> Le 22 juil. 2022 à 16:35, Jon B a é
to make any difference. Perhaps this is
something I need to ask on the Belchertown github page...
On Friday, 22 July 2022 at 12:34:08 UTC+1 jterr...@gmail.com wrote:
> @Jon B
>
> If you are retrieving the values using weewx tags, you can have the daily
> total sunshine duration, in
ntation.
>
> This is corrected now. Sorry !
>
> Le 18 juil. 2022 à 15:43, Jon B a écrit :
>
> Sorry for piggybacking on this conversation, but it seemed like an
> appropriate place to ask this.
>
> I'm trying to install the sunshine duration extension (
> https:/
Sorry for piggybacking on this conversation, but it seemed like an
appropriate place to ask this.
I'm trying to install the sunshine duration extension
(https://github.com/Jterrettaz/sunduration) but I'm getting an error when
trying to create the new database. I've followed the installation
in
something I should do to prevent it?
On Monday, 29 March 2021 at 00:56:09 UTC+1 tke...@gmail.com wrote:
> On Sun, Mar 28, 2021 at 2:36 PM Jon B wrote:
>
>> Ah, thanks, that's done the trick! The data from when the clock changed
>> now appear on my page. Out of interest - while
e you stop weewx before running wee_device.
>
> 2. If you do not have write access to your database, you will have to
> precede the command with "sudo":
>
> *sudo wee_device --dump*
>
>
> -tk
>
> On Sun, Mar 28, 2021 at 12:51 PM Jon B wrote:
>
>>
I also ran into the same problem when the clocks went forward last night.
I've read elsewhere that doing wee_device --dump can solve the issue, but
when I do that I get the error:
weewx.CRCError: Unable to pass CRC16 check while getting data
I also get a bunch of errors like this one:
ERROR we
atabase.
>
> On Mon, Mar 15, 2021 at 5:44 AM Jon B wrote:
>
>> I think I've just tried what you suggested, but it's still picking up the
>> old data. Just to confirm, I've:
>>
>> 1) Stopped weewx
>> 2) sudo wee_device --clear-memory
>>
mory".
>4. If you get no satisfaction, post the logs from the invocation of
>wee_device through its termination.
>
> -tk
>
> On Fri, Mar 12, 2021 at 9:38 AM Jon B wrote:
>
>> Sorry, forgot to add the logs! Here's one example (there are lots of
>> ent
Sorry, forgot to add the logs! Here's one example (there are lots of
entries like this)
INFO weewx.manager: Added record 2020-11-26 08:30:00 GMT (1606379400) to
database 'weewx.sdb'
INFO weewx.manager: Added record 2020-11-26 08:30:00 GMT (1606379400) to
daily summary in 'weewx.sdb'
Seems as t
I've got a new Davis Vantage Pro2 which I've got setup with weewx, using
the Belchertown skin. While I was testing it, I had the station indoors and
so I've got some data from that period. I've installed the station outdoors
now so want to delete the old data, but I can't seem to get rid of it!
19 matches
Mail list logo
