Thanks I will definitely try it out.
In the meantime I discovered, in an other weewx instance where the WH65 is
the secondary/extra sensor, which sends 3 to 4 packets per minute, that the
plots daily to monthly only contain the current wind gust after each 60
seconds, while the statistics
Could weewx be configured to generate an e.g. realtime.txt / clientraw.txt
or something like that, and another weewx system to access and read it live
(into its own loop packets/archive records)?
tke...@gmail.com schrieb am Samstag, 5. März 2022 um 18:04:51 UTC+1:
> Nope. Won't work.
I guess, either the station console stopped sending data packets or you
have some network/firewall issue, maybe an auto-update on the router? But
first, have you tried rebooting the display console? Is it online and
actively uploading to ecowitt/wu? Do you use multiple subnetworks or access
That is the section of the weewx.conf:
##
[Interceptor]
# This section is for the network traffic interceptor driver.
# The driver to use:
driver = user.interceptor
# Specify the hardware device to
Gary,
Pardon me for jumping in on this thread, butseeing Weather Display and
clientraw.txt terms grabbed my attention.
I've read through this message, and it lead me to the WeeWx-WD (end of
life) and the WeeWx-Saratoga portions, which I read, and partially
understand.
My main goal is to
for gw1000 dataset, i had been using top and iotop previously to ascertain that
cpu, memory and i/o usage were extremely low, and ps-efl showed it was spending
its time waiting on interrupt. i would usually just conclude it was slow disk
and spending all its time waiting on i/o completion
Hi Gary … Thank you again !!
clientraw.txt location now changed (Thanks!!)
Everything working like a charm … (day max/min outTemp times, dewpoint)
Probably was the ajaxWEEWXwx.js because when I downloaded again and
reinstall it all issues disappeared
For my dashboard at
We have seen this error before and it's very misleading. Despite the
message, it can be caused by problems either locally or remotely.
1. Make sure the FTP username has write permissions on the server for the
path you specified.
2. Make sure the password is correct. Does it include special
Possibly, but why would weewx try to upload a file that is not there on the
weewx system ?
Or is that what that #FTPlast file does ?
https://groups.google.com/g/weewx-user/c/XwQqsslGKfA suggests removing that
file which should cause weewx to upload everything it finds.
On Wednesday, March 9,
kalli...@gmail.com schrieb am Mittwoch, 9. März 2022 um 18:27:38 UTC+1:
> Reason: '550 /home/weewx/public_html/monthhum.png: No such file or
> directory'
>
I would have listened to that error message and guess, the local file is
missing.
--
You received this message because you are
On Wednesday, March 9, 2022 at 9:27:38 AM UTC-8 kalli...@gmail.com wrote:
> Mar 9 17:50:52 kalli-HP-8440p weewx[17683] ERROR weeutil.ftpupload:
> Failed uploading /home/weewx/public_html/monthhum.png to server
> francium.selfhost.de. Reason: '550 /home/weewx/public_html/monthhum.png:
> No
Hi all,
I run Weewx 4.6.2 on my Notebook whit Ubuntu 20.04 it work's fine but the
upload to my Website didn't work to Awekas it work's.
If i run sudo tail -f /var/log/syslog it show me this
Mar 9 17:50:52 kalli-HP-8440p
I don't know much about Python :-) but I see cnopts=pysftp.CnOpts() in the
sftp.py script. This leads down the typical rabbit-hole of Google, grep,
etc. and I find the pysftp project cookbook and added
"cnopts.compression=True" in there. We'll see if it works - the cookbook
says that compression
I updated my 4.4.0 install on a RPi3b to a fresh 64bit RPlite install. So
far everything looks good. I did encounter one small issue. Since this was
a completely clean install I had to set up the start up scripts to launch
WeeWx when the RPi reboots. I install my weewx folder on an NFS
Hi all,
i do have an Ecowitt HP2551 and pulling the data via WeeWX Interceptor
running as ecowitt-client.
Since this morning Weewx Interceptor shows only "empty queue" with
debugging enabled.
local Website is not updated and no data is uploaded to any of the web
services.
Below is my
I have WeeWX 4.7.0, Blechertown 1.3b1 on a Raspberry 3 with the HiveMQ MQTT
broker.
When trying to get MQTT running I am so far that the following is reported
in the syslog:
Mar 9 13:03:58 Wetter-Raspi weewx[12415] INFO weewx.restx: MQTT: Published
record 2022-03-09 13:03:59 CET (1646827439)
1. SFTP can be used with compression (-C option) but I don't know if it is
used or not in Weewx.
2. I tried to compress all my weewx images with tar and/or gzip. At best I
get less than 30 % reduction. May be it is just enough for you.
3. gzip (or better the library behind it) is in fact used
Hi,
I've spent a bit of time today observing your clientraw.txt and Belchertown
web site. On thing I have noted is that your clientraw.txt only updates
approximately every 1.5 to 2.5 minutes. This suggests that loop packets are
not coming in very often and they arrive irregularly. This could
Problem solved - your hint was extremely helpful. Really, the Engine part
was corrupt. My previous post of Engine was an excerpt from my BACKUP copy
of weewx.conf (taken before uninstall). Due to my uninstall the entry
archive_services was completely corrupt into
archive_services = w,
That looks fine. I'm having trouble seeing how such an an error will
truncate a log entry. Nor do I see uninstalling the forecast extension
would cause such a problem. Keeping debug = 1 can you restart WeeWX and
post the WeeWX log from the WeeWX startup through until the error occurs.
One
[Engine]
# The following section specifies which services should be run and in
what order.
[[Services]]
prep_services = weewx.engine.StdTimeSynch
data_services = ,
process_services = weewx.engine.StdConvert,
weewx.engine.StdCalibrate, weewx.engine.StdQC,
Please post a copy of the [Engine] stanza from weewx.conf.
Gary
On Wednesday, 9 March 2022 at 18:19:36 UTC+10 miwa...@googlemail.com wrote:
> Setting debug=1 within weewx.conf enhances the amount of messages, but
> still a crash:
>
> Mär 09 09:14:43 imurr9 python3[859]: weewx[859] INFO
Setting debug=1 within weewx.conf enhances the amount of messages, but
still a crash:
Mär 09 09:14:43 imurr9 python3[859]: weewx[859] INFO weewx.wxservices:
StdWXCalculate will use data binding wx_binding
Mär 09 09:14:43 imurr9 python3[859]: weewx[859] DEBUG weewx.engine:
Finished loading
I've now compared the log messages from the successful start of weewx 4.5.1
with the current one - the difference occures with data binding wx_binding:
Feb 13 09:08:36 imurr9 python3[500]: weewx[500] INFO weewx.engine:
StdConvert target unit is 0x1
Feb 13 09:08:36 imurr9 python3[500]:
24 matches
Mail list logo
