Re: [weewx-user] Davis VP2 reliability with Rasp Pi zero

[brisguy foo]

Thanks all for the feedback! The engineer in me wants to debug this, but
assuming a UPS does the trick, probably best left alone. I do appreciate
all the effort put into weewx and since the interface is purely through the
api, seems like it must be a logger problem. I am going to take a look at
the Pi power supply though, just to see what it does on power cycle.

On Fri, Jan 6, 2023 at 4:17 AM Greg Troxel  wrote:

> "iams...@gmail.com"  writes:
>
> > I've looked into getting a UPS for the Pi, which really appears to be
> > nothing more than a $15 ext phone battery, but it seems to me this is a
> > weewx problem that should be addressed. Alternately, I can contact Davis
> to
> > see what they say.
> > "
>
> It seems, from long history, that if the computer that is polling the
> data logger goes away suddenly while interacting with the logger, the
> logger can get messed up.   This is arguably a bug in the logger.
>
> My advice, just like the advice you got from others, is get a UPS, which
> will also help avoid filesystem mess on the RPI0.
>
> If you want to trace what's on the serial and experiment and figure out
> what's going on, you certainly can.   But, pretty much everybody with
> the skills to do that believes in "you should get a UPS".
>

-- 
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/CAJ-dst1yVMkWqdDGyi9pD8iic%3D6GkT2-26cr3LrRDu32Xdb4yQ%40mail.gmail.com.

Re: [weewx-user] running weewx directly and as daemon

[brisguy foo]

My original complaint was that I could not get the daemon to START without 
rebooting the system. I never mentioned problems with shutting it down. If 
you look at the log starting around 10:47, you'll see messages indicating 
that weewx has started, but it should have posted a new record at 11:50 
(and every five minutes thereafter), but did not. Same thing starting at 
11:27. At that point, I reboot so I can mount a USB drive onto the system, 
which involves disconnecting the weather-station since I only have one USB 
port I can use! After that reboot, the system ran normally.

Anyway, if I am using the correct commands, I'm fine. I may try running 
more tests using the 'systemctl' on the command line when starting the 
daemon.

On Monday, August 3, 2020 at 8:37:33 AM UTC-7, vince wrote:
>
> On Sunday, August 2, 2020 at 8:25:24 PM UTC-7, brisguy foo wrote:
>
>> In the log, the switching between direct a daemon execution starts around 
>> 10:15 which is when I finally successfully installed version 4.1.1. It 
>> looks like I killed the daemon around 10:15 and fixed an error in the .conf 
>> file and started directly. Then stopped that and tried to start the daemon. 
>> You will see a reboot eventually after that, at which point everything 
>> works. At some point, I also changed the conf debug setting from zero to 1.
>>
>>
> I guess I'm missing what you see in the log that leads you to think it 
> didn't shut down.
>
> Try a test.do a 'sudo systemctl stop weewx' and see what it 
> saysthen do 'sudo systemctl status weewx'then do "ps aux | grep 
> weewx" and see if there are any processes actually running
>

-- 
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/e0464b3f-046f-491f-a00e-34e59f78093bo%40googlegroups.com.

[weewx-user] running weewx directly and as daemon

[brisguy foo]

I had to do some debugging og my weewx installation recently and needed to 
swap back and forth between running directly and as a daemon. However, once 
I used the direct method, I never seem to be able to get the daemon 
launched again without just doing a reboot.

I have been doing the following (starting from a running daemon)
sudo /etc/init.d/weewx stop  # to stop the daemon
sudo weewxd /etc/weewx/weewx.conf  # to run directly
CTL-C   # to stop running directly
sudo /etc/init.d/weewx start  # to start the daemon

After the attempt to start the daemon, the terminal responds [OK], but 
looking at the syslog file, I can see it never did and there is no error 
message. At this point, I reboot and things run fine.

What is the correct way to start/stop these processes?

-- 
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/da07f3e0-1205-4d15-94ce-9b2eb28a8ec3o%40googlegroups.com.

[weewx-user] Re: problem with 4.1.1

[brisguy foo]

That was it, thanks! I should have known that the problem was caused by 
weewx.conf but did not see any mention of that file in the error message 
and was not confident the error occurred the first time I used the modified 
file. Ran into a problem starting the daemon, but I am going to post that 
in a new thread.

On Sunday, August 2, 2020 at 12:04:12 PM UTC-7, vince wrote:
>
> On Sunday, August 2, 2020 at 11:51:54 AM UTC-7, brisguy foo wrote:
>>
>> configobj.DuplicateError: Duplicate keyword name at line 119.
>>
>> Any ideas on how to fix this? 
>>
>
> I'd suggest you look at line 119 in weewx.conf and you'll notice you have 
> a duplicate keyword line there. 
>

-- 
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/b3c493f7-edc4-4f0d-ae33-02e3a5f17427o%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

Thanks Graham. I read that killing the install process will mess up the 
install at a minimum and possibly corrupt the system. Is there a way to get 
back to the install script from the D option?

On Thursday, July 30, 2020 at 11:55:39 PM UTC-7, Graham Eddy wrote:
>
> ctl-Z stop just means you have paused the command and placed it in 
> background - it is still there, waiting, but paused (and holding the lock). 
> bring it back to foreground to resume and interact with it by  $ fg 
>  
> then kill it with ctl-C
> (or use some other method to kill it gently such as$ kill %1)
> then try the command again.
> cheers
>
> On 31 Jul 2020, at 3:24 pm, brisguy foo > 
> wrote:
>
> Sorry, that was a typo. I did run apt-get update (not upgrade). It seemed 
> to run successfully but I just now noticed the following:
>
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Origin' value from '. squeeze' to 'python2 squeeze'
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Label' value from '. squeeze' to 'python2 squeeze'
> N: This must be accepted explicitly before updates for this repository can 
> be applied. See apt-secure(8) manpage for details.
>
> Turns out there was an error when I tried to do the update. I got around 
> this by rerunning the commands to trust weewx repository and configure 
> python 3. Did not do this before because the user's guide says you only 
> need to do it once upon first install.
>
> Anyway, during the weewx install it told me it was going to replace 
> skins.conf and allowed me the D option to see the differences, but I could 
> not figure out how to get out of it. After trying several things, I used 
> CTL-Z which stopped the install process (I knew I would screw it up !). 
> Tried running install afterwards, but it won't run - saying the process is 
> locked.
>
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
> temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), 
> is another process using it?
>
> Is there any was to recover from this?
>
> On Thursday, July 30, 2020 at 6:14:08 PM UTC-7, Kevin Davis wrote:
>>
>> Do an “apt-get update” first to update the package manager so it’s aware 
>> of the newest version numbers. 
>>
>>
>> On Jul 30, 2020, at 6:04 PM, brisguy foo  wrote:
>>
>> 
>> Ah, thanks for that. Should have been able to figure that out myself. 
>>
>> However, I just tried to upgrade using these commands:
>> sudo apt-get upgrade
>> sudo apt-get install weewx
>>
>> And was informed that 3.9.2 is the latest version!
>>
>> Does this mean I have to download the .tar and do it manually? I'm not 
>> too confident I can pull that off...
>>
>> On Thursday, July 30, 2020 at 4:16:29 PM UTC-7, Tom Keffer wrote:
>>>
>>> See the Upgrade Guide. http://www.weewx.com/docs/upgrading.htm
>>>
>>> On Thu, Jul 30, 2020 at 3:25 PM brisguy foo  wrote:
>>>
>>>> I was about to for that anyway. However, now that I am ready, I am not 
>>>> sure how to proceed. I see some info on installing and some on removing 
>>>> but 
>>>> none on upgrading. Do I need to uninstall first? Or is there an apt-get 
>>>> upgrade command?
>>>>
>>>> Thanks again.
>>>>
>>>> On Thursday, July 30, 2020 at 11:54:01 AM UTC-7, Tom Keffer wrote:
>>>>>
>>>>> Found the problem. You're using V3.9.2, but support for the LOOP2 
>>>>> format was not introduced until V4.0.0. You'll need to upgrade to do this.
>>>>>
>>>>> I was misled because the change log (wrongly) said that support for 
>>>>> LOOP2 packets was introduced in V3.7.0, so I assumed support was there 
>>>>> --- 
>>>>> I never bothered to check the actual code base. The log was fixed in 
>>>>> commit 
>>>>> 56ebe96 
>>>>> <https://github.com/weewx/weewx/commit/56ebe963e55c73b030492be9ecb6ad84d6885e2a>
>>>>>
>>>>> Sorry for the confusion.
>>>>>
>>>>> -tk
>>>>>
>>>>> On Thu, Jul 30, 2020 at 10:39 AM brisguy foo  
>>>>> wrote:
>>>>>
>>>>>> I suppose that is possible, but remember, I started the program 
>>>>>> directly, using the /etc/weewx/weewx.conf as the conf file. That is the 
>>>>>> file I sent to this thread.
>>>>>>
>>>>>> Here is the syslog 

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

Sorry, that was a typo. I did run apt-get update (not upgrade). It seemed 
to run successfully but I just now noticed the following:

E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Origin' 
value from '. squeeze' to 'python2 squeeze'
E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Label' 
value from '. squeeze' to 'python2 squeeze'
N: This must be accepted explicitly before updates for this repository can 
be applied. See apt-secure(8) manpage for details.

Turns out there was an error when I tried to do the update. I got around 
this by rerunning the commands to trust weewx repository and configure 
python 3. Did not do this before because the user's guide says you only 
need to do it once upon first install.

Anyway, during the weewx install it told me it was going to replace 
skins.conf and allowed me the D option to see the differences, but I could 
not figure out how to get out of it. After trying several things, I used 
CTL-Z which stopped the install process (I knew I would screw it up !). 
Tried running install afterwards, but it won't run - saying the process is 
locked.

E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), 
is another process using it?

Is there any was to recover from this?

On Thursday, July 30, 2020 at 6:14:08 PM UTC-7, Kevin Davis wrote:
>
> Do an “apt-get update” first to update the package manager so it’s aware 
> of the newest version numbers. 
>
>
> On Jul 30, 2020, at 6:04 PM, brisguy foo > 
> wrote:
>
> 
> Ah, thanks for that. Should have been able to figure that out myself. 
>
> However, I just tried to upgrade using these commands:
> sudo apt-get upgrade
> sudo apt-get install weewx
>
> And was informed that 3.9.2 is the latest version!
>
> Does this mean I have to download the .tar and do it manually? I'm not too 
> confident I can pull that off...
>
> On Thursday, July 30, 2020 at 4:16:29 PM UTC-7, Tom Keffer wrote:
>>
>> See the Upgrade Guide. http://www.weewx.com/docs/upgrading.htm
>>
>> On Thu, Jul 30, 2020 at 3:25 PM brisguy foo  wrote:
>>
>>> I was about to for that anyway. However, now that I am ready, I am not 
>>> sure how to proceed. I see some info on installing and some on removing but 
>>> none on upgrading. Do I need to uninstall first? Or is there an apt-get 
>>> upgrade command?
>>>
>>> Thanks again.
>>>
>>> On Thursday, July 30, 2020 at 11:54:01 AM UTC-7, Tom Keffer wrote:
>>>>
>>>> Found the problem. You're using V3.9.2, but support for the LOOP2 
>>>> format was not introduced until V4.0.0. You'll need to upgrade to do this.
>>>>
>>>> I was misled because the change log (wrongly) said that support for 
>>>> LOOP2 packets was introduced in V3.7.0, so I assumed support was there --- 
>>>> I never bothered to check the actual code base. The log was fixed in 
>>>> commit 
>>>> 56ebe96 
>>>> <https://github.com/weewx/weewx/commit/56ebe963e55c73b030492be9ecb6ad84d6885e2a>
>>>>
>>>> Sorry for the confusion.
>>>>
>>>> -tk
>>>>
>>>> On Thu, Jul 30, 2020 at 10:39 AM brisguy foo  wrote:
>>>>
>>>>> I suppose that is possible, but remember, I started the program 
>>>>> directly, using the /etc/weewx/weewx.conf as the conf file. That is the 
>>>>> file I sent to this thread.
>>>>>
>>>>> Here is the syslog file. Sorry, it is a bit busy since I found that 
>>>>> the daemon did not restart yesterday when I thought it did (still don't 
>>>>> know why - no error message and the terminal indicated success) and would 
>>>>> not start from the command line today so when I ran it directly again, 
>>>>> there were lots of records to catch up. 
>>>>>
>>>>> On Wednesday, July 29, 2020 at 4:43:44 PM UTC-7, Tom Keffer wrote:
>>>>>>
>>>>>> On a side note, when I tried running weewx directly without a config 
>>>>>>> file argument, it would not run, even though my config file is located 
>>>>>>> at 
>>>>>>> /etc/weewx/weewx.conf. Is that a bug?
>>>>>>>
>>>>>>
>>>>>> No, but it suggests that you may not be editing the weewx.conf file 
>>>>>> that weewxd is actually using.
>>>>>>
>>>>>> At this point, I have to ask for a log. Restart weewx, let it run 
>>>>>> th

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

Ah, thanks for that. Should have been able to figure that out myself. 

However, I just tried to upgrade using these commands:
sudo apt-get upgrade
sudo apt-get install weewx

And was informed that 3.9.2 is the latest version!

Does this mean I have to download the .tar and do it manually? I'm not too 
confident I can pull that off...

On Thursday, July 30, 2020 at 4:16:29 PM UTC-7, Tom Keffer wrote:
>
> See the Upgrade Guide. http://www.weewx.com/docs/upgrading.htm
>
> On Thu, Jul 30, 2020 at 3:25 PM brisguy foo  > wrote:
>
>> I was about to for that anyway. However, now that I am ready, I am not 
>> sure how to proceed. I see some info on installing and some on removing but 
>> none on upgrading. Do I need to uninstall first? Or is there an apt-get 
>> upgrade command?
>>
>> Thanks again.
>>
>> On Thursday, July 30, 2020 at 11:54:01 AM UTC-7, Tom Keffer wrote:
>>>
>>> Found the problem. You're using V3.9.2, but support for the LOOP2 format 
>>> was not introduced until V4.0.0. You'll need to upgrade to do this.
>>>
>>> I was misled because the change log (wrongly) said that support for 
>>> LOOP2 packets was introduced in V3.7.0, so I assumed support was there --- 
>>> I never bothered to check the actual code base. The log was fixed in commit 
>>> 56ebe96 
>>> <https://github.com/weewx/weewx/commit/56ebe963e55c73b030492be9ecb6ad84d6885e2a>
>>>
>>> Sorry for the confusion.
>>>
>>> -tk
>>>
>>> On Thu, Jul 30, 2020 at 10:39 AM brisguy foo  wrote:
>>>
>>>> I suppose that is possible, but remember, I started the program 
>>>> directly, using the /etc/weewx/weewx.conf as the conf file. That is the 
>>>> file I sent to this thread.
>>>>
>>>> Here is the syslog file. Sorry, it is a bit busy since I found that the 
>>>> daemon did not restart yesterday when I thought it did (still don't know 
>>>> why - no error message and the terminal indicated success) and would not 
>>>> start from the command line today so when I ran it directly again, there 
>>>> were lots of records to catch up. 
>>>>
>>>> On Wednesday, July 29, 2020 at 4:43:44 PM UTC-7, Tom Keffer wrote:
>>>>>
>>>>> On a side note, when I tried running weewx directly without a config 
>>>>>> file argument, it would not run, even though my config file is located 
>>>>>> at 
>>>>>> /etc/weewx/weewx.conf. Is that a bug?
>>>>>>
>>>>>
>>>>> No, but it suggests that you may not be editing the weewx.conf file 
>>>>> that weewxd is actually using.
>>>>>
>>>>> At this point, I have to ask for a log. Restart weewx, let it run 
>>>>> through the first reporting cycle. Post the resultant log.
>>>>>
>>>>> -tk
>>>>>
>>>> -- 
>>>> 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 
>>>> https://groups.google.com/d/msgid/weewx-user/0cd14da1-7635-44c5-a13b-197d45725537o%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/0cd14da1-7635-44c5-a13b-197d45725537o%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>> 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 
>> https://groups.google.com/d/msgid/weewx-user/38fa16ae-b22e-4611-8d81-053989827c96o%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/38fa16ae-b22e-4611-8d81-053989827c96o%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/ddd2e056-605d-4038-9aad-7e8112a40cf8o%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

I was about to for that anyway. However, now that I am ready, I am not sure 
how to proceed. I see some info on installing and some on removing but none 
on upgrading. Do I need to uninstall first? Or is there an apt-get upgrade 
command?

Thanks again.

On Thursday, July 30, 2020 at 11:54:01 AM UTC-7, Tom Keffer wrote:
>
> Found the problem. You're using V3.9.2, but support for the LOOP2 format 
> was not introduced until V4.0.0. You'll need to upgrade to do this.
>
> I was misled because the change log (wrongly) said that support for LOOP2 
> packets was introduced in V3.7.0, so I assumed support was there --- I 
> never bothered to check the actual code base. The log was fixed in commit 
> 56ebe96 
> <https://github.com/weewx/weewx/commit/56ebe963e55c73b030492be9ecb6ad84d6885e2a>
>
> Sorry for the confusion.
>
> -tk
>
> On Thu, Jul 30, 2020 at 10:39 AM brisguy foo  > wrote:
>
>> I suppose that is possible, but remember, I started the program directly, 
>> using the /etc/weewx/weewx.conf as the conf file. That is the file I sent 
>> to this thread.
>>
>> Here is the syslog file. Sorry, it is a bit busy since I found that the 
>> daemon did not restart yesterday when I thought it did (still don't know 
>> why - no error message and the terminal indicated success) and would not 
>> start from the command line today so when I ran it directly again, there 
>> were lots of records to catch up. 
>>
>> On Wednesday, July 29, 2020 at 4:43:44 PM UTC-7, Tom Keffer wrote:
>>>
>>> On a side note, when I tried running weewx directly without a config 
>>>> file argument, it would not run, even though my config file is located at 
>>>> /etc/weewx/weewx.conf. Is that a bug?
>>>>
>>>
>>> No, but it suggests that you may not be editing the weewx.conf file that 
>>> weewxd is actually using.
>>>
>>> At this point, I have to ask for a log. Restart weewx, let it run 
>>> through the first reporting cycle. Post the resultant log.
>>>
>>> -tk
>>>
>> -- 
>> 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 
>> https://groups.google.com/d/msgid/weewx-user/0cd14da1-7635-44c5-a13b-197d45725537o%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/0cd14da1-7635-44c5-a13b-197d45725537o%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/38fa16ae-b22e-4611-8d81-053989827c96o%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

OK, I tried stopping the daemon and running directly. The LOOP data shows 
no difference between outTemp and windchill although the console shows a 4 
degree difference. I have attached my conf file in case I messed up 
something. I see that when the change to support LOOP2 was submitted, a 
request was made for testers. Was it ever tested?

On a side note, when I tried running weewx directly without a config file 
argument, it would not run, even though my config file is located at 
/etc/weewx/weewx.conf. Is that a bug?

Thanks!


On Tuesday, July 28, 2020 at 5:56:38 PM UTC-7, gjr80 wrote:
>
> On Wednesday, 29 July 2020 10:00:01 UTC+10, brisguy foo wrote:
>>
>> UPDATE:
>>
>> Changed by weewx,conf file to read:
>> [Vantage]
>> ...
>> # Use LOOP2 data in order to get access to wind_chill
>> loop_request = 2
>>
>> Restarted weewx
>>
>> After only an hour or so, I saw that my console was reporting wind-chill 
>> that was 2 to 3 degrees lower than outside temp, but the weewx graph showed 
>> no difference.
>>
>
> Using the plots to check what is happening can give misleading results; 
> not saying that is the case here but some plots are not generated every 
> cycle and there can be caching issues. Best evidence is to look at what is 
> in the database or loop packets/archive records or look at the database.
>  
>
>>
>> Checked the syslog file today, and at the time of the restart found the 
>> following odd statement:
>> 16:40:18 raspberrypi weewx[30378]: wxcalculate: The following values will 
>> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
>> rainRate=prefer_hardware, windrun=prefer_hardware, 
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>> humidex=prefer_hardware, pressure=prefer_hardware, 
>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
>> cloudbase=prefer_hardware
>>
>> It seems odd that weewx would report it is calculating values that have 
>> been set to 'prefer_hardware', plus I only used that for five parameters, 
>> and weewx is reporting it has been set for several more.
>>
>> So now I have two issues:
>> 1. How can I tell whether LOOP2 packets ate being used (the graph 
>> indicates they are not)
>>
>
> There is no direct way that I know of. I would stop WeeWX and then run it 
> directly so you see the loop packets and archive records on the console. 
> What do you see in the loop packets (lines starting with LOOP:) and archive 
> records (lines starting REC:) on the console? How does windchill compare to 
> outTemp? If you are seeing THSW in the loop packets then WeeWX is receiving 
> the LOOP2 format loop packet, if THSW is not there then I suspect you are 
> still using the LOOP format loop packets. 
>  
>
>> 2. Why is weewx reporting it is calculating values that have been set to 
>> 'prefer_hardware'?
>>
>
> If WeeWX is calculating windchill it is most likely because windchill is 
> not being received by WeeWX. Change 'prefer_hardware' to 'hardware' for 
> windchill and restart/reload WeeWX. If windchill disappears it will be 
> because WeeWX is not receiving windchill which implies you are still using 
> LOOP format loop packets.
>
> @tkeffer. Tom, I see the vantage driver does not log what format loop 
> packet is being used, perhaps it should?
>
> Gary
>
>>
>> Thanks,  Stan
>>
>>
>> On Monday, July 27, 2020 at 4:47:41 PM UTC-7, brisguy foo wrote:
>>>
>>> Thanks for the replies guys!
>>>
>>> I did update my conf file as suggested, however I am confused by the 
>>> comment that wind chill "is not in the LOOP or archive record from the 
>>> console".
>>>
>>> I know I was able to see wind chill in historical data downloaded from 
>>> the console logger and displayed using WeatherLink. If you are referring to 
>>> the weewx archive, then I am concerned that the not all LOOP 2 data is 
>>> being stored.
>>>
>>> Please help me understand if you don't mind. I should be able to see the 
>>> result in a few days anyway, but I'd like to know how this works.
>>>
>>> Thanks!
>>>
>>>
>>>
>>> On Friday, July 24, 2020 at 5:21:48 PM UTC-7, Tom Keffer wrote:
>>>>
>>>> Geez, Gary, you're right! So, you would also have to specify LOOP2 
>>>> packets. See the section [Vantage] 
>>>> <http://www.weewx.com/docs/usersguide.htm#[Vantage]> in the User's 
>>>> Guide.
>>>>
>>

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

UPDATE:

Changed by weewx,conf file to read:
[Vantage]
...
# Use LOOP2 data in order to get access to wind_chill
loop_request = 2

Restarted weewx

After only an hour or so, I saw that my console was reporting wind-chill 
that was 2 to 3 degrees lower than outside temp, but the weewx graph showed 
no difference.

Checked the syslog file today, and at the time of the restart found the 
following odd statement:
16:40:18 raspberrypi weewx[30378]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware

It seems odd that weewx would report it is calculating values that have 
been set to 'prefer_hardware', plus I only used that for five parameters, 
and weewx is reporting it has been set for several more.

So now I have two issues:
1. How can I tell whether LOOP2 packets ate being used (the graph indicates 
they are not)
2. Why is weewx reporting it is calculating values that have been set to 
'prefer_hardware'?

Thanks,  Stan


On Monday, July 27, 2020 at 4:47:41 PM UTC-7, brisguy foo wrote:
>
> Thanks for the replies guys!
>
> I did update my conf file as suggested, however I am confused by the 
> comment that wind chill "is not in the LOOP or archive record from the 
> console".
>
> I know I was able to see wind chill in historical data downloaded from the 
> console logger and displayed using WeatherLink. If you are referring to the 
> weewx archive, then I am concerned that the not all LOOP 2 data is being 
> stored.
>
> Please help me understand if you don't mind. I should be able to see the 
> result in a few days anyway, but I'd like to know how this works.
>
> Thanks!
>
>
>
> On Friday, July 24, 2020 at 5:21:48 PM UTC-7, Tom Keffer wrote:
>>
>> Geez, Gary, you're right! So, you would also have to specify LOOP2 
>> packets. See the section [Vantage] 
>> <http://www.weewx.com/docs/usersguide.htm#[Vantage]> in the User's Guide.
>>
>> [Vantage]
>>   loop_request = 2
>>
>>
>> -tk
>>
>> On Fri, Jul 24, 2020 at 5:13 PM gjr80  wrote:
>>
>>> Windchill is only in included in the Davis LOOP2 packet, it’s not in the 
>>> LOOP packet or archive record (the defaults) from the console. So unless 
>>> you have set WeeWX to use the LOOP2 packet WeeWX will never see windchill 
>>> from the console, irrespective of StdWXCalculate settings.
>>>
>>> Gary
>>>
>>> -- 
>>> 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 
>>> https://groups.google.com/d/msgid/weewx-user/9a8a0b4e-4b27-404b-aec4-72cd8dbc7331o%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/2c55be9f-6f74-4873-b9e4-dcfee794940bo%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

Thanks for the replies guys!

I did update my conf file as suggested, however I am confused by the 
comment that wind chill "is not in the LOOP or archive record from the 
console".

I know I was able to see wind chill in historical data downloaded from the 
console logger and displayed using WeatherLink. If you are referring to the 
weewx archive, then I am concerned that the not all LOOP 2 data is being 
stored.

Please help me understand if you don't mind. I should be able to see the 
result in a few days anyway, but I'd like to know how this works.

Thanks!



On Friday, July 24, 2020 at 5:21:48 PM UTC-7, Tom Keffer wrote:
>
> Geez, Gary, you're right! So, you would also have to specify LOOP2 
> packets. See the section [Vantage] 
>  in the User's Guide.
>
> [Vantage]
>   loop_request = 2
>
>
> -tk
>
> On Fri, Jul 24, 2020 at 5:13 PM gjr80 > 
> wrote:
>
>> Windchill is only in included in the Davis LOOP2 packet, it’s not in the 
>> LOOP packet or archive record (the defaults) from the console. So unless 
>> you have set WeeWX to use the LOOP2 packet WeeWX will never see windchill 
>> from the console, irrespective of StdWXCalculate settings.
>>
>> Gary
>>
>> -- 
>> 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 
>> https://groups.google.com/d/msgid/weewx-user/9a8a0b4e-4b27-404b-aec4-72cd8dbc7331o%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/80976d1d-89f9-45b5-a2e0-14b5794b4f7co%40googlegroups.com.

[weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

Thanks for the reply. I did check the weewx.conf file and and found that 
wind chill should be coming from the VP2. See below. I believe your comment 
about when wind chill applies is only for the case where weewx calculates 
the result. The VP2 does not have the restriction of being below 50deg. 
Note that if I use the software supplied by Davis (WeatherLink), it will 
display the wind chill data that matches what is displayed on the console. 
Is there something else I may be missing?

[StdWXCalculate]

[[Calculations]]
# How to calculate derived quantities.  Possible values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = prefer_hardware
windchill = prefer_hardware
heatindex = prefer_hardware
dewpoint = prefer_hardware
inDewpoint = prefer_hardware
rainRate = prefer_hardware

On Friday, July 24, 2020 at 11:03:45 AM UTC-7, brisguy foo wrote:
>
> Hello all,
>
> I have been using weewx (3.9.2.1 with standard skin) successfully for 
> several months now and just noticed that the wind chill graph does not 
> reflect the values reported by my VP2. It always matches the outside temp 
> values. I have seen that weewx can calculate wind chill on its own, but 
> since the VP2 provides this data, I was expecting weewx to use it. Does it?
>
> 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/561d6cb4-b7bf-400a-a017-511f545ea40do%40googlegroups.com.

[weewx-user] wind chill for Vantage Pro 2

[brisguy foo]

Hello all,

I have been using weewx (3.9.2.1 with standard skin) successfully for 
several months now and just noticed that the wind chill graph does not 
reflect the values reported by my VP2. It always matches the outside temp 
values. I have seen that weewx can calculate wind chill on its own, but 
since the VP2 provides this data, I was expecting weewx to use it. Does it?

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/d3d9484a-e40d-457b-a2c3-42f891605a57o%40googlegroups.com.

[weewx-user] Re: VP 2 archive interval vs database vs Wunderground update

[brisguy foo]

Great. Thanks for the help!

On Saturday, January 11, 2020 at 12:09:04 PM UTC-8, vince wrote:
>
> On Saturday, January 11, 2020 at 11:45:22 AM UTC-8, brisguy foo wrote:
>>
>>  so apparently, I am using SQLite even though I did not do anything other 
>> than the normal weewx install.
>>
>
> Yes - sqlite3 is the default
>
> Will this db have all the data from my data logger or just the new records 
>> that weewx has created?
>>
>
> Weewx will backfill anything it can find in the logger from a VP2.
>
> 4. Assuming I DO have to change the archive interval in order to get 
>> faster updates, is there a way for me restore the lost data by updating the 
>> db and if I do so, will it be accessible using weewx reports?
>>
>>
> Weewx reports and graphs whatever is in the database, so if you can get 
> the data into it, the report/graphing engines will report/display it.
>  
>

-- 
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/c980b106-12a9-469d-b3f8-3c5aaf64d9cf%40googlegroups.com.

[weewx-user] VP 2 archive interval vs database vs Wunderground update

[brisguy foo]

Hi All,

Just got weewx running last week on a RP zero and have it successfully 
uploading to Wunderground. I did not opt for the Rapidfire mode since the 
user info seemed to indicate this was risky and/or unnecessary. As a 
result, my PWS page only updates once every 30 minutes since  that is the 
archive interval on my Vantage Pro 2. I was about to change the archive 
interval using wee_device, but it gave me this message: 'Old archive 
interval is 30 minutes, new one will be 10 minutes. Proceeding will change 
the archive interval as well as erase all old archive records.'

I have several questions:

1. I don't really want to lose the two months of data in my data logger - 
specifically the temps and rain totals. I tried changing the weewx.conf 
file to Rapidfire=True to get faster updates, but there was no change. Do I 
have to change the archive interval in order to get faster Wunderground 
updates?
2. Will this change also affect my weewx database?
3. I find the database documentation confusing. It starts by saying two 
types of database can be used, but seems to indicate that the user must 
choose and install one. However, I checked under /var/lib/weewx and found 
that I do have a weewx.sdb file, so apparently, I am using SQLite even 
though I did not do anything other than the normal weewx install. Will this 
db have all the data from my data logger or just the new records that weewx 
has created?
4. Assuming I DO have to change the archive interval in order to get faster 
updates, is there a way for me restore the lost data by updating the db and 
if I do so, will it be accessible using weewx reports?

Thanks,  Stan

-- 
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/b43df574-51a9-40da-9bcc-acb033ebdab4%40googlegroups.com.