On 14 January 2018 at 16:13, Praveen Chandrasekaran
wrote:
> Regarding 3 the data logger does have the data. So why can't the sql
> database be reconstructed?
>
Ah, you have a datalogger, and it's a Davis, I missed that.
The answer is - I don't know. An interesting
Regarding 3 the data logger does have the data. So why can't the sql database
be reconstructed?
One (hopefully last!) Question.
Does the script you have for rorpi setup work with stock systemd. In preinstall
step if I don't replace systemd with sysV does it still work ?
--
You received this
Update:
I upgraded my console to the latest and greatest firmware. Still seeing
network issues so the problem isn't the console firmware. I'm using an
Ethernet to WiFi bridge between logger and network. I think that is my
issue. Going to make some network changes to see if I can isolate my
Hi Praveen,
1) It will keep increasing in size as data is accumulated - the size will
be dependent on archive interval and time (measured in years usually!) I
wouldn't sweat on the size increasing to the point where it would be a
serious problem though, or at least not before you became aware of
I ask the question because whenever I put the heating on I see a change to
the barometer readings on my graphs which implies to me that the pressure
is changed (it appears to fall as the temperature rises). My console is
2/3 up the wall (too high to even read, but good for sensor reception!)
Thanks Glen for such a detailed reply. A few more questions as i m doing my
homework :)
1) The SQL database has data for how many days? 1 day? Wondering how it's size
doesn't just keep increasing
2) If i do rapidfire on WU, WU would also maintain its own archive from live
data i assume
Hi Praveen,
It's on the first page, but I agree that it probably doesn't leap out at
you. You can put it anywhere you like but the default is in memory.
The filesystem layout is defined around an apt install of weewx.
The directory /var/lib/weewx is moved into RAM and mounted as a tmpfs with
a
Yay!
"Finished installing extension '/home/pi/Downloads/weewx_snow.zip’"
> On Jan 13, 2018, at 3:24 PM, Joe Percival wrote:
>
> I think I found the problem here also… I found one section in the earlier
> configuration section where I had not used a closing brace.
>
>>
I think I found the problem here also… I found one section in the earlier
configuration section where I had not used a closing brace.
> On Jan 13, 2018, at 3:12 PM, Joe Percival wrote:
>
> Though this section is almost an exact duplicate of the mem extension
>
Though this section is almost an exact duplicate of the mem extension
install.py file, I am getting a syntax error on the last section of the
file.
File "/var/tmp/weewx_snow/install.py", line 48
files=[('bin/user', ['bin/user/snow.py']),
^
SyntaxError: invalid syntax
here is
That would do it, my understanding of the extension installer is that in the
archive everything needs to be under a single top level directory.
Gary
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop
Hello everyone,
I searched the group for this information, but couldn't find anything
related. My question: is there any advantage of importing WU over default
(out-of-the-box) Cumulus data?...specifically in regard to data
completeness? Do any additional fields get populated from either the
yes. though I have taken out the readme and changelog for the time being.
I have found the problem. I created the zip on a Mac and it created a second
directory inside the archive called _MACOS. That was confusing the installer.
Deleting that directory allowed the installer to proceed (and
I know you outlined your zip structure but it wasn't 100% clear to me. I
package in tgz format not zip but the structure I have in my tgz file is:
name
|
-- install.py
|
-- readme.txt
|
-- changelog
|
-- bin
| |
| -- directories/files to go in $BIN directory
|
-- skins
|
The reports are generated each archive interval so yes fairly frequently. The
problem is the process that generates the reports generates from the last
generated report to the current time, it doesn't 'fill in the gaps'. So when
you first did the import weeWX would have generated the early 2013
Good afternoon Gary,
Yes, the NOAA reports are what I'm talking about. I merely need to delete
these NOAA--mm.txt files and they get regenerated? What is the
regenerate frequency? Is it possible for me to regenerate these manually?
Okay, I just did it and answered my own questions. The
I have tried using the extension installer following the guidance from the
github wiki on an extension package created by modifying the mem extension
example. I do not understand the error message I am getting. Can someone
please explain where I've gone wrong?
My extension package is a
Hi,
Can you be a little more specific with what you mean by 'the new records from
April to Dec 2013 don't show up in the monthly or yearly HTML page'. I would
not expect data from 2013 to be appearing on the month or year page, as those
pages would be showing data from January 2018 and 2018
As far as I was aware the difference between pressure inside and pressure
outside is negligible (unless of course you live in a sealed house). So
deriving barometer and altimeter using inside pressure rather than outside
pressure has negligible effect. Of course if you use inside temperature
I began with a test of wee_import, first with --dry-run then without. I
then imported 1.5 months worth of 2013 data from from=2013-02-18
to=2013-03-31. This worked without a problem and the data showed up in the
monthly and yearly HTML page history.
I then went and modified the weewx.conf
And by the way, the console's firmware version is 1.1.6
--
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,
When I connect the station to a Windows VM, I can successfully read the
data using EasyTemp. So I tried to compare what EasyTemp and weewx are
sending on the USB bus, using wireshark. Unfortunately, although there are
obvious differences, I can't tell what's causing the error.
The two files are
Tom - this has always baffled me - when the pressure reading is taken from
an indoor console which is at a different temperature than outdoors. Maybe
Tom knows the answer - if one carries a console from inside at 20 degrees o
outside at 3 degrees does the pressure recorded on the console
The inside temperature does not enter the calculation. You are correcting
for the weight of the air column outside, which is a function of outside
density, which is a function of outside air temperature.
-tk
Fat-fingered from my Android
On Jan 13, 2018 8:59 AM, "'ml' via weewx-user"
Ok i got itwith the outside temperature value 3.2°C is 1025mbar with the
inside temperature 23.2°C it is 1020mbar so what is now correct air pressure is
measured inside
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from
Have you looked at the code as Tom suggested??
On the link I gave you there is a formula for the calculation which may help
Sent from Mail for Windows 10
From: 'ml' via weewx-user
Sent: 13 January 2018 17:54
To: weewx-user
Subject: Re: [weewx-user] Re: Barometric pressure correction the right
Also Vince, your approach looks lot more simpler than Glenn's approach. But
is there any downside to it?
On Saturday, 13 January 2018 21:38:21 UTC+5:30, Praveen Chandrasekaran
wrote:
>
> Again the same question as to Glenn. Where are the SQL databases stored?
> Are they still on the SD card?
>
Again the same question as to Glenn. Where are the SQL databases stored?
Are they still on the SD card?
On Saturday, 4 February 2017 05:26:34 UTC+5:30, vince wrote:
>
> On Friday, February 3, 2017 at 2:42:09 PM UTC-8, Glenn McKechnie wrote:
>>
>> The read-only pi that vince refers to is a HowTo
Hi Glenn,
Where are the SQL databases stored? Are they still stored on the SD card?
I could not get that reading your page or maybe I missed it.
Regards,
Praveen
On Saturday, 4 February 2017 04:12:09 UTC+5:30, Glenn McKechnie wrote:
>
> The read-only pi that vince refers to is a HowTo at
>
Sorry i didn't get how the barometric pressure is calculated with the
temperature, altitude and absolute pressure can you help?
--
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,
No problems Keith, plenty of younger folk here miss things just as plain :)
Gary
--
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
Gary,
My apologies for not seeing the forest for the trees.
After I found a formula for decoding decimal degrees to deg, min, seconds
what you said was correct. What I hadn't noticed was the 00.64*'. *This was
in minutes, not minutes and seconds as wview was.
Sorry for my lack of attention to
SOLVED. I think the problem was at the console. Took out the batteries,
disconnected the power then I took a dremmel tool and ground out some plastic
that seemed like it wasn’t allowing the data logger to fully seat because the
usb wire was binding. Went through the start up procedure exactly
Hello Maarten
I tried several times to upgrade my station from 1.1.2 to 1.1.4 firmware
through the ws tool app, But I didn't succeeded, I got the message download
fails.
So I cannot give you at this moment an answer if WOW works directly.
But with the weewx coupled to my station it is working
Hi,
Sounds like a bit of a clunky way to do things, but sticking to the question as
written...
One approach could be to write your own weeWX service that would check for your
file and act accordingly. Just subclass off class StdService (in
bin/weewx/engine.py), create a couple of methods that
35 matches
Mail list logo