A slight modification to my issue.
It turns out that the reporter actually runs again - at the top of the next
hour, followed by the strange interceptor packet and second report. Then
nothing for another hour.
This leads to the graph only plotting in hourly intervals, which is a bit
Hi,
I'm running version 4.5.1, with the Interceptor set in 'ecowitt-client'.
I've had a long time issue with reports stopping, and have now caught one.
The log file snippet is shown below, but I'm at a loss to explain what's
happening, as there's no error message, just a strange behavior.
Queries for time spans that are multiples of a day or done on the daily
summary. Otherwise, on the main archive table. So $day uses the daily
summary, and $hour uses the main archive table.
$hour.outTemp.avg could give you N/A either because outTemp does not
appear in the schema, or because there
You are on a pi trying to install something as a non-privileged user into a
directory owned as root.
Try "*sudo* wee_extension --install=/var/tmp/HP1000.tar.gz" and see if that
works.
On Tuesday, April 13, 2021 at 12:08:53 PM UTC-7 ried...@gmail.com wrote:
> I have now tried to reinstall the
Hi,
I tried to get $hour.outTemp.avg, and just got N/A
but $day.pm2_5.avg does work and give me the average over the last 24h. So
it seems my setup is only messing up the "hourly" summary. Any idea where I
should look to try figure this one out?
Regards,
On Monday, April 12, 2021 at
Hi,
New to weewx; I've added support in the SDR driver for my station
(WeatherSense Wireless WeatherRack2 reporting as "Cotech-36795") - it
mostly works great.
2 Questions:
1)
As I am in the southern hemisphere and this station has a solar panel on
it, I have mounted the station facing north
I have now tried to reinstall the HP driver because the driver is not in
the list. Unfortunately, I get an error message during the installation.
xxx@raspberrypi:~# wee_extension --install=/var/tmp/HP1000.tar.gz
Request to install '/var/tmp/HP1000.tar.gz'
Extracting from tar archive
Either dead or missing parts.
On Tuesday, April 13, 2021 at 5:28:53 AM UTC-5 daniel@gmail.com wrote:
> I am in a same boat, looking to be a bit more adventurous with the web
> page.
>
> So many of the links on the showcase page appear to be dead now though.
>
> On Sunday, April 11, 2021 at
Do you edit the index file or create a index_hook_after_station_info.inc
file and put the camera link in here? If you create a file do you just add
a direct link or is there more to it? I realize that I have to edit the
skin.conf to turn on the hook.
Thanks!
On Tuesday, April 13, 2021 at
I am going to have to see if I can increase my outgoing internet speed it looks
like. I can stream to youtube using Blue Iris, which I use to push the weather
to most services. But for some reason, I can’t keep the live youtube stream
connected for very long. I have 10MB fiber out, but
Thanks, I am going to check this out. I just got MQTT over SSL working, wow,
that was tough.
From: weewx-user@googlegroups.com On Behalf Of
DaveStLou
Sent: Friday, April 2, 2021 5:57 AM
To: weewx-user
Subject: Re: [weewx-user] Skin with webcam?
I 'm no expert by any means. I usually
I am in a same boat, looking to be a bit more adventurous with the web page.
So many of the links on the showcase page appear to be dead now though.
On Sunday, April 11, 2021 at 6:18:44 AM UTC+10 peterq...@gmail.com wrote:
> Have you looked through the showcase? https://weewx.com/showcase.html
On Tuesday, 13 April 2021 at 18:14:35 UTC+10 lang@googlemail.com wrote:
> There is a good, brief description of the options to be found at
> https://www.wxforum.net/index.php?topic=34857.msg355511#msg355511
>
Please keep in mind that my post linked above was made over two years ago
when
While the GW1000 API driver provides you all the fields you can see in
the field map (--> wiki, https://github.com/gjr80/weewx-gw1000/wiki),
weewx archives/stores/writes to the database only the fields which are
contained in its database schema.
If you started with weewx 4.x.x that's most
Hello I have had a problem since updating to weewx 4.5.1. Weewx is no
longer running. The following error appears in the log.
Apr 13 09:29:03 raspberrypi weewx[519] INFO weewx.engine: Main loop
exiting. Shutting engine down.
Apr 13 09:29:03 raspberrypi weewx[519] CRITICAL __main__: Caught
More or less. Even more simply, think of WeeWX (and python) as using
timestamps the ‘units’ of which are seconds since epoch. V4.5.0 introduced
a new ‘unit’ of time in the report space that is milliseconds since epoch.
When the report space wants to deal with any other part of WeeWX (and
16 matches
Mail list logo
