Well you already have the data in a file - weewx.sdb - the database file!!!
You can convert the archive table inside the database to a .csv file just
by using the SQLite commands
http://www.sqlitetutorial.net/sqlite-tutorial/sqlite-export-csv/
should tell you how to do this. Your best
Thanks for the replay, what I'm trying to do is basically collecting
accumulated data from the weather station and storing it into an excel file
(or text file), it doesn't matter the way of creating the data file as long
as the results contain the basic weather variables (OutTemp, InTemp,
It would help if you were much more specific!!
Yes, a csv file can be created instead of a .html file by adding a new
'report' using a template for example called newreport.csv.tmpl and have
cheetah create the file every archive interval. Note - every archive
interval will keep overwriting
Ok, let's see if we can get that 1st para to make a bit of sense:
This part of your log extract shows two different processes (1393 and 1338)
trying to communicate with your station, it happens if you start WeeWX again
without stopping it first or doing a restart:
Gary
--
You received this
Hi,
On Saturday, 23 February 2019 14:35:53 UTC+10, Mohamed Al-Sabri wrote:Ouh
> OK now I understand the interval thing!
> How do I know that I’m running two instances? I’m not sure how to kill one
> of them or which one I kill in order to get the data.
>
This part of your log extract shows
Ouh OK now I understand the interval thing!
How do I know that I’m running two instances? I’m not sure how to kill one of
them or which one I kill in order to get the data.
Mohamed,
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
1. You have two instances of WeeWX running. Kill one of them.
2. Your Vantage is set up for a 30 minute archive interval. You're not
going to see anything unless you wait at least that long.
3. If you want a shorter archive interval, use the wee_device
--set-interval=5 command. Yes, it will erase
> 2. You need to set your vantage archive interval to the same as what you
> have in weewx.conf - use wee_device to change the console
>
>
> sudo wee_device --set-interval=5
>
>
>
>
>
>
> 2.6.0.0
>>> 2.6.0.0
>>
> 2.6.0.0
--
You received this message because you are subscribed to
1. You need to sort out the cause of the undervoltage errors which are
filling your log.
2. You need to set your vantage archive interval to the same as what you
have in weewx.conf - use wee_device to change the console
3. Can you give a directory listing of /home/weewx/public_html please.
thanks Peter for the replay! yes now I do have a more clear idea of how do
the archiving thing work!
but, still I can't get any use of it >,< What I'm able to do until now is
just displaying the current data.
On Wednesday, February 20, 2019 at 6:17:35 PM UTC+4, Peter Fletcher wrote:
>
> I hope
I hope that you understand that the 'archive' can only go back as far as
the current data stored in the logger when you first connected it to weewx.
Even if you previously had it connected to Weatherlink, weewx has no way of
accessing any older data. How far the logger's data goes back in time
I hope that you understand that the 'archive' can only go back as far as
the current data stored in the logger when you first connected it to weewx.
Even if you previously had it connected to Weatherlink, weewx has no way of
accessing any older data. How far the logger's data goes back in time
Have you been able to get the built in reports to work for you?
If so, do they display what you need? Any particular reason why you think
you need to go directly to the database instead of just modifying the
reports?
If not, you'll have to give us more information about what you are doing.
See
Hello!!
I'm completely new to the weewx, and I have been in the past 3 days
learning and connecting my weather station to the RPi3 via Data logger usb.
I was able to have it run and showing the current data. However, I have
struggled in playing with the archive. I have completely no idea how
14 matches
Mail list logo
