Also totally missed the other posting - sorry
Susan
--
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
The lack of a 'new line' before the 2nd 'sudo' has something to do with the
formatting of the 'markdown' file I created as it is begin displayed in
GitHub and my lack of experience in doing these things - sorry.
I'll try to get it sorted out once I work out why that part does not work
whereas
vince writes:
>- 'test' your system's powerout behavior. Every computer comes up at a
>predictable date+time when it is powered on, if you do not have a RTC.
>See what that value is.
On BSD, the default behavior on poweron is more or less to use time from
the root superblock,
On Thursday, October 17, 2019 at 11:15:00 AM UTC-7, David VE3STI wrote:
> I have used the RPi because it is a power miser, it is small and it is
> cheap enough to be bought new and 'dedicated' to a single purpose.
>
Yup. Most pi users do the same, as do people with similar tiny/low-power
I am using nginx as the web server for weewx on an RPi3, and all works well
until I try to minimize writes on the SD as suggested to prolong its life.
Once I do that, the web page loads but will never update. Here are the
exact commands I used (deb install):
1. echo "weewx_reports
Xant writes:
> But honestly... is frequency a concern regardless of location?
Some people wish to comply with RF spectrum usage regulations.
It would not surprise me if a company attempted to avoid facilitating
violating the rules, such as by not having the web service work for a
unit that is
This is veering into the tangential but...
My weather logging needs are modest - I'm usually looking for the weather
'at the moment' or for the last several days. Occasionally, rainfall for
the month. My livelihood does not depend on my weather observations. If I
miss weather data during a power
On Thursday, October 17, 2019 at 9:22:24 AM UTC-7, Jared wrote:
>
> Why is that, just curious. I have no issue with Debian, it's just that
> CentOS is more relevant to me professionally.
>
>
>
Centos7 is fine to use. There are just many many more weewx users on
debian derivatives (raspi) and
Why is that, just curious. I have no issue with Debian, it's just that
CentOS is more relevant to me professionally.
On Thursday, October 17, 2019 at 11:52:11 AM UTC-4, vince wrote:
>
> On Thursday, October 17, 2019 at 8:26:54 AM UTC-7, Jared wrote:
>>
>> Thanks, that's great info. I don't
Gary is correct to not initiate an Insolation vs Illuminance debate... been
there, done that.
Please, refer to my previous posting and read the follow-up responses:
https://groups.google.com/d/msg/weewx-user/bUJrHaRnE_w/ajKVjLTtCwAJ
Xant
--
You received this message because you are
On Thursday, October 17, 2019 at 8:26:54 AM UTC-7, Jared wrote:
>
> Thanks, that's great info. I don't mind going CentOS 7. I figured CentOS
> 8 would be a good learning experience as a Linux noob, but if it's that
> much trouble then it's not worth it. I'm guessing by the time I'd need
>
The actions detailed by Thomas Keffer solved the problem!
On Wednesday, October 16, 2019 at 8:51:35 AM UTC-4, Ford Smith wrote:
>
> Until a brief power failure the other day, my weewx reading an Accurite
> weather station was performing perfectly on a Raspberry Pi 4. Since then,
> the upload to
Thanks, that's great info. I don't mind going CentOS 7. I figured CentOS
8 would be a good learning experience as a Linux noob, but if it's that
much trouble then it's not worth it. I'm guessing by the time I'd need
CentOS 8 I'll be able to move to Weewx 4 anyway. Or maybe I'll mess with
Geez RHEL8/CentOS8 is UGLY under the hood in how it does repos.
- I verified that no package "provides" python, so the existing rpm for
weewx will not work as-is.
- You are 'definitely' going to have significant problems trying to
force a weewx rpm installation to happen on
Joe,
In the default configuration, MQTTSubscribe attempts to ensure the data is
in an appropriate time range. This works well in my controlled environment,
but is probably too strict for most setups. There are a lot of knobs we
could turn. Since you are using the server time (use_server_time =
On Thursday, October 17, 2019 at 5:41:32 AM UTC-7, Thomas Keffer wrote:
>
> Yes, that's the problem.
> You cannot expect high-quality data without investing in the hardware. You
> bought an expensive Davis station, why not spend the other $50 to protect
> the data?
>
>
>
Or alternately sell all
Is there a reason you need to do this on centos8 ?
That's very new and very different under the hood from a python perspective
than previous versions (long story).
I think what you are likely running into is internals in the rpms
themselves and what they say they 'provide' in rpm terminology.
Matt,
You don’t need to unzip. The wee_extension —install process takes care of that
as well.
Ian
Sent from my iPhone
> On 17 Oct 2019, at 14:05, Matt wrote:
>
>
> Hi Susan,
>
> I added a post about the struggles I faced a few days ago called "
> New User Setup issues - Raspberry Pi, Fine
Hi,
I'm trying to do a new Weewx installation on CentOS 8 and I'm having some
installation issues regarding python that I can't figure out. I know the
basics of Linux but am not a veteran. I'm following the instructions on
the http://www.weewx.com/docs/redhat.htm page.
I installed as many
Hi Susan,
I added a post about the struggles I faced a few days ago called "
New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports
show values being appended/summed
", this gives a potted history of things.
What I did to get it working is contained in one of the replies
Yes, that's the problem.
You cannot expect high-quality data without investing in the hardware. You
bought an expensive Davis station, why not spend the other $50 to protect
the data?
I have a Davis Envoy, a UPS, and a high-quality embedded PC with a clock.
It has run continuously without a
I'm sorry, but I didn't understand in which way the clock is related to
this problem
Il giorno giovedì 17 ottobre 2019 13:59:09 UTC+2, Andrew Milner ha scritto:
>
> regardless I would recommend that all Rpis controlling weather stations
> have an RTC installed to avoid temporal issues as much
I will have to review that section of the User's Guide. I caved and began
using a UPS quite some time ago - but I think it is going to need a new
battery soon. At this time, I'm some 1,000 km from home so no fiddling with
WeeWX for a while.
When I'm home, I am going to try Thomas Keffer's
Il giorno giovedì 17 ottobre 2019 14:13:51 UTC+2, Thomas Keffer ha scritto:
>
> As it is suggested in other answers here, it would "fix" the problem
>> buying an UPS, but I honestly wolud find a software solution, not coming
>> around the problem in this way (which could also be expensive).
>
> As it is suggested in other answers here, it would "fix" the problem
> buying an UPS, but I honestly wolud find a software solution, not coming
> around the problem in this way (which could also be expensive).
>
There is a software solution: run with record_generation = software. This
The data is different, but the wind graphs best showed examples of what I
was talking about. I think you nailed it, the archive interval on my VP2
was set for 1 minute. I just bumped it up to 5 and from what I see so far
I think it fixed it.
On Thursday, October 17, 2019 at 7:52:35 AM UTC-4,
regardless I would recommend that all Rpis controlling weather stations
have an RTC installed to avoid temporal issues as much as possible.
On Thursday, 17 October 2019 14:26:18 UTC+3, Andrea Cecilia wrote:
>
> I've never seen this section of the User's Guide (it might be relatively
> new),
a stupid question - but are they plotting the same data?? The scales on
the graphs are different I see. Is one plotting max and one plotting
average? Check the skins to find any differences in the plotting - the
station is not likely to be causing the difference unless the stations have
I've never seen this section of the User's Guide (it might be relatively
new), but it is exactly about the problem we are discussing here.
So, the fixing tries they suggest without data loss are two:
1) unplug and reboot the console by removing current and batteries for
about 2 minutes and then
I have 2 setups, 1 is a VP2 with an Envoy hooked up to a Pi. 2nd is a
Vantage Vue with the console hooked up to a Pi. They are both setup pretty
much the same way.
Using the wind graphs as an example. The graphs look fine on the Vue,
however the line graphs on the VP2 seem to merge into each
I should have said that I have a setup.py WeeWX installation so you may
need to make the instructions more general to cover packaged WeeWX
installations (DEB etc) where the location of the WeeWX bin folder maybe
different.
On Thu, 17 Oct 2019 at 07:57, steeple ian wrote:
> Susan,
> The install
Susan,
The install instructions seem to be confusing as they stand. (sudo cd sudo
python ./bin/wee_extension --install /HP1000 sudo python ./bin/wee_config
--reconfigure) and do not work.
I think they should read something like: -
cd ./bin
sudo python wee_extension --install
32 matches
Mail list logo
