And how do I do that?
--
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.
To view this discussion on the web visit
https://gr
probably. Try and plot min wind chill instead of avg and for heat index
plot max and you may get what you expect.
On Sunday, 2 August 2020 06:06:35 UTC+3, Praveen Chandrasekaran wrote:
>
> I see an issue where graph doesn't match the lowest wind chill in stats.
> That's because of averaging?
-
Hi Gary,
I believe I found my problem. Sorry to have caused any confusion.
After I ran wee_install I saw the GW1000 stanzas at the end of weewx.conf
and I falsely assumed it was configured.
I had a ton of problems because I didn't run wee_config.
On Saturday, August 1, 2020 at 12:41:19 AM UTC-5 B
I see an issue where graph doesn't match the lowest wind chill in stats. That's
because of averaging?
--
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+u
It still produces the same errors.
When I look at mqtt data, it gives two different data formats at different
frequency. The shorter format is for wind data which refreshes more frequently;
while the other format is a more complete data including temp, humidity,
uv...which comes every minute. T
I used the term "windchill" also, because there is no equivalent in german.
The term "Gefühlte Temperatur" would include heat index and wind chill as
well. For Weewx there are two separate equations, as Tom Keffer described
here: https://github.com/weewx/weewx/wiki/Wind-chill-and-heat-index.
Ac
On Saturday, August 1, 2020 at 9:17:07 AM UTC-7, Chotechai Piyavongsiri
wrote:
>
> Thanks Vince. I took that line out, it did not help.
>
>
>
Well in the absence of any error logs after you made that change, there is
little we can do to help.
Belchertown runs fine with just its default settings.
Wow. It never even occurred to me that PIL shouldn't be there at all. The
files were there from early May when I cut over to 4.1 and saw some
graphics issues with an extension. It could be even older. I probably ran
uninstall / reinstall on the Python dependencies from ~/weewx. The native
Thanks Vince. I took that line out, it did not help.
On Saturday, 1 August 2020 at 22:13:38 UTC+7 vince wrote:
> On Saturday, August 1, 2020 at 1:24:35 AM UTC-7, gjr80 wrote:
>>
>> The error in your original post relates to an error parsing a config
>> file. There are only two config files invol
On Saturday, August 1, 2020 at 1:24:35 AM UTC-7, gjr80 wrote:
>
> The error in your original post relates to an error parsing a config file.
> There are only two config files involved; weewx.conf and the Belchertown
> skin.conf. As per my previous post I suggest you look in the Belchertown
> ski
Hi Christian,
i beleive better it would be "gefühlte Themperatur" but for the future i
will think to delete this value from the output. I have never seen the
benefit inside this windchill, because it depends on everybodys peronal
feelings and the location where he is at the moment. At the moment
Ah! So, it looks like the problem was caused by installing Pillow from the
weewx home directory at some point.
I can't tell you how many times that has happened to me.
-tk
On Fri, Jul 31, 2020 at 7:23 PM jerry...@gmail.com
wrote:
> Solved. There were residual py*37 files in PIL, so
> rm -rf
Hi Hans,
if you want to be consequent, should it not be "Windkühle" instead of
Windchill...? ;-)
Much nicer would be "Windfrösteln" ...! :-)
Regards,
Christian
hansc...@googlemail.com schrieb am Samstag, 1. August 2020 um 12:50:44
UTC+2:
> Hi Gary,
> it was the plot, now its working, thank
Hi Gary,
it was the plot, now its working, thanks to you and the outher supporting
me.
gjr80 schrieb am Samstag, 1. August 2020 um 10:35:12 UTC+2:
> Did you force WeeWX to regenerate the plot? If a plot involves an
> aggregate the plot is only generated every ‘aggregate interval’ seconds.
> S
Did you force WeeWX to regenerate the plot? If a plot involves an aggregate the
plot is only generated every ‘aggregate interval’ seconds. Since you have an
aggregate interval of seven days that plot will only be generated every seven
days. Just delete all of your plots on your WeeWX machine to
The error in your original post relates to an error parsing a config file.
There are only two config files involved; weewx.conf and the Belchertown
skin.conf. As per my previous post I suggest you look in the Belchertown
skin.conf file.
Gary
--
You received this message because you are subscr
Hi Michael,
i've tried it:
[[[yearrain]]]
yscale = None, None, 0.02
plot_type = bar
rain
aggregate_type = sum
# aggregate_interval = 2629800 # the length of a nominal
month
aggregate_interval = 604800#
I really can't find what causes the error. To sum up my running platform:
Ubuntu 20.04, python3.8.2, Weewx 4.1.1 (using installation guide for
debian), latest Weatherflow UDP driver, latest Weewx mqtt extension,
Weatherflow Tempest.
Belows are the configuration parts relating to my the above, in
18 matches
Mail list logo