Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

gt; >> >> >> >> I let it run for 15 minutes, then cancelled, with no loop packets >> received. >> >> >> >> I will experiment further with the hardware side – maybe something in >> BIOS configures the port in some way. >> >>

Re: [weewx-user] howto fix weewx sqlite database

See the wiki article Cleaning up old "bad" data , in particular, the section *Deleting unwanted records * . On Sun, Jul 24, 2022 at 1:53 AM

Re: [weewx-user] Re: Install user.byows_rpi driver?

Something is off. Could you send me the copy of byows_rpi.py you are using? On Sat, Jul 23, 2022 at 2:33 PM Jan Bennett wrote: > Thank you for your time in responding. > > It is correct that byows_rpi extension > is mostly just a python file >

Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

on the Telstra Mobile Network > Get Outlook for Android <https://aka.ms/AAb9ysg> > -- > *From:* weewx-user@googlegroups.com on > behalf of Tom Keffer > *Sent:* Sunday, July 24, 2022 12:21:45 AM > *To:* weewx-user > *Subject:* Re: [weewx-user] Re: No

Re: [weewx-user] installation and configuration of weewx-saratoga

I don't know anything about the Saratoga extensions, but I do know how to add a column to the database: use wee_database with the --add-column option: *wee_database --add-column=windrun* That may, or may not, help your problem. It's

Re: [weewx-user] Re: Install user.byows_rpi driver?

1, It looks like the byows_pi extension does not use the extension installer, so weewx has no way of knowing of its existence. This is why it doesn't show up in the list of available drivers. 2. As for running byows_pi directly, you have a slight problem with your paths. Try either this cd

Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

Could definitely be a baud rate issue. The driver opens the port using the default pyserial rate, which is 9600, and you seem to be at 115200. Can you change the port rate to 9600? If not, we can try changing the driver to expect 115200. These things are also easier to diagnose by running weewxd

Re: [weewx-user] how to diagnose a davis envoy that lost connection to iss?

I would add one more to your list: change the battery. On Fri, Jul 22, 2022 at 5:47 AM matthew wall wrote: > On Thursday, July 21, 2022 at 12:46:24 PM UTC-4 tke...@gmail.com wrote: > > Many Davis stations show dropped reception at precisely midnight. It > usually only > > stays that way for

Re: [weewx-user] Seasons skin, index.html and telemetry.html not updating

You need only deactivate the Standard skin, then activate the Seasons skin. Delete all the generated files and images --- they will be regenerated again, this time using the Seasons skin. On Thu, Jul 21, 2022 at 5:14 PM willefg wrote: > Thank you, Tom > > To do that I will have to change the

Re: [weewx-user] Seasons skin, index.html and telemetry.html not updating

The logs almost always leave a clue. Set debug=1, then restart weewxd. Post the logs through the first report generation. On Thu, Jul 21, 2022 at 4:30 PM willefg wrote: > Hi, > > I''ve had this issue, where every file generated from the Seasons skin is > constantly updating except the

Re: [weewx-user] Weewx stop to write in database

To avoid, deactivate the virtual environment, then run setup.py using the system's version of Python. Then reactivate. -tk On Tue, Jul 19, 2022 at 12:02 PM Tom Keffer wrote: > 1, It looks like you have two instances of weewx running. Make sure all > instances are stopped before trying to restar

Re: [weewx-user] Weewx stop to write in database

1, It looks like you have two instances of weewx running. Make sure all instances are stopped before trying to restart weewxd: sudo killall weewxd sudo systemctl start weewx 2. While your driver seems to be putting new packets into its internal queue, it's not draining the queue, so the queue

Re: [weewx-user] Weewx stop to write in database

There is almost always a clue in the log. Please stop weewxd, set debug=1, restart weewxd, then let it run through at least the first reporting cycle. Post the log from startup through the reporting cycle. -tk On Tue, Jul 19, 2022 at 8:24 AM ant duro wrote: > I have been using weewx on my

Re: [weewx-user] Macos installation

For some reason, you're missing all your executables (not just weewxd). I am not familiar with pipenv (I use pyenv). I find it curious that the pipenv version of Python went looking for weewxd in '/Users/mbp/gitRepo/weewx/./bin/weewxd', which, presumably, is in a git repository. Where did it get

Re: [weewx-user] Macos installation

Lots of missing information here. First, how did you install? Did you run setup.py? What did you use for setup.cfg? What is in /Users/Shared/weewx? Give us the results of ls -l /Users/Shared/weewx ls -l /Users/Shared/weewx/bin -tk On Tue, Jul 19, 2022 at 7:03 AM Dan Jones wrote: > Hi > > I

Re: [weewx-user] 2 WU questions from new user (AcuRite 01035 USB on RasPi)

Looking through your station, it actually looks pretty good for a rapidfire station. The WU Rapidfire implementation often has a problem converting the rapid RF updates into regular archive records. I would suggest turning off Rapidfire for a while and see if you like the results better. On

Re: [weewx-user] 2 WU questions from new user (AcuRite 01035 USB on RasPi)

Welcome, Tom. WU is incredibly flaky. After a post, data may or may not show up. Could you give us your station ID? On Mon, Jul 18, 2022 at 4:59 PM Tom Stewart wrote: > Greetings! First off, I want to say how grateful I am to have found WeeWX. > I've been running MeteoHub for a few years now,

Re: [weewx-user] WeeWx Calculations

Greg has it exactly right. Until the introduction of LOOP2 packets about 8 or 9 years ago, the Vantage stations behaved this way. They only published pressure reduced to sea-level (SLP), so station pressure (and altimeter pressure) had to be back calculated. -tk On Sun, Jul 17, 2022 at 7:56 AM

Re: [weewx-user] howto fix weewx sqlite database

It is very unlikely that the size of the database is a problem. Like Graham, I have over 15 years of data on mine without a problem. You did not say what kind of storage you are using, but if it is an old SD card, it is much more likely that the card is corrupt. You may be able to recover the

Re: [weewx-user] send data to ecowitt.net

Did you check the wiki ? On Sun, Jul 10, 2022 at 10:49 AM enu...@gmail.com wrote: > I don't see in stdrestful any way to send data to ecowitt. Is there a way? > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user"

Re: [weewx-user] Re: Monitoring RESTful API calls sending weather data

This monkey patch would be pretty safe. The function process_record() is intended to be overridden by subclasses, so it can't really afford to change. Not to mention, log entries can change too! On Wed, Jul 6, 2022 at 1:48 PM vince wrote: > Some creative syslog config file rewrite rules might

Re: [weewx-user] Monitoring RESTful API calls sending weather data

Honestly, scraping the logs isn't so bad. An alternative would be to monkey-patch the member function weewx.restx.RESTThread.process_record(). The replacement version would first call the original version, then, once it returns, post success by whatever means you choose to Home Assistant. On

Re: [weewx-user] Need to supress UV readings going to Weather Underground (WU)

You could try forcing UV to null. In weewx.conf: [StdCalibrate] [[Corrections]] UV = None On Tue, Jul 5, 2022 at 7:09 PM StarMan703 wrote: > I have a 2004 Vantage Pro2 and have started getting sporadic UV readings > when sending data up to Weather Underground (WU). Problem is I "do

Re: [weewx-user] issue when trying to depict rain data from different weewx databases in Seasons skin (current and High/Low)

; And I take it, that if I want to include more data-bindings, I just > enlarge the $archive_data array by more elements ... (1st solution) > > thanks again > cheers > Rainer > > On 06.07.2022 01:42, Tom Keffer wrote: > > It looks like you are using an older version of

Re: [weewx-user] Re: issue when trying to depict rain data from different weewx databases in Seasons skin (current and High/Low)

It looks like you are using an older version of Seasons (before it was parameterized). The variable $archive[1] is the result of evaluating $day, which makes it an instance of weewx.tags.TimespanBinder, built using default values in the initializer. At this point, it's too late to ask it to be

Re: [weewx-user] Can WeeWX be used to capture and save data from multiple stations?

The simplest would be to run 3 different instances of WeeWX on the same computer. See the wiki article weewx-multi . Then nominate one of the instances to do the reporting, making use of the database from the other 2 instances. For example, if you

Re: [weewx-user] new install (4.8) using the GW1000 extension - missing ET?

In order to calculate ET, you'll need outside temperature, radiation, and humidity. From your query, you don't have radiation, and possibly the others. Make sure they are all there. On Mon, Jul 4, 2022 at 9:49 AM John Hill wrote: > Sorry - this is going to sound poorly informed... but here it

Re: [weewx-user] wee_reports timestamp format

Fixed in commit b164c74 <https://github.com/weewx/weewx/commit/b164c74c34ecc6ee2a005d11dcd5e4dc187cebdc> On Sun, Jun 26, 2022 at 3:40 AM Tom Keffer wrote: > The timestamp should be in unix epoch time. You can use a tool such as > epochconvert.com to figure out the timestamp. >

Re: [weewx-user] Generating longer-term reports on added data

Older plots and NOAA records are not automatically regenerated. Did you delete everything before running wee_reports? On Sat, Jul 2, 2022 at 2:46 PM 'Peter Fletcher' via weewx-user < weewx-user@googlegroups.com> wrote: > I have recently added a 'Sunshine minutes/hours' field to weewx's database

Re: [weewx-user] Re: Adding more RESTful services for supplying data

Make sure you read the support page on the website. https://weewx.com/support.html On Wed, Jun 29, 2022 at 9:08 PM Kruse Ludington wrote: > Where is that? URL? > > Best Regards, > > -R. Kruse Ludington > > (M): +1.201.925.4410 > (O): +1.862.308.7040 > (H): +1.201.857.8307 > (F):

Re: [weewx-user] weewx sql database repair tools

Not clear what you're asking, but I'd like to know more about the corruption of the database. I spent a lot of time making sure that commits were atomic. Did I miss something? Could you be more specific about what's wrong with the database? On Mon, Jun 27, 2022 at 2:32 PM VE4PER Andy <

Re: [weewx-user] Problem FTPS WeeWX

I prefer to offer features when they are needed. It's easier to add a feature than to take it away! On Mon, Jun 27, 2022 at 7:44 AM Remy Lavabre wrote: > No Tom, for me it is not necessary. But maybe one day for someone else? > Who knows... > Thank's again Tom > Le lundi 27 juin 2022 à 16:11:38

Re: [weewx-user] Problem FTPS WeeWX

Yes, I will include the fix in the code base. Wouldn't it be good to provide a second parameter for the value > "MinProtocol = TLSv1.2"? Are you saying that we should implement ssl.set_alpn_protocols() as well? Do you have a case where that was necessary? -tk On Mon, Jun 27, 2022 at 5:48 AM

Re: [weewx-user] Problem FTPS WeeWX

s://groups.google.com/d/msgid/weewx-user/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/weewx-user/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com?utm_medium=email_source=footer> >>>>> . >>>>> >&g

Re: [weewx-user] Problem FTPS WeeWX

1f-a51e-a10cf594e42dn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/6dfd9849-4b82-461f-a51e-a10cf594e42dn%40googlegroups.com?utm_medium=email_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group.

Re: [weewx-user] Problem FTPS WeeWX

A little Googling reveals that this problem is caused by outdated libraries on the FTP server. The "set_ciphers" option requests than an older, less secure, protocol be used on the client side in order to match what the server has. We could add support for setting cipher levels, but, before doing

Re: [weewx-user] wee_reports timestamp format

The timestamp should be in unix epoch time. You can use a tool such as epochconvert.com to figure out the timestamp. You're right: it really should be documented. Issue #776 . On Sat, Jun 25, 2022 at 11:56 PM Auchtermuchty Weather wrote: > The help is

Re: [weewx-user] Re: weewx runs, but produces lots of logging errors

loop messages when you run weewxd interactively, and >>> everything else quiets down. Tested on 4.8.0 and debian10 in Docker. >>> >>> On Friday, June 24, 2022 at 4:36:12 AM UTC-7 Tom Keffer wrote: >>> >>>> Yes. See the wiki article *WeeWX v4 and logging &

Re: [weewx-user] Re: weewx runs, but produces lots of logging errors

x.conf, the result is that > weewx just emits the loop messages when you run weewxd interactively, and > everything else quiets down. Tested on 4.8.0 and debian10 in Docker. > > On Friday, June 24, 2022 at 4:36:12 AM UTC-7 Tom Keffer wrote: > >> Yes. See the wiki article *Wee

Re: [weewx-user] Re: weewx runs, but produces lots of logging errors

Yes. See the wiki article *WeeWX v4 and logging .* It should be as simple as adding this to weewx.conf (NOT TESTED): [Logging] [[root]] handlers = console, On Thu, Jun 23, 2022 at 11:31 PM Stefano Vittorio Porta wrote: > Yup, it

Re: [weewx-user] LOOP try problem ...

The default is 1800 seconds. To change it, either see the guide that came with the logger, or use the utility wee_device with the --set-interval option. Did you try resetting the logger using the directions in the wiki section

Re: [weewx-user] LOOP try problem ...

This time, it is using hardware record generation. Did you change it? Also, the hardware archive interval is 1/2 hour, which may be longer than what you want / expect. When downloading archive records from the logger, it is starting from page zero, index zero, which is usually indicative of an

Re: [weewx-user] LOOP try problem ...

It appears that "debug" is not on, so the information in the log will be limited. However, I would guess that weewxd is having trouble connecting with your Vantage. Try setting debug=1 in weewx.conf, then restarting weewxd. Post the log from startup through the first reporting cycle. Also, any

Re: [weewx-user] Determine archive interval from within weewx

Generally, yes they are the same. Formally, the archive interval returned by the engine is the length of time it waits before attempting to create an archive record, whether via hardware, or via software. The value 'interval' in a record is the aggregation time of the values in the record. Off

Re: [weewx-user] Determine archive interval from within weewx

When you instantiate a service, one of the parameters is the engine instance: def __init__(self, engine, config_dict): The archive interval used by the engine can be obtained from it as engine.console.archive_interval -tk On Fri, Jun 10, 2022 at 11:07 AM 'Peter Fletcher' via weewx-user

Re: [weewx-user] Logging noise

Wow, you really like it quiet! I would think one more entry, this one for the engine, should do it: [[[weewx.engine]]] level = WARNING On Sun, Jun 5, 2022 at 2:13 PM drd...@gmail.com wrote: > I have been able to silence most log messages with > > # Whether to log successful

Re: [weewx-user] CWOP/APRS upload does not contain pressure data

Whatever works. Although I'd sure like to know why the in-the-box uploader doesn't work. On Sun, Jun 5, 2022 at 11:01 AM 'Ben' via weewx-user < weewx-user@googlegroups.com> wrote: > Yep, I installed the WeeWX aprs extenstion and configure aprx -- the > extension creates packets containing all

Re: [weewx-user] CWOP/APRS upload does not contain pressure data

I'm really not an expert, but I thought packets sent to CWOP were the same, except for their station ID (and passcode). At least, you're showing up in the findu database: https://www.findu.com/cgi-bin/raw.cgi?call=Dl1ben-13 Now that I look at it, the last 3 packets contain altimeter. Value is

Re: [weewx-user] CWOP/APRS upload does not contain pressure data

NB: CWOP requires *altimeter*. WeeWX needs station pressure (observation type "pressure") plus altitude to calculate it. It looks like altimeter is not the only thing you're missing. Precipitation and wind are also missing, which suggests are more general problem. I would look at the path data

Re: [weewx-user] Scaling Units for different reports

Exactly. That's the big advantage of assigning a type to a unit group. All the formatting and conversion machinery becomes available. On Sun, Jun 5, 2022 at 8:45 AM 'Peter Fletcher' via weewx-user < weewx-user@googlegroups.com> wrote: > Thanks! > I assume that this works 'out of the box'

Re: [weewx-user] Scaling Units for different reports

Sure. Just tell the report to use hours instead of minutes. For example, for tags, it becomes $week.sunshine.sum.hour For a plot, use option 'unit' in skin.conf. [ImageGenerator] ... [[week_images]] ... [[[week_sunshine]]] unit = hour sunshine All documented in

Re: [weewx-user] Barometric pressure uploading to Wunderground

I'm not familiar with the device, but perhaps the bme280 emits pressure more often? On Thu, Jun 2, 2022 at 10:07 AM Mark Fraser wrote: > On 02/06/2022 16:23, Tom Keffer wrote: > > Your rapidfire updates are not including "barometer". > > > > I suspect the reason i

Re: [weewx-user] Sunshine Database

That would make sense. I've had this same problem with pulse counters. Assuming that the sensor returns 0 or 1, one resolution is to use an accumulator that extracts the sum of values (rather than the default average). Then at the end of the archive interval, multiply the sum by the loop

Re: [weewx-user] Barometric pressure uploading to Wunderground

reporting cycle. > > 2. Please post a link to your WU station > > > > On Thu, Jun 2, 2022 at 5:29 AM Mark Fraser > <mailto:mfra...@gmail.com>> wrote: > > > > On 28/05/2022 13:21, Tom Keffer wrote: > > > On Fri, May 27, 2022 at 1:37 PM Mark

Re: [weewx-user] Barometric pressure uploading to Wunderground

2022 at 5:29 AM Mark Fraser wrote: > On 28/05/2022 13:21, Tom Keffer wrote: > > On Fri, May 27, 2022 at 1:37 PM Mark Fraser > <mailto:mfra...@gmail.com>> wrote: > > > > I've been using a WH1080 weather station with weewx via weewx-sdr for > >

Re: [weewx-user] Sunshine Database

My apologies, but I don't fully understand the problem. If the type you are trying to record is literally the amount of time the sun was out during the archive interval, then, in your example, why would no sunshine be recorded for the full 10 minutes? Wouldn't it be something less, but greater

Re: Private Nachricht betreffend: [weewx-user] Err111 Connection refused

>From the log, it looks like your username or password is wrong. If your password uses special characters, particularly spaces or the character '#', you must include it in quotes. You also have some other problems, including a missing extension ("user.alltime"), and an unknown type in one of your

Re: [weewx-user] Err111 Connection refused

t; tab to "Active" > > Tom Keffer schrieb am Mo., 30. Mai 2022, 17:27: > >> Well, something changed between 02:10:49 and 02:15:25. >> >> Can you connect directly to your FTP server using the "ftp" utility or >> something like filezilla? >>

Re: [weewx-user] Update extensions

Either will work, but installing new over old is easiest. On Mon, May 30, 2022 at 7:02 AM Mark Fraser wrote: > If I wanted to upgrade an extension to a newer version, do I uninstall > the old version and then install the new one. Or can I just install the > new version over the old? > > This

Re: [weewx-user] Err111 Connection refused

Well, something changed between 02:10:49 and 02:15:25. Can you connect directly to your FTP server using the "ftp" utility or something like filezilla? On Sun, May 29, 2022 at 10:49 PM weerman wrote: > Hi all, > > Since yesterday my data is not being uploaded via ftp anymore. > Taking a closer

Re: [weewx-user] weewx migration

There seems to be a bug in the real-time gauge extension. It is not checking for null values before attempting some arithmetic. I would suggest filing an issue with the extension's author: https://github.com/gjr80/weewx-realtime_gauge-data/issues On Sun, May 29, 2022 at 11:08 AM

Re: [weewx-user] weewx migration

I don't know much about the interceptor driver, but I would guess that there is something wrong with the sensor map. You have outTemp mapped to "temperature_4". Are you sure that's right? Another option would be to use Gary's Ecowitt driver . It uses the

Re: [weewx-user] weewx migration

Hard to say, but the most likely problem is that you have a 60 second archive interval. LOOP packets may not be arriving fast enough from your station to support that. For example, if your station emits outside temperature only once every 90 seconds, then many records will not contain any valid

Re: [weewx-user] weewx migration

Please read the directions in the link that John posted about how to get a good log. You gave us only 31 seconds worth. We need to see it from when weewxd starts up through the first reporting cycle. On Sat, May 28, 2022 at 1:27 PM hajsek...@gmail.com wrote: > I finally manage to make it work I

Re: [weewx-user] Barometric pressure uploading to Wunderground

Wunderground needs observation type "barometer," that is, the sea-level corrected pressure. To calculate this requires altitude, station pressure, outside temperature, and humidity. If you're missing any one of them, then the value will not be calculated. Double-check what's available. One thing

Re: [weewx-user] Voltage -- Decimal Places

$current.voltage.format("%.3f") See the section on formatting in the *Customizing Guide*. On Fri, May 20, 2022 at 6:56 PM Barry wrote: > Hi, using the Tempest Weather station, Weewx and Belchertown. > > The battery voltage

Re: [weewx-user] Weewx data stops at around 3 am every morning ....

It could be anything. A copy of the log would help. On Thu, May 19, 2022 at 12:13 PM Glenn Vadney wrote: > My weewx data stops processing every morning around 3 am. The logs > coincidentally show that cron / anacron are doing their thing at about that > same time as well. Does anyone else see

Re: [weewx-user] Recovered from crash => fail to start weewx

gt; > > > Anyways, once back at desk I'll surely check that. > > > > Thanks a lot for great pointer! > > > > BR, > > Juha > > > > > > > > ke 18. toukok. 2022 klo 15.38 Tom Keffer kirjoitti: > >> > >> The suffix "

Re: [weewx-user] DegreeDays accessible by a third-party application

Whatever works best for you... On Wed, May 18, 2022 at 11:52 AM PC wrote: > Yes, > but I need these values day after day. > What my old program was doing. > It therefore seems to me that the best solution is to create a specific > table. > I would create it with my old data, then I would read

Re: [weewx-user] DegreeDays accessible by a third-party application

Well, it would be easy enough to create a CSV file using a WeeWX template. It could then be imported into Excel. Something like... #for $month in $year.months #if $month.outTemp.has_data $month.dateTime.format($YM), $month.heatdeg.sum.format($Temp,$NONE,add_label=False),

Re: [weewx-user] DegreeDays accessible by a third-party application

You haven't said what your use case is. It might be quite simple. For example, here is how you would calculate total heating degree-days for this month in Python, using xtype. Most of the complexity is in calculating the starting and stopping times: import time import weewx.manager import

Re: [weewx-user] DegreeDays accessible by a third-party application

Degree-days are calculated on the fly as an xtype variable. Where do you need them? For example, for a template, the total degree-days for a month could be calculated as $month.heatdeg.sum. If you need access from an outside

Re: [weewx-user] Recovered from crash => fail to start weewx

The suffix ".TRG" is a trigger file. Why a trigger file would be associated with WeeWX, I have no idea --- they are not used anywhere in WeeWX. Were you using some custom code that uses triggers? Perhaps when you restored things, you didn't restore the trigger files? I'm not an expert at this,

Re: [weewx-user] Re: Davis Data Logger - Issue

engine: > Copied 0 files to /var/www/html/weewx > May 17 17:10:19 cactus python3[678]: weewx[678] INFO paramiko.transport: > Connected (version 2.0, client OpenSSH_7.6p1) > May 17 17:10:19 cactus python3[678]: weewx[678] INFO paramiko.transport: > Authentication (publickey) successful!

Re: [weewx-user] Re: Davis Data Logger - Issue

I don't see why the patch would stop the "Expected 99, got 0" errors, just make them less traumatic. For your find_rain_gust_day script, why not just use $month.rain.maxsum and $month.wind.maxtime? Look in the template NOAA-%Y.txt.tmpl for clues on how to calculate all these things using tags.

Re: [weewx-user] How to integrate daily values

Unfortunately, it is not possible, at least within the data framework of WeeWX. Normally, these kinds of summaries are generated from the WeeWX database, not the other way around. Your only option would be to create something like the NOAA summaries by hand, then include them on your web server.

Re: [weewx-user] Re: Davis Data Logger - Issue

All, Can you give this version of the driver a try? Rather than restart from the top, it tries a wakeup, then a retry. If that doesn't work after 3 attempts, then it does a restart. https://raw.githubusercontent.com/weewx/weewx/Issue_772/bin/weewx/drivers/vantage.py -tk On Mon, May 9, 2022 at

Re: [weewx-user] Just flipped drivers to Vantage, two questions

The Envoy is functionally identical to the VP2, which is why it reports itself as a VP2. I'm not as confident about the WLIP, but I think it's the same way. On Sat, May 14, 2022 at 8:52 PM Ryan Stasel wrote: > so I have another Envoy, and a Weatherlink IP... and I'm trying to get it >

Re: [weewx-user] Just flipped drivers to Vantage, two questions

Skins are left untouched by upgrades. The ET is probably being calculated in software. Try setting to hardware: [StdWXCalculate] [[Calculations]] ... ET = hardware I am reluctant to allow users to set hardware types to arbitrary values through weewx.conf because 1) it second guesses

Re: [weewx-user] Just flipped drivers to Vantage, two questions

I'm not sure why this matters. The identification is only for the tag $station.hardware. Otherwise, it is ignored. If you want your skin to say "VantageVue" (or, for that matter, anything else), just replace "$station.hardware" with your preference. Or, am I missing something? On Mon, May 16,

Re: [weewx-user] Reason: '<' not supported between instances of 'AggTypeBinder' and 'int'

These kinds of errors can be very difficult to find, and the Cheetah diagnostics don't help much. They refer to the line of the compiled template, which you don't have access to because it is a temporary file. It is possible to compile the template separately, then look at the output, but that's

Re: [weewx-user] Just flipped drivers to Vantage, two questions

1. Yours is a non-standard setup. I'd rather that the MB dev fixed his implementation. 2. That makes sense. 3. With a 60 second archive interval, it's possible that the console will occasionally not have seen the battery info, so it shows as N/A. With a 5 minute interval, it should consistently

Re: [weewx-user] Just flipped drivers to Vantage, two questions

1. The hardware type is determined by the WRD command. You can check what it's returning by setting debug=1, then restarting. Look at the log. The hardware type will be listed and look something like: May 12 15:22:59 nuc weewx[91691] DEBUG weewx.drivers.vantage: Hardware type is 16 For whatever

Re: [weewx-user] GW2000 & WH90 rain rate vs WH80 rain rate.

That's very cool! I'll be eager to see how your regression algorithms fare on future rainy days. On Wed, May 11, 2022 at 11:04 PM Stephen Hocking wrote: > Hi all, > > Thanks to Gary's patience in explaining how the Seasons skin works, I was > able to graph Piezo rain rate (WH90) vs the

Re: [weewx-user] Just flipped drivers to Vantage, two questions

1. I'm afraid I can't offer an opinion on this, because your arrangement is so non-standard. Normally, the station type is read out of EEPROM. 2. After 30 days, the logic in the skin gives up and figures the sensors are gone. So, you can either wait that long, or pare down the list of sensors in

Re: [weewx-user] Re: Ghost values in logger archive records

sons > 4.6) I'll find out just how happy it is. > > But I'll bet it's fine. Thanks again for your work! > > On Sunday, May 8, 2022 at 2:26:52 PM UTC-7 Rob Cranfill wrote: > >> Thanks, I’ll pop the new code in, a take a look after a bit, and let ya >> know. &

Re: [weewx-user] Re: Davis Data Logger - Issue

, e) > time.sleep(self.port.wait_before_retry) > else: > self.on_bad_read = False > self.pkt_count += 1 > yield loop_packet > break > > On May 8, 2022, at 2

Re: [weewx-user] Re: Davis Data Logger - Issue

Now that I think about it, there is an experiment I've been meaning to try. Right now, the Vantage driver tries 3 times, then gives up and restarts the program from the top. The experiment would be to do something not quite so drastic. Rather than restart the program, try a Vantage "wake up"

Re: [weewx-user] Re: Davis Data Logger - Issue

The "Expected 99, got 0" error is pretty common, especially after the logger has done a catch up. I have not noticed any correlation with the age of the logger. What kind of connection are you using? USB? Serial? Serial through a USB converter? The last (converters) are notoriously flaky. -tk

Re: [weewx-user] Re: Ghost values in logger archive records

Or just look for something in the log > files? > > > > > On Fri, May 6, 2022 at 10:24 AM Tom Keffer wrote: > >> Huge thumbs up to Bruce at Davis, who didn't let the ball drop. >> >> While we all know that VantageVues do not support extra sensors, what we >

Re: [weewx-user] Re: Ghost values in logger archive records

64', >>>>> 'inDewpoint': '27.247736039588684', 'inHumidity': '24.0', 'insideAlarm': >>>>> '0', 'inTemp': '64.9', 'maxSolarRad': 'None', 'monthET': '0.0', >>>>> 'monthRain': '0.0', 'outHumidity': '72.0', 'outsideAlarm1': '0', >>>>> 'outsideAla

Re: [weewx-user] Re: Merge database failed

If you want to add something to the database, you have two choices: 1. Create a new database using a custom schema, then transfer over the contents of the old database to the new database using the tool wee_database with the --transfer

Re: [weewx-user] Re: Merge database failed

My apologies, but I'm just not following this. There is no "upgrading" of the database. They are all the same. You can take a database from wview 15 years ago, and run it on a modern WeeWX with no changes. Now it's true that the *default* schema for WeeWX changed in V4.0 from the "wview" schema

Re: [weewx-user] Edit index after update

It's been dayUV, etc., since we parameterized the plots. However, some of the other skins use dayuv. Perhaps they got mixed up? On Sun, May 1, 2022 at 7:49 AM J Jones wrote: > I updated a few days ago and had to edit the index.html.tmpl to get the > UV images to update. Just wondering if it

Re: [weewx-user] Re: After installing Texas Weather driver from Matthew's github no in pick list

t;> I even tried modifying Mathew's install instruction to do so too but >>>>>> it had a run error so I guess that isn't going to work! >>>>>> >>>>>> I will try later after I rest my brain a bit, but am I correct in >>>

Re: [weewx-user] Re: After installing Texas Weather driver from Matthew's github no in pick list

uick port. There may be issues with how the driver >>>>> communicates with the hardware. Give it a try. >>>>> >>>>> You can find the port at https://github.com/tkeffer/weewx-twi >>>>> >>>>> On Sat, Apr 30, 2022 at 1:05 PM DR wrote: >

Re: [weewx-user] Re: After installing Texas Weather driver from Matthew's github no in pick list

d would be too >>>> nervous about goofing something up. I will wait patiently for the system >>>> to work, with revisions being passed along. >>>> >>>> >>>> Thanks for your attention, I'm anxious to try it, and will see if o

Re: [weewx-user] Re: After installing Texas Weather driver from Matthew's github no in pick list

being passed along. >>> >>> >>> Thanks for your attention, I'm anxious to try it, and will see if one of >>> my other stations will work. Do you know off hand if the Peet Brothers >>> driver (another station I have) is working with Python 3?

Re: [weewx-user] Re: After installing Texas Weather driver from Matthew's github no in pick list

t; Thanks for your attention, I'm anxious to try it, and will see if one of > my other stations will work. Do you know off hand if the Peet Brothers > driver (another station I have) is working with Python 3? > > Dale > > > > On 4/30/2022 2:54 PM, Tom Keffer wrote: > > The

Re: [weewx-user] Re: After installing Texas Weather driver from Matthew's github no in pick list

The problem is that the twi driver has not been ported to Python 3. I'll do the port and submit a PR to Matthew. Or, you can try Python 2.7. On Sat, Apr 30, 2022 at 12:22 PM D R wrote: > I did forget to mention that I found twi.py in the /usr/share/weewx/user > directory. It is puzzling to

<    4   5   6   7   8   9   10   11   12   13   >