[weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Susan Mackay]

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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e6967fee-62b0-4a13-bd2e-566f0d9a69c7%40googlegroups.com.

[weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Susan Mackay]

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 it does in other places in the same file.
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0a796fc9-fb34-41cc-a326-fc87df16abbc%40googlegroups.com.

Re: [weewx-user] Re: Davis Datalogger bug

[Greg Troxel]

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, so this predictable/very-past notion doesn't hold.
(I can believe that what you say is true on Linux systems.)

What I've done is to have the script that starts weewx loop until ntpd
reports that it is well synced to remote peers.

And yes, I know I should put in an RTC...

-- 
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://groups.google.com/d/msgid/weewx-user/rmia79zyp3n.fsf%40s1.lexort.com.

Re: [weewx-user] Re: Davis Datalogger bug

[vince]

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 
non-RTC systems (like me - I run on a Seagate Dockstar, which is 
essentially a stripped down PogoPlug).

There have been MANY discussions about weewx/pi/etc. and databases needing 
accurate time here in the past.  Almost too many to recount.

But the short 'software' solution is:

   - disable anything that tries to keep track of the software time either 
   periodically, or when you do an orderly shutdown
   - run ntpd or equivalent in your boot sequence if your system will be 
   connected to an Internet time source
   - '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.

Note: systemd (grr) 'also' seems to have something like the user-space 
'fake-hwclock' that is also in debian(ish) operating systems.  You need to 
disable systemd helping too much (grr!).

Again, do a few controlled tests.  See what time is.  Yank the power.  See 
what date+time it boots to.   Reboot the box.  See what it does 'then' re: 
date+time.   Basically baseline your system. 

Weewx shouldn't start up if the date+time of weewx.conf is newer than the 
system clock, if I remember the code correctly, so you should be safe from 
reboots.

FWIW, I do 'not' have a RTC on my Dockstar nor do I have a UPS for several 
reasons.  I 'do' have the battery in the Davis VP2 console however, so 
theoretically I should be able to run the console on battery there for a 
long long time.  I only had one power out for more than a couple minutes in 
the last 10 years I've had this in place, we were down for about 2 days, 
but the datalogger stayed ok and weewx recovered just fine for me back then 
when power came back up.

Of course your mileage might vary.  RTC is good.  RTC+UPS is better.  All 
comes down to your budget etc.

-- 
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://groups.google.com/d/msgid/weewx-user/230e9226-adad-4a38-903f-f6fe48e17ed0%40googlegroups.com.

[weewx-user] Using fstab causes weewx to not update

[Timothy Buchanan]

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 /var/weewx/reports tmpfs 
size=20M,noexec,nosuid,nodev 0 0" | sudo tee -a /etc/fstab

2. sudo mkdir -p /var/weewx/reports

3. sudo mount -a

4. sudo sed -i -e 's%HTML_ROOT =.*%HTML_ROOT = /var/weewx/reports%' 
/etc/weewx/weewx.conf

5. sudo /etc/init.d/weewx stop

6. sudo /etc/init.d/weewx start

7. sudo ln -s /var/weewx/reports /var/www/html/weewx

8. sudo /etc/init.d/nginx restart

I am using the /etc/nginx/sites-available/default file. I tried replacing 
the server name in the default file with this:

server {
  ...
  location /weewx {
alias /var/www/html/weewx/index.html;
  }
}

as recommended on another of the wiki pages, but nginx will not start with that 
configuration. nginx finds the weewx page with the default file. Any 
suggestions to make this work? Thanks.


-- 
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://groups.google.com/d/msgid/weewx-user/2471ea4e-2805-401e-aa17-1073ad706d6f%40googlegroups.com.

Re: [weewx-user] Re: Weather station recommendations?

[Greg Troxel]

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 operated in a place where it is not approved.   From the US
legal POV this is perfectly reasonable behavior.

-- 
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://groups.google.com/d/msgid/weewx-user/rmimudzyxl4.fsf%40s1.lexort.com.

Re: [weewx-user] Re: Davis Datalogger bug

[David Beach]

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 outage, I'm not too distressed. Not
missing it would be better but missing it is not a show-stopper for me.

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. My RPi
Zero W uses between 50 and 100 mA at 5V. I chose WeeWX because it was free
to play with and use, appeared well supported and was written in Python, a
language I wanted to become more familiar with.

My 'getting stuck on restarting' issues were annoying, not only because I
missed data but because I had to restart things manually, remember (or look
up again!) the command to clear the memory, etc. If it quit while I was
away from home, it was 'dead' until I got back. The RTC (a cheap DS3231
module which required some desoldering/re-soldering to squeeze into the
standard RPi Zero case) didn't do the trick. A few feeble attempts on my
part at some coding didn't eliminate the issue either. I resorted to an APS
UPS that is many times the size of the RPi and likely uses more power to
maintain its battery than the RPi does to run.

I don't know enough about the WeeWX code, the Davis firmware or the logging
module to understand the technical details of this problem. The problem may
be 'baked into' the Davis hardware/firmware. The WeeWX code may be trying
to fix/avoid a problem it didn't create. However, if anyone ever does
figure out a software solution to this thorny problem, I'll be happy to get
rid of my giant UPS. And my hat will be off to you. (But I'll keep using my
RTC - it is now soldered on to my RPi Zero!)

David

On Thu, 17 Oct 2019 at 10:28, vince  wrote:

> 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 your raspberry pi gear and pick up a good used
> computer that 'has' a RTC in it (even a 4 year old mini pc would work) so
> you get correct time through your periodic power outages.
>
> In short, buy a real computer.   The pi are great (I have 'many') but you
> are limited in what they can do without adding things to them.  You have to
> remove those limitations by either adding a realtime clock, or a ups (or
> both), or buying a more capable computer if you want enterprise-level data
> availability.
>
> The other thing to think about is 'does your computer power up when power
> is restored'.  That's not always goodness.  I've fried a lot of
> motherboards over the years in places where the power is very bouncy up and
> down as power is restored to that location.   UPS is almost certainly the
> short term answer, plus a RTC if you want to stick with a pi.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/hOj_mdhkl1E/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2674140d-f230-4451-a8b2-8961f3819a14%40googlegroups.com
> 
> .
>

-- 
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://groups.google.com/d/msgid/weewx-user/CAAMcdj24hUuXDjX6pz8h7jSA98ADk6kUnu08sv0dPJQ8jSs2tg%40mail.gmail.com.

[weewx-user] Re: Python and depdency failures on CentOS 8

[vince]

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 it's kinda historically the reference 
platform weewx was built on.

Just don't go totally bleeding edge latest centos8 or fedora and expect 
everything to work.  They tends to break things historically.

-- 
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://groups.google.com/d/msgid/weewx-user/356fc45a-1141-4921-b201-a9c738937aca%40googlegroups.com.

[weewx-user] Re: Python and depdency failures on CentOS 8

[Jared]

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 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 it later if I'm feeling up to it.  At this point I just want to get 
>> off the ground.
>>
>>
> If you want maximum weewx compatibility, then I'd suggest you go with 
> ubuntu or debian, especially if you're a Linux newbie.
>
>
>

-- 
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://groups.google.com/d/msgid/weewx-user/b1360020-0704-4f87-a718-d73db8feb160%40googlegroups.com.

[weewx-user] Re: MaxSolarRad (from pyephm) is not alligned with Solar-Rad from my Weatherstation

[Xant]

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 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://groups.google.com/d/msgid/weewx-user/1b7ed4cb-90b2-4ac2-a445-8e755f906a3c%40googlegroups.com.

[weewx-user] Re: Python and depdency failures on CentOS 8

[vince]

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 
> CentOS 8 I'll be able to move to Weewx 4 anyway.  Or maybe I'll mess with 
> it later if I'm feeling up to it.  At this point I just want to get off the 
> ground.
>
>
If you want maximum weewx compatibility, then I'd suggest you go with 
ubuntu or debian, especially if you're a Linux newbie.


-- 
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://groups.google.com/d/msgid/weewx-user/427065e5-5276-4e1e-ad5a-b5ff9e928035%40googlegroups.com.

[weewx-user] Re: Weather Underground Upload Fails

[Ford Smith]

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 Weather Underground has failed. I've reinstalled weewx, even 
> created a new PWS on Underground, and finally turned Debug on. Apparently, 
> the problem  is:
>
> *Oct 16 08:40:25 raspberrypi weewx[3114]: restx: Wunderground-PWS: Failed 
> upload attempt 2:  certificate verify*
> I've searched for how to correct this Certificate problem and can find no 
> answers.
> Help!!
>

-- 
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://groups.google.com/d/msgid/weewx-user/b75799be-f95b-49cf-bce4-aa42853f84c8%40googlegroups.com.

[weewx-user] Re: Python and depdency failures on CentOS 8

[Jared]

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 
it later if I'm feeling up to it.  At this point I just want to get off the 
ground.

Thanks very much for your help.

-- 
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://groups.google.com/d/msgid/weewx-user/ac138bda-d910-497b-8f1d-8dff90570b17%40googlegroups.com.

[weewx-user] Re: Python and depdency failures on CentOS 8

[vince]

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 centos8.
   
   
I'd highly recommend going the 'setup.py' route for installing things.  You 
might also need to install the prerequisite packages the hard way if EPEL 
hasn't caught up (which reports say is the case).

-- 
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://groups.google.com/d/msgid/weewx-user/fabb7ebd-979f-4c0c-abd3-41b07a670d40%40googlegroups.com.

[weewx-user] Re: MQTTSubscriber not saving values to database

[Rich Bell]

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 = true) in 
addition to setting ignore_end_time to true you could set ignore_start_time 
to true. This should have the effect of not doing any time checking.
- Rich

On Thursday, 17 October 2019 01:48:51 UTC-4, jmltech wrote:
>
> HI,
> Downloaded the MQTTSubscriber so that I can grab some extra temp and 
> humidity readings from a couple of Arduinos.  They are being published 
> correctly via MQTT, as verified by MQTT-Explorer.
> Got the subscription configured okay (no configuration errors) on weewx, 
> however I'm getting an awfull lot of this type of error in the log file:
>
> Oct 16 23:32:23 salida1 weewx[25885]: MQTTSubscribeService: Ignoring record 
> outside of interval 1571290342.00 1571290344.00 1571290341.905635 
> dateTime: 1571290341.91, extraHum4: 8.0, usUnits: 1
> Oct 16 23:32:39 salida1 weewx[25885]: MQTTSubscribeService: Ignoring record 
> outside of interval 1571290358.00 1571290360.00 1571290357.808515 
> dateTime: 1571290357.81, extraHum4: 8.0, usUnits: 1
> Oct 16 23:32:39 salida1 weewx[25885]: MQTTSubscribeService: Ignoring record 
> outside of interval 1571290358.00 1571290360.00 1571290357.866821 
> dateTime: 1571290357.87, mqttSignal1: -64.0, usUnits: 1
>
> Consequently, I'm not seeing any of the values being written to the database.
>
> Here is what I have in my weewx.conf:
>  Options for extension 'MQTTSubscribe'
> [MQTTSubscribeService]
>  # This section is for the MQTTSubscribe service.
>  
>  # Turn the service on and off.
>  # Default is: true
>  # Only used by the service.
>  enable = True
>  
>  # The MQTT server.
>  # Default is: localhost
>  host = localhost
>  
>  # The port to connect to.
>  # Default is: 1883
>  port = 1883
>  
>  # Maximum period in seconds allowed between communications with the broker.
>  # Default is: 60
>  keepalive = 50
>  
>  # The binding, loop or archive.
>  # Default is: loop
>  # Only used by the service.
>  binding = loop
>
>  # The clientid to connect with.
>  clientid = weewxMQTT
>  
>  # The message handler to use
>  [[message_callback]]
>  # The format of the MQTT payload.
>  # Currently support: individual, json, keyword
>  # Must be specified.
>  type = individual
>
>  # When it is True, the full topic will be the fieldname. The default will be 
> false.
>  full_topic_fieldname = True
>
>  [[[label_map]]]
>  WX/RVGarage/Temperature = extraTemp4
>  WX/JoeWorkshop/Temperature = extraTemp5
>  WX/RVGarage/Humidity = extraHum4
>  WX/JoeWorkshop/Humidity = extraHum5
>  WX/RVGarage/Signal = mqttSignal1
>  WX/JoeWorkshop/Signal = mqttSignal2
>  
>  # The topics to subscribe to.
>  [[topics]]
>  # Units for MQTT payloads without unit value.
>  # Valid values: US, METRIC, METRICWX
>  # Default is: US
>  unit_system = US
>
>  # Even if the payload has a datetime, ignore it and use the server datetime
>  # Default is False
>  use_server_time = True
>
>  # When True, the MQTT datetime will be not be checked that is greater than 
> the last packet processed.
>  # Default is False
>  # Only used by the service.
>  #ignore_start_time = True
>
>  # When the True, the MQTT data will continue to be processed even if its 
> datetime is greater than the packet's datetime.
>  # Default is False
>  # Only used by the service.
>  ignore_end_time = True
>
>  # When it is True, the full topic will be the fieldname. The default will be 
> false.
>  full_topic_fieldname = True
>
>  [[[WX/#]]]
>
> It appears that every published packet is being ignored because of the 
> timestamp.  My log file is growing like crazy.
> Anyone have any ideas?
> Thanks
> Joe
>
>
>
>
>

-- 
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://groups.google.com/d/msgid/weewx-user/5ca3d13f-3a25-41ed-b772-cc5bc50e1821%40googlegroups.com.

Re: [weewx-user] Re: Davis Datalogger bug

[vince]

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 your raspberry pi gear and pick up a good used 
computer that 'has' a RTC in it (even a 4 year old mini pc would work) so 
you get correct time through your periodic power outages.

In short, buy a real computer.   The pi are great (I have 'many') but you 
are limited in what they can do without adding things to them.  You have to 
remove those limitations by either adding a realtime clock, or a ups (or 
both), or buying a more capable computer if you want enterprise-level data 
availability.

The other thing to think about is 'does your computer power up when power 
is restored'.  That's not always goodness.  I've fried a lot of 
motherboards over the years in places where the power is very bouncy up and 
down as power is restored to that location.   UPS is almost certainly the 
short term answer, plus a RTC if you want to stick with a pi.

-- 
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://groups.google.com/d/msgid/weewx-user/2674140d-f230-4451-a8b2-8961f3819a14%40googlegroups.com.

[weewx-user] Re: Python and depdency failures on CentOS 8

[vince]

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.  I'm 
guessing the python2 rpm provides "python2" but no rpm provides "python" 
(unversioned), so the legacy weewx rpms will not work as is on the new os.

The setup.py installation method should work for you just fine I'd think 
(untested).

But personally I'd recommend you just use centos7 since it's supported for 
4+ more years anyway, unless you really want to go bleeding edge with 
centos8.

-- 
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://groups.google.com/d/msgid/weewx-user/c0782294-519b-4fdf-96d7-b6d3f80d9d4a%40googlegroups.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[steeple ian]

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 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 on that post 
> but essentially:
> 
> I'm making progress.  I managed to install the driver using a number of 
> different sources and lots of trial and error.  For anyone else seeing 
> problems, what I did was:
> 
> wget -P /var/tmp weewx-hp1000.zip 
> https://github.com/AussieSusan/HP1000/archive/master.zip
> cd var/tmp
> unzip master.zip
> sudo ./wee_extension --install=/var/tmp/HP1000-master/hp1000.tar.gz
> sudo ./wee_config --reconfigure
> 
> Chose the number next to HP1000 then restarted weewx.
> 
> It's fantastic now it's working and I'm hoping to end up with something like 
> Ian has got eventually.
> 
> On Thursday, 17 October 2019 03:47:05 UTC+1, Susan Mackay wrote:
>> Could you elaborate a bit more for the sake of others trying to do the same? 
>> (Also for me - lets me know what problems others have overcome if/when I 
>> come to update the code.)
>> 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 discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/d4c996cf-d494-41c2-8b91-cf381cbf6966%40googlegroups.com.

-- 
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://groups.google.com/d/msgid/weewx-user/75DDD462-1194-4ECD-9FB4-537931A2CF05%40gmail.com.

[weewx-user] Python and depdency failures on CentOS 8

[Jared]

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 of the prerequisites as I could.  None of the commands 
worked as-is.  First I installed python 2 with *sudo yum install python2* 
and then I was able to run *sudo yum install python2-cheetah* and *sudo 
pip2 install pyserial* and *sudo pip2 install pyusb*.  The only other 
package name I got a result for was on *sudo yum install python2-setuptools* 
but it said this was installed already.

At this point I figured I would at least try to run the Weewx install, so I 
got the .rpm file and attempted to install it with *rpm -i*.  But it failed 
all python dependencies.

error: Failed dependencies:
python is needed by weewx-3.9.2-1.rhel.noarch
python-cheetah is needed by weewx-3.9.2-1.rhel.noarch
python-configobj is needed by weewx-3.9.2-1.rhel.noarch
python-imaging is needed by weewx-3.9.2-1.rhel.noarch
python-setuptools is needed by weewx-3.9.2-1.rhel.noarch


I'm sure something is goofy with having by python2 and python3 on the same 
OS.  I couldn't run *python* by itself, so I looked around as best I could 
and wound up running *sudo alternatives --set python /usr/bin/python2* but 
this didn't make the rpm any happier.

The output of *whereis python* returns:

python: /usr/bin/python2.7 /usr/bin/python /usr/lib/python3.6 
/usr/lib/python2.7 /usr/lib64/python3.6 /usr/lib64/python2.7 
/usr/include/python3.6m /usr/include/python2.7 
/usr/share/man/man1/python.1.gz


Other potentially useful info:

[me@SERVER ~]$ *ls -alh /usr/bin | grep python*
lrwxrwxrwx   1 root root  36 Oct 17 07:32 python -> 
/etc/alternatives/unversioned-python
lrwxrwxrwx   1 root root   9 Oct  8 17:08 python2 -> python2.7
-rwxr-xr-x   1 root root9.1K Oct  8 17:08 python2.7
lrwxrwxrwx   1 root root  24 Oct 17 07:32 unversioned-python -> 
/etc/alternatives/python
[me@SERVER ~]$ *ls -alh /usr/lib | grep python*
drwxr-xr-x3 root root   27 Oct 16 14:06 python2.7
drwxr-xr-x.   3 root root   27 Oct  7 14:00 python3.6
[me@SERVER ~]$


I figure at this point any tinkering will only make the problem worse, so I 
thought it was a good time to reach out.


Thanks.

-- 
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://groups.google.com/d/msgid/weewx-user/7162c81f-9634-4a1c-bd79-a388615d192e%40googlegroups.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Matt]

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 on that 
post but essentially:

I'm making progress.  I managed to install the driver using a number of 
different sources and lots of trial and error.  For anyone else seeing 
problems, what I did was:

wget -P /var/tmp weewx-hp1000.zip 
https://github.com/AussieSusan/HP1000/archive/master.zip
cd var/tmp
unzip master.zip
sudo ./wee_extension --install=/var/tmp/HP1000-master/hp1000.tar.gz
sudo ./wee_config --reconfigure

Chose the number next to HP1000 then restarted weewx.

It's fantastic now it's working and I'm hoping to end up with something 
like Ian has got eventually.

On Thursday, 17 October 2019 03:47:05 UTC+1, Susan Mackay wrote:

> Could you elaborate a bit more for the sake of others trying to do the 
> same? (Also for me - lets me know what problems others have overcome 
> if/when I come to update the code.)
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d4c996cf-d494-41c2-8b91-cf381cbf6966%40googlegroups.com.

Re: [weewx-user] Re: Davis Datalogger bug

[Thomas Keffer]

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 single failure for over 11 years. It can
be done at modest cost!

-tk


On Thu, Oct 17, 2019 at 5:26 AM Andrea Cecilia  wrote:

>
>
> 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).
>>>
>>
>> There is a software solution: run with record_generation = software. This
>> essentially bypasses the logger and its tendency to corrupt memory. But, it
>> also means you won't enjoy the benefits of the logger and its offline
>> logging capabilities.
>>
>> If $5 is too much for a clock, at least be sure to read the section in
>> the Wiki on removing the "fake clock":
>> https://github.com/weewx/weewx/wiki/Raspberry-Pi#b-remove-the-fake-clock
>>
>>
> The problem of this solution is that if a power outage happens, the RPi
> ceases acquiring data, and these data are going to be lost.
> Consider the specific case in which I'm having most troubles: I installed
> a Davis station in my farmland house, where I usually go once a month, and
> where power outages may happen at every thunderstorm. I will lost all the
> data coming during power outages, and they are lot of data!
>
> --
> 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://groups.google.com/d/msgid/weewx-user/e39000fe-4ff5-4d9f-b830-0c7b7e9e3811%40googlegroups.com
> 
> .
>

-- 
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://groups.google.com/d/msgid/weewx-user/CAPq0zEBzbARo2WGPqio%2BQQgYfHJo4Z5J4vHbNttDajkPOray7w%40mail.gmail.com.

Re: [weewx-user] Re: Davis Datalogger bug

[Andrea Cecilia]

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 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), 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 plug it again;
>> 2) make a /home/weewx/bin/wee_device --dump.
>> They also specificate that if these won't work, it is necessary to give a 
>> --clera-memory as I did, but in this case you lose the data.
>>
>> 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). 
>>
>> So, it remains to try the 2 points up here when the problem will come out 
>> again. Did anyone try?
>>
>>
>> Il giorno mercoledì 16 ottobre 2019 13:40:59 UTC+2, Thomas Keffer ha 
>> scritto:
>>>
>>> This is likely a case of memory corruption, brought on by time not being 
>>> synced during the reboot, due to the lack of an on-board clock. It was not 
>>> a problem with Weatherlink because you were not running it on an RPi.
>>>
>>> See the section *WeeWX generated HTML pages, but does not update them 
>>> * in 
>>> the User's Guide.
>>>
>>> But, as Andrew suggested, we would have to see the log from startup to 
>>> be sure.
>>>
>>> -tk
>>>
>>> On Wed, Oct 16, 2019 at 4:04 AM Andrew Milner  
>>> wrote:
>>>
 what came just before the log you posted?  why is weewx attempting to 
 do a catchup? had weewx just been started?  had communications been lost 
 for some reason? We need to know what is causing weewx to attempt a 
 catchup 
 in the first place.  You can never post too much log




 On Wednesday, 16 October 2019 13:52:51 UTC+3, Andrea Cecilia wrote:
>
> here it is. As you can see, there is no "added record [...] to 
> weewx.sdb" line, which indicates that it is not downloading data from the 
> datalogger, and the reson (I think) is explained in the highlighted line.
>
> Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Getting archive 
> packets since 2019-10-16 09:05:00 CEST (1571209500)
> Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Gentle wake up 
> of console successful
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Retrieving 5 page
> (s); starting index= 4
> *Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: DMPAFT complete: 
> page timestamp 2019-10-15 13:20:00 CEST (1571138400) less than final 
> timestamp 2019-10-16 09:05:00 CEST (1571209500)*
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Catch up complete
> .
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running 
> reports for latest time in the database.
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Requesting 200 
> LOOP packets.
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running 
> report 'StandardReport'
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Gentle wake up 
> of console successful
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Found 
> configuration file /home/weewx/skins/Standard/skin.conf for report 
> 'StandardReport'
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: cheetahgenerator: using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', '
> weewx.ch
> eetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: manager: Daily summary 
> version is 2.0
> Oct 16 10:30:17 raspberrypi weewx-vp2[511]: cheetahgenerator: 
> Generated 16 files for report StandardReport in 2.31 seconds
> Oct 16 10:30:17 raspberrypi weewx-vp2[511]: manager: Daily summary 
> version is 2.0
> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: imagegenerator: Generated 
> 15 images for StandardReport in 1.36 seconds
> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: copygenerator: copied 0 
> files to /home/weewx/public_html/vp2
> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: reportengine: Running 
> report 'FTP'
> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: reportengine: Found 
> configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Attempting 
> 

Re: [weewx-user] Re: Davis Datalogger bug

[David Beach]

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 suggestion to run
with "record_generation
= software" because I currently don't care about missing some data during a
power failure. And at this point, if I do have to restart for any reason, I
have to clear the memory anyway because my RTC didn't seem to fix the issue.

David

On Thu, 17 Oct 2019 at 07:26, Andrea Cecilia  wrote:

> 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 plug it again;
> 2) make a /home/weewx/bin/wee_device --dump.
> They also specificate that if these won't work, it is necessary to give a
> --clera-memory as I did, but in this case you lose the data.
>
> 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).
>
> So, it remains to try the 2 points up here when the problem will come out
> again. Did anyone try?
>
>
> Il giorno mercoledì 16 ottobre 2019 13:40:59 UTC+2, Thomas Keffer ha
> scritto:
>>
>> This is likely a case of memory corruption, brought on by time not being
>> synced during the reboot, due to the lack of an on-board clock. It was not
>> a problem with Weatherlink because you were not running it on an RPi.
>>
>> See the section *WeeWX generated HTML pages, but does not update them
>> * in
>> the User's Guide.
>>
>> But, as Andrew suggested, we would have to see the log from startup to be
>> sure.
>>
>> -tk
>>
>> On Wed, Oct 16, 2019 at 4:04 AM Andrew Milner 
>> wrote:
>>
>>> what came just before the log you posted?  why is weewx attempting to do
>>> a catchup? had weewx just been started?  had communications been lost for
>>> some reason? We need to know what is causing weewx to attempt a catchup in
>>> the first place.  You can never post too much log
>>>
>>>
>>>
>>>
>>> On Wednesday, 16 October 2019 13:52:51 UTC+3, Andrea Cecilia wrote:

 here it is. As you can see, there is no "added record [...] to
 weewx.sdb" line, which indicates that it is not downloading data from the
 datalogger, and the reson (I think) is explained in the highlighted line.

 Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Getting archive
 packets since 2019-10-16 09:05:00 CEST (1571209500)
 Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Gentle wake up of
 console successful
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Retrieving 5 page(
 s); starting index= 4
 *Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: DMPAFT complete:
 page timestamp 2019-10-15 13:20:00 CEST (1571138400) less than final
 timestamp 2019-10-16 09:05:00 CEST (1571209500)*
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Catch up complete.
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running
 reports for latest time in the database.
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Requesting 200
 LOOP packets.
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running
 report 'StandardReport'
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Gentle wake up of
 console successful
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Found
 configuration file /home/weewx/skins/Standard/skin.conf for report
 'StandardReport'
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: cheetahgenerator: using
 search list ['weewx.cheetahgenerator.Almanac',
 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', '
 weewx.ch
 eetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
 'weewx.cheetahgenerator.Extras']
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: manager: Daily summary
 version is 2.0
 Oct 16 10:30:17 raspberrypi weewx-vp2[511]: cheetahgenerator: Generated
 16 files for report StandardReport in 2.31 seconds
 Oct 16 10:30:17 raspberrypi weewx-vp2[511]: manager: Daily summary
 version is 2.0
 Oct 16 10:30:18 raspberrypi weewx-vp2[511]: imagegenerator: Generated
 15 images for StandardReport in 1.36 seconds
 Oct 16 10:30:18 raspberrypi weewx-vp2[511]: copygenerator: copied 0
 files to /home/weewx/public_html/vp2
 Oct 16 10:30:18 raspberrypi weewx-vp2[511]: reportengine: Running
 report 'FTP'
 Oct 16 10:30:19 raspberrypi weewx-vp2[511]: reportengine: Found
 configuration file /home/weewx/skins/Ftp/skin.conf for 

Re: [weewx-user] Re: Davis Datalogger bug

[Andrea Cecilia]

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). 
>>
>
> There is a software solution: run with record_generation = software. This 
> essentially bypasses the logger and its tendency to corrupt memory. But, it 
> also means you won't enjoy the benefits of the logger and its offline 
> logging capabilities.
>
> If $5 is too much for a clock, at least be sure to read the section in the 
> Wiki on removing the "fake clock": 
> https://github.com/weewx/weewx/wiki/Raspberry-Pi#b-remove-the-fake-clock
>  
>
The problem of this solution is that if a power outage happens, the RPi 
ceases acquiring data, and these data are going to be lost.
Consider the specific case in which I'm having most troubles: I installed a 
Davis station in my farmland house, where I usually go once a month, and 
where power outages may happen at every thunderstorm. I will lost all the 
data coming during power outages, and they are lot of data! 

-- 
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://groups.google.com/d/msgid/weewx-user/e39000fe-4ff5-4d9f-b830-0c7b7e9e3811%40googlegroups.com.

Re: [weewx-user] Re: Davis Datalogger bug

[Thomas Keffer]

>
> 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
essentially bypasses the logger and its tendency to corrupt memory. But, it
also means you won't enjoy the benefits of the logger and its offline
logging capabilities.

If $5 is too much for a clock, at least be sure to read the section in the
Wiki on removing the "fake clock":
https://github.com/weewx/weewx/wiki/Raspberry-Pi#b-remove-the-fake-clock

-- 
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://groups.google.com/d/msgid/weewx-user/CAPq0zEDFC2bjNP9ZdNLsjVjr3prusfAUzJ%3DtsvaFK-KSnFnxAA%40mail.gmail.com.

[weewx-user] Re: 2 different setups, graphs don't look the same.

[John Burricelli]

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, Andrew Milner wrote:
>
> 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 
> different intervals specified.  Have you verified that both stations a) 
> have the same interval in weewx.conf  b)are both using either hardware or 
> software record generation and c) the stations themselves have the same 
> archive interval specified as is specified in weewx.conf (change with 
> wee_device if needed)
>
>
>
> On Thursday, 17 October 2019 14:23:55 UTC+3, John Burricelli wrote:
>>
>> 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 other. I have 
>> the archive interval set for both at 300.  
>>
>> Is there some sort of setting I have overlooked somewhere?
>>
>>
>> [image: VP2.png]
>>
>> [image: VantageVue.png]
>>
>>

-- 
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://groups.google.com/d/msgid/weewx-user/db9f3dea-5aa2-45b5-96cf-495189783c7e%40googlegroups.com.

Re: [weewx-user] Re: Davis Datalogger bug

[Andrew Milner]

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), 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 plug it again;
> 2) make a /home/weewx/bin/wee_device --dump.
> They also specificate that if these won't work, it is necessary to give a 
> --clera-memory as I did, but in this case you lose the data.
>
> 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). 
>
> So, it remains to try the 2 points up here when the problem will come out 
> again. Did anyone try?
>
>
> Il giorno mercoledì 16 ottobre 2019 13:40:59 UTC+2, Thomas Keffer ha 
> scritto:
>>
>> This is likely a case of memory corruption, brought on by time not being 
>> synced during the reboot, due to the lack of an on-board clock. It was not 
>> a problem with Weatherlink because you were not running it on an RPi.
>>
>> See the section *WeeWX generated HTML pages, but does not update them 
>> * in 
>> the User's Guide.
>>
>> But, as Andrew suggested, we would have to see the log from startup to be 
>> sure.
>>
>> -tk
>>
>> On Wed, Oct 16, 2019 at 4:04 AM Andrew Milner  
>> wrote:
>>
>>> what came just before the log you posted?  why is weewx attempting to do 
>>> a catchup? had weewx just been started?  had communications been lost for 
>>> some reason? We need to know what is causing weewx to attempt a catchup in 
>>> the first place.  You can never post too much log
>>>
>>>
>>>
>>>
>>> On Wednesday, 16 October 2019 13:52:51 UTC+3, Andrea Cecilia wrote:

 here it is. As you can see, there is no "added record [...] to 
 weewx.sdb" line, which indicates that it is not downloading data from the 
 datalogger, and the reson (I think) is explained in the highlighted line.

 Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Getting archive 
 packets since 2019-10-16 09:05:00 CEST (1571209500)
 Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Gentle wake up of 
 console successful
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Retrieving 5 page(
 s); starting index= 4
 *Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: DMPAFT complete: 
 page timestamp 2019-10-15 13:20:00 CEST (1571138400) less than final 
 timestamp 2019-10-16 09:05:00 CEST (1571209500)*
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Catch up complete.
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running 
 reports for latest time in the database.
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Requesting 200 
 LOOP packets.
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running 
 report 'StandardReport'
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Gentle wake up of 
 console successful
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Found 
 configuration file /home/weewx/skins/Standard/skin.conf for report 
 'StandardReport'
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: cheetahgenerator: using 
 search list ['weewx.cheetahgenerator.Almanac', 
 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', '
 weewx.ch
 eetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
 'weewx.cheetahgenerator.Extras']
 Oct 16 10:30:15 raspberrypi weewx-vp2[511]: manager: Daily summary 
 version is 2.0
 Oct 16 10:30:17 raspberrypi weewx-vp2[511]: cheetahgenerator: Generated 
 16 files for report StandardReport in 2.31 seconds
 Oct 16 10:30:17 raspberrypi weewx-vp2[511]: manager: Daily summary 
 version is 2.0
 Oct 16 10:30:18 raspberrypi weewx-vp2[511]: imagegenerator: Generated 
 15 images for StandardReport in 1.36 seconds
 Oct 16 10:30:18 raspberrypi weewx-vp2[511]: copygenerator: copied 0 
 files to /home/weewx/public_html/vp2
 Oct 16 10:30:18 raspberrypi weewx-vp2[511]: reportengine: Running 
 report 'FTP'
 Oct 16 10:30:19 raspberrypi weewx-vp2[511]: reportengine: Found 
 configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
 Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Attempting 
 connection to ftp.meteoregionelazio.it
 Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Connected to ftp
 .meteoregionelazio.it
 Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Uploaded file /
 

[weewx-user] Re: 2 different setups, graphs don't look the same.

[Andrew Milner]

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 
different intervals specified.  Have you verified that both stations a) 
have the same interval in weewx.conf  b)are both using either hardware or 
software record generation and c) the stations themselves have the same 
archive interval specified as is specified in weewx.conf (change with 
wee_device if needed)



On Thursday, 17 October 2019 14:23:55 UTC+3, John Burricelli wrote:
>
> 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 other. I have 
> the archive interval set for both at 300.  
>
> Is there some sort of setting I have overlooked somewhere?
>
>
> [image: VP2.png]
>
> [image: VantageVue.png]
>
>

-- 
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://groups.google.com/d/msgid/weewx-user/92ca6ff3-3856-45c1-af25-dbb62b2d3cf5%40googlegroups.com.

Re: [weewx-user] Re: Davis Datalogger bug

[Andrea Cecilia]

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 plug it again;
2) make a /home/weewx/bin/wee_device --dump.
They also specificate that if these won't work, it is necessary to give a 
--clera-memory as I did, but in this case you lose the data.

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). 

So, it remains to try the 2 points up here when the problem will come out 
again. Did anyone try?


Il giorno mercoledì 16 ottobre 2019 13:40:59 UTC+2, Thomas Keffer ha 
scritto:
>
> This is likely a case of memory corruption, brought on by time not being 
> synced during the reboot, due to the lack of an on-board clock. It was not 
> a problem with Weatherlink because you were not running it on an RPi.
>
> See the section *WeeWX generated HTML pages, but does not update them 
> * in 
> the User's Guide.
>
> But, as Andrew suggested, we would have to see the log from startup to be 
> sure.
>
> -tk
>
> On Wed, Oct 16, 2019 at 4:04 AM Andrew Milner  > wrote:
>
>> what came just before the log you posted?  why is weewx attempting to do 
>> a catchup? had weewx just been started?  had communications been lost for 
>> some reason? We need to know what is causing weewx to attempt a catchup in 
>> the first place.  You can never post too much log
>>
>>
>>
>>
>> On Wednesday, 16 October 2019 13:52:51 UTC+3, Andrea Cecilia wrote:
>>>
>>> here it is. As you can see, there is no "added record [...] to 
>>> weewx.sdb" line, which indicates that it is not downloading data from the 
>>> datalogger, and the reson (I think) is explained in the highlighted line.
>>>
>>> Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Getting archive 
>>> packets since 2019-10-16 09:05:00 CEST (1571209500)
>>> Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Gentle wake up of 
>>> console successful
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Retrieving 5 page(s
>>> ); starting index= 4
>>> *Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: DMPAFT complete: 
>>> page timestamp 2019-10-15 13:20:00 CEST (1571138400) less than final 
>>> timestamp 2019-10-16 09:05:00 CEST (1571209500)*
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Catch up complete.
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running 
>>> reports for latest time in the database.
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Requesting 200 
>>> LOOP packets.
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running 
>>> report 'StandardReport'
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Gentle wake up of 
>>> console successful
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Found 
>>> configuration file /home/weewx/skins/Standard/skin.conf for report 
>>> 'StandardReport'
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: cheetahgenerator: using 
>>> search list ['weewx.cheetahgenerator.Almanac', 
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', '
>>> weewx.ch
>>> eetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>>> 'weewx.cheetahgenerator.Extras']
>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: manager: Daily summary 
>>> version is 2.0
>>> Oct 16 10:30:17 raspberrypi weewx-vp2[511]: cheetahgenerator: Generated 
>>> 16 files for report StandardReport in 2.31 seconds
>>> Oct 16 10:30:17 raspberrypi weewx-vp2[511]: manager: Daily summary 
>>> version is 2.0
>>> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: imagegenerator: Generated 15 
>>> images for StandardReport in 1.36 seconds
>>> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: copygenerator: copied 0 
>>> files to /home/weewx/public_html/vp2
>>> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: reportengine: Running 
>>> report 'FTP'
>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: reportengine: Found 
>>> configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Attempting 
>>> connection to ftp.meteoregionelazio.it
>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Connected to ftp.
>>> meteoregionelazio.it
>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Uploaded file /
>>> www.meteoregionelazio.it/stazioni/soriano/weewx/vp2/daypond.png
>>>
>>>
>>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> 

[weewx-user] 2 different setups, graphs don't look the same.

[John Burricelli]

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 other. I have 
the archive interval set for both at 300.  

Is there some sort of setting I have overlooked somewhere?


[image: VP2.png]

[image: VantageVue.png]

-- 
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://groups.google.com/d/msgid/weewx-user/b7270097-9222-422c-a344-cb084458e21f%40googlegroups.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[steeple ian]

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 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 /[path_to]/HP1000-master.zip
> sudo python wee_config --reconfigure
>
> This works for me.
>
> Thanks,
> Ian
>
> On Thu, 17 Oct 2019 at 03:47, Susan Mackay  wrote:
>
>> Could you elaborate a bit more for the sake of others trying to do the
>> same? (Also for me - lets me know what problems others have overcome
>> if/when I come to update the code.)
>> 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 discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/4bfbb7f6-dc47-43dd-8e88-5bc60e0e428f%40googlegroups.com
>> 
>> .
>>
>

-- 
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://groups.google.com/d/msgid/weewx-user/CADASSaRounw%2BOOd%2BM-_zBVpR2M0F-ASMXVF7fRCccAb0c-9Prg%40mail.gmail.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[steeple ian]

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 /[path_to]/HP1000-master.zip
sudo python wee_config --reconfigure

This works for me.

Thanks,
Ian

On Thu, 17 Oct 2019 at 03:47, Susan Mackay  wrote:

> Could you elaborate a bit more for the sake of others trying to do the
> same? (Also for me - lets me know what problems others have overcome
> if/when I come to update the code.)
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4bfbb7f6-dc47-43dd-8e88-5bc60e0e428f%40googlegroups.com
> 
> .
>

-- 
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://groups.google.com/d/msgid/weewx-user/CADASSaRiSWx2nsYp%2BnfDDmQ7PdtEP3L0P-k4OE5Dv6HRUA3eyA%40mail.gmail.com.