[weewx-user] ecowitt ws80

the top of my ecowitt ws80 (the light sensor) has partly filled with condensation and stopped working. the rest of the ws80 is still working. is this ‘expected’ of an exposed ws80 (how else to get UV?) or is it a fault (demand a replacement)? Graham Eddy -- You received this

[weewx-user] Re: loop data with fineoffsetusb weather station

Yes, the FineOffsetUSB driver emits loop packets just as the simulator does it’s just that they are emitted much less frequently. You might find the FineOffsetUSB section of the Hardware Guide

[weewx-user] yearwindvec calculation problem

I noticed that something recently has gone wrong with my year wind vector graphic. The y axis is broken. This seems to have happened around the transition to 4.3 The monthwindvec graphic is ok [image: monthwindvec.png] but the yearwindvec y axis is scaled about 100 times too large [image:

Re: [weewx-user] Re: Rain Rate Calc Problem?

HI At the end of testing..starting from only seasons skin, MQTT disabled etc, direct run weewx, all the way to fully operational and not once did the rainRate cease to operate including shutdowns reboots etc. Simply could not fault it. We have had now rainfall last couple of days so I was

[weewx-user] Re: Need help: Bresser Weather 6in1 Pro WiFi and weewx Interceptor

The tool to import from WU is built into WeeWX. It is called wee_import. There may be an update for it though that is not part of WeeWXnot sure. I've actually never used it. I don't know what the data limit is nor how much you need to import. I suppose you could do it in chunks if

[weewx-user] loop data with fineoffsetusb weather station

can we have loop data with fineoffsetusb weather station for example wh1080 , like the simulator generating? -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

I don’t recommend reverting to 4.2 as it has some issues. The problem you are describing now is do to some issues in your db; specifically, intervals of 0 (4.3 is less forgiving). I found a thread to address it from Jan 6. I’ve pasted Tom’s response below. Rather than deleting records, if

[weewx-user] Re: No module named wmr200 (Weewx 4.3.0)

Ok, I see WMR200 has been removed in December 2020, and is now an extension. I install the extension, and I get more errors -- Logs begin at Wed 2021-01-20 16:50:14 CET. -- Jan 20 22:53:44 vegan python2[7867]: weewx[7867] CRITICAL __main__: File "/usr/share/weewx/weewx/manager.py",

Re: [weewx-user] No module named wmr200 (Weewx 4.3.0)

See the 4.3 change log here: https://github.com/weewx/weewx/releases The WMR200 driver is no longer supported. An unsupported version can be found at https://github.com/weewx/weewx-wmr200. Support for LaCrosse WS23xx and Oregon WMR300 will continue. > On Jan 20, 2021, at 1:46 PM, Invisible Man

[weewx-user] No module named wmr200 (Weewx 4.3.0)

Hey! What's happening?! I've upgraded weewx 4.2.0 to 4.3.0 (on a Raspberry Pi) and I get this error ! ``` Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Initializing weewx version 4.3.0 Jan 20 22:33:39 vegan python2[6532]: weewx[6532] INFO __main__: Using Python 2.7.16

[weewx-user] Re: Need help: Bresser Weather 6in1 Pro WiFi and weewx Interceptor

Sorry I cannot edit my previous post - So here as additional question - Do you maybe have the link to the weewx extension? Didn't find it here https://github.com/weewx/weewx/wiki. Steinwolf schrieb am Mittwoch, 20. Januar 2021 um 21:03:43 UTC+1: > Oh Ok. So I think I maybe misunderstood some

[weewx-user] Re: Need help: Bresser Weather 6in1 Pro WiFi and weewx Interceptor

Oh Ok. So I think I maybe misunderstood some posts I found online. So I dont pay anything aslong as I dont download the data to frequently? In some postings they say, that you have to pay after one year anyway. I saw the API thing before, but here you can only download the real time data, I

Re: [weewx-user] How to limit syslog logging

So taking your advice, I looked into the bme280wx.py file and noticed that there were a number of places where it was writing out information to various file; syslog, debug and user. When I commented those lines out, voila no more excessive logging. Thanks again tk Lee On Wednesday, January

Re: [weewx-user] How to limit syslog logging

Those things are generally set in /etc/rsyslog.d On Wed, Jan 20, 2021 at 10:54 AM LeaF wrote: > tk > Thanks for the observation. I'll do some snooping around the bme280 and > see what I can find. > > (It's not only syslog getting overwhelmed with entries, but debug and user > log files are

Re: [weewx-user] How to limit syslog logging

tk Thanks for the observation. I'll do some snooping around the bme280 and see what I can find. (It's not only syslog getting overwhelmed with entries, but debug and user log files are filled with the same info) Thanks Lee On Wednesday, January 20, 2021 at 10:50:01 AM UTC-8 tke...@gmail.com

Re: [weewx-user] How to limit syslog logging

It looks like an extension you are using, bme280, is what is creating the chatter. Unfortunately, from the little log snippet you gave, it does not appear to be WeeWX V4 compliant, so muzzling it will not be as easy as a weewx.conf setting. You could ask the author to update it to V4, then you

[weewx-user] How to limit syslog logging

I have a question regarding what goes into the /var/log/syslog file. I’m running the latest version of weewx on a Raspberry Pi 4. My station is a Peet Bros Ultimeter 100. I also added a Adafruit BME280 breakout board to measure pressure and humidity. This all works very well. Thank you

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

Thanks to Vince, Rich and all who took the time to investigate this problem. Happy that it’s not WeeWX or Belchertown, two fine programs! I hope to release my WXFeeds service extension within the next few days. Regards, Garry On Wednesday, January 20, 2021 at 8:19:32 AM UTC-8 vince wrote: >

Re: [weewx-user] Re: Huge Rainrate

Ah, there you go. Unless you ask for it, that's not what is going to get plotted or reported. On Wed, Jan 20, 2021 at 8:38 AM Karen K wrote: > It was the "max" field. > > tke...@gmail.com schrieb am Mittwoch, 20. Januar 2021 um 16:15:16 UTC+1: > >> Do you recall which field in

[weewx-user] Re: From MQTT to WeeWX

That was easy. Thank you very much, Rich. On Wednesday, January 20, 2021 at 4:34:20 PM UTC+2 bell...@gmail.com wrote: > After installation, you will need to update the MQTTSubscribeService to > look something like this. > [MQTTSubscribeService] > host = replace with your broker > # any

Re: [weewx-user] Re: Huge Rainrate

It was the "max" field. tke...@gmail.com schrieb am Mittwoch, 20. Januar 2021 um 16:15:16 UTC+1: > Do you recall which field in archive_day_rainRate showed the high value? > The schema for that table is > > CREATE TABLE archive_day_rainRate (dateTime INTEGER NOT NULL UNIQUE > PRIMARY KEY, min

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

Well FWIW, it's not Belchertown.I took my minimalist demo-skin and aded the one include line in it and boy does it grow. Two tests with a restart that's obvious. On Wednesday, January 20, 2021 at 7:07:23 AM UTC-8 garrya...@gmail.com wrote: > I haven’t made any changes yet but in

Re: [weewx-user] Re: weewx 4.3.0 uses Python 2.7 instead of Python 3

Thank you very much, the pointer to /etc/default/weewx was the solution. I changed the entry from python2 to python3. This then revealed after a restart of weewx an error within the forecast extension which led me to update the extension which removed the error and finally reports are

Re: [weewx-user] Re: Huge Rainrate

Do you recall which field in archive_day_rainRate showed the high value? The schema for that table is CREATE TABLE archive_day_rainRate (dateTime INTEGER NOT NULL UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count INTEGER, wsum REAL, sumtime INTEGER); If

Re: [weewx-user] Re: Huge Rainrate

Your are right. I looked for "rainrate" but it is "rainRate" (case sensitive). And "rainRate" is set from the data the WeatherLinkLive device sends. So it is nothing inside weewx. On the other hand the huge value in the summeries table (that the topic started with) did not come out of the

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

I haven’t made any changes yet but in thinking about your workaround, it will be interesting to see if Cheetah actuality processes the included include file or if it skips it because the outer include file’s attributes are static. If Cheetah doesn’t process the inner include file, it still

[weewx-user] Re: From MQTT to WeeWX

After installation, you will need to update the MQTTSubscribeService to look something like this. [MQTTSubscribeService] host = replace with your broker # any other MQTT options you need, like port, user, password, etc. [[message_callback]] type = individual [[topics]]

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

Very clever! Thanks!! I’ll give it a try in a few hours. Regards, Garry Lockyer C: +1.250.689.0686 E: ga...@lockyer.ca > On Jan 20, 2021, at 06:24, bell...@gmail.com wrote: > > Note, it is growing - just much slower. > >> On Wednesday, 20 January 2021 at 09:13:35 UTC-5 bell...@gmail.com

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

Note, it is growing - just much slower. On Wednesday, 20 January 2021 at 09:13:35 UTC-5 bell...@gmail.com wrote: > Garry, > I might have a workaround for you. Wrap your html file in a template. > something like this. > index.html.tmp (this is in the belchertown skin) > #include

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

Garry, I might have a workaround for you. Wrap your html file in a template. something like this. index.html.tmp (this is in the belchertown skin) #include index_hook_after_charts.inc index_hook_after_charts.inc (this is the 'wrapper', naturally if you 'owned' index.html.tmpl you would not need

[weewx-user] Re: GW1000 poll interval settings / limitations

There is no formal lower limit for the polling interval, though in reality it is effectively one second plus the time it takes for the driver to poll the GW1000, obtain the required data emit the loop packet (the one second limit comes from a one second delay in the loop that polls the GW1000).

Re: [weewx-user] Re: Huge Rainrate

I'm not familiar with the WeatherLink, but if it's like the other Davis products, it emits its own version of rainRate. By default, this is what will get used unless you have weewx calculate it in software. See the section [[Calculations]]

[weewx-user] Re: Huge Rainrate

>From /etc/weewx.conf: [Station] station_type = WeatherLinkLiveUDP # Options for extension 'WeatherLinkLiveUDP' [WeatherLinkLiveUDP] wll_ip = XXX.XXX.XXX.XXX poll_interval = 10 driver = user.weatherlinkliveudp hardware = Davis Vantage Pro2 Karen K schrieb am Mittwoch,

[weewx-user] Re: Huge Rainrate

The new value was much lower, but still very high. So I looked into the database and found that: sqlite> select dateTime,rain,rainrate from archive where dateTime>161096 and dateTime<1610964000; 1610960100|0.0|0.0 1610960400|0.0|0.0 1610960700|0.0|0.0 1610961000|0.0|0.0

Re: [weewx-user] Re: weewx 4.3.0 uses Python 2.7 instead of Python 3

The file /etc/default/weewx controls which version of Python to use. Look in there. However, it will not work unless the Python 3 prerequisites have been installed. If they have not, then you are better off following the instructions in the WeeWX Debian guide

[weewx-user] Re: Huge Rainrate

Now I found time to run wee_database --rebuild-daily --from=2021-01-17 After that, the value was much lower. Karen K schrieb am Dienstag, 19. Januar 2021 um 23:25:07 UTC+1: > Since yesterday I see a huge maximum monthly rainrate of 1280 mm/h. So I > searched the database using sqlite3

[weewx-user] Re: weewx 4.3.0 uses Python 2.7 instead of Python 3

Just to add that Python 3 works: root@brix:~# python3 --version Python 3.6.9 Rene schrieb am Mittwoch, 20. Januar 2021 um 12:56:27 UTC+1: > Hi all, > I'm running weewx 4.3.0 and it still uses Python 2.7 although I have > installed Python 3 and /usr/bin/weewxd contains: > > #!/bin/sh >

[weewx-user] weewx 4.3.0 uses Python 2.7 instead of Python 3

Hi all, I'm running weewx 4.3.0 and it still uses Python 2.7 although I have installed Python 3 and /usr/bin/weewxd contains: #!/bin/sh app=weewxd # Get the weewx location and interpreter. Default to something sane, but # look for overrides from the system defaults.

[weewx-user] Re: From MQTT to WeeWX

Update on example payload: {"time":"2021-01-20 13:28:57","model":"Solight-TE44","id":4,"channel":1,"temperature_C":-7.1,"mic":"CRC"} {"time":"2021-01-20 13:29:20","model":"LaCrosse-WS2310","id":242,"humidity":78} On Wednesday, January 20, 2021 at 9:44:52 AM UTC+2 Tarmo wrote: > The topics are

Re: [weewx-user] Re: Wmr 200 rain gauge replacement

Thanks everyone, I will definitly look at the Ecowitt GW1000 solution. Le mardi 19 janvier 2021 à 19:11:56 UTC+1, tke...@gmail.com a écrit : > Just to pile on, let me mention the WMR200 is no longer supported by > WeeWX. The API and driver are too frustrating. > > On Tue, Jan 19, 2021 at

Re: [weewx-user] Re: Database Backup File not a Database Error

I am in the process of industrialising my backups, but this script works from the command line and may give you an idea of how to backup your database without having to stop and start weewx. I will shortly have a post up on how to do this once I have it working properly On Wednesday, January

[weewx-user] Re: Generate failed with exception ''

Thanks all, You gave me the pointers on where to look and the issue was the sed command I was using, it as also updating group_altitude sed -i "s:altitude =.*:altitude = $WEEWX_ALTITUDE:g" /home/weewx/weewx.conf Changing it to sed -i "s: altitude =.*: altitude = $WEEWX_ALTITUDE:g"

[weewx-user] GW1000 poll interval settings / limitations

Question about shortening the poll interval an implications / recommendations... My setup is I’ve got 2x GW1000’s both reading lots of “shared” sensors but one reading at WS80 and one reading a WS68. I then have 2x Raspberry Pi’s concurrently, both running the API in driver mode and receiving