[weewx-development] Re: WeeWX and CoCoRaHS

Hi, Short answer, I am not aware of anyone doing this. Though I qualify that by saying I am not a CoCoRaHS user. Also bear in mind this is the development group where the audience is much smaller than the user group . You may have more luck in the user

Re: [weewx-development] Re: V4.6.0 beta 7

This is a known b7 bug that has subsequently been fixed. I suggest you wait for b8. Gary On Tuesday, 7 December 2021 at 04:24:07 UTC+10 sali...@gmail.com wrote: > hello, > > I installed the skin belchertown on weewx 4.6.0b7 but it doesn't work > > see the errors... > > Dec 6 19:15:17

Re: [weewx-development] Re: V4.6.0 beta 3

On Saturday, 16 October 2021 at 07:07:31 UTC+10 bill.g...@gmail.com wrote: > And another option, replace the ISS. > Yes, but given that ISS data is clearly getting to the console/logger (the loop packets are fine) and since the logger is solely responsible for constructing the hardware

Re: [weewx-development] Re: V4.6.0 beta 3

gt; not enabled. Skipping. > Oct 14 19:45:59 weewx weewx[29782] DEBUG weewx.reportengine: Report > 'RSYNC' not enabled. Skipping. > Oct 14 19:47:04 weewx weewx[29782] INFO weewx.engine: Main loop exiting. > Shutting engine down. > Oct 14 19:47:04 weewx weewx[29782] INFO wee

Re: [weewx-development] Re: V4.6.0 beta 3

> > This confirms my earlier testing, it's not coming from the console, > something is touching the LOOP packet, and it's the same value all the > time. > Well we don't know that for sure, certainly I've not seen a loop packet emitted directly by the driver/station that contains bogus data,

Re: [weewx-development] Re: V4.6.0 beta 3

at least 10 minutes and see it leafTemp1 appears anywhere. If it appears does it appear in LOOP: or REC: lines or both? Post the output here. Again you can check your database if you wish Gary > > On Tuesday, October 12, 2021 at 11:09:39 PM UTC-7 gjr80 wrote: > >> OK,

Re: [weewx-development] Re: V4.6.0 beta 3

t; > On Tuesday, October 12, 2021 at 10:09:15 PM UTC-7 gjr80 wrote: > >> Unfortunately I don’t see any wee_debug output attached? I’d suggest we >> find the source and fix the problem at source. The driver is most likely >> the culprit but when you are displaying LOOP packe

Re: [weewx-development] Re: V4.6.0 beta 3

he source, forcing the field to NULL should prevent display. > > So I guess what you'd suggest is: > stop weewxd. > set the leafWet1 to NULL > run wee_reports > check the web page to see if leafWet1 is gone. > > > On Tuesday, October 12, 2021 at 9:37:36 PM UTC-7 gjr80 wro

Re: [weewx-development] Re: V4.6.0 beta 3

Wet2 to > NULL so the graph and label shouldn't print. > 4. but this is new behavior from beta2 to beta3. > > My brain hurts. > > On Tuesday, October 12, 2021 at 8:01:20 PM UTC-7 gjr80 wrote: > >> On more thing, re Seasons template versioning. Tom has sta

Re: [weewx-development] Re: V4.6.0 beta 3

On more thing, re Seasons template versioning. Tom has started versioning the Seasons template so if you have a look in skins/Seasons/index.html.tmpl you should find a version number in the first few lines, eg: ## Copyright 2009-2018 Tom Keffer, Matthew Wall ## Distributed under terms of

[weewx-development] Re: Tools in config.py

everything in one place with the user only needing to use one command (with various command line options). If interested the relevant section of the GW1000 driver can be found on Github here <https://github.com/gjr80/weewx-gw1000/blob/master/bin/user/gw1000.py#L5673> . Gary On Tuesday, 20 Jul

[weewx-development] Re: Tools in config.py

t be found within the search path. > > And I have no glue, how to do that. > > I placed the Python part of the script in the bin directory (not bin/user, > bin only). But what to do with the shell part of the script? > > gjr80 schrieb am Montag, 19. Juli 2021 um 22:47:23 UTC+2: >

[weewx-development] Re: Tools in config.py

I’m not sure if I understand your question correctly but provided you are setting the ‘files’ parameter in install.py you can fairly much put anything anywhere in the WeeWX bin and skins tree branches irrespective of WeeWX install type (eg specifying bin/user will see the installer

[weewx-development] Re: series and json tags

You need to define a tag to cover the period for which you want the stats and then add the newly defined tag to the search list. The stats example gives some example code for doing exactly that for $alltime and $seven_day tags.

[weewx-development] Re: How to debug cheetah report not reporting

First thing is the WeeWX log, sometimes it is not the error you are looking for in the log but rather what is missing from the log. What does the log show with debug = 1 Second thing, the iconic-color.html.tmpl is pretty basic with the majority of the 'work' being done via an include. Chances

Re: [weewx-development] getting /home/weewx/bin into $PATH

I do think a bit of this is self-inflicted on our behalf. If you have a look at the various command strings in the docs, the wiki, readmes for extensions on GitHub etc you will see a lot that include no path with no mention that a path may be required. This is fine for package installs but

[weewx-development] Re: wee_debug and new user support

On Sunday, 18 April 2021 at 04:09:22 UTC+10 vince...@gmail.com wrote: > On Saturday, April 17, 2021 at 6:07:01 AM UTC-7 mwall wrote: > > the quantity of information is not a problem. users' ability to run the > tool and post the output is the problem. lets make that easier. > > Agree. Maybe

Re: [weewx-development] Re: What happens in Weewx around 3AM

shut down weewx nightly to do my backups just so I get a >> clean backup. So you may want to have weewx shutdown just before your >> backup job kicks off then start back up again. >> >> On Feb 13, 2021, at 17:37, gjr80 wrote: >> >>  >> >> Looks p

[weewx-development] Re: What happens in Weewx around 3AM

>> 1001.275146484375, 1001.266845703125] >> LOOP: 2021-02-13 02:58:19 CET (1613181499) altimeter: >> 30.228797789343705, dateTime: 1613181499, extraTemp2: 66.181999, >> inDewpoint: 39.459679025970544, inHumidity: 39.3890380859375, inTemp: >> 64.74145507

[weewx-development] Re: What happens in Weewx around 3AM

Hi, Probably easiest if you post a log extract showing the lead up to a failure and the actual error trace. Also what version of WeeWX are you running and is WeeWX running under python 2 or python 3? Gary On Sunday, 14 February 2021 at 03:39:13 UTC+10 sbar...@gmail.com wrote: > Hi, > > My

[weewx-development] Re: What is wrong with my driver?

I think it might be worth taking a couple of steps back here and having a look at what you are trying to do, if not for your benefit then for mine. As I understand it you have started with a weatherflow driver that picks up UDP packets and emits that data in loop packets for WeeWX to ingest.

[weewx-development] Re: What is wrong with my driver?

The big plus for implementing genArchiveRecords() is that if genArchiveRecords() can provide historical archive records you have the ability to catch up if WeeWX looses its connection to the station. Without genArchiveRecords() catchup is not possible. If there is no ability to provide

[weewx-development] Re: What is wrong with my driver?

It might be worth revising the operation of genLoopPackets() and genArchiveRecords(), in particular when running under hardware and software record generation. The task of genLoopPackets() is to emit loop packets and these packets are processed and accumulated by WeeWX. The accumulated loop

Re: [weewx-development] Polling interval confusion

2021 at 06:00:34 UTC+10 Jan-Jaap van der Geer wrote: > On Tuesday, February 9, 2021 at 10:56:34 AM UTC+1 gjr80 wrote: > >> That being said there is no requirement for that to be so, hence why you >> see words like ‘if’ and not ‘must’. >> > > The 'if' conc

Re: [weewx-development] Polling interval confusion

lob/f90473fb97909a80151d097f6f9799c26bba798c/bin/weeutil/weeutil.py#L132> function. Gary On Wednesday, 10 February 2021 at 06:06:28 UTC+10 Jan-Jaap van der Geer wrote: > On Tuesday, February 9, 2021 at 1:48:18 PM UTC+1 gjr80 wrote: > >> Very simply, when your driver is emitting loop packets your time >>

Re: [weewx-development] Polling interval confusion

with the right treatment for vector data). Losing precision of min/max > values and their timestamps is acceptable (at least for reasonable short > archive_interval settings) > > > gjr80 schrieb am Dienstag, 9. Februar 2021 um 13:48:18 UTC+1: > >> Very simply, when

Re: [weewx-development] Polling interval confusion

but it could be the sum or the last or the first value, it depends). Gary On Tuesday, 9 February 2021 at 22:42:18 UTC+10 gjr80 wrote: > OK, let's work through it. The hardware stored data at one minute > intervals, so between 11:05:00am to 11:10:00am the hardware will have five > store

Re: [weewx-development] Polling interval confusion

gt; Lets assume the archive_interval 11:05:00am to 11:10:00am is to be > backfilled. The driver gets the stored archive values from the hardware, > where the maxvalue was at 11:07:00am. > Is the maxvalue in the archive_day_xxx table for that day timestamped with > 11:07:00am or with 11

Re: [weewx-development] Polling interval confusion

If your one loop packet was the only loop packet received by WeeWX in that archive interval then the archive record that WeeWX would synthesise from that solitary loop packet would be the same as that loop packet. If as you said that loop packet was stored by hardware and if the driver's

Re: [weewx-development] Polling interval confusion

On Tuesday, 9 February 2021 at 19:43:50 UTC+10 michael.k...@gmx.at wrote: > Thanks Gary. > So if the driver "wants" to control the archive interval, it is overriden? > For my personal reality, 1 Minute is too short. > Simply put, if WeeWX is using hardware record generation and the driver

Re: [weewx-development] Polling interval confusion

On Tuesday, 9 February 2021 at 19:40:43 UTC+10 Jan-Jaap van der Geer wrote: > On Tuesday, 9 February 2021 at 10:23:40 UTC+1 gjr80 wrote: > >> To clarify, the archive interval coming from the driver or weewx.conf is >> quite acceptable. >> >> If a driver has the a

Re: [weewx-development] Polling interval confusion

To clarify, the archive interval coming from the driver or weewx.conf is quite acceptable. If a driver has the ability to emit archive records then it MAY also control the archive period (by the same token it may not). Consequently, if you are using driver emitted archive records (ie hardware

Re: [weewx-development] Re: Beta of V4.3.0 available

I guess your Fit-PC has a bit more oomph than my Rpi3B. You probably could drop the five months to something smaller, but you know as soon as you do there will be someone out there who clean installed 4.2.0 with more days in the logger than you choose to patch. I guess no matter what some folks

Re: [weewx-development] Re: Beta of V4.3.0 available

does from 1-Jun-2020, > so should go very fast. > > On Tue, Dec 29, 2020 at 8:20 PM gjr80 wrote: > >> Have to say I am impressed. First time upgrading a weewx-multi install >> with wee_config --upgrade and it worked just fine, on both WeeWX >> instances. Not

Re: [weewx-development] Re: Beta of V4.3.0 available

Have to say I am impressed. First time upgrading a weewx-multi install with wee_config --upgrade and it worked just fine, on both WeeWX instances. Noticed the re-weighting from v2 to v3 when I upgraded the simple (ecowitt) install, so was preparing myself to manually re-weight a couple of

[weewx-development] Re: How to Access summaries in a restful driver

Hi, You are on the right track but making things difficult for yourself by trying to use the daily summaries to obtain day max/min aggregates. Whilst it’s true that the day max/min values can be found in the daily summaries they are also available by querying the archive table. In this case

[weewx-development] Re: GW1000 driver

lp with testing on > my old mac server as well as my new raspberry > > does gw1000 have a data logger like my very aged vp2 which allows catch-up > after an outage? (i've looked at driver header comments but not delved the > code as yet) > > On Tuesday, 21 July 2020 12:50:2

Re: [weewx-development] GW1000 driver

GW1000 is at the > top of the list. > > On Mon, Jul 20, 2020 at 7:50 PM gjr80 wrote: > >> I have developed an API based driver for the Ecowitt GW1000 WiFi Gateway. >> So what? Well the current means of receiving data from the GW1000 involves >> the GW1000 pushin

Re: [weewx-development] GW1000 driver

v0.1.0b2 fixes an issue with --default-map. Can download and re-install the extension <https://github.com/gjr80/weewx-gw1000/releases> or simply download the updated gw1000.py using: $ wget https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py and replace user/

[weewx-development] GW1000 driver

but can also be operated as a WeeWX service that augments loop packets with GW1000 data. The driver will operate under WeeWX 4.x python 2 and 3 and under WeeWX 3.9.x (probably some earlier 3.x versions as well). The driver can be found on GitHub <https://github.com/gjr80/weewx-gw1000> a

[weewx-development] Re: Stupid Database Question

My advice; by all means restructure your archive table and schema as required to suit but don't try manually adjusting the daily summary tables. Far easier and safer to use wee_database to drop and then rebuild them - almost certain to get yourself tied in knots one way or another otherwise.

[weewx-development] Re: Adding values from StdService trought StdConvert

Exactly, you need to implement genStartupRecords() in your driver. Writing a service will add no benefits; rather it will add unnecessary complexity (there is already an established mechanism for catchup) and by stepping outside the established mechanism you risk your driver/service not working

[weewx-development] Re: Adding values from StdService trought StdConvert

If I understand correctly you are trying to write a WLL driver that not only emits loop packets/archive records but also catchup archive records. if that is the case I think you are making this way more complex than it need be. A driver should only be concerned with emitting loop packets and

[weewx-development] Re: Reloading of weewx driver

The line you highlighted is a consequence of the error rather than the cause. When WeeWX reloads the driver WeeWX essentially does a soft restart, it shuts everything down beforehand. Here is you error: Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: Caught OSError: timed out Jul 4

[weewx-development] Reloading of weewx driver

Hi, Ideally a driver should not be reloaded, though WeeWX will reload a driver under certain error conditions. This (reload) should be logged and I would expect some sort of error would also be logged. I would suggest posting a log extract covering the period a few minutes before the reload

[weewx-development] Syslog use in thread possibly cause thread exit?

Hi, Can’t see why syslog is not thread safe, before v4 the WeeWX report engine ran in a separate thread and all logging was done through syslog and I don’t recall there ever being a syslog/thread issue. Likewise a number of WeeWX v3 and earlier 3rd party drivers/services use threading and

[weewx-development] Re: Adding density altitude

ltimeter is calculated from pressure altimeter will not be available either until the temperature from 12 hours ago is available. Gary > > This was the reason behind the need for my 'abspressure' calculation. > > Y > > Le lundi 8 juin 2020 04:50:16 UTC+2, gjr80 a

[weewx-development] Re: Adding density altitude

, format) from which I have no idea on how to 1) call it in > the above script and 2) isolate only its value for my calculation ? > > Your help would be much appreciated ... > > Yann > > > Le dimanche 30 septembre 2018 04:07:27 UTC+2, gjr80 a écrit : >> >> Jac

[weewx-development] Re: Intent to Implement: Aviation Unit System

Hi, 2.5 years and no activity (and no related changes to the WeeWX codebase) so I would say the thread is fairly well dead. I would go back to the 2nd post in the thread. WeeWX has a built-in unit conversion/formatting system. This system supports unit conversion/formatting options for tags

Re: [weewx-development] Feature Request : Add calculate method standard OMM on daily database

Hi, The implementation of there original change you suggest does not require a new/changed driver but rather substantial changes to the WeeWX archive service as well a a number of peripheral utilities/code, there is no way to avoid this. As Tom said a big job. Gary -- You received this

Re: [weewx-development] Re: weewx 4.0 doesnt do a clean exit

I suggest we all calm down and wait to hear from Tom, there was a pre-3.9.2 commit that solely changed the terminate stacktrace from debug to info log output. But it appeared as debug output in 3.9.2. There is also a couple of seemingly unexplained changes (I can’t find the commit) between

[weewx-development] weewx 4.0 doesnt do a clean exit

Not sure I see an error there, just a copy of the stack trace. Gary -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [weewx-development] Feature Request : Add calculate method standard OMM on daily database

Hmm, seems this thread has managed to spill into the user forum as well If I am understanding the intent correctly this would seem to be a step up in complexity from what has previously been discussed at issue #91

[weewx-development] Re: Feinstaubsensor in WeeWX einbinden

Hallo, Ich hoffe, Sie können mein Google Deutsch verstehen. Es kann hilfreich sein, wenn wir Ihre WeeWX-Konfiguration verstanden haben und wissen, welche Daten WeeWX von Ihrer Station sammelt. Ein Debug-Protokollextrakt wird dies tun. Könnten Sie weewx.conf bearbeiten, debug = 1 setzen,

[weewx-development] Re: Using 4.0.0b18 with steel series but weewx isnt generating public_html/index.php

I presume you mean index.html, the skin generates index.html not index.php. Going to need to see a debug=1 log extract covering at least a couple of archive intervals. Would also help to see your [StdReport] stanza from weewx.conf or a wee_debug report. In either case do check before you post

[weewx-development] Re: testing 4.0.0b18 need help esolving issue

Any errors in logs, crashes, unexplained restarts, anything on the generated pages that does not look right. One of the main things sought during beta is users with different stations/setups. This has been a long beta, up to 18 now, so it’s likely most issues have been found. In fact release

[weewx-development] Re: testing 4.0.0b18 need help esolving issue

That is interesting, that skin has been around for years and a quick look at the history indicates rainrate has been there from day one. Surprised that has not been picked up (and fixed) earlier. Will submit a PR to the repo owner. Gary -- You received this message because you are subscribed

[weewx-development] Re: testing 4.0.0b18 need help esolving issue

No, the WeeWX image generator is being called by a skin and the skin is asking for a plot that includes field rainrate. Have a look in your skin config file skin.conf under [[ImageGenerator]]. Gary -- You received this message because you are subscribed to the Google Groups

[weewx-development] testing 4.0.0b18 need help esolving issue

Case matters, WeeWX uses field rainRate not rainrate.Try using rainRate. Gary -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [weewx-development] Re: python3

On Sunday, 26 April 2020 02:34:59 UTC+10, Tom Keffer wrote: > > I tried Debian Buster in virtualbox and had the same issues appear >> >> > I'm not following. Are you saying that a Buster upgrade removed pyserial > and configobj? > That concerned me too, tried using serial under python2 on my

[weewx-development] Re: python3

Yes i386 is 32 bit, amd64 is 64bit. Which you use depends how you setup your VM, or how you setup your VM will determine which ISO. Either will be fine. Gary On Saturday, 25 April 2020 21:44:55 UTC+10, Cat22 wrote: > > Ok, my bad - i thought the amd64 said arm64 - I will restart the install >

[weewx-development] Re: python3

Looks about right or it’s amd64 friend for 64bit. Gary -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To

[weewx-development] Re: python3

Haven’t used any USB under virtualbox, do all my WeeWX development work on Debian VMs under virtualbox but just use simulator, never with a live station. Give 4b18 a go, only said to hold off to keep things simple, but then I encountered tumbleweed. Gary -- You received this message because

[weewx-development] Re: python3

SteelSeries will be fine, or if not an easy fix. I see b18 is the currently available beta on the development downloads page, it’s about 24 days old though most of the commits since b18 are fairly minor. I’d be tempted to give b18 a go. Bit sneaky changing things like that, first time I have

[weewx-development] Re: python3

Interesting, https://software.opensuse.org/ says it does exist, though as I said I am not an openSUSE user. Might need an openSUSE user to help. WeeWX v4 is pretty stable. If you are (were) running a plain vanilla WeeWX install you should not have too many problems running the beta. The only

[weewx-development] Re: python3

OK so a missing python serial package is the issue. Not an openSUSE user but when I look at tumbleweed it shows a python-pyserial package and a python3-pyserial package. You can’t install python-pyserial? Gary -- You received this message because you are subscribed to the Google Groups

[weewx-development] python3

Hi, > So, I am having issues running weewx because "Python 2.7 reached the end of > its life on January 1st, 2020." I find this hard to believe. WeeWX v4, which is still in beta, (but will be released real soon now) will be python 2 and 3 compatible. I would suggest you wait for WeeWX v4 to

[weewx-development] weewx-historical

Not sure I like where this whole Xtypes thing is going. I have a perfectly good SLE that does half as much as this with 50% more lines of code that I will now have to retire. :) Gary -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To

Re: [weewx-development] Memory leak in StdReport?

So maybe one of those updated modules is the problem. Running with one plot still calls PIL so if PIL is the leak it will still show. As Vince said you really need to work systematically to find the culprit. PIL seemed to be low hanging fruit to me. Gary -- You received this message because

[weewx-development] Re: weewx version 4 can't keep up in time

On Thursday, 26 March 2020 13:21:55 UTC+10, Lucas Heijst wrote: > I think the fact that weewx can't keep up in time to handle the 1-minute > archive data is the reason that the memory is filled. > I think you are being a little harsh here Luc. From what i can read of the log extracts you are

[weewx-development] Re: weewx 4.0.0b16 wee_import - calculate missing data problems

Luc, Some comments below. Gary On Monday, 23 March 2020 03:27:50 UTC+10, Lucas Heijst wrote: > > Gary, > > I completed a run from 2019-02-04 to 2019-03-01 and got 6957 records. > > The derived data went OK. > > 23 records had NULL for cloudbase, humidex and apptemp because outhumidity > was

[weewx-development] Re: weewx 4.0.0b16 wee_import - calculate missing data problems

On Monday, 23 March 2020 02:09:52 UTC+10, Lucas Heijst wrote: > > > In my case I want to import a year of data! > Given WU's history of flakiness and given that your year of data will require 350 odd WU API calls via the internet, I would not be doing this as one big import; you are just

[weewx-development] Re: weewx 4.0.0b16 wee_import - calculate missing data problems

Luc, Did you let the wee_import session run until completion? There was a change in the way missing derived obs are calculated by wee_import under WeeWX 4.0. Previously missing derived records were calculated record by record at time of record import, now under 4.0 missing derived obs are

[weewx-development] Re: How to implement rain and rainRate fields in a new driver?

Bill, My two cents. This is a very common situation, many stations provide one (or more) cumulative rainfall values. Since WeeWX requires a per-interval or delta value all you do is pick one of the cumulative rain values (in your case Rain Today is the obvious choice) and calculate the

[weewx-development] Re: v4beta mystery element values in packets from test driver

On Sunday, 1 March 2020 10:55:37 UTC+10, Vince Skahan wrote: > > I was worried weewx was making stuff up :-) > Actually there is a fair bit of effort made to ensure WeeWX does not make things up (windDir = None when windSpeed == 0, culling of fields from drivers etc) Gary -- You received

[weewx-development] Re: v4beta mystery element values in packets from test driver

A few things to remember: 1. The console output from running WeeWX directly is not the output from the driver rather it is the resulting packet/records after all WeeWX services have been run (StdConvert, StdCaibrate, StdWXCalculate etc). Have a look at the [[Services]] stanza at the bottom of

[weewx-development] Re: is there a driver (not extension) for http get of json data ?

FWIW I wrote a Bloomsky driver a few years ago that hits the bloomsky API for json data every so often. Is not a combined service/driver nor is the mapping as sophisticated as described by Matthew. https://github.com/gjr80/weewx-bloomsky Code should be python 2/3 compatible but have not yet

[weewx-development] Re: wee_import fixes - Gary

to 2015 to Nov 2017 is > done. > My PI is quite busy running days and nights :-) > > I will pull service request in future > Nicolas > > Le samedi 22 février 2020 07:30:10 UTC+4, gjr80 a écrit : >> >> Below issues should be fixed now. The epoch issue was interesting.

[weewx-development] Re: wee_import fixes - Gary

that is not what they are returning. But given WUs recent track record that does not surprise me. Gary On Saturday, 22 February 2020 09:46:55 UTC+10, gjr80 wrote: > > Nicolas, > > Thanks for the feedback, I will get onto looking at each issue. Some > initial comments below. > &g

[weewx-development] Re: wee_import fixes - Gary

Nicolas, Thanks for the feedback, I will get onto looking at each issue. Some initial comments below. Gary On Friday, 21 February 2020 18:54:29 UTC+10, Nicolas CUVILLIER wrote: > > Gary > > I am trying to import my historical data from underground. > If I understood you wrote the utility > > I

Re: [weewx-development] WeeWx archiving

Hmm, wouldn't be a daylight saving change to put clocks back in November each year would there? Gary On Wednesday, 12 February 2020 10:31:36 UTC+10, Tom Keffer wrote: > > Yes, modulo DST weirdness, you should see 288 counts per day. > > Are the high counts consistent? That is, every day? > >

[weewx-development] Re: git repo

that's here not her On Monday, 3 February 2020 11:06:00 UTC+10, gjr80 wrote: > > Yes, any final last minute changes will go to master from her on in. > > Gary > > On Monday, 3 February 2020 10:00:43 UTC+10, P Simmons wrote: >> >> So, I notice that the "dev

[weewx-development] Re: git repo

Yes, any final last minute changes will go to master from her on in. Gary On Monday, 3 February 2020 10:00:43 UTC+10, P Simmons wrote: > > So, I notice that the "development" has been trailing "master". For > testing, should I now switch to "master"? > -- You received this message because

[weewx-development] beta weewx-4.0.0b10 problem updating to Wunderground

Ted, Have a look at the last few posts in weewx-user, WU is having (more) issues. Gary -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[weewx-development] Re: Additions to database schema for 5 Vantage LOOP2 Observations

My apologies, I should pay more attention to what is written rather than what I thought was written. There has long been an issue on github to ship WeeWX with an additional schema. Consequently 4.0 will ship with what is called the ‘wview extended schema’ with the emphasis on the full suite of

[weewx-development] Re: Additions to database schema for 5 Vantage LOOP2 Observations

Hi, Good news, support for LOOP2 is already in 4.0 - from the 4.0 changes doc: *Support for the Vantage LOOP2 packet format. Fixes issue #374.* You can have a look at issue 374 if you want further details. Gary PS. Remember that whilst LOOP2

Re: [weewx-development] Re: V4.0.0b4 is up

Appreciate you have managed to disable cmon but for future reference manual uninstallation of an extension is fairly easy once you know what to look for. There is no simple 'find this and do this', the amount of work involved and where to work depends on the extension. A skin/report based

Re: [weewx-development] Re: V4.0.0b4 is up

As far as I am aware development versions are generally distributed as setup.py installs only and not as a (deb or rpm) package. For setup.py installs you need to manually install the service files. Refer to the Run section of the setup.py install instructions http://weewx.com/docs/setup.htm

[weewx-development] Re: Rpi 3B+ vs Rpi 4B - same SD card, different WeeWX behaviour

Don't see this as a WeeWX or a skin issue, rather one of hardware/OS compatibility. I am not surprised that a SD card with Linux setup for a RPi 3B+ does not work without change on a RPi 4. That's a bit like taking the hard disk out of my PC and plugging it into a different PC and expecting

Re: [weewx-development] Sync'd with development now getting database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

> leading to the timestamps being off by an hour / overlapping with data in > the same hour from prior to the upgrade. :-/ > > Regards, > \Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad) > > On Nov 16, 2019, at 9:19 PM, gjr80 > > wrote: > >  > Wou

Re: [weewx-development] Sync'd with development now getting database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Would appreciate some more info on this, I just used 4.0 wee_debug it it obfuscated a new WU API key as expected. The obfuscation code is pretty basic, for WU it is if key name == 'api_key' then value with 'XXX obfuscated by wee_debug XXX'. I seem to remember you changing WU config option

Re: [weewx-development] Re: Beta of Version 4 is available

; > On Sat, Nov 16, 2019 at 4:32 PM gjr80 > > wrote: > >> 4.0 is throwing the following for me under python 3.5.3: >> >> Nov 17 10:27:34 stretch41 weewx[16116] INFO weewx.engine: Starting main >> packet loop. >> Nov 17 10:30:14 stretch41 weewx[16116] I

Re: [weewx-development] Re: Beta of Version 4 is available

4.0 is throwing the following for me under python 3.5.3: Nov 17 10:27:34 stretch41 weewx[16116] INFO weewx.engine: Starting main packet loop. Nov 17 10:30:14 stretch41 weewx[16116] INFO weewx.manager: Added record 2019 -11-17 10:30:00 AEST (1573950600) to database 'weewx.sdb' Nov 17 10:30:14

Re: [weewx-development] Re: Beta of Version 4 is available

Just a note for anyone who may be toying with the new --calc-missing functionality in wee_database; it is broken in the current beta (b1). I should have a commit that fixes it this afternoon and I guess that will appear in the next beta. Gary -- You received this message because you are

[weewx-development] Re: windrun calculations

A couple of thoughts... If you did this: > UPDATE weewx.archive SET windrun = (windSpeed * `interval` / 60.0) where > windSpeed > 0; > > and after rebuilding have this: MariaDB [weewx]> SELECT * FROM `archive_day_windrun` ORDER BY `sum` DESC LIMIT 1; >

Re: [weewx-development] Consolidate database interval records?

wee_import does not do any form of record aggregation, it just reads in the records as they appear in the source and applies one of three methods of determining the interval field for each record. Firstly it can derive the interval field as the difference between successive record timestamps

[weewx-development] Re: Week and Month plots not being generated?

Hi Henry, The [ImageGenerator] stanza looks fine. There is no practical way to confirm if you have dots in your plots other than careful observation of the generated plot. Have a read of the section ‘Dots in your plots’ (http://weewx.com/docs/usersguide.htm#dots_in_plots) in the Users Guide,

[weewx-development] Re: Week and Month plots not being generated?

Hi, Are you sure the plots are being generated without data? Under some circumstances plots can be generated with data points only (ie no connecting lines between the data points) and to a casual observer they can look like there is not data being plotted at all (especially if there are only

[weewx-development] Re: WU Forecast

Correct the forecasting extension is not part of WeeWX per se. Matthew maintains it and it is not available in a publicly accessible repo as far as I know. Unfortunately you will need to wait for Matthew to pick up on this. Gary On Friday, 21 June 2019 13:33:56 UTC+10, Jerome Helbert wrote: >

Re: [weewx-development] Engine exception: TypeError: descriptor 'lower' requires a 'str' object but received a 'unicode'

t;/usr/bin/python" so out-of-the-box, > dev/4.0 will run under python2 in such a scenario. > > Did I miss some documentation on how to get setup.py to choose python3 > across the board? > > Regards, > \Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad Pro) > >

  1   2   >