I was able to restore all the data, doing as I planned: (i) the records
collected during the power outage have been recovered from davis data
logger, (ii) the subsequent records were already in the database but with
wrong dateTime, so I just fixed its value shifting it 118m in the future.
Then,
Today I had a power outage, from the 06:01 CEST to the 07:51 CEST.
So the last record added by weewx before the outage was at 06:01 CEST. From
logs (reporting here only last two lines):
pi@raspberrypi:~ $ journalctl -b -1
Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO
c-missing that
> is misbehaving.
>
> Gary
>
> On Wednesday, 17 August 2022 at 10:27:55 UTC+10 tke...@gmail.com wrote:
>
>> Just a long shot, but are you running weewxd while doing the import?
>>
>> On Tue, Aug 16, 2022 at 4:09 AM Andrea Di Saverio
>> wrote:
>>
&
f.max_delta_12h)
File "/usr/share/weewx/weewx/manager.py", line 438, in getRecord
(time_start_ts, time_stop_ts, timestamp))
File "/usr/share/weewx/weedb/sqlite.py", line 44, in guarded_fn
raise weedb.OperationalError(e)
weedb.OperationalError: da
Ok, then I will go for the third solution, and use the `wee_database
--cal-missing` utility.
Thank you so much for your support, I'll let you know about the result.
Il giorno lunedì 15 agosto 2022 alle 22:46:53 UTC+2 gjr80 ha scritto:
> Yes, that explains why those five derived obs were not
Hello gjr80,
sorry for my late reply, it has been a busy week, and thanks for got tested
my data.
I was unable to dig out something useful from logs: we can consider them as
gone.
Anyway: checking my `/etc/weewx/weewx.conf` I remembered I have this
configuration:
[StdWXCalculate]
Thanks for your answer.
The two conditions you listed are satisfied: the necessary other values are
present in my csv, and no records were already existing for such period in
the database.
Answering your questions:
- Those are my data (a sample):
CSV data (more fields than used in the
I imported ~1 year of data from csv, using this `import.conf` configuration:
source = CSV
[CSV]
file = my-data.csv
interval = 1
qc = True
calc_missing = True
ignore_invalid_data = True
tranche = 250
UV_sensor = False
Sorry for my late replay.
Yes, the suggestion solved my problem. I was not installing as root user.
Thank you.
Il giorno giovedì 4 agosto 2022 alle 01:46:26 UTC+2 david@gmail.com ha
scritto:
> @disaveri Did this solve your problem?
>
> Btw: I released 2.0.1 which resolves the
Hello,
not sure if this is the right place or if it's better to start a new
thread. In that case, please let me know.
Anyway...
I was trying to install Daveiano's skin to my weewx installation, on my
raspberry, but the attempt failed. This the log:
pi@raspberrypi:~ $ wee_extension
nt types of hardware and to
> be very configurable. Hence the many stages and options.
>
>
> On Sun, Jul 31, 2022 at 3:17 PM Andrea Di Saverio
> wrote:
>
>> Thanks for your explanation, but still I didn't get a point:
>> values in my weewx database are simply read
ecord. With loop_request=1, the value will be from pure software, with
> loop_request=2, it will be from the Davis hardware.
>
> 3. It's true, so this question is moot. However, I will add that the
> frequency of LOOP packets is hardwired in the Davis stations at 2.5
> seconds. It cann
How does Weewx collect data?
Let's take my setup as example.
I have a Davis Vantage Vue with a data logger configured to store data
every 1 minute.
In my Weewx configuration, the `loop_request` param in the `[Vantage]`
section is set to 3, and the `archive_interval` in the `[StdArchive]`
How does Weewx collect data?
Let's take my setup as example.
I have a Davis Vantage Vue with a data logger, and it is configured to
store data every 1 minute.
In my Weewx configuration, the `loop_request` param in the `[Vantage]`
section is set to 3, and the `archive_interval` in the
it worked like a charm, thx
Il giorno lunedì 18 luglio 2022 alle 12:12:10 UTC+2 gjr80 ha scritto:
> I assume your are referring to the so called 'monthly climatological' and
> 'climatological' (yearly) reports? If so, I suggest you delete all such
> reports from your WeeWX machine and they
Hi,
I started using WeeWX On *September 3, 2021*.
After almost one year of usage, happy of it, few days ago I successfully
imported in weewx, from csv, data of the previous year: from September
*2020* to *September 5, 2021* (so last records overlapped, but with no
issue, they were excluded by
years ago, the
> Vantage stations behaved this way. They only published pressure reduced to
> sea-level (SLP), so station pressure (and altimeter pressure) had to be
> back calculated.
>
> -tk
>
> On Sun, Jul 17, 2022 at 7:56 AM Greg Troxel wrote:
>
>>
>> And
If, as stated
here https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter,
the `pressure` is the raw value measured by the station, why is it in the
`Calculations` section in the configuration file
(https://www.weewx.com/docs/usersguide.htm#[[Calculations]])?
I expected it
So, if I am correct, I always have to specify `unix_epoch` as unit system
for datetime field in the map, and then I have to correctly set my date
format in the `raw_datetime_format` according
to
https://docs.python.org/2/library/datetime.html#strftime-and-strptime-behavior
Thanks,
Andrea
Il
Hello everybody.
I'm reading the doc about the importing process from csv file
https://www.weewx.com/docs/utilities.htm#[CSV] and I'm confused about the
configuration of the `dateTime` field: in the example csv provided by the
doc, the date and time is `23 May 2018 13:00`. Let me quote:
```
20 matches
Mail list logo