I updated to 3.7.0 and had MySQL bin log_format error and replication
stopped.
I edited the pi my.cnf and added binlog_format=row but I left the NAS
format as mixed.
weewx happy with its config and replication started without a problem.
Nev
On Monday, March 20, 2017 at 6:10:56 AM UTC+10, Nevi
On Mon, Mar 20, 2017 at 8:34 PM, gjr80 wrote:
> Since you have rapidfire on WU should be being fed the loop windSpeed
> values. The loop windSpeed values appear in gauge-data.txt in the wlatest
> field not the wspeed field you are using; wspeed is the 'average wind
> speed' which will be the aver
Since you have rapidfire on WU should be being fed the loop windSpeed
values. The loop windSpeed values appear in gauge-data.txt in the wlatest
field not the wspeed field you are using; wspeed is the 'average wind
speed' which will be the average wind speed over an archive period or 5
minutes d
Good work, I must admit I had been stuck in the 'file transfer' paradigm
rather than 'data transfer' and whilst I have had loop based RSYNC working
on my LAN there was too much contention for my liking. I will have have a
look at this and see how your approach works for me.
Gary
On Tuesday, 21
On Tuesday, 21 March 2017 12:28:02 UTC+10, Alec Bennett wrote:
>
> I made a quick page that updates some data from the real time gauge using
> Ajax:
>
> sinkingsensation.com/wind
>
> It takes some data from live_data.json (currently wspeed, wgust, bearing,
> domwinddir) and displays it, updating
And comparing the page I just made (sinkingsensation.com/wind) to my
Weather Underground page
(https://www.wunderground.com/personal-weather-station/dashboard?ID=KCAPETAL93#history),
the data is slightly different. Does anyone know what data the WU updater
uses, and why it would be different?
I made a quick page that updates some data from the real time gauge using
Ajax:
sinkingsensation.com/wind
It takes some data from live_data.json (currently wspeed, wgust, bearing,
domwinddir) and displays it, updating every 2 seconds.
I'd like to add the highest gust of the day though, and I'm
Be sure I will do it.
El 20 mar. 2017 9:12 p. m., "Alec Bennett" escribió:
> Please post your progress, I'm also interested in doing this.
>
> In the past I experimented with doing this with a Moteino (
> https://lowpowerlab.com/guide/moteino/), and found an Arduino script that
> could in theory
Please post your progress, I'm also interested in doing this.
In the past I experimented with doing this with a Moteino
(https://lowpowerlab.com/guide/moteino/), and found an Arduino script that
could in theory be used with a Moteino to get the data from a Davis ISS,
but I couldn't get it worki
I really like the wind gauge on Weather Underground:
https://www.wunderground.com/personal-weather-station/dashboard?ID=KCAPETAL93
I'd like to make something similar using the Realtime Gauge extension and
an ajax call. Does anyone happen to know of a starting point that might
already exist?
-
>
> The short answer to your question is no, nothing like that exists at the
> moment. If you have your web server (or process that wil use
> gauge-data.txt) on your weeWX machine then it is a simple matter for the
> generated file to be saved wherever you want, but if you need to transfer
> t
Yes, Luc's modifications have been incorporated into the driver.
Please set debug=1, restart weewx, then post the entries around the "No
" message.
Also, what model of logger are you using? Do you use a serial-to-USB
converter?
-tk
On Mon, Mar 20, 2017 at 7:31 AM, Rune Laegreid wrote:
> Hi,
>
Hi,
I am diving into this old conversation with a question.
Has this issue been solved and distributed in the latest weewx release?
My Vantage Pro2 fails once a fortnight or so and every third to fifth time
I restart the service I get the error message:
Vantage: No received from console.
I am
Unfortunately, no.
I suppose one could write a driver extension to extract the highs and lows
from the console, then use them for reporting purposes. But, that's a
completely different architecture from weewx, which uses the database to
calculate highs and lows. But, if you're good with Python, it
Apparently what I wrote as a bit missleading.
Tom & Andrew, you are totally right. I was talking about the records for
high/low of the days/month and years in the console memory. Somehow I
thought that weewx will get ahold of it and incorporate it into the reports.
Tom: The logger contains 1MB
I didn't think there was a memory on the vp2 console itself - just high low
values for day, month and year - and to have more retained you needed a
weatherlink logger or similar.
Am I wrong? What data do you actually have within the console itself
rather than in the logger?
Maybe I'm not unde
I'm not sure what you are referring to. The console has some memory for
odds and ends like the graph on its screen, highs and lows, etc., but it
does not store data records. Only the logger does that.
A standard Davis logger holds 2560 records. For a 5 minute archive
interval, that's just short of
I once edited my database, when my rainmeter didn't function as it should.
For testing, after cleaining it, I poored some water through it, an ended
up with exceptionally high rain rates in my database...;) I deleted those
manually afterwards. This might be the cause. Furthermore, I once had a
Hi Tom,
thanks for your reply.
I tried your suggestion with the wee_device --dump command (after backing
up the sql db)
It seems that the tool dumped all records out of the logger memory, which
go back until yesterday 16:30 but it does not get ahold of the data stored
in the VP2 console memory
19 matches
Mail list logo
