Thanks to all who suggested various solutions or approaches. I perhaps was
overly-specific in the original question, saying I wanted to run a script,
when all along the solution was under my nose: there is an example provided
in the standard distro that does, I think, just what I want -
/usr/sh
Hi,
Pull requests are always welcome :)
Gary
On Thursday, 10 June 2021 at 06:16:08 UTC+10 chv...@gmail.com wrote:
>
> Hi. Congratulations on Weewx.
> It would be quite a detail that in future versions the possibility of
> adding hexadecimal colors with Alpha channel will be included. Currently
Hi. Congratulations on Weewx.
It would be quite a detail that in future versions the possibility of
adding hexadecimal colors with Alpha channel will be included. Currently,
the function to create the image from RGB to RGBA must be modified in
genplot.py and also add in utilities.py the conditi
@michael: No, that is not what I am saying. In fact, the converse is
likely true: that it ALSO stopped recording data in the database, as there
are no more messages of the sort "Added record ... to database" INFO level
messages in my logs once this occurred, as can be seen in my original post
@JRJ: So, you're saying that WeeWX stopped generating reports but data
still was recorded in the database, correct?
If yes, it seems unlikely that it's a driver issue and more on the weewx
engine's side.
cub...@gmail.com schrieb am Mittwoch, 9. Juni 2021 um 20:22:01 UTC+2:
> @chris: yes, indee
Jay:
I tried 'sudo service weewx restart', and it did NOT fix the problem. I
rebooted the machine, and it worked
great. Hopefully, now that I've got debug enabled, if it happens again,
I can debug it.
Thank you for sharing your WMII driver for Python 3!
Chris Shaker
On 6/9/2021 11:20 AM, Ja
@chris: yes, indeed, the issue on my system was that weewx stopped
producing reports (and also there were no reporting-related messages in the
log. I do am now running with debug set to 1 in the config.
JRJ
On Wednesday, June 9, 2021 at 12:09:08 PM UTC-5 cjsh...@gmail.com wrote:
> JRJ:
>
> A
@Chris: Version 3 weewx with my wmII was rock solid. I didn't run the
wmII more than a day under version 4, so I can't speak to that. I had no
issues restarting weewx - didn't need a reboot.
NOTE: systemd behavior, being what it is, if a service crashes, it still
is not STOPPED, and it won'
My weewx (ver 4.5.1-1) stopped generating reports at 4:00 AM, with no error
messages.
I've now set debug=1, and turned off my crontab reboot, to try to collect
some data when/if
it happens again.
Using Davis WMII, serial port, on RPi4 running Raspbian buster, fully up to
date. I removed
Python
I have set debug to 1, and disabled the crontab reboot, to see if I can
collect some debug data.
Chris Shaker
On Wednesday, June 9, 2021 at 10:09:08 AM UTC-7 Christopher Shaker wrote:
> JRJ:
>
> Are you saying that weewx stopped generating reports? My weewx stopped
> generating reports, with n
JRJ:
Are you saying that weewx stopped generating reports? My weewx stopped
generating reports, with no error messages, at 4:00 AM. Restarting service
weewx did not fix it. Rebooting my raspberry pi DID fix it. So, I added a
crontab entry to reboot my raspberry pi each morning:
5 4 * * * /sbin/
@michael: It should not be related to the SCP upload, which continues even
after weewx has gone "night night". It is running from a cron, not under
weewx. It merely copies the generated HTML/graphics up to another
machine. It runs every 17 minutes. If it were, say, locking up a file
and
@vince: I worked in IT for over 36 years, and with UNIX and "C" since
1976. I know what I am doing. There can be lots of reasons why an issue
appears on one machine vs. another, often related to the timing
relationship between events. Yes, it occurred to me that logging at the
DEBUG level i
13 matches
Mail list logo
