On Monday, 23 January 2017 15:20:59 UTC-8, Louis De Lange wrote:
>
> This is a question about writing records to 3rd party databases such as
> Meteotemplate.
>
> In addition to WeeWX I have a site running Meteotemplate with it's own
> MySQL database. The nor
This is a question about writing records to 3rd party databases such as
Meteotemplate.
In addition to WeeWX I have a site running Meteotemplate with it's own
MySQL database. The normal way of filling the Meteotemplate database is
through clientraw.txt or realtime.txt and cron jobs, but I
On Monday, 23 January 2017 15:37:18 UTC-8, Tom Keffer wrote:
>
> On Mon, Jan 23, 2017 at 3:20 PM, Louis De Lange <kilo...@gmail.com
> > wrote:
>
>>
>> 1. The meteotemplate database uses a type datetime primary key, rather
>> than unix epoch
On Monday, 23 January 2017 16:12:33 UTC-8, mwall wrote:
>
> louis,
>
> it sounds like you have 'direct deposit' to meteotemplate under control,
> but here is a different approach: a meteotemplate uploader:
>
> https://github.com/matthewwall/weewx-meteotemplate
>
> it is based on this
On Monday, 23 January 2017 16:25:26 UTC-8, Louis De Lange wrote:
>
>
>
> On Monday, 23 January 2017 15:37:18 UTC-8, Tom Keffer wrote:
>>
>> On Mon, Jan 23, 2017 at 3:20 PM, Louis De Lange <kilo...@gmail.com>
>> wrote:
>>
>>>
>>> 1.
On Tuesday, 28 February 2017 07:50:50 UTC-8, vince wrote:
>
>
> I run weewx on a computer with 128MB RAM, if that helps any.
>
> One thing to watch for is the forecast extension, which can use a 'lot' of
> memory (or it did for me), but weewx plus a couple skins is very light
> typically.
>
1.I cant find a version number on the download zip file or the
interceptor.py file - I can tell you that I downloaded the driver on July
25, 2016
2.
On Monday, 5 September 2016 17:42:57 UTC-7, mwall wrote:
>
>
> which version of the interceptor driver are you using?
>
> how are you
1. I cant find a version number on the download zip file or the
interceptor.py file - I can tell you that I downloaded the driver on July
25, 2016
2. I am using Weather logger V2.1.9 firmware, so I send the data directly
to the same port that Interceptor is configured to monitor
3. It does
I was not suggesting using FreeBSD - I simply mentioned that using it might
contribute to overall system stability.
My point was that FO supplies some of their stations with the Observer receiver
module (and accompanying indoor pressure sensor). There is no indoor console
required and hence
n/user/imageStackedWindRose3.py
>
> Note this file has the import Image/ImageDraw fix from a few days ago so
> that issue should not give you any more grief. Thanks for pointing out the
> issues.
>
> Gary
>
>
> On Wednesday, 14 December 2016 03:11:47 UTC+10, Louis De
Correction on previous post - the StackedWindRose segment in the weewx.conf
file only occurs once - I copied the text twice by mistake on posting.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving
Gary,
Thanks for that. I changed it to windSpeed and it worked!
Now the really perplexing thing - my station provides gust data (even
though it appears in 4km/h increments). I know windGust is in the database
and to prove it I ran a query shown below listing the dateTime, windSpeed
and
I have a strange issue with the wdStackedWindRose template and would
appreciate enlightenment.
I get the following in the log:
*Dec 11 09:01:30 goflexhome weewx[22115]: reportengine: Unable to
instantiate generator
user.imageStackedWindRose3.ImageStackedWindRoseGenerator*
*Dec 11 09:01:30
On Saturday, 10 December 2016 18:59:27 UTC-8, mwall wrote:
>
> On Saturday, December 10, 2016 at 9:27:02 PM UTC-5, Louis De Lange wrote:
>>
>> It was absolutely a matter of formatting. With the right formatting I
>> can round to whole numbers of rain or snow.
>>
Thanks for a really great tool, and in general thanks for all the support
you and Tom and others are providing.
I am currently using version 3.08, and it has an issue that the forecast
quantities for rain or snow are in US units.
Although I can change the display units to metric, the
Tom,
Absolutely agree about saving the incremental data, which is what I am
really after.
The reason I am also saving the cumulative data and using the last saved
record to calculate the current incremental value is to limit an error that
will be present if my server goes offline for a few
This question is more related to python programming than using weewx, but I
cant find a solution - so I hope that Tom and the other gurus can point me
in the right direction.
I am writing a function to capture power consumption from the utility
meter. As part of that I am storing the
Just upgraded two separate systems to 3.7.1 with no problems whatsoever -
one running a Fine Offset Observer with MySQL on FreeBSD and one running a
Vantage Pro with SQLite on Arch Linux on a Seagate Goflex Home ARM5.
When a new release comes out and it seems like there are lots of problems
It's a wunderground thing. Your log will say that records have been
uploaded correctly, but they are mysteriously missing.
Use the utility wunderfixer that comes with weewx to fill in the missing
data.
On Thursday, 16 March 2017 14:22:14 UTC-7, Theophanis Kontogiannis wrote:
>
> Hello all.
>
On Tuesday, 14 March 2017 14:25:11 UTC-7, Hayden Thring wrote:
>
> thanks, was wondering about doing it too, just not sure where to go, so
> thanks.
>
Hayden,
On what router are you running weewx? How much flash memory and how much
ram do you have. I considered installing weewx on OpenWRT
While there seem to be great excitement for the new meteotemplate uploader,
I previously wrote a service that updates my meteotemplate database
directly without an intermediate php script. In the service i use a
."getSql("INSERT INTO" statement. This works really well and I even
resolved the
Tom,
I can monitor for the "(2006, 'MySQL server has gone away')" error with
the try statement. Perhaps I can use that to restart the connection to the
mysql server, as long as I know the command to use? This way you dont have
to change the driver.
On Thursday, 1 June 2017 05:46:43
As a previous owner of a Fine Offset station I can confirm that I noticed
this same behavior. Living in Canada where our homes are heated, I could
clearly see the altimeter reading (my station did not support barometer
correction to sea level) seesaw with the furnace operating and shutting
Thanks Gary. Works like a charm, simple.
On Sunday, 28 January 2018 12:48:00 UTC-8, gjr80 wrote:
>
> Hi,
>
> Why not do it directly in your template rather than via weeWX dot codes? I
> think $$ should produce a literal $ in a cheetah template. Maybe something
> like:
>
>
Busy redoing my website template with MaterializeCSS framework.
To correctly create the dropdown for the various NOAA summaries I have to
create an href tag as follows:
$monthYear
Without the .txt suffix the NOAA-$monthYear tag works fine, but as soon as
I add .txt to make
Thanks Tom,
Backslash escape character did not work but following the cheetah manual
and enclosing the variable in brackets did.
$monthYear
Might be useful for other people too.
On Sunday, 18 February 2018 18:35:18 UTC-8, Tom Keffer wrote:
>
> Try putting a backslash in front of any special
I have a remote site that I want to connect to my home network using MQTT
and utilize minimal data transfer.
The plan is to have weewx on one Raspberry Pi Zero at the remote site
receiving the data from the weather station, archive it and publish to a
MQTT broker using mwall's MQTT
y.
>
> Also, my guess would be you want aggregate since that will put all
> observations in 1 published message, as opposed to individual topics like
> weather/outTemp, weather/humidity, weather/barometer, etc.
>
> Hope this helps a little bit.
>
>
> On Saturday, Septe
Gary,
Good point about the time to complete the reports, I will keep that in
mind.
At this stage with 2 years of data my report cycle takes only a few
seconds, but with more data it will eventually become a problem.
--
You received this message because you are subscribed to the Google
In a template am trying to create a table showing the average temperature
for the month to date and then a historical list of the avg temp for all
months in the datebase.
I tried doing this with the iterators and I note the following example in
the customization guide
#for $month in
Gary how did you know that ?! - It works ! Thank you.
--
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 weewx-user+unsubscr...@googlegroups.com.
For more options,
I have created my own html template and I am playing around with adding
some stuff that require the use of the template iterator - I asked a
related but different question about that yesterday.
I just noticed that calling any $month tag before I invoke *#for month in
year.months* iterator the
Gary,
I just want to confirm that you suggested approach with alltime works, and
further I can iterate a *year.months* loop within an *alltime.years* loop.
For the benefit of anyone else, the code to print the avg temperature for
every month in the database is as follows:
Richard,
If you read through the restx.py file that controls all of the restx
services such wunderground uploads you will notice a number of parameters
that can be specified, such as post_interval and server_url. When you read
through the user guide you might notice that these specific
I need WeeWX to post a request to this public endpoint. (besides
> updating WU and CWOP) :)
>
> Hope this clarifies my needs
>
> Best regards
> Richard
>
>
>
> Op za 27 okt. 2018 om 22:45 schreef Louis De Lange >:
>
>> Richard,
>>
>> To
On Wednesday, 12 December 2018 08:24:48 UTC-8, P Simmons wrote:
> Please define "pretty close".
> Thanks!
>
Check it out for yourself on the website below.
The only thing that is slightly off is the humidity and this is due to the
mounting of the sensor in a box that allows the
Pat, one more thing that's is really useful is that the weather board has an
extra RJ11 connector with 3 spare analog input channels that can me used for
additional sensors such as solar, etc.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
I recently came across a really excellent solution for putting together
your own weather station on the cheap with high quality sensors - and most
importantly a very useful weather HAT to use with a Raspberry PI to connect
all the sensors.
It comes complete with a 4 part step by step tutorial
In my BYO station I noticed strange notches in the barometer graph that I
cannot explain
Since barometer is calculated by weewx in this case I am trying to
understand the cause, I cannot imagine that the formula for calculating
barometer from pressure will cause this. If anyone has any idea
wrote:
>
> @Louis De Lange, thanks for mentioning this. By any chance, do you recall
> where you read that FineOffset was using indoortemp for pressure
> calculations?
>
> On Sunday, January 14, 2018 at 2:35:33 PM UTC-5, Louis De Lange wrote:
>>
>> As a previous owner
k that are
> not included in the tutorial in order for your code to work.
>
> Any other pointers would also be appreciated
>
> Thank in advance!
>
> On Wednesday, December 12, 2018 at 5:53:25 AM UTC+2, Louis De Lange wrote:
>>
>> I recently came across a
I tried this method of updating today as well. Jan 29 and 30 simply fails. Jan
31 appears to upload missing data successfully, but the data never shows up at
on WU.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
Time to revisit this old post as I finally spent some time with morrowwm's
wxMesh driver to make slight modifications required for this use case.
It has been working well for the last week and I am making it available in
case it may be useful for someone else. If there is sufficient interest
43 matches
Mail list logo
