A most important point Greg!
Specially nowadays, when Open Source seems "old school", and glad to those
that still carries and supports this flag. Hope for continuing dev,
expanding adoption and application.
Besides proprietary, also thanks Highcharts for keeping free for
Non-commercial use ap
Xant writes:
> For a start, to note that Grafana vs Highcharts might "bananas vs
> apples" Grafana intended to IoT monitoring, while Highcharts for
> generic plotting.
Another significant difference is that Grafana is Open Source and
Highcharts is proprietary.
https://shop.highsoft.com/fa
This posting is a "review" and sharing feedback regarding the Grafana
experience. Not intended to be an "in-depth" discussion, neither great
debate, just personal "pros and cons" for WeeWX.
For a start, to note that Grafana vs Highcharts might "bananas vs
apples" Grafana intended to IoT mon
Agree!
In parallel to wind gust... wind direction. Sure, always "cool" to see that
your website and PWS are "alived". And now, to be true to the original
posting "is still worthwhile"?
I might had said "yes", when WU and rapidfire had their time, and it was
interesting to see it live... but W
I tried another provider and got:
Dec 4 21:19:06 weewxPi weewx[14230]: lowBattery: #1
Dec 4 21:19:06 weewxPi weewx[14230]: lowBattery: #2
Dec 4 21:19:06 weewxPi weewx[14230]: lowBattery: using SMTP_SSL
Dec 4 21:19:06 weewxPi weewx[14230]: lowBattery: #6
Dec 4 21:19:06 weewxPi weewx[14230]: l
I modified lowBattery.py in line 118 to have txBatteryStatus = 1 and
altered all the syslog lines to log on info level:
#Copyright (c) 2009-2015 Tom Keffer
#See the file LICENSE.txt for your rights.
"""Example of how to implement a low battery alarm in weewx.
*
On Wednesday, December 4, 2019 at 9:11:15 AM UTC-8, Andrew Milner wrote:
>
> i have never seen the justification for rapidfire wrt 'standard' weather
> readings - nothing changes fast enough in a meaningful manner to justify
> the computing overheads imho.
>
>
>
Wind gust is the only thing I've e
i have never seen the justification for rapidfire wrt 'standard' weather
readings - nothing changes fast enough in a meaningful manner to justify
the computing overheads imho.
On Wednesday, 4 December 2019 18:53:13 UTC+2, Xant wrote:
>
> I finally did it... not total WU unplug, but "half-unplu
I finally did it... not total WU unplug, but "half-unplug". As I also serving
data to other services, I just disabled "rapid fire" to WU, saving resources as
to deal with other stuff.
X
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubs
Good to hear you got it working. Thanks in advance for saving me some time;
bookmarked :-) I've also ordered some extra sensors so again interested to
hear how you get on, though I am probably not going to be uploading any
data from these to any public sites.
--
You received this message becau
a suggestion - reverse the test so you get the mail if battery is ok
On Wednesday, 4 December 2019 10:01:41 UTC+2, Michi Kaa wrote:
>
> It's never too silly to ask that kind of stuff. Yes, i did :). Bad
> credentials should lead to an error-entry in the log, as far as I remember
> the code.
>
It's never too silly to ask that kind of stuff. Yes, i did :). Bad
credentials should lead to an error-entry in the log, as far as I remember
the code.
What I could probably do is modifying lowBattery.py in a way that it will
send warnings, when the battery is not empty and do more logging.
--
12 matches
Mail list logo
