Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

As this thread has drawn on I agree the solution is in the driver. I found it had to believe that a driver could have been around for so long with an incorrect 'pressure' being used and the issue never having come up before. Sure enough, this thread

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

if indeed, and i now tend to agree, the station displays and outputs a manually adjusted barometer which is set to a sea level reading from local weather stations and not pressure then barometer should be set to hardware and pressure and altimeter set to software, and not as i previously

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

OK… The “pressure” that your station is displaying is what it should be displaying: the ambient air pressure, correct for your altitude. In weewx, this is called “barometer” because that is what weather stations report for barometric pressure. “Altimeter” is basically the same thing; there

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

It is likely that I am mis-using the terms altimeter, barometer, and pressure. I'll clarify what I mean here. What I previously defined as 'correct' pressure is that the pressure reported by my station (LaCrosse WS-2813U-IT) matches the National Weather Service barometer reading (

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

What I am defining as 'correct' pressure is the barometer value that matches the local reading from the National Weather Service (NWS) for my area. In other words, the pressure on my weather station (LaCrosse WS-2813U-IT) matches what the NWS is reporting as Barometer (

Re: [weewx-user] png images for index.html not updating but the data is being updated and the /smartphone images are being updated

Another silly question, what would cause the updates to stop like that? It ran for a weekend with the new data logger attached to the console. I moved the data logger to the envoy and in less than 24 hours it froze and stopped updating. I did a weewx stop, wee_device --start , weewx start to

Re: [weewx-user] png images for index.html not updating but the data is being updated and the /smartphone images are being updated

> > I did clear the cache on Chrome. I even opened IE that I haven't used in >>> over a year and tried it but you're right, it's working now... LOL, I >>> don't know what happened. >> >> Could it take a while to update the png images? > >>> >> -- You received this message because you

Re: [weewx-user] png images for index.html not updating but the data is being updated and the /smartphone images are being updated

On Friday, February 14, 2020 at 5:32:18 PM UTC-7, Thomas Keffer wrote: > > They look OK from my end. Did you update the cache in your browser? > > On Fri, Feb 14, 2020 at 3:49 PM Troy Lass > > wrote: > >> Ok, I'm still fighting issues here but thought I'd start a new thread... >> >> Davis pro2

Re: [weewx-user] Re: users guide for python3 installation

I see now why I sent you the command to install python3’s configobj. The subject is python3 installation. Back to python 2... You should always update before you install. Let’s try to get things into better shape. Run the following commands in order: sudo apt-get update sudo apt-get upgrade

[weewx-user] Re: users guide for python3 installation

I am using python 2.7. I tried the sudo apt-get install python-configobj resulting in an error: Err http://mirrordirector.raspbian.org/raspbian/ weezy/main python-configobj all 4.7.7+ds-4 404 not found Failed to fetch

Re: [weewx-user] png images for index.html not updating but the data is being updated and the /smartphone images are being updated

They look OK from my end. Did you update the cache in your browser? On Fri, Feb 14, 2020 at 3:49 PM Troy Lass wrote: > Ok, I'm still fighting issues here but thought I'd start a new thread... > > Davis pro2 > Currently using envoy with brand new datalogger. I'd recently purchased > it to

Re: [weewx-user] Re: Belchertown station_observations bindings

I think I understand but to be certain; your Pi is only saving its values right to database? On Friday, February 14, 2020 at 6:43:28 PM UTC-5, mercurystorm wrote: > > I am not sending the data from the 2nd Pi via MQTT as it’s not real time > like wind etc from the weather station.. that data is

Re: [weewx-user] Re: Belchertown station_observations bindings

I am not sending the data from the 2nd Pi via MQTT as it’s not real time like wind etc from the weather station.. that data is being sent from mqtt on the main pi with the rtl_433 dongle On Fri 14 Feb 2020 at 23:07, Pat wrote: > Are you using MQTT for updates? If I recall from a few months ago

Re: [weewx-user] Re: users guide for python3 installation

Oops. That is correct. For python2, sudo apt-get install python-configobj > On Feb 14, 2020, at 3:21 PM, vince wrote: > >  >> On Friday, February 14, 2020 at 3:15:45 PM UTC-8, John Kline wrote: >> Try: >> sudo apt-get install python3-configobj >> > > That's not going to work with weewx

Re: [weewx-user] Re: users guide for python3 installation

On Friday, February 14, 2020 at 3:15:45 PM UTC-8, John Kline wrote: > > Try: > sudo apt-get install python3-configobj > > That's not going to work with weewx 3.9.2 which requires python2 (see my other reply from a minute ago) -- You received this message because you are subscribed to the Google

[weewx-user] Re: users guide for python3 installation

On Friday, February 14, 2020 at 2:49:44 PM UTC-8, david glenn wrote: > > I found my error and the setup.py was in the tar download. > Unfortunately, ./setup.py build fails to import configobj > I have been unable to download the module using: > > sudo apt-get install configobj > or > pip

Re: [weewx-user] Re: users guide for python3 installation

Try: sudo apt-get install python3-configobj > On Feb 14, 2020, at 2:49 PM, david glenn wrote: > >  > I found my error and the setup.py was in the tar download. Unfortunately, > ./setup.py build fails to import configobj > I have been unable to download the module using: > > sudo apt-get

[weewx-user] Re: Belchertown station_observations bindings

Also, is your raspberry pi submitting it's observations to the weewx loop, or only saving directly to a database? On Friday, February 14, 2020 at 6:07:14 PM UTC-5, Pat wrote: > > Are you using MQTT for updates? If I recall from a few months ago part of > the challenge is that the station

[weewx-user] Re: Belchertown station_observations bindings

Are you using MQTT for updates? If I recall from a few months ago part of the challenge is that the station observation box is updated from the MQTT data packets, and I don't think MQTT is multiple binding capable. So I could potentially update a 2nd binding on initial load, but not on MQTT

[weewx-user] Re: users guide for python3 installation

I found my error and the setup.py was in the tar download. Unfortunately, ./setup.py build fails to import configobj I have been unable to download the module using: sudo apt-get install configobj or pip install configobj in fact I cannot download 'pip' !!! what am I doing wrong? thanks

[weewx-user] Belchertown station_observations bindings

The station info box doesn't support multiple bindings... It's on my list of things to try and figure out but haven't had time to dedicate to it. Can you send me a sample of your additional database? I could use it as a sample set for testing. -- You received this message because you are

[weewx-user] Re: users guide for python3 installation

I was able to successfully download and expand the tar file ie. the checksums were correct. However, the next 2 statements stopped me: ./setup.py build sudo ./setup.py install ./setup.py: No such file or directory I tried ~$ python ez_setup.pybut no such file or directory How do I

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Thanks to everone who commented and esp Pat, I cleared browser cache, restarted weewx and closes browser page and reopened and now looks great, as I wanted. This [[roseplt]] was on the graph doc page so I copy/pasted it to graph.conf, Don't know why but removing it cured the [homepage] deal.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

Thank you, works a treat! I just have to remember to test new Interceptor versions then edit if needed. On Friday, February 14, 2020 at 11:36:59 AM UTC-5, Vetti52 wrote: > > When looking at interceptor.py version 0.53, there is not yet a wh40batt > sensor listed at the class ecowitt-client

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

When I deleted [[roseplt]] and put the [homepage] back in, no errors but there are now two wind roses. On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

I have [[chart5]] [[roseplt]] title = Wind Rose [[[windRose]]] It looks like I have the same brackets. The diff is [[roseplt]] Am I suppose to delete that? On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown

[weewx-user] Belchertown station_observations bindings

Heya I use rtl_433 to download my data which does *not* provide me with the inTemp, inHumidity and Barometer readings - I have set these up on a separate raspberry pi with a BMP280 and DHT22 and saving them to a separate MySQL database which i have then used multiple bindings to generate

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Your windrose isn't defined correctly. Replace it with this instead. Note the number of brackets. [[chart5]] title = Wind Rose [[[windRose]]] On Friday, February 14, 2020 at 3:20:21 PM UTC-5, ed100 wrote: > > here it is > > On Thursday, February 13, 2020 at 4:54:46 PM

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

here it is On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are a bunch of fields in the weewx mariadb database that I will > never use. I did some searching to how to do

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Send me your whole graphs.conf. On Friday, February 14, 2020 at 3:05:05 PM UTC-5, ed100 wrote: > > Pat, removed the [homepage] section at about line 35 thru line 42 in > graph.conf. I just copied the .conf from example. > > Then got errors: > Feb 14 14:00:28 localhost weewx[25495] INFO

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

When I put the [homepage] things back it errors went away. On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are a bunch of fields in the weewx mariadb database that I

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Pat, removed the [homepage] section at about line 35 thru line 42 in graph.conf. I just copied the .conf from example. Then got errors: Feb 14 14:00:28 localhost weewx[25495] INFO weewx.restx: MQTT: Published record 2020-02-14 14:00:00 CST (1581710400) Feb 14 14:00:28 localhost weewx[25495]

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Your customized graphs.conf has a Homepage section within it somewhere. Remove that and it should go away on next archive interval. On Friday, February 14, 2020 at 2:33:44 PM UTC-5, ed100 wrote: > > Thanks, i read on net and saw at least 5 different ideas about how to > comment. > I imagine it

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

John: Holy Cow, That is more than a 3 minute read, I heard that when a coder says he will have some piece of code done in 10 mins you think, that means 10 hours., Don't thinkI could read and understand it in 3 weeks. I did bookmark it. On Thursday, February 13, 2020 at 4:54:46 PM UTC-6,

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Thanks, i read on net and saw at least 5 different ideas about how to comment. I imagine it was a bad copy/paste. The screenshot shows Homepage kind of by itself. What I expected to happen was windrose where homepage is and cpu temp where windrose is. The way I get cpu temp is my bcrobotics

Re: [weewx-user] Re: Using Belchertown skin, Want to drop some database fields

A Cheetah user’s guide is here: https://pythonhosted.org/Cheetah/users_guide/index.html > On Feb 14, 2020, at 11:21 AM, Pat wrote: > >  > My guess is the --> was a bad copy/paste from something else. > > To comment a line, use 2 #'s. > > ## this is a comment. > > > >> On Friday,

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

My guess is the --> was a bad copy/paste from something else. To comment a line, use 2 #'s. ## this is a comment. On Friday, February 14, 2020 at 2:19:22 PM UTC-5, ed100 wrote: > > How do you comment lines in .tmpl? > Removing the --> fixed errors: > > Feb 14 13:15:32 localhost

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

How do you comment lines in .tmpl? Removing the --> fixed errors: Feb 14 13:15:32 localhost weewx[25227] INFO weewx.cheetahgenerator: Generated 11 files for report Belchertown in 1.61 seconds On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

There was "-->" somewhere in reference to page-header.inc? That's wrong so yes that should be removed. Not sure why that's there. Which extra homepage link? Your windrose and CPU temp are specific to your install (e.g. I don't have CPU temp). So I don't know what you're referring to. Can you

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

In this line: #include "page-header.inc" --> so I made it #include "page-header.inc" and restarted weewx, waiting to see if that fixed it, bet it does. Now if I can also get rid of the extra Homepage link just before the windrose and cpu temp. You think that

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

skins/Belchertown/page-header.inc I'm not sure what that last error is all about but it mentions this file. On Friday, February 14, 2020 at 2:05:09 PM UTC-5, ed100 wrote: > > Not sure --I will look, where do I find page-header.inc? > > On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Not sure --I will look, where do I find page-header.inc? On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are a bunch of fields in the weewx mariadb database that I will >

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Did you make any changes to page-header.inc ? On Friday, February 14, 2020 at 1:53:49 PM UTC-5, ed100 wrote: > > I downloaded weewx_data.json.tmpl and I am using the beta. > > Restarted weewx with the new .tmpl and got following error: > > Feb 14 12:50:30 localhost weewx[24717] INFO weewx.restx:

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

I downloaded weewx_data.json.tmpl and I am using the beta. Restarted weewx with the new .tmpl and got following error: Feb 14 12:50:30 localhost weewx[24717] INFO weewx.restx: MQTT: Published record 2020-02-14 12:50:00 CST (1581706200) Feb 14 12:50:31 localhost weewx[24717] ERROR

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Ah, yes this error a Belchertown error. I see why, I don't have the conditional wrapped around it. Oops. I just pushed a commit to fix it . You're using the beta version of the skin, replace your

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

I would expet you to be reporting barometer = sea level pressure which is pressure adjusted for temperature and altitudebecause weather stations always report sea level pressures. Is what you call 'correct' pressure the raw pressure of the instrument or a pressure which you have set. Does the

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

got related error--from syslog: Feb 14 10:45:33 localhost weewx[22817] INFO weewx.restx: MQTT: Published record 2020-02-14 10:45:00 CST (1581698700) Feb 14 10:45:33 localhost weewx[22817] INFO user.belchertown: version 1.1b8 Feb 14 10:45:34 localhost weewx[22817] INFO user.belchertown: New

Re: [weewx-user] 'ascii' codec can't decode byte 0xc3

Looks good! If I could contribute, here we go! Thanks! Am Donnerstag, 13. Februar 2020 21:42:44 UTC+1 schrieb Thomas Keffer: > > There’s no reason not to try it. A gettext() solution could easily be > implemented using search list extensions. > > Now that I think about it, it would be a good

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

When looking at interceptor.py version 0.53, there is not yet a wh40batt sensor listed at the class ecowitt-client (Consumer). You may insert in interceptor.py after line 2249 wh65.batt an extra line like 'wh65batt': 'wh65_battery', 'wh40batt': 'wh40_battery',

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

I can do it. On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are a bunch of fields in the weewx mariadb database that I will > never use. I did some searching to how to

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Sure, make sure you have database backups just in case. Try removing the radiation column from the archive table, and drop the entire archive_day_radiation table. Then disable the StandardReport skin as mentioned above in weewx.conf, then restart weewx and see what errors you get. On

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Not public. After I got the error, I put radiation/day radiation back into database so can't go back and look at logs or test. I could drop the column and test it. Do I also need to drop the archive_day as well? On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

You've lost me slightly. Is your site public that I could take a peek at? If you disable the Standard skin in weewx.conf by setting enabled=false under [[StandardReport]], then restart weewx, does the error in syslog clear? On Friday, February 14, 2020 at 10:51:20 AM UTC-5, ed100 wrote: > >

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

Andrew, that's a good questions; let me clarify. This issue started when Weather Underground (WU) stopped showing my station on the maps. I found out that was because I was reporting an incorrect barometric 'pressure.' As I dug into the details I found that my *station *was displaying the

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Pat: got it. I sent cpu temp as extraTemp1, when I added extraTemp1 to station_observations it did not get added till I commented out the if statement so for some reason weewx didn't think there was data but there was. When commented out displays next to radar just fine and graphs at bottom

Re: [weewx-user] Re: Using Belchertown skin, Want to drop some database fields

On Friday, February 14, 2020 at 7:33:38 AM UTC-8, John Kline wrote: > > Question for ed100–not necessarily the cause of the issue– > did you drop the archive_day_radiation table when you removed radiation > from the schema? > > > Agree. Most of the skins I've seen plot things conditionally if

Re: [weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Question for ed100–not necessarily the cause of the issue– did you drop the archive_day_radiation table when you removed radiation from the schema? > On Feb 14, 2020, at 7:28 AM, Pat wrote: > >  > It's in there as part of the code, but it should only be processed if there's > data. As

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

It's in there as part of the code, but it should only be processed if there's data. As defined by these lines here . The error you're having is with ImageGenerator, which Belchertown

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Wonder how radiation got into Belchertown/jason/weewx_data.json.tmpl ? On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are a bunch of fields in the weewx mariadb database

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Doesn't appear to be Belchertown related based on this line. Looks like something with the Standard skin you have loaded (which is saving output to /var/www/html/weewx) Generated 9 files for report StandardReport in 2.76 seconds Feb 13 15:50:44 localhost weewx[2940] ERROR weewx.reportengine:

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

>From syslog (right after this it just has usual MQTT publish, etc): Feb 13 15:50:34 localhost weewx[2940] INFO weewx.manager: Added record 2020-02-13 15:50:00 CST (1581630600) to database 'weewx' Feb 13 15:50:34 localhost weewx[2940] INFO weewx.manager: Added record 2020-02-13 15:50:00 CST

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

The log snippet you posted gave no context, a skin is trying to plot radiation but we can't tell which. You might be using Belcehertown but are you also still generating Standard or Seasons? The answer will be in the log, just needed to see a bit more :) Gary On Friday, 14 February 2020

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

It is in Belchertown/jason/weewx_data.json.tmpl On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote: > > I have the Belchertown skin with MQTT running nicely after some serious > help from folks here. > There are a bunch of fields in the weewx mariadb database that I will > never

Re: [weewx-user] Re: Using Belchertown skin, Want to drop some database fields

"radiation" has to be in there somewhere. It's not hardwired into WeeWX. On Fri, Feb 14, 2020 at 4:48 AM ed100 wrote: > Nope, the word radiation is not in skin.conf and not in graph.conf. Was > first thing I did was search for the radiation in Belchertown directory. I > just put radiation back

[weewx-user] Re: Using Belchertown skin, Want to drop some database fields

Nope, the word radiation is not in skin.conf and not in graph.conf. Was first thing I did was search for the radiation in Belchertown directory. I just put radiation back in database cause I didn't want to mess with any error trapping right now. I knew how I caused it. Thomas: I told you I

[weewx-user] Re: Interceptor empty queue

Hi everyone Problem solved, copied an old record sent from WH2600 into a bash script and with a cronjob every 5 minutes sending this record into the interceptor, weewx fetches all electricty and adds into the data base and updates an old weather record. Feel free to ask for the bash script.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

I am not sure I understand what you think is wrong with the readings of Pressure 29.89 Barometer 32.609 Altimeter 32.40 and why you believe something is wrong On Friday, 14 February 2020 05:57:36 UTC+2, Dan Blanchard wrote: > > Altitude is 2,320 ft. and the values are in the screen shot on the