Re: [weewx-user] Skin with webcam?

Here is my integration with Belchertown: https://www.trebacz.com/weather/ happy to share whatever helps On Friday, April 2, 2021 at 4:57:09 AM UTC-7 DaveStLou wrote: > I 'm no expert by any means. I usually just try things I find here: > w3school's > HTML Tutorial

Re: [weewx-user] Re: Version 4.5.0 released

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

Re: [weewx-user] Re: which skin is aborting on me ?

*Think I found a bug...* *No way it was my edits...* *Oops, yup it was me...* * - weewx-user bug report haiku* Found it. What was happening is I was trying to generate some images from a one-time test of the 'historical' extension that I disabled a long time ago, but neglected to comment

Re: [weewx-user] Re: which skin is aborting on me ?

On Friday, April 2, 2021 at 3:06:25 PM UTC-7 gjr80 wrote: > Tracking down the skin should be easy with debug = 1, you simply look for > the line containing: > > Found configuration file /home/weewx/skins/xx/skin.conf for report > 'y' > > immediately before the error, the problem skin

Re: [weewx-user] Re: which skin is aborting on me ?

Tracking down the skin should be easy with debug = 1, you simply look for the line containing: Found configuration file /home/weewx/skins/xx/skin.conf for report 'y' immediately before the error, the problem skin will be xx and the problem report (in weewx.conf) will be y. In

[weewx-user] Re: which skin is aborting on me ?

I'm leaning that way, but might be a custom extension I cooked up years ago. I'm bleeding through reenabling them one by one to figure it out. My more general question is whether there's a way to log which skin was being processed when an abort like this happened. That might be a nice

[weewx-user] Re: which skin is aborting on me ?

Or alternatively, the report in weewx.conf immediately before lastrain. Gary On Saturday, 3 April 2021 at 07:55:19 UTC+10 gjr80 wrote: > Perhaps vds-local? > > Gary > > On Saturday, 3 April 2021 at 07:08:17 UTC+10 vince wrote: > >> I notice in my syslog that I have one skin aborting every run:

Re: [weewx-user] Re: Version 4.5.0 released

FWIW, it's more work but a generally better way to approach essentially forking things in core weewx is to create your own skin based on some starting point, disable the skin that comes with weewx, and enable your custom skin that has a different name. Bonus points if you make your custom

[weewx-user] Re: which skin is aborting on me ?

Perhaps vds-local? Gary On Saturday, 3 April 2021 at 07:08:17 UTC+10 vince wrote: > I notice in my syslog that I have one skin aborting every run: > > Apr 2 14:00:29 debian weewx[8936] INFO weewx.cheetahgenerator: Generated > 9 files for report vds-local in 7.99 seconds > Apr 2 14:00:29

Re: [weewx-user] Re: Version 4.5.0 released

peter, the redhat and debian packages define a set of files as 'configuration' files. these are files that are distributed in weewx, and any of those files that are modified will result in a "something changed, do you want to keep your changes or accept the new version" prompt. nominally

Re: [weewx-user] 'systemctl stop' sends SIGKILL not SIGTERM on RPi

KILL is definitely not desirable. i'm debugging this now on centos with systemd, weewx, and rtl_433. for example, the sdr driver spawns the rtl_433 command, and if you kill weewx, you end up with a rogue process, and the next time you start weewx, weewx will fail. as another example, if you

Re: [weewx-user] Re: Version 4.5.0 released

I'm using the regular Raspberry Pi version of Debian, and I am afraid that I don't have a copy of the output of the apt session. However, diffing my Seasons skin.conf with the new version saved as skin.conf.dpkg-dist shows (apart from my modifications, of course) changes in the predefined

[weewx-user] which skin is aborting on me ?

I notice in my syslog that I have one skin aborting every run: Apr 2 14:00:29 debian weewx[8936] INFO weewx.cheetahgenerator: Generated 9 files for report vds-local in 7.99 seconds Apr 2 14:00:29 debian weewx[8936] INFO weewx.reportengine: Copied 0 files to /home/weewx/public_html Apr 2

Re: [weewx-user] Re: Version 4.5.0 released

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-user@googlegroups.com> wrote: > What has changed in the Seasons skin? When I apt upgraded my Pi today, I > got the usual "What do you

Re: [weewx-user] Re: Version 4.5.0 released

Version 4.5.1 out. My apologies. On Fri, Apr 2, 2021 at 1:12 PM Tom Keffer wrote: > My mistake. I knew there was a reason why we didn't transition the old > wview schema to the new V4 style! > > I should have a dot-dot release out later today. > > -tk > > On Fri, Apr 2, 2021 at 12:14 PM Mks Mk

Re: [weewx-user] Re: Version 4.5.0 released

My mistake. I knew there was a reason why we didn't transition the old wview schema to the new V4 style! I should have a dot-dot release out later today. -tk On Fri, Apr 2, 2021 at 12:14 PM Mks Mk wrote: > the upgrade to 4.5 from 4.4 failed and weewx is broken please advice > used these

[weewx-user] Re: Version 4.5.0 released

the upgrade to 4.5 from 4.4 failed and weewx is broken please advice used these commands for upgrade sudo apt update apt list --upgradable (4.5 was showing) sudo apt full-upgrade then I answered "N" to the upgrade select to keep my old files Apr 2 21:31:49 raspberrypi systemd[1]: Starting LSB:

[weewx-user] Re: Version 4.5.0 released

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

Re: [weewx-user] PM2 - Process Manager 2 and WeeWX

You of course are correct! Adding a USB dongle would also mean adding a USB hub so a nice “small box with only Davis console connection” becomes more grand. Not impossible but not something I want to do. Regards, Garry Lockyer C: +1.250.689.0686 E: ga...@lockyer.ca > On Apr 2, 2021, at

Re: [weewx-user] PM2 - Process Manager 2 and WeeWX

Off on a tangent... Not impossible to use wired internet with a Pi Zero. You just need a USB to Ethernet dongle. https://www.amazon.com/AmazonBasics-USB-Ethernet-Network-Adapter/dp/B00M77HLII I don't have this one exactly, but a similar one. For my application I needed a USB adaptor from the

Re: [weewx-user] PM2 - Process Manager 2 and WeeWX

In the absence of a detailed description of your setup, what problem you are trying to solve, and why you think you need to touch weewx at all after it starts up, there's nothing we can do to help you here.You're jumping to a conclusion that you have to touch something, but you've given us

Re: [weewx-user] PM2 - Process Manager 2 and WeeWX

Thanks for the advice. I will forego using PM2, or any other process manager, at this time, and give "netmon.sh" a try. But! Re: "if you can figure out a way to tell when (if) you need to touch weewx at all." that's why I was hoping to use something like PM2 'casue it seems to me they

Re: [weewx-user] PM2 - Process Manager 2 and WeeWX

Sorry for late response. Using a RPi Zero W so no chance to use wire. In fact, virtually no chance to make any changes to network at remote site. Regards, Garry On Sunday, March 28, 2021 at 1:03:52 PM UTC-7 tomn...@frontier.com wrote: > Hi Gary, esp. in a remote location like that, can you

Re: [weewx-user] Re: Version 4.5.0 released

Upgrading using "weewx-master.zip" appears to have worked perfectly! Thanks Tom! On Friday, April 2, 2021 at 10:03:53 AM UTC-7 tke...@gmail.com wrote: > My apologies. Forgot that little step! > > On Fri, Apr 2, 2021 at 9:41 AM Tarmo wrote: > >> I'm sure, it is just temporarily in >>

Re: [weewx-user] Re: Version 4.5.0 released

My apologies. Forgot that little step! On Fri, Apr 2, 2021 at 9:41 AM Tarmo wrote: > I'm sure, it is just temporarily in > weewx.com/downloads/development_versions/weewx-4.5.0.tar.gz > > On Friday, April 2, 2021 at 6:11:42 PM UTC+3 tke...@gmail.com wrote: > >> *Change log* >> >> The utility

[weewx-user] Re: Version 4.5.0 released

Does a "get code" from github, which gets you "weewx-master.zip", get the exact same package as weewx.com/downloads/development_versions/weewx-4.5.0.tar.gz? Going to try using "weewx-master.zip" . . . Regards, Garry On Friday, April 2, 2021 at 9:41:28 AM UTC-7 Tarmo wrote: > I'm sure, it

[weewx-user] Re: Version 4.5.0 released

I'm sure, it is just temporarily in weewx.com/downloads/development_versions/weewx-4.5.0.tar.gz On Friday, April 2, 2021 at 6:11:42 PM UTC+3 tke...@gmail.com wrote: > *Change log* > > The utility wee_database has new options --add-column, --rename-column, and > --drop-columns for adding,

[weewx-user] Version 4.5.0 released

*Change log* The utility wee_database has new options --add-column, --rename-column, and --drop-columns for adding, renaming, and deleting columns in the database. New optional tag ".series()", for creating and formatting series in templates. See the document series_tags.md in the docs

Re: [weewx-user] 'systemctl stop' sends SIGKILL not SIGTERM on RPi

some of my services do have state that i need to save on termination, so it is important to me > On 3 Apr 2021, at 1:42 am, Tom Keffer wrote: > > SIGKILL is unclean behavior, but it should not cause any harm. The only state > worth worrying about is the database and, there, all writes are

Re: [weewx-user] 'systemctl stop' sends SIGKILL not SIGTERM on RPi

SIGKILL is unclean behavior, but it should not cause any harm. The only state worth worrying about is the database and, there, all writes are done as transactions. If the SIGKILL happens in the middle of one, it will not be committed. Of course, that's the theory! On Fri, Apr 2, 2021 at 7:36 AM

[weewx-user] 'systemctl stop' sends SIGKILL not SIGTERM on RPi

using the provided weewx.service on an RPi, ‘sudo systemctl stop weewx’ sends SIGKILL instantly (twice), which is a very unclean termination of weewx and causes me problems. has anyone encountered this and has a proper fix? so far as i can tell from the manuals (particularly ‘systemd.kill' and

Re: [weewx-user] Imported rain data not being summarised.

Hello, If I understand correctly, you deleted, then regenerated all of the NOAA monthly and yearly reports. When you say "precipitation summary data remains blank," do you mean each line in one of the summaries? Or, do you mean the totals at the bottom of the page? And, is it every line? Or,

Re: [weewx-user] Skin with webcam?

I 'm no expert by any means. I usually just try things I find here: w3school's HTML Tutorial . I'm sure there's room for improvement. With that intro, I've attached the index_hook_after_station_info.inc I created which includes the link to YouTube livestream

Re: [weewx-user] Skin with webcam?

I am also interested in how you did this. Thanks. Op donderdag 1 april 2021 om 14:02:24 UTC+2 schreef Mitchell Tuckness: > I don't suppose you would be interested in sharing the code you used to > modify the Belchertown to look so nice. I am horrible on HTML, but I am > pretty good at

[weewx-user] Imported rain data not being summarised.

Hi. Help needed please. I have imported several years of data from my old weather station into weewx.sdb. In particular, I imported the rain data into the [rain] field in the archive table and left the [rainRate] field blank. I then ran ‘sudo wee_database --drop-daily’ followed by ‘sudo

[weewx-user] Vaisala WXT520 automatic mode

Hello everybody I'm using weewx on a Raspi 3B together with the Vaisala WXT520. The WXT is sending automatic messages (ASCII, 0R1: 3s, 0R2: 15s, 0R3: 60s, 0R0: 60s). After starting weewx everthing looks OK but after sometimes houres, sometimes days, weewx stop working. In the syslog I can see

[weewx-user] Re: Cloud Base

Any ideas? Thanks Il giorno martedì 30 marzo 2021 alle 18:38:31 UTC+2 ginfo...@gmail.com ha scritto: > Good morning. > I cannot see the Cloud Base detection on my site, I was told that I need > to update the weewx.conf file > How should I do? > Thanks and good luck to all > -- You received