Great; thanks Tom!
> On Jul 2, 2020, at 5:44 AM, Tom Keffer wrote:
>
>
> Just run wee_config with the --reconfigure option. Definitely don't start a
> 2nd database.
>
> Graphs may show a slight jump over the transition from differences in
> calibration. Nothing you can do about that.
>
>
Just run wee_config with the --reconfigure option. Definitely don't start a
2nd database.
Graphs may show a slight jump over the transition from differences in
calibration. Nothing you can do about that.
-tk
On Wed, Jul 1, 2020 at 2:26 PM Kevin Davis wrote:
> I've been running on a Acu-Rite
At the moment I have the following errors
Since no loop-data.txt is generated, rsync is diabled
Jul 2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:
> Traceback (most recent call last):
> Jul 2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:
> File
It’s formatting a sum for a unix_epoch type. Sum doesn’t make sense for this
type; but the observation,
which I unfortunately don’t log, seems to have a scalar accumulator.
This doesn’t seem right to me. I could skip summing, etc. for this type; but
this is strange.
I’ll put out an update
On second thought, I can think of reasons to have times in the packet. So, I
take back
being very interested in the log info from version 1.3.2.
I’ll push a 1.3.3 shortly that skips formatting the sum of unix_epoch
observations.
> On Jul 2, 2020, at 10:44 AM, John Kline wrote:
>
>
> OK, I
Most of it’s in the subject line. The log before/around this looks like:
Jul 2 16:39:36 weather user.info weewx[1629] INFO weewx.imagegenerator:
Generated 4 images for report BigImages in 4.15 seconds
Jul 2 16:39:36 weather user.debug weewxd: translategenerator.pyc: No
language override
1.3.3 is pushed. I won’t try to format the sums of unix_epoch observation
types.
Please let me know how this works for you.
Cheers,
John
> On Jul 2, 2020, at 11:22 AM, John Kline wrote:
>
>
> On second thought, I can think of reasons to have times in the packet. So, I
> take back
>
OK, I pushed 1.3.2. It will catch and skip the FMT_SUM_ when something
goes wrong.
It will also log the incident and include the obstype, the unit_type and the
unit_group. I am VERY
interested in seeing this information. Please send it.
Cheers,
John
> On Jul 2, 2020, at 10:21 AM, John Kline
Hi Tom, I´ve got the same issue with my AcuRite 5n1 regarding wind speed
coming out 60% higher than normal. Did you already solve the issue? In such
case, would you kindly share the solution?
Otherwise I can so some tests as I have an older version (sdr driver
version 0.64), running in an
One more place to change.
Change the LoopData>Include section in weewx.conf. That should include
FMT_SUM_rain rather than FMT_day_rain_total.
In addition to changing WeatherBoard, I’ll change the doc in LoopData as
day_rain_total is likely to be a source of confusion for many.
> On Jul 2,
>> On Jul 2, 2020, at 10:28 PM, Geni 0815 wrote:
>
> Errors are no longer logged
That’s good.
> The translation doesn't work anymore:
> [[Rename]]
> kph = kmh
The README says:
Rename : Used to specify which fields to include and which names should be used
as keys (i.e., what these fields
Errors are no longer logged
The translation doesn't work anymore:
[[Rename]]
kph = kmh
Rain amount is not in the loop-data.txt
Currently live here: https://affolter.familyds.net/wetter/weatherboard/
Is it possible to get the appTemp displayed?
Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb
It appears that weewx can't talk to whatever device is on your USB. Are you
sure you have the WMR 200 configured correctly? Is it plugged in?
These errors aren't even happening in the AQI code.
On Wednesday, July 1, 2020 at 11:36:39 PM UTC-7, Rahul Bedi wrote:
>
> Tried and gives the following
I can't keep weewx running on my raspberry pi. It keeps failing with:
Jul 2 21:13:10 obs weewx[18459] ERROR weewx.drivers.vantage: Unable to
wake up console
Jul 2 21:13:10 obs weewx[18459] ERROR weewx.engine: Import of driver
failed: Unable to wake up Vantage console ()
Jul 2 21:13:10 obs
That's not much of a log excerpt to go by, but here are a few things to
check:
1. Are there other entries in the system log? For example, is there an
instance of modemmanager that is competing for the same port? Or, some
other process? You can list what processes are using a port with the 'lsof'
Yes. Works with no issues outside of the script.
It's not clear to me as to why this script is even trying to talk to the
weather station. Shouldn't it be just be moving data from one database to
the other ?
On Fri, 3 Jul, 2020, 9:45 am jonathan koren,
wrote:
> It appears that weewx can't
As mentioned in a couple of threads there have been a lot of recent changes
to naming in rtl_433 which has broken sdr.py. These changes are listed in a
couple of places on the rtl_433 github and were first introduced over a
year ago and now seem to be the default withe current version of
Tried and gives the following message and it hangs:
pi@PrideWeatherStation:/var/lib/weewx $ sudo /usr/share/weewx/aqi_backfill
--start_time 1592634016 --end_time 1593670517 /etc/weewx/weewx.conf
Starting backfill from 1592634016 2020-06-20 11:50:16
No handlers could be found for logger
There's a new weewx-aqi release (1.3)
https://github.com/jonathankoren/weewx-aqi/releases/tag/v1.3 so make sure
you get that. It has some changes that effect aqi_backfill, including the
fix for this.
Be aware, aqi_backfill pretty temperamental.
On Wednesday, July 1, 2020 at 3:57:10 AM
19 matches
Mail list logo
