[weewx-user] Images in the Seasons Page Disappeared

[Steve Culp]

The seasons page stopped displaying the page full of graphs but the 
seasons code is still generating all of them as far as I can tell. 
Something must be abnormal in a seasons config file somewhere but I cant 
figure it out at my "Hello World!" programming expertise level. LOL.


I have never purposely modified any of the seasons files because it 
worked as expected with all graphs and  no issues right after installation.


Any hints or ideas from this group are welcome.

http://w5sdc.net/weather/seasons

Thanks in  advance,

--
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/694310dd-1e0f-42d9-9a19-ce89f9397604%40gmail.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Steve Gee]

I ended up adding the weewx user to the plughw group which fixed the 
problem with rtl_433 not starting:

sudo adduser weewx plughw
sudo systemctl restart weewx.service

On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík wrote:

> @Matthew:
>
> That makes sense yep. Thanks a lot for detailed explanation. I cannot 
> change port 80 on my hardware so I will review other options :)
>
> st 7. 2. 2024 v 8:08 odesílatel matthew wall  napsal:
>
>> another option is to put a proxy in front of interceptor.  configure 
>> interceptor to listen on a high port, say 8080, then run nginx binding to 
>> port 80 as a reverse proxy to interceptor, proxying all traffic or just 
>> specific requests.
>>
>> m
>>
>> -- 
>> 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/5BuR3BSQfeY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%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/3239d8e8-5e87-420a-a660-74666b1847ben%40googlegroups.com.

[weewx-user] Belchertown skin UK earthquakes

['Steve Daniels' via weewx-user]

Is it possible to add UK Earthquake data to the Belchertown skin
https://www.bgs.ac.uk/technologies/web-services/georss-feeds-uk-and-worldwide-earthquake-map/

There is an RSS feed linked to from that page

Thanks
Steve

-- 
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/c2ca14da-496f-4b43-a0fe-6d8dea5b0372n%40googlegroups.com.

Re: [weewx-user] Re: Need help with change to SFTP

[Steve Meltz]

Gary..thank you for the reply
 I think I have it sorted out. In my old version of Weewx, I made a few
changes in weewx.conf which seems to have worked, and as you said, the
Steel Guages are not affected.

On Sat, Dec 30, 2023, 12:31 AM gjr80  wrote:

> Steve,
>
> Sorry I cannot help with SFTP, but if you are using the realtime gauge
> data extension to drive your Steel Series gauges and use the HTTP POST or
> rsync to transfer gauge-data.txt to you server, the change to SFTP will
> have no impact on your gauges. The HTTP POST and rsync capabilities used by
> the realtime gauge data extension is completely independent of any
> transfers performed by the StdReport service.
>
> Gary
>
> On Thursday 28 December 2023 at 09:07:30 UTC+10 Steve2Q wrote:
>
>> Hello. I am a long time user, but have not had any reason (so far) to
>> update from V3.8.2. In the past few weeks, I have had problems where my
>> files stopped uploading to DreamHost. They found the error on their end,
>> but recommend that I change for FTP to SFTP. I have two questions:
>>
>> 1. Will this affect my Steel Gauges which continue working fine even when
>> the "regular" Weewx files are not uploading?
>>
>> 2. I am a very casual user, so I found that the directions on the Wiki
>> are insufficient to make me comfortable making the change. Can anyone walk
>> me through how to do it?
>>
>> Thanks, Steve
>>
> --
> 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/raoMHaewaOY/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/3fa2d55b-6062-4916-9eb4-631f4b887fd9n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/3fa2d55b-6062-4916-9eb4-631f4b887fd9n%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/CAH0o-any6uTKNo%2BO_Af7_RjNDjW-4hE%2BzKtKTmGAUMgg4MvjAw%40mail.gmail.com.

[weewx-user] Re: What are the defaut weewx data keys?

[Steve Coffin]

Thank you. Perfect

On Tuesday, December 12, 2023 at 4:53:16 PM UTC-7 vince wrote:

> Look at the schema for the db.
>
> https://github.com/weewx/weewx/blob/V5/src/schemas/wview_extended.py
>
> On Tuesday, December 12, 2023 at 3:44:56 PM UTC-8 Steve Coffin wrote:
>
>> I'm going to use the Fileparse dirver to pipe data from my home made WS 
>> to Weewx
>> I'd just like a complete list of the default keys for the key value 
>> pairs. I think the ones listed below some of them. Thanks for your help.
>>
>> windSpeed
>> windDir
>> outTemp
>> rain_total
>> barometer
>> inTemp
>> outHumidity
>> inHumidity
>> day_of_year
>> minute_of_day
>>
>

-- 
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/5c2d26bc-9937-4815-9627-28db0048f601n%40googlegroups.com.

[weewx-user] What are the defaut weewx data keys?

[Steve Coffin]

I'm going to use the Fileparse dirver to pipe data from my home made WS to 
Weewx
I'd just like a complete list of the default keys for the key value pairs. 
I think the ones listed below some of them. Thanks for your help.

windSpeed
windDir
outTemp
rain_total
barometer
inTemp
outHumidity
inHumidity
day_of_year
minute_of_day

-- 
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/3752f00a-cc35-47f7-b275-8cbfe1757e21n%40googlegroups.com.

[weewx-user] Re: Starting weewx

[Steve Fowler]

I had a similar problem when I installed the latest version of weewx.  It 
did not create the weewx web folder in /var/www/html.  Instead it put it in 
the /home/weewx folder so I created a link to it in the ./www/html folder.

On Saturday, November 25, 2023 at 9:52:16 AM UTC-8 vince wrote:

> No description of your setup in your problem report but you generally need 
> to open an actual URL in your browser, not the path that location is on 
> your filesystem.
>
> Try opening http://somehostname/weewx/index.html and see if that 
> worksbut...I can't say specifically what "somehostname" should be for 
> your installation given no description of your setup... but if you are 
> running weewx and webserver and browser on the same box, 
> http://127.0.0.1/weewx/index.html should work if you installed and 
> configured a webserver.
>
> Or... if your weewx is on the same computer as the browser you might be 
> able to use the browser "File" =>"Open File" menu, in which case you want 
> to use the filesystem path ala /var/www/html/weewx/index.html to open a 
> local file.
>
> Not much more we can help if you don't tell us what your setup actually is.
>
> On Saturday, November 25, 2023 at 3:51:23 AM UTC-8 JOHN CHENIS wrote:
>
>> I installed weewx but when i add this ( var/www/html/weewx/index.html)
>> to my google windows I get google search and not START/STOP.
>> What am I doling wrong?  Please help.
>> Thanks, John
>>
>

-- 
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/53706eac-c179-414c-aa05-118595b76985n%40googlegroups.com.

[weewx-user] Re: Upgraded OS and Weewx - fails to start

[Steve Fowler]

I hadn't posted it, but after installing weewx it failed to create the 
weewx web folder in /var/www/html directory.  Instead it ended up in weewx 
home.  So I created a link.

On Tuesday, November 14, 2023 at 1:16:20 PM UTC-8 Sylvain M wrote:

> I had the same problem with OpenSuse Tumbleweed where a big update even 
> blocked python-based system programs such as firewalld (it's not nothing), 
> others and of course weewx.
> I was able to check all the programs for errors with the command:
>
> # 
> *systemctl list-units --state=failed*
> I made a link from python3.11 to python3 which is the reference for many 
> programs:
>
> #* ln /usr/bin/python3.11 /usr/bin/python3*
>
> All programs worked again while avoiding changes in all files.
>
> Le samedi 11 novembre 2023 à 16:49:36 UTC+1, Steve Fowler a écrit :
>
>> Looks like I got it running by going back and running setup.py.  Whatever 
>> failed in the deb package install was corrected and the service started. 
>>
>> On Saturday, November 11, 2023 at 6:44:39 AM UTC-8 Steve Fowler wrote:
>>
>>> Followed the instructions for Debian install using deb package in the 
>>> weewx docs for python 3.  It downloaded the latest stable 4.10.2.  I 
>>> installed using root and not the weewx user if that makes and difference. 
>>> The system has python 3.11.2.  
>>>
>>> On Friday, November 10, 2023 at 9:40:12 PM UTC-8 vince wrote:
>>>
>>>> Which 'latest' ?  v4 or v5 beta ?
>>>> Which instructions ?
>>>>
>>>> On Friday, November 10, 2023 at 9:03:33 PM UTC-8 Steve Fowler wrote:
>>>>
>>>>> Just upgraded to Debian 12 and installed the latest version of weewx 
>>>>> according to the install steps for Debian.  Everything seemed to go along 
>>>>> smoothly until the end and I get this:
>>>>> Job for weewx.service failed because the control process exited with 
>>>>> error code.
>>>>> See "systemctl status weewx.service" and "journalctl -xeu 
>>>>> weewx.service" for details.
>>>>> invoke-rc.d: initscript weewx, action "start" failed.
>>>>> × weewx.service - LSB: weewx weather system
>>>>>  Loaded: loaded (/etc/init.d/weewx; generated)
>>>>>  Active: failed (Result: exit-code) since Fri 2023-11-10 20:26:25 
>>>>> PST; 22ms ago
>>>>>Docs: man:systemd-sysv-generator(8)
>>>>> Process: 12332 ExecStart=/etc/init.d/weewx start (code=exited, 
>>>>> status=1/FAILURE)
>>>>> CPU: 299ms
>>>>>
>>>>> Nov 10 20:26:25 corv-weewx systemd[1]: Starting weewx.service - LSB: 
>>>>> weewx weather system...
>>>>> Nov 10 20:26:25 corv-weewx weewx[12332]: Starting weewx weather 
>>>>> system: weewx
>>>>> Nov 10 20:26:25 corv-weewx weewx[12343]: Traceback (most recent call 
>>>>> last):
>>>>> Nov 10 20:26:25 corv-weewx weewx[12343]:   File 
>>>>> "/usr/share/weewx/weewxd", line 29, in 
>>>>> Nov 10 20:26:25 corv-weewx weewx[12343]: import user.extensions
>>>>> Nov 10 20:26:25 corv-weewx weewx[12343]: ModuleNotFoundError: No 
>>>>> module named 'user.extensions'
>>>>> Nov 10 20:26:25 corv-weewx weewx[12332]:  failed!
>>>>> Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Control process 
>>>>> exited, code=exited, status=1/FAILURE
>>>>> Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Failed with 
>>>>> result 'exit-code'.
>>>>> Nov 10 20:26:25 corv-weewx systemd[1]: Failed to start weewx.service - 
>>>>> LSB: weewx weather system.
>>>>> dpkg: error processing package weewx (--configure):
>>>>>  installed weewx package post-installation script subprocess returned 
>>>>> error exit status 1
>>>>> Processing triggers for man-db (2.11.2-2) ...
>>>>> Processing triggers for libc-bin (2.36-9+deb12u3) ...
>>>>> Errors were encountered while processing:
>>>>>  weewx
>>>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>>>
>>>>> systemctl and journalctl both point to weewxd not finding module 
>>>>> user.extentions. 
>>>>>
>>>>> Any help would be appreciated.
>>>>> Steve
>>>>>
>>>>>

-- 
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/83bad196-9729-4813-b3e2-3ac46fdbd590n%40googlegroups.com.

[weewx-user] Re: Upgraded OS and Weewx - fails to start

[Steve Fowler]

Looks like I got it running by going back and running setup.py.  Whatever 
failed in the deb package install was corrected and the service started. 

On Saturday, November 11, 2023 at 6:44:39 AM UTC-8 Steve Fowler wrote:

> Followed the instructions for Debian install using deb package in the 
> weewx docs for python 3.  It downloaded the latest stable 4.10.2.  I 
> installed using root and not the weewx user if that makes and difference. 
> The system has python 3.11.2.  
>
> On Friday, November 10, 2023 at 9:40:12 PM UTC-8 vince wrote:
>
>> Which 'latest' ?  v4 or v5 beta ?
>> Which instructions ?
>>
>> On Friday, November 10, 2023 at 9:03:33 PM UTC-8 Steve Fowler wrote:
>>
>>> Just upgraded to Debian 12 and installed the latest version of weewx 
>>> according to the install steps for Debian.  Everything seemed to go along 
>>> smoothly until the end and I get this:
>>> Job for weewx.service failed because the control process exited with 
>>> error code.
>>> See "systemctl status weewx.service" and "journalctl -xeu weewx.service" 
>>> for details.
>>> invoke-rc.d: initscript weewx, action "start" failed.
>>> × weewx.service - LSB: weewx weather system
>>>  Loaded: loaded (/etc/init.d/weewx; generated)
>>>  Active: failed (Result: exit-code) since Fri 2023-11-10 20:26:25 
>>> PST; 22ms ago
>>>Docs: man:systemd-sysv-generator(8)
>>> Process: 12332 ExecStart=/etc/init.d/weewx start (code=exited, 
>>> status=1/FAILURE)
>>> CPU: 299ms
>>>
>>> Nov 10 20:26:25 corv-weewx systemd[1]: Starting weewx.service - LSB: 
>>> weewx weather system...
>>> Nov 10 20:26:25 corv-weewx weewx[12332]: Starting weewx weather system: 
>>> weewx
>>> Nov 10 20:26:25 corv-weewx weewx[12343]: Traceback (most recent call 
>>> last):
>>> Nov 10 20:26:25 corv-weewx weewx[12343]:   File 
>>> "/usr/share/weewx/weewxd", line 29, in 
>>> Nov 10 20:26:25 corv-weewx weewx[12343]: import user.extensions
>>> Nov 10 20:26:25 corv-weewx weewx[12343]: ModuleNotFoundError: No module 
>>> named 'user.extensions'
>>> Nov 10 20:26:25 corv-weewx weewx[12332]:  failed!
>>> Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Control process 
>>> exited, code=exited, status=1/FAILURE
>>> Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Failed with result 
>>> 'exit-code'.
>>> Nov 10 20:26:25 corv-weewx systemd[1]: Failed to start weewx.service - 
>>> LSB: weewx weather system.
>>> dpkg: error processing package weewx (--configure):
>>>  installed weewx package post-installation script subprocess returned 
>>> error exit status 1
>>> Processing triggers for man-db (2.11.2-2) ...
>>> Processing triggers for libc-bin (2.36-9+deb12u3) ...
>>> Errors were encountered while processing:
>>>  weewx
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>
>>> systemctl and journalctl both point to weewxd not finding module 
>>> user.extentions. 
>>>
>>> Any help would be appreciated.
>>> Steve
>>>
>>>

-- 
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/4f667bcb-ac91-43c0-998d-32a8715777a8n%40googlegroups.com.

[weewx-user] Re: Upgraded OS and Weewx - fails to start

[Steve Fowler]

Followed the instructions for Debian install using deb package in the weewx 
docs for python 3.  It downloaded the latest stable 4.10.2.  I installed 
using root and not the weewx user if that makes and difference. The system 
has python 3.11.2.  

On Friday, November 10, 2023 at 9:40:12 PM UTC-8 vince wrote:

> Which 'latest' ?  v4 or v5 beta ?
> Which instructions ?
>
> On Friday, November 10, 2023 at 9:03:33 PM UTC-8 Steve Fowler wrote:
>
>> Just upgraded to Debian 12 and installed the latest version of weewx 
>> according to the install steps for Debian.  Everything seemed to go along 
>> smoothly until the end and I get this:
>> Job for weewx.service failed because the control process exited with 
>> error code.
>> See "systemctl status weewx.service" and "journalctl -xeu weewx.service" 
>> for details.
>> invoke-rc.d: initscript weewx, action "start" failed.
>> × weewx.service - LSB: weewx weather system
>>  Loaded: loaded (/etc/init.d/weewx; generated)
>>  Active: failed (Result: exit-code) since Fri 2023-11-10 20:26:25 
>> PST; 22ms ago
>>Docs: man:systemd-sysv-generator(8)
>> Process: 12332 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=1/FAILURE)
>> CPU: 299ms
>>
>> Nov 10 20:26:25 corv-weewx systemd[1]: Starting weewx.service - LSB: 
>> weewx weather system...
>> Nov 10 20:26:25 corv-weewx weewx[12332]: Starting weewx weather system: 
>> weewx
>> Nov 10 20:26:25 corv-weewx weewx[12343]: Traceback (most recent call 
>> last):
>> Nov 10 20:26:25 corv-weewx weewx[12343]:   File 
>> "/usr/share/weewx/weewxd", line 29, in 
>> Nov 10 20:26:25 corv-weewx weewx[12343]: import user.extensions
>> Nov 10 20:26:25 corv-weewx weewx[12343]: ModuleNotFoundError: No module 
>> named 'user.extensions'
>> Nov 10 20:26:25 corv-weewx weewx[12332]:  failed!
>> Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Control process 
>> exited, code=exited, status=1/FAILURE
>> Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>> Nov 10 20:26:25 corv-weewx systemd[1]: Failed to start weewx.service - 
>> LSB: weewx weather system.
>> dpkg: error processing package weewx (--configure):
>>  installed weewx package post-installation script subprocess returned 
>> error exit status 1
>> Processing triggers for man-db (2.11.2-2) ...
>> Processing triggers for libc-bin (2.36-9+deb12u3) ...
>> Errors were encountered while processing:
>>  weewx
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>> systemctl and journalctl both point to weewxd not finding module 
>> user.extentions. 
>>
>> Any help would be appreciated.
>> Steve
>>
>>

-- 
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/b9f55758-7b7c-4e8a-a405-a50d392a50bfn%40googlegroups.com.

[weewx-user] Upgraded OS and Weewx - fails to start

[Steve Fowler]

Just upgraded to Debian 12 and installed the latest version of weewx 
according to the install steps for Debian.  Everything seemed to go along 
smoothly until the end and I get this:
Job for weewx.service failed because the control process exited with error 
code.
See "systemctl status weewx.service" and "journalctl -xeu weewx.service" 
for details.
invoke-rc.d: initscript weewx, action "start" failed.
× weewx.service - LSB: weewx weather system
 Loaded: loaded (/etc/init.d/weewx; generated)
 Active: failed (Result: exit-code) since Fri 2023-11-10 20:26:25 PST; 
22ms ago
   Docs: man:systemd-sysv-generator(8)
Process: 12332 ExecStart=/etc/init.d/weewx start (code=exited, 
status=1/FAILURE)
CPU: 299ms

Nov 10 20:26:25 corv-weewx systemd[1]: Starting weewx.service - LSB: weewx 
weather system...
Nov 10 20:26:25 corv-weewx weewx[12332]: Starting weewx weather system: 
weewx
Nov 10 20:26:25 corv-weewx weewx[12343]: Traceback (most recent call last):
Nov 10 20:26:25 corv-weewx weewx[12343]:   File "/usr/share/weewx/weewxd", 
line 29, in 
Nov 10 20:26:25 corv-weewx weewx[12343]: import user.extensions
Nov 10 20:26:25 corv-weewx weewx[12343]: ModuleNotFoundError: No module 
named 'user.extensions'
Nov 10 20:26:25 corv-weewx weewx[12332]:  failed!
Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Control process 
exited, code=exited, status=1/FAILURE
Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Failed with result 
'exit-code'.
Nov 10 20:26:25 corv-weewx systemd[1]: Failed to start weewx.service - LSB: 
weewx weather system.
dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error 
exit status 1
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)

systemctl and journalctl both point to weewxd not finding module 
user.extentions. 

Any help would be appreciated.
Steve

-- 
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/80c0c05f-f153-4f2a-82af-13fd714b3a7fn%40googlegroups.com.

Re: [weewx-user] VantageVue rain collector delay

[Steve C]

The wx station is mounted on a steel pole in an open space in my backyard 
and is very easy to access. As I mentioned, I disassembled it as recently 
as yesterday. No birds, no spiders, no nuts, no trees. It is almost like a 
clock. I am (as of this writing) still collecting .01" every 10 minutes or 
6 times an hour. 

On Monday, May 1, 2023 at 7:47:17 AM UTC-4 bgra...@umw.edu wrote:

> I think Graham has the answer. About twice a year, squirrels crack nuts 
> into my rain gauge funnel and I get the slow drip.
> It must be a very uncomfortable task with all the bird spikes around the 
> outside…
> Cheers,
> Bob
> grattans.org/wx
>
> On Monday, May 1, 2023 at 7:28:56 AM UTC-4 Paul R Anderson wrote:
>
>> Very strange blocked rain funnel would be the number one suspect. Only 
>> other thing that comes to mind is residual 'rain' falling from a tree 
>> canopy, or any other object that could hold rain droplets, and release them 
>> long after the rain shower has ended. Wondering if any trees have started 
>> to encroach on the area above your rain gauge?
>>
>> Paul
>>
>> On Mon, May 1, 2023 at 7:03 AM Steve C  wrote:
>>
>>> I removed it again yesterday and checked the tip bucket and entrance and 
>>> exit paths for blockages but found none. The rain ended several hours ago, 
>>> but my Vue is still counting .01" every few minutes this morning.
>>>
>>> http://livefreeorpi.com 
>>>
>>> On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
>>>
>>>> I remember such behavior when a spider let the remains of her meals 
>>>> drop into the rain bucket.
>>>>
>>>> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>>>>
>>>>> is the outlet from rain bucket partially blocked?
>>>>> *⊣GE⊢*
>>>>>
>>>>> On 29 Apr 2023, at 11:48 pm, Steve C  wrote:
>>>>>
>>>>> Important distinction! I meant to mention that. Yes, the software 
>>>>> seems perfectly fine. The console is reporting the 'slow drip' and WeeWX 
>>>>> logs it accordingly. Being a hardware issue I can move this to a Davis 
>>>>> forum if it is inappropriate here. 
>>>>>
>>>>> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>>>>>
>>>>>>  What does the console show?
>>>>>>
>>>>>> On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:
>>>>>>
>>>>>>> Sorry for the long post, but the details might matter. We had a 
>>>>>>> significant rain event last weekend and my rain gauge responded in a 
>>>>>>> very 
>>>>>>> weird way (which it has done before). It was raining when I got up in 
>>>>>>> the 
>>>>>>> AM, 1/2 inch collected already. After about 3/4in, it POURED and the 
>>>>>>> rain 
>>>>>>> rate slowed to something like .07in/hour. I replaced the rain gauge 
>>>>>>> (with 
>>>>>>> the Davis rehab kit) last fall and went out in the downpour to check 
>>>>>>> the 
>>>>>>> bucket/collector. No blockages, not full of water...
>>>>>>>
>>>>>>> My next door neighbor's device report 2.19" of rain when it ended 
>>>>>>> that day. Mine reported 1.90", however it continued to report .01 or 
>>>>>>> .02 
>>>>>>> clicks at a time until it finally stopped at .42" the next day 
>>>>>>> (although we 
>>>>>>> had no rainfall) for a storm total of 2.32", not terribly far off from 
>>>>>>> my 
>>>>>>> neighbor's 2.19".  I have attached the chart that illustrates the slow 
>>>>>>> collection- as if the collection was full of water that slowly leaked 
>>>>>>> out 
>>>>>>> (can't be the case). 
>>>>>>>
>>>>>>> The very next day we had a brief, heavy thunderstorm. Both my 
>>>>>>> neighbor and I reported the same .30" for the even[image: 
>>>>>>> Screenshot2023-04-24.png]t.
>>>>>>>
>>>>>>> Weewx  4.9.1
>>>>>>> Vantage Vue with an IPconnect.  
>>>>>>>
>>>>>>> We're looking at another 1-3" of rain this weekend, and I'd love to 
>>>&

Re: [weewx-user] VantageVue rain collector delay

[Steve C]

I removed it again yesterday and checked the tip bucket and entrance and 
exit paths for blockages but found none. The rain ended several hours ago, 
but my Vue is still counting .01" every few minutes this morning.

http://livefreeorpi.com 

On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:

> I remember such behavior when a spider let the remains of her meals drop 
> into the rain bucket.
>
> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>
>> is the outlet from rain bucket partially blocked?
>> *⊣GE⊢*
>>
>> On 29 Apr 2023, at 11:48 pm, Steve C  wrote:
>>
>> Important distinction! I meant to mention that. Yes, the software seems 
>> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it 
>> accordingly. Being a hardware issue I can move this to a Davis forum if it 
>> is inappropriate here. 
>>
>> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>>
>>>  What does the console show?
>>>
>>> On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:
>>>
>>>> Sorry for the long post, but the details might matter. We had a 
>>>> significant rain event last weekend and my rain gauge responded in a very 
>>>> weird way (which it has done before). It was raining when I got up in the 
>>>> AM, 1/2 inch collected already. After about 3/4in, it POURED and the rain 
>>>> rate slowed to something like .07in/hour. I replaced the rain gauge (with 
>>>> the Davis rehab kit) last fall and went out in the downpour to check the 
>>>> bucket/collector. No blockages, not full of water...
>>>>
>>>> My next door neighbor's device report 2.19" of rain when it ended that 
>>>> day. Mine reported 1.90", however it continued to report .01 or .02 clicks 
>>>> at a time until it finally stopped at .42" the next day (although we had 
>>>> no 
>>>> rainfall) for a storm total of 2.32", not terribly far off from my 
>>>> neighbor's 2.19".  I have attached the chart that illustrates the slow 
>>>> collection- as if the collection was full of water that slowly leaked out 
>>>> (can't be the case). 
>>>>
>>>> The very next day we had a brief, heavy thunderstorm. Both my neighbor 
>>>> and I reported the same .30" for the even[image: 
>>>> Screenshot2023-04-24.png]t.
>>>>
>>>> Weewx  4.9.1
>>>> Vantage Vue with an IPconnect.  
>>>>
>>>> We're looking at another 1-3" of rain this weekend, and I'd love to 
>>>> hear any suggestions!
>>>>
>>>> Thanks,
>>>> Steve
>>>>
>>>> -- 
>>>> 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%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+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%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/8bed9005-ec36-4258-8acd-0d392c00d0a1n%40googlegroups.com.

Re: [weewx-user] VantageVue rain collector delay

[Steve C]

Important distinction! I meant to mention that. Yes, the software seems 
perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it 
accordingly. Being a hardware issue I can move this to a Davis forum if it 
is inappropriate here. 

On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:

>  What does the console show?
>
> On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:
>
>> Sorry for the long post, but the details might matter. We had a 
>> significant rain event last weekend and my rain gauge responded in a very 
>> weird way (which it has done before). It was raining when I got up in the 
>> AM, 1/2 inch collected already. After about 3/4in, it POURED and the rain 
>> rate slowed to something like .07in/hour. I replaced the rain gauge (with 
>> the Davis rehab kit) last fall and went out in the downpour to check the 
>> bucket/collector. No blockages, not full of water...
>>
>> My next door neighbor's device report 2.19" of rain when it ended that 
>> day. Mine reported 1.90", however it continued to report .01 or .02 clicks 
>> at a time until it finally stopped at .42" the next day (although we had no 
>> rainfall) for a storm total of 2.32", not terribly far off from my 
>> neighbor's 2.19".  I have attached the chart that illustrates the slow 
>> collection- as if the collection was full of water that slowly leaked out 
>> (can't be the case). 
>>
>> The very next day we had a brief, heavy thunderstorm. Both my neighbor 
>> and I reported the same .30" for the even[image: 
>> Screenshot2023-04-24.png]t.
>>
>> Weewx  4.9.1
>> Vantage Vue with an IPconnect.  
>>
>> We're looking at another 1-3" of rain this weekend, and I'd love to hear 
>> any suggestions!
>>
>> Thanks,
>> Steve
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%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/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%40googlegroups.com.

[weewx-user] VantageVue rain collector delay

[Steve C]

Sorry for the long post, but the details might matter. We had a significant 
rain event last weekend and my rain gauge responded in a very weird way 
(which it has done before). It was raining when I got up in the AM, 1/2 
inch collected already. After about 3/4in, it POURED and the rain rate 
slowed to something like .07in/hour. I replaced the rain gauge (with the 
Davis rehab kit) last fall and went out in the downpour to check the 
bucket/collector. No blockages, not full of water...

My next door neighbor's device report 2.19" of rain when it ended that day. 
Mine reported 1.90", however it continued to report .01 or .02 clicks at a 
time until it finally stopped at .42" the next day (although we had no 
rainfall) for a storm total of 2.32", not terribly far off from my 
neighbor's 2.19".  I have attached the chart that illustrates the slow 
collection- as if the collection was full of water that slowly leaked out 
(can't be the case). 

The very next day we had a brief, heavy thunderstorm. Both my neighbor and 
I reported the same .30" for the even[image: Screenshot2023-04-24.png]t.

Weewx  4.9.1
Vantage Vue with an IPconnect.  

We're looking at another 1-3" of rain this weekend, and I'd love to hear 
any suggestions!

Thanks,
Steve

-- 
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/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com.

Re: [weewx-user] wee_config utility (and others) won't run

[Steve C]

Google may be our friend, and indeed, a Google search did to this old 
thread by searching for "wee_database: command not found". Specifically, 
this should be included:  
* cd /home/weewx/bin*
*  ./wee_config /home/weewx/weewx.conf --help*

 I see no way that I could add it to the WeeWX Utilities Guide, but it 
would be great if this were in the documentation. 

I am sure I will get some heat for being grumpy, and I have been fighting 
errors all day, so I am frustrated for sure. How can I help update the 
documentation? The MySQL info was wrong in the main doc for example, Debian 
has switched to MariaDB as the default package some time ago. Which again, 
Google was helpful in pointing out, whereas the WeeWx doc is outdated.  
https://www.weewx.com/docs/usersguide.htm#configuring_mysql  sudo apt 
install mysql-client is no longer correct. 

On Saturday, November 3, 2018 at 12:40:41 PM UTC-4 tke...@gmail.com wrote:

> The shell scans a "path" to find an executable. By default, your current 
> directory is not in the path. This is for security reasons: it prevents you 
> from accidentally running something in your current directory that you may 
> have forgotten about, or downloaded.
>
> You must explicitly tell the shell that you know it's in your current 
> directory. You do this by prepending './' to the executable file. So, it 
> becomes
>
> *  cd /home/weewx/bin*
> *  ./wee_config /home/weewx/weewx.conf --help*
>
> -tk
>
> On Sat, Nov 3, 2018 at 9:14 AM David Beach  wrote:
>
>> I have a reliable weewx installation on a Raspberry Pi using a Vantage 
>> Vue. And it is still working well.
>>
>> But, I disliked the scattered directories of the standard installation so 
>> I set up a new SD card with Raspian Stretch. I followed the setup.py 
>> installation instructions (with only a few minor detours!) I set it to 
>> Simulator and weewx seems to work fine in that mode. I can view the web 
>> page at /home/weewx/public_html/index.html with the 'fake' data streaming 
>> in.
>>
>> However, when I try to run a utility, by typing "wee_config --help" for 
>> example, I get:
>>
>> bash: wee_device: command not found
>>
>> If I precede it with sudo, I get:
>>
>> sudo: wee_config: command not found
>>
>> Even if I change directories so that I am in the /home/weewx/bin 
>> directory and I can see the wee_config file just sitting there, I get the 
>> same result. I would like to be able to use wee_config so I can change the 
>> driver to my Vantage when I'm ready to switch.
>>
>> I am no Linux or weewx expert. Is there some mystical permission or path 
>> I need to change? I hope that someone spots an obvious problem.
>>
>> Thanks!
>>
>> David
>>
>> -- 
>> 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+...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/6b881629-18d6-4715-a5c5-158527449305n%40googlegroups.com.

Re: [weewx-user] Windchill Text Value / Graph Discrepancy

[Steve Schindler]

My apologies. I probably could have phrased that better. You are correct 
that VP2s can generate windchill via hardware; however, an older unit like 
mine with older firmware doesn't send the windchill value in the LOOP 
packets.  

On Tuesday, January 3, 2023 at 9:39:03 AM UTC-5 jo...@johnkline.com wrote:

> > Tom and Gary confirmed that the VP2 hardware generated values for 
> windchill are only available in the LOOP2 packets.
>
> I’m not sure why you think that is relevant.  The question is, whether 
> software or hardware generated, do the loop packets have windchill.  I 
> confirmed they do contain windchill (for my VP2) before my initial reply.
>
> On Jan 3, 2023, at 6:06 AM, Steve Schindler  wrote:
>
> 
>
> Thanks for the suggestion but I don't think that's the issue with my 
> setup.  In a previous discussion (
> https://groups.google.com/g/weewx-user/c/roOG0u8YPX4/m/Tc4vWnznAgAJ), Tom 
> and Gary confirmed that the VP2 hardware generated values for windchill are 
> only available in the LOOP2 packets.
>
> ---
> tke...@gmail.com
> Jul 24, 2020, 8:21:48 PM
>
> to weewx-user
> 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  <https://groups.google.com/>> 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
> ---
>
> And the User's Guide states "Not all stations support LOOP2 data. You need 
> firmware version 1.90 or later."
>
> So I don't think the loop_hilo parameter will affect the windchill value 
> with my setup.
>
>
> On Saturday, December 31, 2022 at 1:07:01 PM UTC-5 jo...@johnkline.com 
> wrote:
>
>> Tom and friends will know for sure, but I believe the low you are seeing 
>> (at 07:31) is from the archive_day_windchill table.
>>
>> You likely have the following in your weewx.conf
>> # Whether to include LOOP data in hi/low statistics
>> loop_hilo = True
>>
>> This tells weewx (well, it tells it to do exactly what the comment says). 
>>  Note: vantage loop packets do indeed include windchill.
>>
>> The archive table (produced from vantage archive records) does not 
>> include this low and the graphs are produced from archive records.
>>
>> I don’t think you are seeing anything *wrong*.
>>
>> Note: these highs and lows in the daily stats get wiped out if you run 
>> wee_database —rebuild-daily (which is unfortunate).
>>
>> On Dec 31, 2022, at 9:21 AM, Steve Schindler  wrote:
>>
>> During the recent cold weather, I noticed a discrepancy between the 
>> windchill minimum value in the table and the value/time shown on the graph. 
>> For 12-24-22, the Low Wind Chill in the Since Midnight table is 23.6F at 
>> 07:31, but the graph doesn't reflect that value. It shows a low of about 
>> 27F at about 8:00. For 12-25-22, the temperature discrepancy is about the 
>> same but time difference is greater. See the screenshots below. All other 
>> values (temp, humidity, wind) agree between the table and the graphs.
>>
>>
>>
>> I'm using a Davis VP2 with firmware version 1.82 so WeeWX is calculating 
>> the windchill value. 
>>
>> Any thoughts on what's happening and how it can be corrected?
>>
>> I'm in Florida so my troubleshooting/testing opportunities are limited to 
>> when a cold front passes through. However, I suspect that heat index has 
>> the same problem and, if so, I'll have plenty of time to work on that that 
>> this summer. :-)
>>
>> 12-24
>>
>> 
>>
>>
>> 12-25
>>
>> 
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>> 
>>
>> 
>>
>> -- 
>

Re: [weewx-user] Windchill Text Value / Graph Discrepancy

[Steve Schindler]

Thanks for the suggestion but I don't think that's the issue with my 
setup.  In a previous discussion 
(https://groups.google.com/g/weewx-user/c/roOG0u8YPX4/m/Tc4vWnznAgAJ), Tom 
and Gary confirmed that the VP2 hardware generated values for windchill are 
only available in the LOOP2 packets.

---
tke...@gmail.com
Jul 24, 2020, 8:21:48 PM

to weewx-user
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 https://groups.google.com/>> 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
---

And the User's Guide states "Not all stations support LOOP2 data. You need 
firmware version 1.90 or later."

So I don't think the loop_hilo parameter will affect the windchill value 
with my setup.


On Saturday, December 31, 2022 at 1:07:01 PM UTC-5 jo...@johnkline.com 
wrote:

> Tom and friends will know for sure, but I believe the low you are seeing 
> (at 07:31) is from the archive_day_windchill table.
>
> You likely have the following in your weewx.conf
> # Whether to include LOOP data in hi/low statistics
> loop_hilo = True
>
> This tells weewx (well, it tells it to do exactly what the comment says). 
>  Note: vantage loop packets do indeed include windchill.
>
> The archive table (produced from vantage archive records) does not include 
> this low and the graphs are produced from archive records.
>
> I don’t think you are seeing anything *wrong*.
>
> Note: these highs and lows in the daily stats get wiped out if you run 
> wee_database —rebuild-daily (which is unfortunate).
>
> On Dec 31, 2022, at 9:21 AM, Steve Schindler  wrote:
>
> During the recent cold weather, I noticed a discrepancy between the 
> windchill minimum value in the table and the value/time shown on the graph. 
> For 12-24-22, the Low Wind Chill in the Since Midnight table is 23.6F at 
> 07:31, but the graph doesn't reflect that value. It shows a low of about 
> 27F at about 8:00. For 12-25-22, the temperature discrepancy is about the 
> same but time difference is greater. See the screenshots below. All other 
> values (temp, humidity, wind) agree between the table and the graphs.
>
>
>
> I'm using a Davis VP2 with firmware version 1.82 so WeeWX is calculating 
> the windchill value. 
>
> Any thoughts on what's happening and how it can be corrected?
>
> I'm in Florida so my troubleshooting/testing opportunities are limited to 
> when a cold front passes through. However, I suspect that heat index has 
> the same problem and, if so, I'll have plenty of time to work on that that 
> this summer. :-)
>
> 12-24
>
> 
>
>
> 12-25
>
> 
>
> -- 
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%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/70448a2d-6bfb-4e85-9e56-97f489dbf515n%40googlegroups.com.

[weewx-user] Re: No module named 'Cheetah'

[Steve]

Thanks Vince.

I will update the OS when I get a chance, the Pi does a few other things 
besides Weewx. But like you mentioned, unless I get it current, I'll be 
battling stuff like this forever. I rolled back to v4.3.0 as I saved the 
image before playing with it.

On Tuesday, 1 November 2022 at 05:45:07 UTC+11 vince wrote:

> On Monday, October 31, 2022 at 10:29:34 AM UTC-7 Steve wrote:
>
>> @rpi3:~# pip install Cheetah3
>> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. 
>> Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 
>> will drop support for Python 2.7 in January 2021. 
>>
>
> Now would be a great time to switch to python3 if you can, given that 
> python2 is almost two years out of supportespecially since you are 
> running a setup.py installation and can easily do a backup of the whole 
> /home/weewx tree in one step...just in case.
>
> As Tom suggested, just use 'pip3' and 'python3' to be darn certain you use 
> the desired 'supported' python version for your os.
>
> Also, your os is 'really' out of date as well if you see python 3.5 in 
> /usr/lib.  A current raspi would have python 3.9 in /usr/lib, so you might 
> think about spending the five or so bucks and tossing a new SD card in with 
> current RaspiOS and getting everything current now.  Your time is worth 
> something to you too, as you might be battling version things for a long 
> time otherwise
>
>
>

-- 
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/44bb855a-d963-4149-bafe-1f0527b2e3d5n%40googlegroups.com.

[weewx-user] Re: No module named 'Cheetah'

[Steve]

I did try @rpi3:/home/weewx/bin# sudo pip3 install cheetah3

Traceback (most recent call last):
  File "/usr/local/bin/pip3", line 5, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
3019, in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
3003, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
3032, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
657, in _build_master
return cls._build_from_requirements(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
670, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
849, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pip==8.1.0' distribution was not 
found and is required by the application
@rpi3:/home/weewx/bin#

On Tuesday, 1 November 2022 at 05:45:07 UTC+11 vince wrote:

> On Monday, October 31, 2022 at 10:29:34 AM UTC-7 Steve wrote:
>
>> @rpi3:~# pip install Cheetah3
>> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. 
>> Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 
>> will drop support for Python 2.7 in January 2021. 
>>
>
> Now would be a great time to switch to python3 if you can, given that 
> python2 is almost two years out of supportespecially since you are 
> running a setup.py installation and can easily do a backup of the whole 
> /home/weewx tree in one step...just in case.
>
> As Tom suggested, just use 'pip3' and 'python3' to be darn certain you use 
> the desired 'supported' python version for your os.
>
> Also, your os is 'really' out of date as well if you see python 3.5 in 
> /usr/lib.  A current raspi would have python 3.9 in /usr/lib, so you might 
> think about spending the five or so bucks and tossing a new SD card in with 
> current RaspiOS and getting everything current now.  Your time is worth 
> something to you too, as you might be battling version things for a long 
> time otherwise
>
>
>

-- 
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/cef127a8-b73a-4b2e-a81f-67e3c717dca0n%40googlegroups.com.

[weewx-user] No module named 'Cheetah'

[Steve]

Probably the wrong forum to ask, but I'm at my wits end. I've always used 
the setup.py method to update WeeWx.

I updated WeeWX to 4.9.1 from maybe 4.3.0? Followed the setup.py 
instructions (in /usr there are python3 and python3.5 directories).

I get an error in the log file "No module named 'Cheetah'"

I get this in my terminal 

@rpi3:~# pip install Cheetah3
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. 
Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 
will drop support for Python 2.7 in January 2021. More details about Python 
2 support in pip can be found at 
https://pip.pypa.io/en/latest/development/release-process/#python-2-support 
pip 21.0 will remove support for this functionality.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: Cheetah3 in 
/usr/local/lib/python2.7/dist-packages (3.2.6.post1)

-- 
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/9d0031f0-08eb-465e-a16d-a3c6cfba5721n%40googlegroups.com.

Re: [weewx-user] Re: FTP failure

[Steve Meltz]

Thanks Gary...no worries. I just wanted to update you with my findings. I
certainly don't expect real time responses!
Steve
ps..I removed the old gauge-data.txt files from the server, and they are
not being generated (or the server isn't allowing them to upload).


On Wed, Sep 21, 2022 at 8:33 PM gjr80  wrote:

> Steve,
>
> Apologies, have been tied up the last two days. I don't think there is any
> need to re-installl anything, everything is there it's just a case of
> working out why the php script is not accepting and saving gauge-data.txt and
> perhaps tweaking a SteelSeries Gauges setting or two. I also glimpsed a
> javascript error the other night. I have a few things I want to try today,
> let me work through them and I will get back to you.
>
> Gary
> On Thursday, 22 September 2022 at 01:32:16 UTC+10 Steve2Q wrote:
>
>> Gary: I am still trying to get things working.
>>
>> Here is where I am at currently;
>> Software versions:
>> Weewx:3.8.2
>> SteelSeries Gauges:   2.7.3
>> Rtgd:   0.3.7
>>
>> The gauge-data.text file is not updating with loops. It is there, but
>> when I refresh it does not change   (
>> https://photokinetics.org/Weather/gauge-data.txt )
>>
>> When I set Debug =1, I get the following error every loop (approx 2.5
>> seconds)
>> Sep 21 11:00:43 raspberrypi weewx[920]: rtgdthread: Failed to post data:
>> Unexpected response
>>
>> Everything else appears to be working: on startup, I get this:
>>
>> Sep 21 11:10:24 raspberrypi weewx[1311]: rtgd: RealTimeGaugeData scroller
>> text will use Weather Underground forecast data
>> Sep 21 11:10:24 raspberrypi weewx[1311]: rtgdthread:
>> '/var/tmp/gauge-data.txt' wil be generated. min_interval is None
>>
>> In your opinion, at this point, should I uninstall SteelSeries and Rtgd
>> on my RPi, and deleted the /ss directory on the web server and start over?
>>
>>
>> On Monday, September 19, 2022 at 9:46:07 AM UTC-4 Steve2Q wrote:
>>
>>> Gary..I changed the .php file locally and uploaded it to the /ss
>>> directory. This did not change anything, however one thing I see is that
>>> gauge-data.txt has not changed since 9/17. I am starting to wonder if it
>>> may be best to uninstall/reinstall steel gauges from weewx?
>>>
>>>
>>> --
> 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/Nb_3fPRRiok/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/6d79fe05-b536-4234-a70c-5a74ebe4abf7n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/6d79fe05-b536-4234-a70c-5a74ebe4abf7n%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/CAH0o-anKrHgZ0rMM9C6mXEZvkdxrHrJqxfokccXby49r_ut-YQ%40mail.gmail.com.

Re: [weewx-user] Re: FTP failure

[Steve Meltz]

Gary..I changed the .php file locally and uploaded it to the /ss directory.
This did not change anything, however one thing I see is that
gauge-data.txt has not changed since 9/17. I am starting to wonder if it
may be best to uninstall/reinstall steel gauges from weewx?

-- 
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/CAH0o-ak0%3D-9-hLGMpBwASTuTWQonXn-WJw97oTE%2Bq-9MXLm5XA%40mail.gmail.com.

Re: [weewx-user] Re: FTP failure

[Steve Meltz]

Gary..I will check for the .php file later today...thanks
Vince..I intend on changing to Rsync once I get the gauges working again.
I'm sure I will have some problems when I do it,  and don't want to try and
fix 2 problems at the same time.

On Sat, Sep 17, 2022, 10:13 PM vince  wrote:

> You really should consider switching to rsync as your uploader.   It will
> go through all those files in a second or two total if you have any kind of
> reasonable internet bandwidth.   All you need to do is some relatively
> simple ssh setup so you can do a password-less ssh to your internet site.
>
> --
> 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/Nb_3fPRRiok/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/b9f21a2a-6a77-4cdf-bce9-d009f6623b8an%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/CAH0o-akG%3Df6K4suRMWCYYP98rYfiRQJFt2c7EsJu_Ch5eubcBw%40mail.gmail.com.

[weewx-user] Re: SteelSeries Wind Rose Blank

[Steve Culp]

Around 30 minutes after I upgraded to 0.5.0 the rain and wind gauges became 
stuck with bogus values. Bummer.

StackedWindRose   3.0.1 creates a nice rose chart in jpg format, so I have 
added it to the gauge display as a substitute and removed rtgd 0.5.0 from 
the system.

Oh well, all of this effort by you and I was worth a try I suppose. The 
wind rose gauge upgrade was nice while it lasted.

http://w5sdc.net/weewx/ss

Thanks and so long for now,

Steve

On Monday, August 2, 2021 at 10:13:14 AM UTC-5 Steve Culp wrote:

> Gary,
>
> Thanks for fixing the link.
>
> Extension NameVersion   Description
> Rtgd  0.5.0 WeeWX support for near realtime updating of 
> the SteelSeries Weather Gauges.
> forecast  3.2.14Generate and display weather and tide 
> forecasts.
> StackedWindRose   3.0.1 Stacked windrose image generator for WeeWX.
> SteelSeries   2.7.6 A weeWX extension for the SteelSeries Weather 
> Gauges.
>
> I found and installed a 0.4.0 version and it bought the wind rose online; 
> however, the barometer gauge would quit after around 12 hours. When I 
> installed 0.5.0 this morning, the barometer gauge became functional again 
> on it's own.
>
> Thank You for your quick response and solution. This is also a great 
> opportunity to thank you and Tom for all of the hard work that has gone 
> into WeeWX and it's extensions over the years.
>
> The next 12 hours are the real test now.
>
> Thanks,
>
> Steve
>
> s...@w5sdc.net
>
>
>
>
>
> On Sunday, August 1, 2021 at 7:47:41 PM UTC-5 gjr80 wrote:
>
>> Apologies, should work now.
>>
>> Gary
>>
>> On Monday, 2 August 2021 at 09:05:02 UTC+10 steve...@gmail.com wrote:
>>
>>> root@w5sdc:~# wget -P /var/tmp 
>>> https://github.com/gjr80/weewx-realtime_gauge-data/releases/download/v0.5.0/rtgd-0.5.0.tar.gz
>>> --2021-08-01 18:01:42--  
>>> https://github.com/gjr80/weewx-realtime_gauge-data/releases/download/v0.5.0/rtgd-0.5.0.tar.gz
>>> Resolving github.com (github.com)... 140.82.113.4
>>> Connecting to github.com (github.com)|140.82.113.4|:443... connected.
>>> HTTP request sent, awaiting response... 404 Not Found
>>> 2021-08-01 18:01:43 ERROR 404: Not Found.
>>>
>>>
>>> On Sunday, August 1, 2021 at 1:27:19 PM UTC-5 Steve Culp wrote:
>>>
>>>> I have upgraded weeWX to 4.5.1 and steelseries to 2.76 and still have 
>>>> the wind rose gauge with no vector plots. The odo works fine and the popup 
>>>> graph for the wind rose gauge shows the wind vectors so it looks like the 
>>>> data it needs to populate the gauge is available but not being plotted for 
>>>> some reason.
>>>>
>>>> Is there a known fix or patch for this? The log files don't contain any 
>>>> errors related to the wind rose or any other function of WeeWX.
>>>>
>>>> http://w5sdc.net/weewx/ss
>>>>
>>>> Thanks in advance.
>>>>
>>>>
>>>>

-- 
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/ece5a694-f3fb-4e80-b375-ecc0b87e11a1n%40googlegroups.com.

[weewx-user] Re: SteelSeries Wind Rose Blank

[Steve Culp]

Gary,

Thanks for fixing the link.

Extension NameVersion   Description
Rtgd  0.5.0 WeeWX support for near realtime updating of the 
SteelSeries Weather Gauges.
forecast  3.2.14Generate and display weather and tide forecasts.
StackedWindRose   3.0.1 Stacked windrose image generator for WeeWX.
SteelSeries   2.7.6 A weeWX extension for the SteelSeries Weather 
Gauges.

I found and installed a 0.4.0 version and it bought the wind rose online; 
however, the barometer gauge would quit after around 12 hours. When I 
installed 0.5.0 this morning, the barometer gauge became functional again 
on it's own.

Thank You for your quick response and solution. This is also a great 
opportunity to thank you and Tom for all of the hard work that has gone 
into WeeWX and it's extensions over the years.

The next 12 hours are the real test now.

Thanks,

Steve

s...@w5sdc.net





On Sunday, August 1, 2021 at 7:47:41 PM UTC-5 gjr80 wrote:

> Apologies, should work now.
>
> Gary
>
> On Monday, 2 August 2021 at 09:05:02 UTC+10 steve...@gmail.com wrote:
>
>> root@w5sdc:~# wget -P /var/tmp 
>> https://github.com/gjr80/weewx-realtime_gauge-data/releases/download/v0.5.0/rtgd-0.5.0.tar.gz
>> --2021-08-01 18:01:42--  
>> https://github.com/gjr80/weewx-realtime_gauge-data/releases/download/v0.5.0/rtgd-0.5.0.tar.gz
>> Resolving github.com (github.com)... 140.82.113.4
>> Connecting to github.com (github.com)|140.82.113.4|:443... connected.
>> HTTP request sent, awaiting response... 404 Not Found
>> 2021-08-01 18:01:43 ERROR 404: Not Found.
>>
>>
>> On Sunday, August 1, 2021 at 1:27:19 PM UTC-5 Steve Culp wrote:
>>
>>> I have upgraded weeWX to 4.5.1 and steelseries to 2.76 and still have 
>>> the wind rose gauge with no vector plots. The odo works fine and the popup 
>>> graph for the wind rose gauge shows the wind vectors so it looks like the 
>>> data it needs to populate the gauge is available but not being plotted for 
>>> some reason.
>>>
>>> Is there a known fix or patch for this? The log files don't contain any 
>>> errors related to the wind rose or any other function of WeeWX.
>>>
>>> http://w5sdc.net/weewx/ss
>>>
>>> Thanks in advance.
>>>
>>>
>>>

-- 
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/967ae644-32a2-4c26-99b1-4755fd22e421n%40googlegroups.com.

[weewx-user] Re: SteelSeries Wind Rose Blank

[Steve Culp]

root@w5sdc:~# wget -P /var/tmp 
https://github.com/gjr80/weewx-realtime_gauge-data/releases/download/v0.5.0/rtgd-0.5.0.tar.gz
--2021-08-01 18:01:42--  
https://github.com/gjr80/weewx-realtime_gauge-data/releases/download/v0.5.0/rtgd-0.5.0.tar.gz
Resolving github.com (github.com)... 140.82.113.4
Connecting to github.com (github.com)|140.82.113.4|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-08-01 18:01:43 ERROR 404: Not Found.


On Sunday, August 1, 2021 at 1:27:19 PM UTC-5 Steve Culp wrote:

> I have upgraded weeWX to 4.5.1 and steelseries to 2.76 and still have the 
> wind rose gauge with no vector plots. The odo works fine and the popup 
> graph for the wind rose gauge shows the wind vectors so it looks like the 
> data it needs to populate the gauge is available but not being plotted for 
> some reason.
>
> Is there a known fix or patch for this? The log files don't contain any 
> errors related to the wind rose or any other function of WeeWX.
>
> http://w5sdc.net/weewx/ss
>
> Thanks in advance.
>
>
>

-- 
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/b4aa888e-50ee-4278-9fd6-964b32b5377en%40googlegroups.com.

[weewx-user] SteelSeries Wind Rose Blank

[Steve Culp]

I have upgraded weeWX to 4.5.1 and steelseries to 2.76 and still have the 
wind rose gauge with no vector plots. The odo works fine and the popup 
graph for the wind rose gauge shows the wind vectors so it looks like the 
data it needs to populate the gauge is available but not being plotted for 
some reason.

Is there a known fix or patch for this? The log files don't contain any 
errors related to the wind rose or any other function of WeeWX.

http://w5sdc.net/weewx/ss

Thanks in advance.


-- 
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/e11ab10b-412c-4e3f-b7ae-ed2d0b91ff28n%40googlegroups.com.

Re: [weewx-user] Belchertown Forecast Interval

['Steve Woodford' via weewx-user]

> On 21 Apr 2021, at 13:23, Pete Geenhuizen  wrote:
> 
> I've just recently started looking into changing my weewx skin to Belchertown.
> I've been able to figure out most of what I want, however no matter how much 
> tinkering I do the one thing that totally escapes me is the Forecast interval 
> option.  No matter what I've tried 

It’s a new feature, available in the as-yet unreleased Belchertown-v1.3b. 
You’ll need to install from latest GitHub master to get it.

Steve

-- 
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/C4672CDC-4DBB-4AC7-B35E-2B63D7C1EA2E%40mctavish.co.uk.

Re: [weewx-user] Crash on startup following 4.3.0 -> 4.5.1 update

['Steve Woodford' via weewx-user]

> On 21 Apr 2021, at 11:08, 'Steve Woodford' via weewx-user 
>  wrote:
> 
> I attempted a WeeWX update this morning, from 4.3.0 to 4.5.1. It did not go 
> well.

Bad form replying to myself, but ...

After further investigation, it turned out to be due to an errant record in the 
DB. The record’s “ET” field was blank; neither NULL nor a valid float. Not sure 
how it got there, but using an sqlite editor and setting it back to NULL did 
the trick.

Steve

-- 
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/CDE0E210-3BCA-4A07-B427-7793949A047A%40mctavish.co.uk.

[weewx-user] Crash on startup following 4.3.0 -> 4.5.1 update

['Steve Woodford' via weewx-user]

I attempted a WeeWX update this morning, from 4.3.0 to 4.5.1. It did not go 
well.

When the daemon is started, I see the following in the log file after about 10 
seconds:

weewx[97779] CRITICAL __main__: Caught unrecoverable exception:
weewx[97779] CRITICAL __main__:   could not convert string to float: ''
weewx[97779] CRITICAL __main__:   Traceback (most recent call last):
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewxd", line 151, in main
weewx[97779] CRITICAL __main__:   engine = 
weewx.engine.StdEngine(config_dict)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/engine.py", line 93, in __init__
weewx[97779] CRITICAL __main__:   self.loadServices(config_dict)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/engine.py", line 161, in loadServices
weewx[97779] CRITICAL __main__:   obj = 
weeutil.weeutil.get_object(svc)(self, config_dict)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/wxservices.py", line 91, in __init__
weewx[97779] CRITICAL __main__:   self.db_manager = 
engine.db_binder.get_manager(data_binding=data_binding, initialize=True)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 584, in get_manager
weewx[97779] CRITICAL __main__:   self.manager_cache[data_binding] 
= open_manager(manager_dict, initialize)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 732, in open_manager
weewx[97779] CRITICAL __main__:   return 
manager_cls.open_with_create(manager_dict['database_dict'],
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 164, in open_with_create
weewx[97779] CRITICAL __main__:   dbmanager = cls(connection, 
table_name=table_name, schema=schema)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 881, in __init__
weewx[97779] CRITICAL __main__:   self.patch_sums()
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 1344, in patch_sums
weewx[97779] CRITICAL __main__:   
self.recalculate_weights(start_d=datetime.date(2020, 6, 1))
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 1262, in 
recalculate_weights
weewx[97779] CRITICAL __main__:   self._do_tranche(mark_d, 
end_of_tranche_d, weight_fn, progress_fn)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/manager.py", line 1301, in _do_tranche
weewx[97779] CRITICAL __main__:   day_accum.addRecord(rec, 
weight=weight)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/accum.py", line 436, in addRecord
weewx[97779] CRITICAL __main__:   func(self, record, obs_type, 
add_hilo, weight)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/accum.py", line 495, in add_value
weewx[97779] CRITICAL __main__:   self[obs_type].addHiLo(val, 
record['dateTime'])
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weewx/accum.py", line 168, in addHiLo
weewx[97779] CRITICAL __main__:   val = to_float(val)
weewx[97779] CRITICAL __main__: File 
"/Volumes/Data1/Users/weewx/bin/weeutil/weeutil.py", line 1276, in to_float
weewx[97779] CRITICAL __main__:   return float(x) if x is not None 
else None
weewx[97779] CRITICAL __main__:   ValueError: could not convert string 
to float: ''
weewx[97779] CRITICAL __main__:   Exiting.

Looks like it might be trying to fix the DB.

The DB worked fine with 4.3.0, and is originally from my previous WView 
installation.

Any idea what I might be doing wrong? Do I need to update via 4.4 instead?

Steve

-- 
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/342B2D2D-CDC7-441F-83FA-6A9F913673DF%40mctavish.co.uk.

Re: [weewx-user] New weather station UK

['Steve Woodford' via weewx-user]

I’m the wrong person to ask about off-the-shelf recommendations; I built my 
own: https://www.mctavish.co.uk/weather/about/ 
<https://www.mctavish.co.uk/weather/about/>

Steve

> On 6 Mar 2021, at 14:33, Auchtermuchty Weather  wrote:
> 
> Thanks that what I needed to know.
> 
> So what weather station would you suggest?
> 
> On Saturday, 6 March 2021 at 13:55:30 UTC Steve Woodford wrote:
> Be aware that WH-1080 and its ilk have had several incompatible on-air 
> protocol changes over the years. You’d be gambling with your £75.69...
> 
> Steve
> 
> 
>> On 6 Mar 2021, at 12:18, Auchtermuchty Weather > > wrote:
>> 
> 
>> I think it might be time to replace my weather station as a number of 
>> sensors are not working as they should, and replacements are now expensive.
>> 
>> I'm looking for a FineOffset as I'm currently using an old Maplins as a 
>> WH1080, one that uses the same sensors would do me another 10 years.
>> 
>> Or
>> 
>> Would this do the trick?
>> 
>> MISOL 1 set of Spare part (outdoor unit) for Professional Wireless Weather 
>> Station: Amazon.co.uk: Garden & Outdoors 
>> <https://www.amazon.co.uk/MISOL-outdoor-Professional-Wireless-Weather/dp/B00EJFCM1M/ref=sr_1_32?crid=3QF58J4XI4Y8F=1=weather+stations+with+outdoor+sensor+wireless=1615033043=p_36%3A7000-8000=388997011=weather+%2Caps%2C130=8-32>
>>  
>> 
>>  
>> 
> 
>> -- 
>> 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+...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c72de1b4-33ca-49e1-b71a-c5b61365ddf0n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/c72de1b4-33ca-49e1-b71a-c5b61365ddf0n%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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/ba67e7ca-72a8-4cc9-88b3-35d85a4b2b0en%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/ba67e7ca-72a8-4cc9-88b3-35d85a4b2b0en%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/295E9C01-5867-4EC4-82D8-D8759A9D0838%40mctavish.co.uk.

Re: [weewx-user] New weather station UK

['Steve Woodford' via weewx-user]

Be aware that WH-1080 and its ilk have had several incompatible on-air protocol 
changes over the years. You’d be gambling with your £75.69...

Steve

> On 6 Mar 2021, at 12:18, Auchtermuchty Weather  wrote:
> 
> I think it might be time to replace my weather station as a number of sensors 
> are not working as they should, and replacements are now expensive.
> 
> I'm looking for a FineOffset as I'm currently using an old Maplins as a 
> WH1080, one that uses the same sensors would do me another 10 years.
> 
> Or
> 
> Would this do the trick?
> 
> MISOL 1 set of Spare part (outdoor unit) for Professional Wireless Weather 
> Station: Amazon.co.uk: Garden & Outdoors 
> <https://www.amazon.co.uk/MISOL-outdoor-Professional-Wireless-Weather/dp/B00EJFCM1M/ref=sr_1_32?crid=3QF58J4XI4Y8F=1=weather+stations+with+outdoor+sensor+wireless=1615033043=p_36%3A7000-8000=388997011=weather+%2Caps%2C130=8-32>
>  
> 
>  
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/c72de1b4-33ca-49e1-b71a-c5b61365ddf0n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/c72de1b4-33ca-49e1-b71a-c5b61365ddf0n%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/833E4A62-5961-4D38-8F5C-E3E460B0F2BF%40mctavish.co.uk.

Re: [weewx-user] Simple Question for Standard Skin

[Steve Wagener]

?
On Monday, March 1, 2021 at 10:10:09 AM UTC-6 vince wrote:

> On Monday, March 1, 2021 at 6:57:54 AM UTC-8 wagt...@charter.net wrote:
>
>> I assumed that is commonly understood. Guess I asked in the wrong place. 
>> I was looking for some help with that. Also wondering why a simple "just 
>> html" thing isn't included in the standard skin. -saw-
>>
>>
> Wow.
>
> You can get some help by doing a google search for "html button" and 
> looking at the examples that are in every page that search returns.
>
>  
>

-- 
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/08c1339e-4f34-4506-a361-899d95ccfc24n%40googlegroups.com.

Re: [weewx-user] Simple Question for Standard Skin

[Steve Wagener]

Thanks for sending me in the right direction. Exactly the help I needed. I 
may be out of my league in trying some of this for the first time but I'm 
not sure where else to get help to begin learning. Getting closer. I'lll 
publish my results once I get it fully tested. I'm just doing a generic 
install and trying to get a couple of tweaks. I'm not a developer nor a 
programmer but I did have some Sun OS training back in the 80's that helps 
me with the command line and the VI editor. Thanks again for the help! -saw-

On Monday, March 1, 2021 at 10:27:11 AM UTC-6 tke...@gmail.com wrote:

> It's not in the Standard skin because not everyone wants, or needs, a 
> smartphone formatted version, so a link is not always needed.
>
> Figure out where you want the link located in the Standard skin index 
> template index.html.tmpl, then place something like this in that location 
> (NOT TESTED):
>
> Smartphone formatted
>
>
> Then, make sure you enable the smartphone skin! In weewx.conf:
>
> [[SmartphoneReport]]
> # The SmartphoneReport uses the 'Smartphone' skin, and the images 
> and
> # files are placed in a dedicated subdirectory.
> skin = Smartphone
> enable = true
> HTML_ROOT = public_html/smartphone
>
>
>
> On Mon, Mar 1, 2021 at 6:57 AM Steve Wagener  wrote:
>
>> I assumed that is commonly understood. Guess I asked in the wrong place. 
>> I was looking for some help with that. Also wondering why a simple "just 
>> html" thing isn't included in the standard skin. -saw-
>>
>> On Sunday, February 28, 2021 at 7:32:20 PM UTC-6 tke...@gmail.com wrote:
>>
>>> Of course. It's just HTML. You can link anything.
>>>
>>> On Sun, Feb 28, 2021 at 3:33 PM Steve Wagener  
>>> wrote:
>>>
>>>> Is there a way of having a smartphone button added to the standard 
>>>> skin. I've seen it a older standard skin in the screenshots on Weewx.com 
>>>> http://www.weewx.com/screenshots/hoodriver.png
>>>>
>>>> Thanks in advance. 
>>>>
>>>> -saw-
>>>>
>>>> -- 
>>>> 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/e894a225-03b8-48e7-b975-515d1bb1cecfn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/e894a225-03b8-48e7-b975-515d1bb1cecfn%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4ac7042e-2103-43fa-b054-2372bb4a3918n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/4ac7042e-2103-43fa-b054-2372bb4a3918n%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/f4375586-d06d-483c-8e8b-f3d47fa5260cn%40googlegroups.com.

Re: [weewx-user] Simple Question for Standard Skin

[Steve Wagener]

Thanks for your attempt at helping me. Your message to me is quite clear. 
-saw-
On Monday, March 1, 2021 at 10:10:09 AM UTC-6 vince wrote:

> On Monday, March 1, 2021 at 6:57:54 AM UTC-8 wagt...@charter.net wrote:
>
>> I assumed that is commonly understood. Guess I asked in the wrong place. 
>> I was looking for some help with that. Also wondering why a simple "just 
>> html" thing isn't included in the standard skin. -saw-
>>
>>
> Wow.
>
> You can get some help by doing a google search for "html button" and 
> looking at the examples that are in every page that search returns.
>
>  
>

-- 
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/3e2932de-bbc4-43a2-a203-37050da67e4an%40googlegroups.com.

Re: [weewx-user] Simple Question for Standard Skin

[Steve Wagener]

I assumed that is commonly understood. Guess I asked in the wrong place. I 
was looking for some help with that. Also wondering why a simple "just 
html" thing isn't included in the standard skin. -saw-

On Sunday, February 28, 2021 at 7:32:20 PM UTC-6 tke...@gmail.com wrote:

> Of course. It's just HTML. You can link anything.
>
> On Sun, Feb 28, 2021 at 3:33 PM Steve Wagener  wrote:
>
>> Is there a way of having a smartphone button added to the standard skin. 
>> I've seen it a older standard skin in the screenshots on Weewx.com 
>> http://www.weewx.com/screenshots/hoodriver.png
>>
>> Thanks in advance. 
>>
>> -saw-
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e894a225-03b8-48e7-b975-515d1bb1cecfn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/e894a225-03b8-48e7-b975-515d1bb1cecfn%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/4ac7042e-2103-43fa-b054-2372bb4a3918n%40googlegroups.com.

[weewx-user] Simple Question for Standard Skin

[Steve Wagener]

Is there a way of having a smartphone button added to the standard skin. 
I've seen it a older standard skin in the screenshots on Weewx.com 
http://www.weewx.com/screenshots/hoodriver.png

Thanks in advance. 

-saw-

-- 
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/e894a225-03b8-48e7-b975-515d1bb1cecfn%40googlegroups.com.

Re: [weewx-user] WeeWx and time

[Steve Sykes]

The procedures worked to clear the bad data. Thank you Tom.

Steve

On Monday, February 15, 2021 at 4:06:27 PM UTC tke...@gmail.com wrote:

> You didn't post a log, but I'm guessing that jumping around in time 
> corrupted the logger's memory. See the section *WeeWX generates HTML 
> pages, but it does not update them 
> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them>*
>  
> in the Wiki.
>
> On Mon, Feb 15, 2021 at 6:43 AM Steve Sykes  wrote:
>
>> I have had to change the server I am using for WeeWx 4.2.0 to GMT. I have 
>> checked the Vantage Pro2 weather station and it is also set to GMT. As soon 
>> as I changed the time the WeeWx web page stopped updating. I have tried 
>> restarting WeeWx and running it via command line. It is running normally 
>> but still no webpage updates. Wunderground is also not getting updated so 
>> it is not just the local page. If I set the server back to EST, everything 
>> works fine.
>> Anyone have an idea to fix this?
>>
>> 73
>> Steve KD2OM
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/80a46d95-cefc-4247-8c8a-67799386b7d0n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/80a46d95-cefc-4247-8c8a-67799386b7d0n%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/2350238c-de48-42e7-bff4-ead70e11bf57n%40googlegroups.com.

[weewx-user] WeeWx and time

[Steve Sykes]

I have had to change the server I am using for WeeWx 4.2.0 to GMT. I have 
checked the Vantage Pro2 weather station and it is also set to GMT. As soon 
as I changed the time the WeeWx web page stopped updating. I have tried 
restarting WeeWx and running it via command line. It is running normally 
but still no webpage updates. Wunderground is also not getting updated so 
it is not just the local page. If I set the server back to EST, everything 
works fine.
Anyone have an idea to fix this?

73
Steve KD2OM

-- 
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/80a46d95-cefc-4247-8c8a-67799386b7d0n%40googlegroups.com.

[weewx-user] Re: 0 files copied to /home/weewx/public_html

[Steve Sykes]

Thank you Gary, I just wondered if it was a problem, I don't usually look 
at the log file but I had a problem where WeeWx wasn't starting reliably. I 
will just ignore the line.

Steve

On Tuesday, October 27, 2020 at 11:56:46 AM UTC gjr80 wrote:

> Hi,
>
> I presume the message you refer to is:
>
> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
> files to /home/weewx/public_html
>
> This is normal and is not necessarily a sign that anything is amiss. The 
> line concerned is the from the CopyGenerator and is quite correct, it did 
> not copy any files. The CheetahGenerator is creating files from your 
> cheetah templates and the ImageGenerator is creating image files for your 
> plots. These generators place the generated files in the correct 
> destination directory not the CopyGenerator.
>
> The CopyGenerator <http://weewx.com/docs/customizing.htm#[CopyGenerator]> 
> is used to copy static files from a skin directory to somewhere else on the 
> system. It is typically used to copy static css or javascript files for use 
> by a web server. The CopyGenerator has two modes of operation; copy once 
> where it copies files on the first report cycle after WeeWX has started or 
> copy always where it copies the specified files on every report cycle. The 
> WeeWX Seasons and Standard skins (by default) run the CopyGenerator (along 
> with the CheetahGenerator and ImageGenerator) on each report cycle but 
> the CopyGenerator is not used to copy any files.
>
> If the line is annoying you can do one of two things. You can prevent the 
> Seasons skin from invoking the CopyGenerator by removing it from the 
> generator_list config setting at the bottom of the Seasons skin config file 
> (skins/Seasons/skin.conf). You could also set log_success = false under 
> [StdReport] in weewx.conf, but this will also have the effect of silencing 
> all log entries for all generators not just the CopyGenerator.
>
> Gary
>
>
> On Tuesday, 27 October 2020 20:34:59 UTC+10, Steve Sykes wrote:
>>
>> I am getting this message in my log file, but the weewx wepbage is 
>> updating as it should. I have also looked in the  public_html directory and 
>> see files of the latest update interval so files are being copied in spite 
>> of the log file data.
>> Can anyone explain this?
>>
>> Steve KD2OM
>>
>>
>>
>> TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 
>> LEN=329 
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
>> 2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
>> 2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 0.32 seconds
>> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 0.18 seconds
>> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
>> files to /home/weewx/public_html
>>
>>

-- 
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/5a4428f5-b90f-44ab-bdb0-cbb5b6e57f9en%40googlegroups.com.

[weewx-user] 0 files copied to /home/weewx/public_html

[Steve Sykes]

I am getting this message in my log file, but the weewx wepbage is updating 
as it should. I have also looked in the  public_html directory and see 
files of the latest update interval so files are being copied in spite of 
the log file data.
Can anyone explain this?

Steve KD2OM



TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 LEN=329 
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 0.32 seconds
Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 0.18 seconds
Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
files to /home/weewx/public_html

-- 
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/cdde9f00-3350-427a-927e-8785d0b9a297n%40googlegroups.com.

Re: [weewx-user] New installation on Ubuntu 18.04

[Steve Sykes]

I tried to upload the log file but for some reason it wouldn't upload. 

I believe the problem with the webpage was that python-cheetah didn't 
install.  During the original install  apt install phonython3-cheetah 
didn't work so I used the other method shown on the installation page. 
Apparently that didn't work either but I didn't realize it. After more 
research I got pip3 install cheetah3 to work.
Now the webpage shows up. I believe it is working correctly now.

I have tried to upload the log but I keep getting an error.

Steve


-- 
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/1d544226-9f70-4cf2-a5ff-b7c83abc7dd9n%40googlegroups.com.

Re: [weewx-user] New installation on Ubuntu 18.04

[Steve Sykes]

Tom,
Here is the log file. 


-- 
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/77ba3ec0-7fa9-4214-a8dc-0bdc90b10c9dn%40googlegroups.com.

[weewx-user] New installation on Ubuntu 18.04

[Steve Sykes]

I have installed weewx using setup.py. It seems to run, my weather station 
is a Davis Vantage Pro2 and the ip data logger.  This is the dump when 
using weewx status -l.

I believe the issue is that there is no index.html in either 
/home/weewx/public_html or /var/www/html

additionally I don't know why  the line in the status dump says 0 files 
copied and also that 'StandardReport' not is enabled.

● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (running) since Thu 2020-10-08 11:56:39 EDT; 1h 34min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 21471 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 22114 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
Tasks: 2 (limit: 4915)
   CGroup: /system.slice/weewx.service
   └─22132 /usr/bin/python3 /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG weewx.restx: 
CWOP: Connected to server cwop.aprs.net:14580
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] INFO 
weewx.imagegenerator: Generated 15 images for report Season… seconds
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] INFO 
weewx.reportengine: Copied 0 files to /home/weewx/public_html
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'SmartphoneReport' not enabled.…kipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'FTP' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.reportengine: Report 'RSYNC' not enabled. Skipping.
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] INFO weewx.restx: 
CWOP: Published record 2020-10-08 13:30:00 EDT…2178200)
Oct 08 13:30:18 Plexserver weewxd[22132]: weewx[22132] DEBUG 
weewx.drivers.vantage: Gentle wake up of console successful
Hint: Some lines were ellipsized, use -l to show in full.


Steve

-- 
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/0a571137-49a6-4e33-9870-eae065ad2b2bn%40googlegroups.com.

Re: [weewx-user] Re: alarm module - multiple alarms

[Steve Meltz]

Thats why I did not do the upgrade. 3.8.2 does everything I want, plus I
did not want my Steel Guages to be broken.

On Sat, Sep 19, 2020, 3:57 AM pligg...@gmail.com 
wrote:

>
> Tried this again today but it doesn't send email. I see the expression
> true in the logs. Has anyone got some idea why the old alarm.py works fine
> but not the "new" alarm_multi.py?
> First tried on weewx 3.9.1 and now on 4.0.0 but still the same result.
> //Mikael
> tisdag 12 mars 2019 kl. 09:06:50 UTC+1 skrev pligg...@gmail.com:
>
>> Hi!
>>
>> Does anyone got this to work on weewx 3.9.1?
>>
>> I had the original alarm.py working, but this one doesn't send email. I
>> get the alarm expression true in the log but it never sends an email.
>> I double checked the credentials and the smtp settings.
>>
>> /Mikael
>>
>>
>> Den onsdag 1 maj 2013 kl. 19:06:00 UTC+2 skrev William Phelps:
>>>
>>> I modified the example "alarm.py" to support multiple alarms.  The
>>> entries in weewx.conf now look like this:
>>>
>>> [Alarm]
>>>   time_wait = 3600
>>>   smtp_host = smtp.mymailserver.com
>>>   smtp_user = myusername
>>>   smtp_password = mypassword
>>>   mailto = au...@adomain.com, anoth...@someplace.com
>>>   from = m...@mydomain.com
>>>
>>>   count = 2
>>>   expression.0 = "outTemp < 40.0"
>>>   subject.0 = "Alarm message from weewx - Low temperature!"
>>>   expression.1 = "outTemp > 90.0"
>>>   subject.1 = "Alarm message from weewx- High temperature!"
>>>
>>> I've attached a zip of alarm.py
>>>
>>> It's still "static" - to change the alarms, you have to restart weewx
>>> after editing weewx.conf.  I thought about having alarm.py re-fetch the
>>> config data but that seems like it might be a performance hit since the
>>> code is attached to the NEW_ARCHIVE_RECORD event.  Maybe attach another
>>> event to re-read the config data?
>>>
>>> William
>>>
>> --
> 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/-IGQC3CpXAE/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/a17bef02-59e7-4429-a38c-064ae7379ea8n%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/CAH0o-a%3DX_HRLJ8fZ9Z0OWmWBn0qBB0%2BA2Yrh75RbRXd7H7XXow%40mail.gmail.com.

Re: [weewx-user] Re: Belchertown Skin, Websockets, Firefox Fail to Connect

[Steve C]

I've updated the skin to 1.2rc2, and I have narrowed the problem down to an 
SSL/MQTT issue. I had failed in the past, but today successfully got WeeWX 
to update via TLS after I changed the MQTT setting in weewx.conf to 
"tls_version = tlsv1.2". That makes sense, the Mosquitto broker wants TLS 
1.1 or higher and a previous update is what probably broke my install.

If I leave it there, and upload via TLS and use HTTP for websockets, 
Firefox and Chrome both work (HTTPS expectedly fails for both). If I 
uncomment the three cert lines in the the Mosquitto config, HTTP and HTTPS 
Chrome work, but HTTP and HTTPS Firefox fail:

listener 9001
certfile /etc/letsencrypt/live/livefreeorpi.com/cert.pem
cafile /etc/letsencrypt/live/livefreeorpi.com/chain.pem
keyfile /etc/letsencrypt/live/livefreeorpi.com/privkey.pem
protocol websockets

Other than the note about updating the weewx.conf to reflect possible newer 
TLS implementations, I can take this up further on a Mosquitto forum, but 
thought I would pass it along here as it seems to be popping up now and 
then for others too.

On Sunday, August 9, 2020 at 2:27:02 PM UTC-4, Pat wrote:
>
> Interesting, it fails for me too in Firefox. It could be the version of 
> the MQTT Websocket library you're using in 1.1. In 1.2 there are some 
> updates to the MQTT websockets code.
>
> My site - belchertownweather.com - is using the latest development 1.2 
> release candidate 
>  and it 
> works for me in Firefox. Give the development version a try - note 1.2 is 
> focused on using Aeris Weather as a forecast provider, however DarkSky is 
> supported. Please read the readme for the new skin.conf variables to be 
> used 
>  
> and changelog for all the breaking changes 
>  
> so far in this upgrade. 
>
>
> On Wednesday, August 5, 2020 at 9:09:19 PM UTC-4 bth...@gmail.com wrote:
>
>> With or without openvpn, all works fine for all browsers, except MS Edge, 
>> Chromium, developer edition not working if having openvpn connected. 
>> Strange.
>>
>> On Wednesday, 5 August 2020 at 17:21:51 UTC+7 gary@gmail.com wrote:
>>
>>> Odd that one browser for each of us refuses to connect.
>>> I'm not using a VPN, so yours works fine without the VPN but fails when 
>>> you use it?
>>>
>>>
>>>
>>> On 8/4/2020 11:55 PM, Chotechai Piyavongsiri wrote:
>>>
>>> I mean Microsoft Edge chromium.
>>>
>>> On Wednesday, 5 August 2020 at 10:54:10 UTC+7 Chotechai Piyavongsiri 
>>> wrote:
>>>
 I have no problem with any browsers, including Firefox. I'm using 
 secured websockets. 
 The only problem I have is with Microsoft Edge, WS will not work when I 
 connect my OpenVPN, same message as you got (Firefox works). I still don't 
 know the reason.

 On Tuesday, 4 August 2020 at 23:11:56 UTC+7 gary@gmail.com wrote:

> I have a curious issue here. 
> I normally use Edge from Windows 10 to browse. All is working fine.
> I use Firefox in troubleshooting and browsed to my weather page.
> No connection to the websocket feed.
> Open Edge, no problem. Chrome from my phone, no problem. Safari from 
> my wife's iPhone, no problem.
>
> Disabled all plugins in Firefox, still get  Failed connecting to the 
> weather station. Please try again later! 
>
> Tried from a Linux machine using Firefox, same result.
>
> Any ideas?
>
 -- 
>>> 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/nwHdhPVd5o0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/0c145e3e-1e5f-4cea-ba00-fc09059a60edn%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/591b4f66-de42-49ac-a0c9-8336f22da10fo%40googlegroups.com.

Re: [weewx-user] Re: Belchertown Skin, Websockets, Firefox Fail to Connect

[Steve C]

I use Firefox as my regular browser and have been chasing this issue for 
some time now. The live data worked for many months but has stopped with 
the "Failed connecting to the weather station. Please try again later!" 
only on Firefox. It works fine on Chrome and Edge (which share the same 
engine so that probably makes sense). If it's OK to post a URL, you can see 
the behavior here: http://livefreeorpi.com . My setup is a Vantage Vue, I'm 
running WeeWX 4.1.1, my own 3.1.1 Mosquitto broker, on Debian10 virtual 
machines. 
On Wednesday, August 5, 2020 at 6:21:51 AM UTC-4 gary@gmail.com wrote:

> Odd that one browser for each of us refuses to connect.
> I'm not using a VPN, so yours works fine without the VPN but fails when 
> you use it?
>
>
>
> On 8/4/2020 11:55 PM, Chotechai Piyavongsiri wrote:
>
> I mean Microsoft Edge chromium.
>
> On Wednesday, 5 August 2020 at 10:54:10 UTC+7 Chotechai Piyavongsiri wrote:
>
>> I have no problem with any browsers, including Firefox. I'm using secured 
>> websockets. 
>> The only problem I have is with Microsoft Edge, WS will not work when I 
>> connect my OpenVPN, same message as you got (Firefox works). I still don't 
>> know the reason.
>>
>> On Tuesday, 4 August 2020 at 23:11:56 UTC+7 gary@gmail.com wrote:
>>
>>> I have a curious issue here. 
>>> I normally use Edge from Windows 10 to browse. All is working fine.
>>> I use Firefox in troubleshooting and browsed to my weather page.
>>> No connection to the websocket feed.
>>> Open Edge, no problem. Chrome from my phone, no problem. Safari from my 
>>> wife's iPhone, no problem.
>>>
>>> Disabled all plugins in Firefox, still get  Failed connecting to the 
>>> weather station. Please try again later! 
>>>
>>> Tried from a Linux machine using Firefox, same result.
>>>
>>> Any ideas?
>>>
>> -- 
> 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/nwHdhPVd5o0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/0c145e3e-1e5f-4cea-ba00-fc09059a60edn%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/d81e2f27-35be-4e59-b1d9-5a1973292472n%40googlegroups.com.

[weewx-user] Re: Problems with SDR driver failure to start process.

[Steve Kennedy]

I'm having a similar problen with a RPI3 with buster (debian 10)

i have the logs 

On Friday, 12 June 2020 06:25:14 UTC+10, weather list wrote:
>
> Running RTL_433 manually outputs:
>
> time  : 2020-06-11 14:09:10
> model : Ambient Weather F007TH Thermo-Hygrometer   
>   House Code: 175   Channel   : 1 Battery   : OK   
>  Temperature: 89.3 F
> Humidity  : 41 % Integrity : CRC
>
>
> Running  sudo PYTHONPATH=bin python bin/user/sdr.py the F007TH is not 
> parsed:
> out:[u'{"time" : "2020-06-11 18:16:14", "model" : "Ambient Weather F007TH 
> Thermo-Hygrometer", "device" : 175, "channel" : 1, "battery" : "OK", 
> "temperature_F" : 89.300, "humidity" : 41, "mic" : "CRC"}\n']
>
> sdr.py has a parser for the AmbientF007TH:
> class AmbientF007THPacket(Packet):
> # 2017-01-21 18:17:16 : Ambient Weather F007TH Thermo-Hygrometer
> # House Code: 80
> # Channel: 1
> # Temperature: 61.8
> # Humidity: 13 %
>
> #IDENTIFIER = "Ambient Weather F007TH Thermo-Hygrometer"
> IDENTIFIER = "Ambientweather-F007TH"
> PARSEINFO = {
> 'House Code': ['house_code', None, lambda x: int(x)],
> 'Channel': ['channel', None, lambda x: int(x)],
> 'Temperature': [
> 'temperature', re.compile('([\d.-]+) F'), lambda x: float(x)],
> 'Humidity': ['humidity', re.compile('([\d.]+) %'), lambda x: 
> float(x)]}
>
> @staticmethod
> def parse_text(ts, payload, lines):
> pkt = dict()
> pkt['dateTime'] = ts
> pkt['usUnits'] = weewx.METRIC
> pkt.update(Packet.parse_lines(lines, 
> AmbientF007THPacket.PARSEINFO))
> house_code = pkt.pop('house_code', 0)
> channel = pkt.pop('channel', 0)
> sensor_id = "%s:%s" % (channel, house_code)
> pkt = Packet.add_identifiers(
> pkt, sensor_id, AmbientF007THPacket.__name__)
> return pkt
>
> # {"time" : "2017-01-21 13:01:30", "model" : "Ambient Weather F007TH 
> Thermo-Hygrometer", "device" : 80, "channel" : 1, "temperature_F" : 61.800, 
> "humidity" : 10}
> # as of 06feb2020:
> # {"time" : "2020-02-05 19:33:11", "model" : "Ambientweather-F007TH", 
> "id" : 201, "channel" : 5, "battery_ok" : 1, "temperature_F" : 39.400, 
> "humidity" : 60, "mic" : "CRC"}
>
> @staticmethod
> def parse_json(obj):
> pkt = dict()
> pkt['dateTime'] = Packet.parse_time(obj.get('time'))
> pkt['usUnits'] = weewx.US
> house_code = obj.get('device', 0)
> channel = obj.get('channel')
> pkt['temperature'] = Packet.get_float(obj, 'temperature_F')
> pkt['humidity'] = Packet.get_float(obj, 'humidity')
> sensor_id = "%s:%s" % (channel, house_code)
> pkt = Packet.add_identifiers(
> pkt, sensor_id, AmbientF007THPacket.__name__)
> return pkt
>
> My sdr.conf section for SDR:
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
> #path = /usr/local/bin/rtl_433
> #log_unknown_sensors = False
> #log_unmapped_sensors = True
> [[sensor_map]]
> extraTemp2 = temperature.*.AmbientF007THPacket# pool 
> temperature
>
>
> When run under weeex-multi using:
> sudo /etc/init.d/weewx start sdr
>
> I find this in the log; I think this must be the problem but I have not 
> been able to figure out how to fix it:
> import of driver failed: failed to start process 'rtl_433 -M utc -F json': 
> [Errno 2] No such file or directory ()
> Jun 11 15:56:05 NUC2498 weewx-sdr[1653]: engine: Unable to load driver: 
> failed to start process 'rtl_433 -M utc -F json': [Errno 2] No such file or 
> directory
>
>
> Debian 9
> WeeWx 3.92
> Intel NUC
>
>
>

-- 
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/f6323292-6d0a-42d5-aace-aa68f3554df8o%40googlegroups.com.

[weewx-user] FIXED - Re: OpenWeatherMap 0.9 extension on weewx 4.1.1 not working

[Steve Magnuson]

Thanks again, Gary.  I added user.owm.OpenWeatherMap manually to weewx.conf 
per your instructions and it's working fine now.

Steve.

On Monday, June 29, 2020 at 3:19:34 PM UTC-7, gjr80 wrote:
>
> For some reason the extension installer did not add the OWM uploader to 
> the list of RESTful services to be run. You can fix it manually, just edit 
> weewx.conf, goto [Engine] [[Services]] and add “, user.owm.OpenWeatherMap” 
> to the end of the restful_services setting, something like: 
>
> restful_services = weewx.restx.StdStationRegistry, 
> weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
> weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
> user.owm.OpenWeatherMap 
>
> Save weewx.conf and restart WeeWX. Check the log to see that OWM was 
> loaded on startup and then called every archive period. 
>
> 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9a9ed099-96fb-4e95-915e-53690343d528o%40googlegroups.com.

[weewx-user] Re: OpenWeatherMap 0.9 extension on weewx 4.1.1 not working

[Steve Magnuson]

Gary,

Obfuscated wee_debug output is attached.

Steve

On Monday, June 29, 2020 at 1:41:23 PM UTC-7, gjr80 wrote:
>
> Hi, 
>
> The OWM uploader is not loading and no error is thrown which points 
> towards a fundamental config error. Could please run wee_debug (
> http://weewx.com/docs/utilities.htm#wee_debug_utility) and post a copy of 
> the output. Before posting the wee_debug output check it for any sensitive 
> info such as passwords, user names, api keys etc. wee_debug is good at 
> obfuscating such info but it’s not perfect. 
>
> 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a07a14fa-9713-4f18-9b62-2c9a221470a8o%40googlegroups.com.
Using verbosity=1, displaying most info

wee_debug output will be sent to stdout(console)

Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'

System info
  Platform:   Linux-4.19.118-v7l+-armv7l-with-debian-10.4
  Python Version: 3.7.3

Load Information
  1 minute load average:  0.01
  5 minute load average:  0.05
  15 minute load average: 0.08

General Weewx info
  Weewx version 4.1.1 detected.

Station info
  Station type: Vantage
  Driver:   weewx.drivers.vantage

Driver info
[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet 
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
type = serial

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
port = /dev/ttyUSB0

# If the connection type is ethernet, an IP Address/hostname is required:
host = 1.2.3.4

##
# The rest of this section rarely needs any attention. 
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5

# The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
loop_request = 1

# The id of your ISS station (usually 1). If you use a wind meter connected
# to a anemometer transmitter kit, use its id
iss_id = 1

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
timeout = 4

# How long to wait before trying again (in seconds)
wait_before_retry = 1.2

# How many times to try before giving up:
max_tries = 4

# Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
model_type = 2

# The driver to use:
driver = weewx.drivers.vantage

Currently installed extensions
Extension NameVersion   Description
owm   0.9   Upload weather data to OpenWeatherMap.

Archive info
  Database name:weewx.sdb
  Table name:   archive
  Version   2.0
  Unit system:  1 (US)
  First good timestamp: 2020-06-28 17:50:00 PDT (1593391800)
  Last good timestamp:  2020-06-29 14:50:00 PDT (1593467400)
  Number of records:252
  weewx (weewx.conf) is set to use an archive interval of 300 seconds.
  The station hardware was not interrogated in determining archive interval.

Databases configured in weewx.conf
  Database name:weewx.sdb
  Database driver:  weedb.sqlite

  Database name:weewx
  Database driver:  weedb.mysql
  Database host:localhost


Parsed and obfuscated weewx.conf
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.1.1

##

#   This section is for information

[weewx-user] OpenWeatherMap 0.9 extension on weewx 4.1.1 not working

[Steve Magnuson]

07] DEBUG weewx.reportengine: Running reports 
for latest time in the database.
Jun 29 09:55:15 lrpi weewx[21607] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.
Jun 29 09:55:15 lrpi weewx[21607] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Jun 29 09:55:15 lrpi weewx[21607] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jun 29 09:55:15 lrpi weewx[21607] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jun 29 09:55:16 lrpi weewx[21607] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jun 29 09:55:16 lrpi weewx[21607] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 29 09:55:16 lrpi weewx[21607] DEBUG weewx.restx: CWOP: Connected to 
server cwop.aprs.net:14580
Jun 29 09:55:16 lrpi weewx[21607] INFO weewx.restx: Wunderground-PWS: 
Published record 2020-06-29 09:55:00 PDT (1593449700)
Jun 29 09:55:16 lrpi weewx[21607] INFO weewx.restx: CWOP: Published record 
2020-06-29 09:55:00 PDT (1593449700)
Jun 29 09:55:16 lrpi weewx[21607] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 0.74 seconds
Jun 29 09:55:16 lrpi weewx[21607] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 29 09:55:17 lrpi weewx[21607] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 0.56 seconds
Jun 29 09:55:17 lrpi weewx[21607] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx
Jun 29 09:55:17 lrpi weewx[21607] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jun 29 09:55:17 lrpi weewx[21607] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jun 29 09:55:17 lrpi weewx[21607] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jun 29 09:55:17 lrpi weewx[21607] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Jun 29 09:55:17 lrpi weewx[21607] DEBUG weewx.reportengine: Report 'RSYNC' 
not enabled. Skipping.


Thanks,

Steve

-- 
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/c5e17fe7-0bf1-4304-8523-3cf85fa2d300o%40googlegroups.com.

[weewx-user] FIXED - Re: Weewx 4.1.1 on RPi 4B running latest Buster lite image: Wundergound regular 5 minute posts don't work, but rapidfire does

[Steve Magnuson]

Fixed!  "Temporal chaos' indeed.  I cleared the station memory, and for 
good measure removed the database file and /var/www/html/weewx files again 
and everything started working.  Wunderground and CWOP are now updating as 
expected.  Thanks for the pointer.

Steve

On Sunday, June 28, 2020 at 4:49:21 PM UTC-7, gjr80 wrote:
>
> Quite possible the issue is related, Davis stations tend to be slightly 
> more susceptible to temporal chaos than some other stations. Your RPi and 
> console might have the correct time but it is quite possible the change in 
> times has caused issues for your logger. It’s possible things will come 
> good but since you’ve restarted with a new database and checked the time on 
> the RPi/console you might as well go the trifecta and clear the loggers 
> memory as well. Refer to the wiki article ‘Troubleshooting Davis stations’ (
> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory).
>  
> If you read through the ‘Corrupt station memory’ section you will see 
> mention of clearing the station memory with the WeeWX utility wee_device. 
> Try that, note you will need to stop WeeWX first. 
>
> 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a8254b4f-249c-4609-a814-fbae18d957a7o%40googlegroups.com.

[weewx-user] Re: Weewx 4.1.1 on RPi 4B running latest Buster lite image: Wundergound regular 5 minute posts don't work, but rapidfire does

[Steve Magnuson]

Log file for a 10 minute duration attached.

I think I might have a clue as to what is going on.  Prior to installing 
weewx on this Pi, I installed another app that inexplicably set my timezone 
to the UK, 8 hours ahead.  I then installed weewx, noticed the time was 
wrong, and changed the timezone to my own (US/Pacific).  Since my last 
post, I deleted /var/lib/weewx/weewx.sdb and the contents of 
/var/www/html/weewx and those TypeErrors I had disappeared.  However, new 
"ignore historical record" errors started appearing in the logs with 
timestamps in the future.  Also, this is another clue:

Jun 28 15:50:15 lrpi weewx[14691] DEBUG weewx.drivers.vantage: DMPAFT 
complete: page timestamp 2020-06-28 10:25:00 PDT (1593365100) less than 
final timestamp 2020-06-28 19:20:00 PDT (1593397200)

So, it's possible it might just start working in a few hours, after 19:20 
this evening(?)

My Vue's time is correct and the Pi's time is also correct.  I have 
installed a RTC on the Pi and it does work.

-Steve

On Sunday, June 28, 2020 at 1:37:11 PM UTC-7, Steve Magnuson wrote:
>
> I've just installed weewx for the first time on a Rpi 4B (latest Buster 
> lite image) per instructions.  I've enabled Wunderground and CWOP, both of 
> which were working fine on my Meteobridge.  I'm using this 
> /etc/weewx/weewx.conf configuration:
>
> [Station]
>
> # Description of the station location
> location = "Bellingham, WA"
>
> # Latitude in decimal degrees. Negative for southern hemisphere
> latitude = 48.753
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = -122.472
>
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 90, foot
>
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file with a 'driver' parameter indicating the driver to be 
> used.
> station_type = Vantage
>
> .
> .
> .
>
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
>
> # Connection type: serial or ethernet 
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
>type = serial
>
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
>port = /dev/ttyUSB0
> .
> .
> .
> [[CWOP]]
> # This section is for configuring posts to CWOP.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify the station ID (e.g., CW1234).
> enable = true
> station = AG7GN
> .
> .
> .
>   [[Wunderground]]
> # This section is for configuring posts to the Weather Underground.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station (e.g., 'KORHOODR3') and password.
> # To guard against parsing errors, put the password in quotes.
> enable = true
> station = KWABELLI109
> password = **
> 
> # If you plan on using wunderfixer, set the following
> # to your API key:
> api_key = ***
> 
> # Set the following to True to have weewx use the WU "Rapidfire"
> # protocol. Not all hardware can support it. See the User's Guide.
> rapidfire = False
>
>
> After starting weewx and waiting about 15 minutes, no data is sent to 
> either CWOP or Wunderground.  My debug-enabled log looks like this at 
> startup:
>
> Jun 28 12:06:46 lrpi systemd[1]: Starting LSB: weewx weather system...
> Jun 28 12:06:47 lrpi weewx[6066] INFO __main__: Initializing weewx version 
> 4.1.1
> Jun 28 12:06:47 lrpi weewx[6066] INFO __main__: Using Python 3.7.3 
> (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
> Jun 28 12:06:47 lrpi weewx[6066] INFO __main__: Platform 
> Linux-4.19.118-v7l+-armv7l-with-debian-10.4
> Jun 28 12:06:47 lrpi weewx[6066] INFO __main__: Locale is 'en_US.UTF-8'
> Jun 28 12:06:47 lrpi weewx[6066] INFO __main__: PID file is 
> /var/run/weewx.pid
> Jun 28 12:06:47 lrpi weewx[6070] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Jun 28 12:06:47 lrpi weewx[6070] INFO __main__: Debug is 1
> Jun 28 12:06:47 lrpi weewx[6070] DEBUG __main__: Initializing engine
> Jun 28 12:06:47 lrpi weewx[6070] INFO weewx.engine: Loading station type 
> Vantage (weewx.drivers.vantage)
> Jun 28 12:06:47 lrpi weew

[weewx-user] Weewx 4.1.1 on RPi 4B running latest Buster lite image: Wundergound regular 5 minute posts don't work, but rapidfire does

[Steve Magnuson]

x.reportengine: Copied 5 files to 
/var/www/html/weewx
Jun 28 12:10:19 lrpi weewx[6070] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jun 28 12:10:19 lrpi weewx[6070] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jun 28 12:10:19 lrpi weewx[6070] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jun 28 12:10:19 lrpi weewx[6070] DEBUG weewx.reportengine: Report 'FTP' not 
enabled. Skipping.
Jun 28 12:10:19 lrpi weewx[6070] DEBUG weewx.reportengine: Report 'RSYNC' 
not enabled. Skipping.


I don't know if they are related or not.

Thanks for having a look.

Steve

-- 
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/41a01628-8a7c-4eb4-868c-5583e080e0b9o%40googlegroups.com.

Re: [weewx-user] weewx4 locks up Vantage2 console

[Steve Koone]

Resolved:  After ten hours of fighting this mess, I finally found the 
solution to my issue.  Clear the memory in the console.

Issue this command at the terminal screen prompt:

wee_device --clear-memory

I tested this on two separate consoles both of which locked up the screen 
(frozen) and no keyboard response.  Issue the command even if the console 
is locked up.  After this, both consoles corrected themselves almost 
immediately and began working normally, and the software began reporting to 
CWOP as it always had in the past.

As for any logical explanation:  It seems the software sends some sort of 
command to the console when the software boots up.  Apparently the console 
doesn't like what it sees and it pukes.  The only way to fix it without 
clearing memory is to pull the batteries and restart from the beginning.  
The software acts as if nothing is/was wrong.

I can confirm that I NEVER had this happen before and I've used weewx for 
years with no issues.  Yes I have had to occasionally clear the console 
memory for one reason or another but never to have the console completely 
lock up and be totally non-responsive.

Screw the log.  This is not to be diagnosed from some log.  This is a 
software / hardware conflict that should have been documented and 
highlighted to look at after a major software release such as this.  I've 
reinvented the wheel 14 times already today just to find this one fix. 


On Friday, May 1, 2020 at 5:46:57 PM UTC-4, Tom Keffer wrote:
>
> Unlikely. This driver has been around for a while. More likely it is a 
> configuration problem on your end.
>
> In any case, I simply cannot help you without the log. Instructions were 
> included in my earlier post.
>
> On Fri, May 1, 2020 at 11:45 AM Steve Koone  > wrote:
>
>> I don't know how to pull a log.
>>
>> All I can tell you is this.  I'm using a pi2 w/ an FTDI USB to serial 
>> adapter.  Every time weewx starts, it locks up the Vantage console.
>>
>> I have tried Deb 10 with python 2 and 3.
>>
>> I have tried Deb 8 with python 2
>>
>> I just tried Deb 9 with python 2.  Everything locks up communication to 
>> the Vantage2 console.  It never did this with 3.92 and earlier.  I have to 
>> pull the batteries in the Vantage2 console and hard reboot the thing. 
>>
>> I guarantee you I won't be the only one reporting this problem.
>>
>>
>> On Friday, May 1, 2020 at 10:22:10 AM UTC-4, Tom Keffer wrote:
>>>
>>> You're not giving us much information. How about a log? See the Wiki 
>>> article *Help! Posting to weewx-user 
>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>* for 
>>> how to get a good log.
>>>
>>> On Fri, May 1, 2020 at 6:55 AM Steve Koone  wrote:
>>>
>>>> All-  The upgrade to weewx v4 isn't working here.  When I start up v4 
>>>> it almost immediately sends the Vantage console into lock up with the 
>>>> letter 'R' in the lower right corner.
>>>>
>>>> I'm reverting back to v3.92.
>>>>
>>>> -- 
>>>> 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/e7679cae-b478-4469-92bc-8b79fe5876a3%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/e7679cae-b478-4469-92bc-8b79fe5876a3%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/c0b9b4e0-6676-44b4-9272-bc6f1df39068%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/c0b9b4e0-6676-44b4-9272-bc6f1df39068%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/255405c6-cc0f-49a4-8ac6-4ea0328ba8d1%40googlegroups.com.

Re: [weewx-user] weewx4 locks up Vantage2 console

[Steve Koone]

I don't know how to pull a log.

All I can tell you is this.  I'm using a pi2 w/ an FTDI USB to serial 
adapter.  Every time weewx starts, it locks up the Vantage console.

I have tried Deb 10 with python 2 and 3.

I have tried Deb 8 with python 2

I just tried Deb 9 with python 2.  Everything locks up communication to the 
Vantage2 console.  It never did this with 3.92 and earlier.  I have to pull 
the batteries in the Vantage2 console and hard reboot the thing. 

I guarantee you I won't be the only one reporting this problem.


On Friday, May 1, 2020 at 10:22:10 AM UTC-4, Tom Keffer wrote:
>
> You're not giving us much information. How about a log? See the Wiki 
> article *Help! Posting to weewx-user 
> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>* for 
> how to get a good log.
>
> On Fri, May 1, 2020 at 6:55 AM Steve Koone > 
> wrote:
>
>> All-  The upgrade to weewx v4 isn't working here.  When I start up v4 it 
>> almost immediately sends the Vantage console into lock up with the letter 
>> 'R' in the lower right corner.
>>
>> I'm reverting back to v3.92.
>>
>> -- 
>> 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/e7679cae-b478-4469-92bc-8b79fe5876a3%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/e7679cae-b478-4469-92bc-8b79fe5876a3%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/c0b9b4e0-6676-44b4-9272-bc6f1df39068%40googlegroups.com.

[weewx-user] weewx4 locks up Vantage2 console

[Steve Koone]

All-  The upgrade to weewx v4 isn't working here.  When I start up v4 it 
almost immediately sends the Vantage console into lock up with the letter 
'R' in the lower right corner.

I'm reverting back to v3.92.

-- 
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/e7679cae-b478-4469-92bc-8b79fe5876a3%40googlegroups.com.

[weewx-user] Re: Updating historical data in database?

[Steve Preston]

Geez... that was almost too easy : )

Thanks!
Steve


On Saturday, April 18, 2020 at 10:03:13 AM UTC-7, Steve Preston wrote:
>
> I just realized that I imported a few years of data from WLK files where I 
> accidentally swapped the inside vs outside humidity (a bug which is now 
> fixed in my wlkReader app). 
> So now I would like to update these values in the database.
>
> Does wee_import "update" records which match the timestamp of existing 
> records in the database or does it only ADD new records?  I'm assuming that 
> it only adds records.  So I suspect that I will need to remove all the 
> historical WLK data from my WeeWx database, then import the correct data 
> again.  Does this make sense?
>
> Thanks
> Steve
>
>

-- 
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/b650da1b-be42-46a6-806c-2acb5af79fdb%40googlegroups.com.

[weewx-user] Updating historical data in database?

[Steve Preston]

I just realized that I imported a few years of data from WLK files where I 
accidentally swapped the inside vs outside humidity (a bug which is now 
fixed in my wlkReader app). 
So now I would like to update these values in the database.

Does wee_import "update" records which match the timestamp of existing 
records in the database or does it only ADD new records?  I'm assuming that 
it only adds records.  So I suspect that I will need to remove all the 
historical WLK data from my WeeWx database, then import the correct data 
again.  Does this make sense?

Thanks
Steve

-- 
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/68aa3172-cce9-4b8b-8a3f-f872dbba1cb5%40googlegroups.com.

[weewx-user] Re: Importing WLK files from Davis Instruments WeatherLink software

[Steve Preston]

Opps!  I just found (and fixed) a bug in the wlkReader app.  It was 
swapping Inside / Outside humidity (wrong label on CSV header).

Steve


On Tuesday, April 14, 2020 at 3:24:16 PM UTC-7, Steve Preston wrote:
>
> This is just a FYI for the group.  After using WeatherLink for 15+ years, 
> I have finally switched to WeeWx!
>
> I wrote a basic Windows app for converting the WLK files into CSV format 
> for importing the data into WeeWx.  This app is pretty basic - no real data 
> checks and no attempt to adjust for differences in the archive interval (my 
> station was already logging at 5 minute intervals).  And it is setup to 
> import one month at a time: reads one *.wlk file and writes one *.csv 
> file.  But I've moved over a few years of data to WeeWx without any 
> problems (so far).  The app is written in C# with visual studio and I'm 
> happy to share code and/or executables.
>
> Steve
>
>

-- 
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/f6a32662-d01e-41c4-9df1-9ae1d8557580%40googlegroups.com.

[weewx-user] Re: Importing WLK files from Davis Instruments WeatherLink software

[Steve Preston]

Gary,

Your response has addressed my questions.  During my past imports I have 
avoided running wee_import while WeeWx is adding new data to the database 
(during the typical 5 minute intervals in my case).  I will add a comment 
to the ReadMe instructions on the GitHub page for wlkReader - suggesting 
that others do the same.

Thanks
Steve


On Tuesday, April 14, 2020 at 3:24:16 PM UTC-7, Steve Preston wrote:
>
> This is just a FYI for the group.  After using WeatherLink for 15+ years, 
> I have finally switched to WeeWx!
>
> I wrote a basic Windows app for converting the WLK files into CSV format 
> for importing the data into WeeWx.  This app is pretty basic - no real data 
> checks and no attempt to adjust for differences in the archive interval (my 
> station was already logging at 5 minute intervals).  And it is setup to 
> import one month at a time: reads one *.wlk file and writes one *.csv 
> file.  But I've moved over a few years of data to WeeWx without any 
> problems (so far).  The app is written in C# with visual studio and I'm 
> happy to share code and/or executables.
>
> Steve
>
>

-- 
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/8f408f30-82d9-4584-926a-547a83ac9c34%40googlegroups.com.

[weewx-user] Re: Importing WLK files from Davis Instruments WeatherLink software

[Steve Preston]

Actually... I have two questions about the importing process with 
wee_import.

1. Is it OK to run the wee_import process during an archive interval 
"update"?
2. How does wee_import handle changes in the archive interval.  All of the 
data I have imported to this point has been from wlk files that had a five 
minute interval.  I may eventually find some earlier wlk files with a 
shorter, 1 min, interval.  Will this be a problem for wee_import?

Thanks
Steve

On Tuesday, April 14, 2020 at 3:24:16 PM UTC-7, Steve Preston wrote:
>
> This is just a FYI for the group.  After using WeatherLink for 15+ years, 
> I have finally switched to WeeWx!
>
> I wrote a basic Windows app for converting the WLK files into CSV format 
> for importing the data into WeeWx.  This app is pretty basic - no real data 
> checks and no attempt to adjust for differences in the archive interval (my 
> station was already logging at 5 minute intervals).  And it is setup to 
> import one month at a time: reads one *.wlk file and writes one *.csv 
> file.  But I've moved over a few years of data to WeeWx without any 
> problems (so far).  The app is written in C# with visual studio and I'm 
> happy to share code and/or executables.
>
> Steve
>
>

-- 
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/0d626c25-da03-4b49-90ee-e5a39cba9419%40googlegroups.com.

[weewx-user] Re: Importing WLK files from Davis Instruments WeatherLink software

[Steve Preston]

I have put the app on GitHub. And the readme has a fair amount of info:
https://github.com/stevepr/wlkReader

I'm happy to include a note on the wiki as well.  But I'm not sure of the 
proper method for adding info to the wiki. If someone can tell me how I 
will give it a try.

Steve


On Tuesday, April 14, 2020 at 3:24:16 PM UTC-7, Steve Preston wrote:
>
> This is just a FYI for the group.  After using WeatherLink for 15+ years, 
> I have finally switched to WeeWx!
>
> I wrote a basic Windows app for converting the WLK files into CSV format 
> for importing the data into WeeWx.  This app is pretty basic - no real data 
> checks and no attempt to adjust for differences in the archive interval (my 
> station was already logging at 5 minute intervals).  And it is setup to 
> import one month at a time: reads one *.wlk file and writes one *.csv 
> file.  But I've moved over a few years of data to WeeWx without any 
> problems (so far).  The app is written in C# with visual studio and I'm 
> happy to share code and/or executables.
>
> Steve
>
>

-- 
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/fdeca8d4-a4d3-4890-a42d-b264368abd02%40googlegroups.com.

[weewx-user] Importing WLK files from Davis Instruments WeatherLink software

[Steve Preston]

This is just a FYI for the group.  After using WeatherLink for 15+ years, I 
have finally switched to WeeWx!

I wrote a basic Windows app for converting the WLK files into CSV format 
for importing the data into WeeWx.  This app is pretty basic - no real data 
checks and no attempt to adjust for differences in the archive interval (my 
station was already logging at 5 minute intervals).  And it is setup to 
import one month at a time: reads one *.wlk file and writes one *.csv 
file.  But I've moved over a few years of data to WeeWx without any 
problems (so far).  The app is written in C# with visual studio and I'm 
happy to share code and/or executables.

Steve

-- 
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/6d172d9f-d0f1-422c-9af2-31ed1c47d12f%40googlegroups.com.

Re: [weewx-user] Davis Vantage Problem

[Steve Shuff]

Hello Thomas,
Many thanks for your input.
Having followed your advice I now have the system up and running again, I
think it must have been corrupt memory.
All sorted and many thanks.

Kind regards.

On Thu, Apr 2, 2020 at 12:21 PM Thomas Keffer  wrote:

> Things to try:
>
> 1. It's possible the the logger was disturbed when you replaced the
> batteries. Try reseating it in the Envoy.
>
> 2. Your symptoms don't quite fit the usual pattern of corrupt memory, but
> it's worth trying to clear the memory of the logger anyway. Follow the
> directions under Corrupt station memory
> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>
>  to
> clear the memory.
>
> -tk
>
>
> On Thu, Apr 2, 2020 at 2:35 AM Steve Shuff  wrote:
>
>> Hi All,
>> I am hopeful someone can shed some light on this error .
>>
>> My setup consist of a RPi 3 (Raspbian) running WeeWX 3.9.2 to which is
>> connected a Davis Envoy logger, The ISS is transmitting OK as can be
>> verified on the indoor console.
>>
>> The setup runs fine until the Envoy batteries died, these were replaced
>> and the Pi rebooted and the system restarted.
>> Now my data is not being produced on the graphs etc , Upon looking at the
>> syslog I see two errors,
>>
>> Apr  2 10:12:10 raspberrypi weewx[1195]: vantage: LOOP try #1; error:
>> Expected to read 99 chars; got 0 instead
>>
>> Apr  2 10:11:56 raspberrypi weewx[1195]: vantage: DMPAFT try #2; error:
>> Unable to pass CRC16 check while sending data to Vantage console
>>
>> Has anyone experienced this problem and what was the cure ? It has done
>> it before when the batteries previously failed but I dont know what I did
>> to remedy the situation.
>> Thanks for any 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/9b1973cc-a646-421c-85c0-44e58ece7f93%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/9b1973cc-a646-421c-85c0-44e58ece7f93%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/CAPq0zEB8CXqvToL7BSaRBB0Oe6SkMUGy-ggoMeh3Ym0DFLEsNw%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEB8CXqvToL7BSaRBB0Oe6SkMUGy-ggoMeh3Ym0DFLEsNw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
Steve Shuff.

-- 
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/CADNpUBGN-raepuap-PUJiGmJ20M2xGK-5nJR5VTR%3D7i93uibvg%40mail.gmail.com.

[weewx-user] Davis Vantage Problem

[Steve Shuff]

Hi All,
I am hopeful someone can shed some light on this error .

My setup consist of a RPi 3 (Raspbian) running WeeWX 3.9.2 to which is 
connected a Davis Envoy logger, The ISS is transmitting OK as can be 
verified on the indoor console.

The setup runs fine until the Envoy batteries died, these were replaced and 
the Pi rebooted and the system restarted.
Now my data is not being produced on the graphs etc , Upon looking at the 
syslog I see two errors,

Apr  2 10:12:10 raspberrypi weewx[1195]: vantage: LOOP try #1; error: 
Expected to read 99 chars; got 0 instead

Apr  2 10:11:56 raspberrypi weewx[1195]: vantage: DMPAFT try #2; error: 
Unable to pass CRC16 check while sending data to Vantage console

Has anyone experienced this problem and what was the cure ? It has done it 
before when the batteries previously failed but I dont know what I did to 
remedy the situation.
Thanks for any 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/9b1973cc-a646-421c-85c0-44e58ece7f93%40googlegroups.com.

[weewx-user] Re: weewx v4 new extended schema - so good !

[Steve Koone]

This looks great Vince, and thanks for sharing your results!

Is this something that we can apply our existing v3 systems now, or do we 
have to wait until v4 is released?

Speaking of which, can anyone (developers perhaps?) advise as to an 
official release time frame for weewx v4?  Is it soon or still down the 
road a ways?

-Stephen

-- 
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/3279a602-a0b4-4690-9903-e8c582d8f910%40googlegroups.com.

[weewx-user] Re: 4.0.0b12 & user.log & syslog files

[Steve]

Thanks Tom,

I knew it would be (embarrassing) simple. Running Interceptor 0.53 now and 
all seems good. I should have twigged that /bin/user wouldn't have changed 
when I updated. Sorry about that.

Regards,

Steve. 

-- 
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/ff549a82-db5c-4351-9469-2c6af8c0964a%40googlegroups.com.

Re: [weewx-user] 4.0.0b12 & user.log & syslog files

[Steve]

Thanks Tom,

I knew it would be (embarrassing) simple. Running Interceptor 0.53 now and 
all seems good. I should have twigged that /bin/user wouldn't have changed 
when I updated. Sorry about that.

Regards,

Steve. 

On Tuesday, 25 February 2020 00:12:57 UTC+11, Thomas Keffer wrote:
>
> WeeWX V4 using a different logging system. The interceptor driver has been 
> updated to use this new system, but it looks like you might be using the 
> old version of the driver. Current version is 0.53
>
> The new logging system allows you to customize the output. See the Wiki 
> article *Proposal for logging events in V4 
> <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging>*.
>
> -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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/16d94722-1083-4afb-9645-f599cf33cc15%40googlegroups.com.

Re: [weewx-user] 4.0.0b12 & user.log & syslog files

[Steve]

Sorry Tom,

Before updated to 4.0.0b12, my syslog, user.log & debug didn't fill up with 
interceptor messages every coupe of seconds.

On Monday, 24 February 2020 23:50:48 UTC+11, Thomas Keffer wrote:
>
> Hello, Steve
>
> Is there a question in there? I'm not sure what you're asking...
>
> On Sun, Feb 23, 2020 at 9:09 PM Steve > 
> wrote:
>
>> Hi,
>>
>> A bit of back ground, I run weewx on an RPi and use ramlog to minimise SD 
>> card writes, ramlog puts all the log files into ram and once a day writes 
>> them to the SD card. 20mb has been enough for years, but since installing 
>> 4.0.0b12 weewx has been filling the user.log and syslog , weewx.log looks 
>> ok.
>>
>> I moved from v3.9.1 because I wanted to download some data from my PWS on 
>> Wunderground (worked OK).
>>
>> I've probably missed something simple?
>>
>> Thanks, Steve.
>>
>> weewx.conf
>>
>> # This section is for general configuration information.
>>
>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>> debug = 0
>>
>> # Root directory of the weewx data file hierarchy for this station
>> WEEWX_ROOT = /home/weewx
>>
>> # Whether to log successful operations
>> log_success = False
>>
>> # Whether to log unsuccessful operations
>> log_failure = False
>>
>> # How long to wait before timing out a socket (FTP, HTTP) connection
>> socket_timeout = 20
>>
>> # Do not modify this. It is used when installing and updating weewx.
>> version = 4.0.0b12
>>
>> [[Wunderground]]
>> # This section is for configuring posts to the Weather 
>> Underground.
>> 
>> # If you wish to do this, set the option 'enable' to true,
>> # and specify a station (e.g., 'KORHOODR3') and password.
>> enable = false
>> station = IVICTORI391
>> password = mypassword
>> 
>> # Set the following to True to have weewx use the WU "Rapidfire"
>> # protocol. Not all hardware can support it. See the User's Guide.
>> rapidfire = False
>> 
>> # If you plan on using wunderfixer, set the following
>> # to your API key:
>> api_key = my api key
>>
>>
>> syslog
>>
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: ServerThread: GET: 
>> ID=IVICTORI390==69.3=80=63.0=69.3=174=4.47=7.38=0.00=0.00=0.00=2.52=5.34=290.73=2=70.7=69=30.20=0=2020-2-24%200:24:32=Weather%20logger%20V2.1.9=updateraw=1=5
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: raw data: 
>> ID=IVICTORI390=steve=69.3=80=63.0=69.3=174=4.47=7.38=0.00=0.00=0.00=2.52=5.34=290.73=2=70.7=69=30.20=0=2020-2-24%200:24:32=Weather%20logger%20V2.1.9=updateraw=1=5
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> rainin=0.00
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> dailyrainin=0.00
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> monthlyrainin=2.52
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> realtime=1
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> rtfreq=5
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> PASSWORD=steve
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> ID=IVICTORI390
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> softwaretype=Weather%20logger%20V2.1.9
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> action=updateraw
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
>> weeklyrainin=0.00
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: raw packet: 
>> {'wind_speed': 4.47, 'humidity_in': 69.0, 'temperature_in': 70.7, 
>> 'barometer': 30.2, 'windchill': 69.3, 'dewpoint': 63.0, 'battery': 0.0, 
>> 'humidity_out': 80.0, 'uv': 2.0, 'radiation': 290.73, 'rain': 0.0, 
>> 'dateTime': 1582503872, 'temperature_out': 69.3, 'wind_dir': 174.0, 
>> 'rain_total': 5.34, 'usUnits': 1, 'wind_gust': 7.38}
>> Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: mapped packet: 
>> {'barometer': 30.2, 'windchill': 69.3, 'dewpoint': 63.0, 'outHumidity': 
>> 80.0, 'UV': 2.0, 'radiation': 290.73, 'rain': 0.0, 'dateTime': 1582503872, 
>> 'windDir': 174.0, 'outTemp': 69.3, 'windSpeed': 4.47, 'txBatteryStatus': 
>> 0.0, 'inTemp': 70.7, 'windGust': 7.38, 'inHumidity': 69.0, 'usUnits': 1}
>> Feb 24 11:

[weewx-user] 4.0.0b12 & user.log & syslog files

[Steve]

Hi,

A bit of back ground, I run weewx on an RPi and use ramlog to minimise SD 
card writes, ramlog puts all the log files into ram and once a day writes 
them to the SD card. 20mb has been enough for years, but since installing 
4.0.0b12 weewx has been filling the user.log and syslog , weewx.log looks 
ok.

I moved from v3.9.1 because I wanted to download some data from my PWS on 
Wunderground (worked OK).

I've probably missed something simple?

Thanks, Steve.

weewx.conf

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /home/weewx

# Whether to log successful operations
log_success = False

# Whether to log unsuccessful operations
log_failure = False

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.0.0b12

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
enable = false
station = IVICTORI391
password = mypassword

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = False

# If you plan on using wunderfixer, set the following
# to your API key:
api_key = my api key


syslog

Feb 24 11:24:33 rpi3 weewxd: interceptor: ServerThread: GET: 
ID=IVICTORI390==69.3=80=63.0=69.3=174=4.47=7.38=0.00=0.00=0.00=2.52=5.34=290.73=2=70.7=69=30.20=0=2020-2-24%200:24:32=Weather%20logger%20V2.1.9=updateraw=1=5
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: raw data: 
ID=IVICTORI390=steve=69.3=80=63.0=69.3=174=4.47=7.38=0.00=0.00=0.00=2.52=5.34=290.73=2=70.7=69=30.20=0=2020-2-24%200:24:32=Weather%20logger%20V2.1.9=updateraw=1=5
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
rainin=0.00
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
dailyrainin=0.00
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
monthlyrainin=2.52
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
realtime=1
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
rtfreq=5
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
PASSWORD=steve
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
ID=IVICTORI390
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
softwaretype=Weather%20logger%20V2.1.9
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
action=updateraw
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: ignored parameter 
weeklyrainin=0.00
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: raw packet: 
{'wind_speed': 4.47, 'humidity_in': 69.0, 'temperature_in': 70.7, 
'barometer': 30.2, 'windchill': 69.3, 'dewpoint': 63.0, 'battery': 0.0, 
'humidity_out': 80.0, 'uv': 2.0, 'radiation': 290.73, 'rain': 0.0, 
'dateTime': 1582503872, 'temperature_out': 69.3, 'wind_dir': 174.0, 
'rain_total': 5.34, 'usUnits': 1, 'wind_gust': 7.38}
Feb 24 11:24:33 rpi3 weewxd: interceptor: MainThread: mapped packet: 
{'barometer': 30.2, 'windchill': 69.3, 'dewpoint': 63.0, 'outHumidity': 
80.0, 'UV': 2.0, 'radiation': 290.73, 'rain': 0.0, 'dateTime': 1582503872, 
'windDir': 174.0, 'outTemp': 69.3, 'windSpeed': 4.47, 'txBatteryStatus': 
0.0, 'inTemp': 70.7, 'windGust': 7.38, 'inHumidity': 69.0, 'usUnits': 1}
Feb 24 11:24:43 rpi3 weewxd: interceptor: MainThread: empty queue
Feb 24 11:24:49 rpi3 weewxd: interceptor: ServerThread: GET: 
ID=IVICTORI390==69.3=79=62.6=69.3=220=5.14=7.38=0.00=0.00=0.00=2.52=5.34=284.55=2=70.7=69=30.20=0=2020-2-24%200:24:48=Weather%20logger%20V2.1.9=updateraw=1=5
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: raw data: 
ID=IVICTORI390=steve=69.3=79=62.6=69.3=220=5.14=7.38=0.00=0.00=0.00=2.52=5.34=284.55=2=70.7=69=30.20=0=2020-2-24%200:24:48=Weather%20logger%20V2.1.9=updateraw=1=5
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
rainin=0.00
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
dailyrainin=0.00
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
monthlyrainin=2.52
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
realtime=1
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
rtfreq=5
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
PASSWORD=steve
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
ID=IVICTORI390
Feb 24 11:24:49 rpi3 weewxd: interceptor: MainThread: ignored parameter 
softwarety

Re: [weewx-user] Re: WxForum down?

[Steve Anderson]

Sweet.  I clicked the link in the e-mail notification without really 
reading and BAM, I was in WXForum.  It was like falling down the rabbit 
hole :-)

On Friday, January 24, 2020 at 11:47:50 AM UTC-6, galfert wrote:
>
> http://74.208.29.36/index.php
>

-- 
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/ac443a5c-ac4f-4f52-a5a5-f75b1a285b4f%40googlegroups.com.

[weewx-user] Re: WxForum down?

[Steve Anderson]

Anybody got the IP address?  That should work.

On Tuesday, January 21, 2020 at 10:34:18 AM UTC-6, Paul Grunwald wrote:
>
>
> me (pgrunwald change) 
> 9:33 AM (less than a minute ago)
> https://notopening.com/site/wxforum.net
>
> Anyone know what is going on?
>
>

-- 
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/b04ca6fe-0b90-4c23-8fa0-7c6107ded89c%40googlegroups.com.

[weewx-user] Re: improve readability of daily charts - Seasons skin

[Steve M]

Rich, 

I changed the Archive interval from the default of 30 minutes to 10 minutes 
using wee_device, which then produced the intended line chart, instead of 
the separate dots the 30 minute archive interval produced. I also changed 
the line width in the skin.conf file from 5 to 1.  That produces a very 
nice graph. I'm satisfied with the results for now.

Thanks for the pointer to the solution.

Steve

On Sunday, January 19, 2020 at 12:02:24 AM UTC-6, rich T wrote:
>
>
> Steve
>
> Lets see what happens
>
> Rich
>
> On Sunday, January 19, 2020 at 12:44:44 AM UTC-5, Steve M wrote:
>
>> Thanks, Rich.  I hadn't found that doc.  I've applied that change, and 
>> I'll check the data in the morning.
>>
>> Steve
>>
>> On Saturday, January 18, 2020 at 12:16:55 PM UTC-6, rich T wrote:
>>>
>>> Did you check out this link: 
>>> http://www.weewx.com/docs/usersguide.htm#dots_in_plots
>>>
>>> On Saturday, January 18, 2020 at 12:53:19 PM UTC-5, Steve M wrote:
>>>>
>>>> I realized I didn't post an image of the default Daily charts, showing 
>>>> the almost unreadable chart points.  Attaching another image of this.
>>>> Steve
>>>>
>>>> On Saturday, January 18, 2020 at 3:55:45 AM UTC-6, Steve M wrote:
>>>>>
>>>>> I'm just getting started with WeeWx 3.9.2 using the Seasons skin.  I 
>>>>> got it running well, but the Daily History Charts are almost unreadable 
>>>>> because the chart points are widely separated dots.  The Week, Month, 
>>>>> Year 
>>>>> charts have enough points plotted together to be easily visible. 
>>>>>
>>>>> I've tried been trying to correct in the the skins.conf file with 
>>>>> limited success. I tried changing the marker_type from "none" to the 
>>>>> other 
>>>>> choices, but that produces a readable but ugly chart. What can I do to 
>>>>> get 
>>>>> a readable line chart, as I've seen in examples in developer discussions 
>>>>> of 
>>>>> the seasons skin?  I've attached an example of my graph.  
>>>>>
>>>>> Also where can I adjust the frequency of web page updates?  I've seen 
>>>>> discussions of Archive Interval, and report-timing, but can't find where 
>>>>> hthey are set or can be adjusted.
>>>>>
>>>>> I'm running on a Rasbperry Pi 3, with LXQT window manager.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Steve
>>>>>
>>>>>
>>>>>

-- 
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/5725041c-9c4d-423b-8c5c-04297ba5443d%40googlegroups.com.

[weewx-user] Re: improve readability of daily charts - Seasons skin

[Steve M]

Thanks, Rich.  I hadn't found that doc.  I've applied that change, and I'll 
check the data in the morning.

Steve

On Saturday, January 18, 2020 at 12:16:55 PM UTC-6, rich T wrote:
>
> Did you check out this link: 
> http://www.weewx.com/docs/usersguide.htm#dots_in_plots
>
> On Saturday, January 18, 2020 at 12:53:19 PM UTC-5, Steve M wrote:
>>
>> I realized I didn't post an image of the default Daily charts, showing 
>> the almost unreadable chart points.  Attaching another image of this.
>> Steve
>>
>> On Saturday, January 18, 2020 at 3:55:45 AM UTC-6, Steve M wrote:
>>>
>>> I'm just getting started with WeeWx 3.9.2 using the Seasons skin.  I got 
>>> it running well, but the Daily History Charts are almost unreadable because 
>>> the chart points are widely separated dots.  The Week, Month, Year charts 
>>> have enough points plotted together to be easily visible. 
>>>
>>> I've tried been trying to correct in the the skins.conf file with 
>>> limited success. I tried changing the marker_type from "none" to the other 
>>> choices, but that produces a readable but ugly chart. What can I do to get 
>>> a readable line chart, as I've seen in examples in developer discussions of 
>>> the seasons skin?  I've attached an example of my graph.  
>>>
>>> Also where can I adjust the frequency of web page updates?  I've seen 
>>> discussions of Archive Interval, and report-timing, but can't find where 
>>> hthey are set or can be adjusted.
>>>
>>> I'm running on a Rasbperry Pi 3, with LXQT window manager.
>>>
>>>
>>> Thanks,
>>> Steve
>>>
>>>
>>>

-- 
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/801d3812-80f7-4860-841d-06d495d12c12%40googlegroups.com.

[weewx-user] Re: improve readability of daily charts - Seasons skin

[Steve M]

I realized I didn't post an image of the default Daily charts, showing the 
almost unreadable chart points.  Attaching another image of this.
Steve

On Saturday, January 18, 2020 at 3:55:45 AM UTC-6, Steve M wrote:
>
> I'm just getting started with WeeWx 3.9.2 using the Seasons skin.  I got 
> it running well, but the Daily History Charts are almost unreadable because 
> the chart points are widely separated dots.  The Week, Month, Year charts 
> have enough points plotted together to be easily visible. 
>
> I've tried been trying to correct in the the skins.conf file with limited 
> success. I tried changing the marker_type from "none" to the other choices, 
> but that produces a readable but ugly chart. What can I do to get a 
> readable line chart, as I've seen in examples in developer discussions of 
> the seasons skin?  I've attached an example of my graph.  
>
> Also where can I adjust the frequency of web page updates?  I've seen 
> discussions of Archive Interval, and report-timing, but can't find where 
> hthey are set or can be adjusted.
>
> I'm running on a Rasbperry Pi 3, with LXQT window manager.
>
>
> Thanks,
> Steve
>
>
>

-- 
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/ed477361-8b24-488f-831d-d6967ec5a1b4%40googlegroups.com.

[weewx-user] improve readability of daily charts - Seasons skin

[Steve M]

I'm just getting started with WeeWx 3.9.2 using the Seasons skin.  I got it 
running well, but the Daily History Charts are almost unreadable because 
the chart points are widely separated dots.  The Week, Month, Year charts 
have enough points plotted together to be easily visible. 

I've tried been trying to correct in the the skins.conf file with limited 
success. I tried changing the marker_type from "none" to the other choices, 
but that produces a readable but ugly chart. What can I do to get a 
readable line chart, as I've seen in examples in developer discussions of 
the seasons skin?  I've attached an example of my graph.  

Also where can I adjust the frequency of web page updates?  I've seen 
discussions of Archive Interval, and report-timing, but can't find where 
hthey are set or can be adjusted.

I'm running on a Rasbperry Pi 3, with LXQT window manager.


Thanks,
Steve


-- 
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/4114fd6f-18dc-488a-ba7f-6459612348db%40googlegroups.com.

Re: [weewx-user] Webcam Streaming

[Steve Meltz]

Still no luck..I am continuing my research.

On Tue, Dec 24, 2019, 11:17 AM p q  wrote:

> can you get to the webcam URL from outside the firewall?
>
> On Tue, Dec 24, 2019 at 6:37 AM Steve2Q  wrote:
>
>> Hello (and Happy Holidays to all!) I am trying to have the image from a
>> streaming webcam added to my weewx page. I have it functioning over the
>> wireless network in my home, but I cannot see it from the outside world.
>> The following are the settings I am using:
>>
>> In skin.conf I have:
>> [Extras]
>> # Put any extra tags here that you want to be available in the
>> templates
>>
>> # Here's an example.
>> # This radar image will be available as $Extras.radar_img
>> radar_img = http://radar.weather.gov/ridge/lite/N0R/AMX_loop.gif
>> # This URL will be used as the image hyperlink:
>> # radar_url =
>> http://radar.weather.gov/ridge/radar.php?rid=amx=N0R=1110=yes
>> radar_url = http://www.spaghettimodels.com/cities/westpalmbeach.htm
>> # URL for Blitzortung.org; added 08/23/15
>>  [[lightning]]
>>  lightning_img = http://www.blitzortung.org/Images/image_b_us.png
>> #lightning_url =
>> http://www.blitzortung.org/Webpages/index.php?lang=en_0=32
>>  lightning_url =
>> http://www.blitzortung.org/live_lightning_maps.php?map=32
>> # end of addition
>>  [[webcam]]
>>  hyperlink = http://xxx.xxx.x.xx:8081
>>
>> In index.html.tmpl is:
>>
>>  #if $Extras.has_key('radar_img')
>> 
>>   
>> 
>>   Click image for expanded radar loop
>>   
>> > />
>>   Click image for more Florida lightning info
>>   
>> http://xxx.xxx.x.xx:8081; alt="Webcam" />
>>  
>> #end if
>>
>> In my router, I added a port forwarding entry of xxx.xxx.x.xx:8081
>>
>> Thanks for any guidance...
>>
>> --
>> 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/3b8e4f53-a722-4567-913b-452fa9a850b0%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Peter Quinn
> (415)794-2264
>
> --
> 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/oNqNUgwdIR0/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/CAA1SM21415y_xeFCrxrsj%3DMEGUTFkTABoZO3bTQtJr9Dtr%3DdRg%40mail.gmail.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/CAH0o-akrpTyvBPbQm1OdQLUTRQVZKD2u6_BQDTxiCZi9iVG3pA%40mail.gmail.com.

Re: [weewx-user] Re: Which way to make progress ?

[Steve Shuff]

Hello Vince
Thanks for the reply

The CR1000 based weather station ftp the data to Weather Underground in the
following format,


https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=KCASANFR5=XX=2000-01-01+10%3A32%3A35=230=12=12=70=0=29.1=68.2=90===vws%20versionxx=updateraw

As your probably aware WU has been having several issues recently and I
fear that one day soon they will cease to offer their service.
My station (CR1000) has many sensors which currently WU no longer support
ie soil temp, leaf wetness and others.

This is why I would like to develop a system whereby the CR1000  (based in
a remote location) will ftp the data to an FTP server on the Pi via the WWW
, then customise Weewx to suite my needs. An Apache2 webserver would then
display the data for interested parties to view.
I already have an Apache2 server on the Pi but i'm not sure if you can FTP
into that ?
The point of my first email was to see if anyone had done something similar
and if they were in a position to offer any advice as to how to go about
the project.

Best regards.



https:/

/weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=KCASANFR5=XX=2000-01-01+10%3A32%3A35=230

eedmph=12=12=70=0=29.1=68.2=90===vws%20versionxx=updateraw


On Wed, Oct 9, 2019 at 5:04 PM vince  wrote:

> On Wednesday, October 9, 2019 at 2:54:00 AM UTC-7, Steve Shuff wrote:
>
>>  CR1000 is already doing an FTP upload to the Weather Underground server
>> every 10 minutes (and I can add a bit of code so the station will FTP data
>> to a server on my Raspberry Pi)
>> then get Weewx to interpret the FTP file and display the data.
>>
>>
> If you're ftp'ing pre-computed HTML files then weewx has nothing to do
> with it, the webserver would display whatever you upload.
>
> Or you could write something to read your file and write to a weewx db and
> 'then' have weewx generate the HTML files.
>
> But if all you want to do is cook up static HTML, I'd probably not include
> weewx at all.  I'd read the FTP'd fine and generate HTML via a python
> script run via cron.
>
> --
> 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/a283f467-0ac1-4af1-9fe2-93948523cba0%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/a283f467-0ac1-4af1-9fe2-93948523cba0%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
Steve Shuff.

-- 
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/CADNpUBGwH9Eu_8wOmyqJn34vVO5Wwq70P5gftAfFiJk38vb_Ww%40mail.gmail.com.

[weewx-user] Which way to make progress ?

[Steve Shuff]

Hello Folks,
Hoping someone can help me out on this one please, 
I have a Davis Vantage Pro station sending data to the Davis Envoy which is 
plugged in to the Raspberry Pi running Weewx all is good and no problems 
there !
Also I have access to a Campbell Scientific CR1000 system, uploading data 
to Weather Underground, Which I am thinking about moving away from because 
of their recent issues.

The CR1000 station has many sensors and I am of the opinion that it would 
be well suited to Weewx although I may have to  develop a driver for it .
 CR1000 is already doing an FTP upload to the Weather Underground server 
every 10 minutes (and I can add a bit of code so the station will FTP data 
to a server on my Raspberry Pi)
then get Weewx to interpret the FTP file and display the data.
Has anyone been down this road already ? I did read recently this article 
https://itsmereal.com/raspberry-pi-web-server-apache-php-mysql-phpmyadmin-ftp/ 
which 
seemed relevant or can it be made simpler than this ?
Thanks for any 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/f3c1ba45-bc33-42fc-92b1-5f4d44b4c064%40googlegroups.com.

[weewx-user] Using WeeWX with CSV or MySQL as data source

[Steve Shuff]

Hi, I just read your post regarding the Campbell scientific station, Did you 
make any progress ? I have a cr1000 based station with multiple sensors and 
would be very interested in using Weewx with the setup. 

-- 
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/e45a6b23-cb66-49fd-b034-641f8fd500b6%40googlegroups.com.

Re: [weewx-user] weewx stopped with

[Steve Shuff]

Cancel
On Sat, 7 Sep 2019, 09:11 peter,  wrote:

> weewx stopped this morning with an error I don't understand. I also
> doesn't want to start either.
>
> Can some please advise what would be the cause?
> I have Davis Vantage Vue + few other inputs from text files I log into
> database. This week I added logging of a big integer values into 'hail'
> field.
>
> This is the status:
> sep 07 10:00:55 weather weewx[447]: File
> "/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
> sep 07 10:00:55 weather weewx[447]:   _day_summary.addRecord(
> record, weight=_weight)
> sep 07 10:00:55 weather weewx[447]: File
> "/usr/share/weewx/weewx/accum.py", line 260, in addRecord
> sep 07 10:00:55 weather weewx[447]:   func(self, record,
> obs_type, add_hilo, weight)
> sep 07 10:00:55 weather weewx[447]: File
> "/usr/share/weewx/weewx/accum.py", line 318, in add_value
> sep 07 10:00:55 weather weewx[447]:   self[obs_type].addHiLo(
> val, record['dateTime'])
> sep 07 10:00:55 weather weewx[447]: File
> "/usr/share/weewx/weewx/accum.py", line 78, in addHiLo
> sep 07 10:00:55 weather weewx[447]:   "got type '%s' ('%s')" %
> (type(val), val))
> sep 07 10:00:55 weather weewx[447]:   ValueError: accum:
> ScalarStats.addHiLo expected float or int, got type '' (
> 'nan')
> sep 07 10:00:55 weather weewx[447]:   Exiting.
>
> 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/75ebceae-9bb1-40f8-8ef5-96b1cedaf1d0%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/CADNpUBFJTaYHE23__N6dA-We5VTcf5tQeAeF814sa8ya7jVCLg%40mail.gmail.com.

Re: [weewx-user] Re: Belchertown skin 1.0 released!

[Steve Shuff]

Cancel
On Sat, 31 Aug 2019, 17:07 Stefan,  wrote:

> Hello Pat.
> Thank you for your answer. I think you mean this one. I had made various
> changes, but without success. Which variables do I have to use there?
> Do not see any color in the wind.
>
> See this: https://www.meteo-oberwallis.ch/wetter/glis/user/
>
> // Change the color of the windSpeed_kph variable
> function update_windSpeed_kph( wind ) {
> outTemp = parseFloat( wind ).toFixed(0); // Convert back to decimal
> literal
> if ( wind <= 0 ) {
> jQuery(".curwindspeed").css( "color", "#1278c8" );
> } else if ( wind <= -3.8 ) {
> jQuery(".curwindspeed").css( "color", "#30bfef" );
> } else if ( wind <= 0 ) {
> jQuery(".curwindspeed").css( "color", "#1fafdd" );
> } else if ( wind <= 4.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(0,172,223,1)" );
> } else if ( wind <= 10 ) {
> jQuery(".curwindspeed").css( "color", "#71bc3c" );
> } else if ( wind <= 12.7 ) {
> jQuery(".curwindspeed").css( "color", "rgba(90,179,41,0.8)" );
> } else if ( wind <= 18.3 ) {
> jQuery(".curwindspeed").css( "color", "rgba(131,173,45,1)" );
> } else if ( wind <= 21.1 ) {
> jQuery(".curwindspeed").css( "color", "rgba(206,184,98,1)" );
> } else if ( wind <= 23.8 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,174,0,0.9)" );
> } else if ( wind <= 26.6 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,153,0,0.9)" );
> } else if ( wind <= 29.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,127,0,1)" );
> } else if ( wind <= 32.2 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,79,0,0.9)" );
> } else if ( wind <= 35 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,69,69,1)" );
> } else if ( wind <= 43.3 ) {
> jQuery(".curwindspeed").css( "color", "rgba(255,104,104,1)" );
> } else if ( wind >= 43.4 ) {
> jQuery(".curwindspeed").css( "color", "rgba(218,113,113,1)" );
> }
> }
>
> Am Samstag, 31. August 2019 15:03:59 UTC+2 schrieb Pat:
>>
>> The code doesn't exist in the skin as it is right now, but it would be
>> easy to add.
>>
>> Create a new function in the belchertown.js.tmpl file for the wind speed
>> and the colors you want. You could copy something like this for the
>> temperature
>> .
>> Then have the wind speed go through that function
>> 
>> to change it's color. Use the temperature live section
>> 
>> for an example of this.
>>
>> On Saturday, August 31, 2019 at 5:53:06 AM UTC-4, Stefan wrote:
>>>
>>> Hello.
>>> I have a question. Can the wind speed in Belchertown also be colored? eg
>>> from 40 km yellow and from 80 red and from 120 purple? I mean in live
>>> view.
>>>
>>> [image: Unbenannt.PNG]
>>>
>>> Thanks for 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/097832b9-8b60-4fb5-ab57-00cd96f89cb8%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/CADNpUBFCjx%3D2rEJyxyGvReicxob9w%3DFtDVk_7mwG2vdpg68VzQ%40mail.gmail.com.

[weewx-user] Enabling Windrun

[Steve Schindler]

I am trying to display windrun using WeeWX ver. 3.9.2 and a Davis VP2 
station. Currently on my web page, I'm seeing the literal tag 
"$day.windrun.sum" vice a value.

I did some digging around and discovered in Issue #250 that "StdWXCalculate 
can optionally (it is disabled by default) augment each archive record with 
a calculated windrun field." So I added windrun to StdWXCalculate (although 
I'm not sure that this is still required):

[StdWXCalculate]

[[Calculations]]
# Derived quantities are calculated by this service. 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
# Added windrun 8-24-2019
windrun = software

Also in that Issue, Tom mentioned "It should be possible to sum the archive 
records and get the total for the day. However, this is only possible if 
windrun appears in the database."

This make me think that I need to add a new observation type (windrun) to 
the WeeWx database.

Am I on the right track here?

Log file is attached.

-- 
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/08c01789-84e6-49cb-959c-042ac08293a5%40googlegroups.com.
Aug 25 15:31:44 watson weewx[2423]:   for _loop_packet in 
self.genDavisLoopPackets(200):
Aug 25 15:31:44 watson weewx[2423]: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 535, in genDavisLoopPackets
Aug 25 15:31:44 watson weewx[2423]:   _buffer = self.port.read(99)
Aug 25 15:31:44 watson weewx[2423]: File 
"/home/weewx/bin/weewx/drivers/vantage.py", line 256, in read
Aug 25 15:31:44 watson weewx[2423]:   _buffer = 
self.serial_port.read(chars)
Aug 25 15:31:44 watson weewx[2423]: File 
"/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 442, in read
Aug 25 15:31:44 watson weewx[2423]:   ready,_,_ = 
select.select([self.fd],[],[], self._timeout)
Aug 25 15:31:44 watson weewx[2423]: File 
"/home/weewx/bin/weewx/engine.py", line 812, in sigTERMhandler
Aug 25 15:31:44 watson weewx[2423]:   raise Terminate
Aug 25 15:31:44 watson weewx[2423]:   Terminate
Aug 25 15:32:37 watson weewx[2470]: engine: Initializing weewx version 3.9.2
Aug 25 15:32:37 watson weewx[2470]: engine: Using Python 2.7.3 (default, Nov 24 
2017, 21:13:24) #012[GCC 4.6.3]
Aug 25 15:32:37 watson weewx[2470]: engine: Platform 
Linux-4.1.19+-armv6l-with-debian-7.11
Aug 25 15:32:37 watson weewx[2470]: engine: Locale is 'en_US.UTF-8'
Aug 25 15:32:37 watson weewx[2470]: engine: pid file is /var/run/weewx.pid
Aug 25 15:32:37 watson weewx[2474]: engine: Using configuration file 
/home/weewx/weewx.conf
Aug 25 15:32:37 watson weewx[2474]: engine: Debug is 1
Aug 25 15:32:37 watson weewx[2474]: engine: Initializing engine
Aug 25 15:32:37 watson weewx[2474]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Aug 25 15:32:37 watson weewx[2474]: vantage: Driver version is 3.1.1
Aug 25 15:32:37 watson weewx[2474]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 5.00
Aug 25 15:32:37 watson weewx[2474]: vantage: Gentle wake up of console 
successful
Aug 25 15:32:37 watson weewx[2474]: vantage: Hardware type is 16
Aug 25 15:32:37 watson weewx[2474]: vantage: ISS ID is 1
Aug 25 15:32:37 watson weewx[2474]: vantage: Hardware name: Vantage Pro2
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.engine.StdTimeSynch
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.engine.StdConvert
Aug 25 15:32:37 watson weewx[2474]: engine: StdConvert target unit is 0x1
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdConvert
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.engine.StdCalibrate
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdCalibrate
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service weewx.engine.StdQC
Aug 25 15:32:37 watson weewx[2474]: engine: Finished loading service 
weewx.engine.StdQC
Aug 25 15:32:37 watson weewx[2474]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Aug 25 15:32:37 watson 

Re: [weewx-user] Problem with Rain in Weewx.

[Steve Harris]

So I've now changed the archive period to 300 seconds.

How blimming odd!

It "Seems" to have fixed it.

I fired weewx rain at it at 22:46, 0.011 in the first weewx file.

I then fired a 0.022 in the next minute

and then another 0.022 in the next minute

So total rain was 0.055 .

That calculated correctly in weewx 


So it DOES appear that a 5 minute archive interval seems to make things
correct!

How strange!

Ok, well thanks to gjr80 because you must just be right!!
I will keep an eye on this!


On Sun, 18 Aug 2019 at 22:18, Steve Harris  wrote:

> Hi Gary
>
> Thanks for the reply.
>
> I've just changed the archive interval back to 300 (5 minutes). and I'm
> going to do some more testing.
>
> I'm manually just adding some rain into the weewx file to see if I can
> work out what is going on.
>
> I'll keep you posted
>
> Thanks for your help
>
> On Sun, 18 Aug 2019 at 22:10, gjr80  wrote:
>
>> Hi,
>>
>> Suggest you put some logging into the modified driver you are using so
>> you can see what is being read when.
>>
>> Likely unrelated but I get uneasy when loop interval == archive interval.
>> Sooner or later you are likely to have an archive interval with no loop
>> data. Shouldn’t really cause any catastrophic failures, just a personal
>> preference.
>>
>> 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-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/7ccd9cec-d3af-4e13-9efd-68a4e9b4e053%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/CAD%3Dnsok768pMOzTSC3iX0K_qGPrpgFembz0JKvaNOcSFEyrSFQ%40mail.gmail.com.

Re: [weewx-user] Problem with Rain in Weewx.

[Steve Harris]

Hi Gary

Thanks for the reply.

I've just changed the archive interval back to 300 (5 minutes). and I'm
going to do some more testing.

I'm manually just adding some rain into the weewx file to see if I can work
out what is going on.

I'll keep you posted

Thanks for your help

On Sun, 18 Aug 2019 at 22:10, gjr80  wrote:

> Hi,
>
> Suggest you put some logging into the modified driver you are using so you
> can see what is being read when.
>
> Likely unrelated but I get uneasy when loop interval == archive interval.
> Sooner or later you are likely to have an archive interval with no loop
> data. Shouldn’t really cause any catastrophic failures, just a personal
> preference.
>
> 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-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/7ccd9cec-d3af-4e13-9efd-68a4e9b4e053%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/CAD%3DnsomaOydvend9%3DhanB83fKksQYeEO8G%2BeghtiRiRQKzOAjQ%40mail.gmail.com.

[weewx-user] Problem with Rain in Weewx.

[Steve Harris]

Hi All,

Hope you're all well.

My weather station is at http://www.raynesparkweather.co.uk

The station is custom built from an Arduino and some weather sensors that 
you got with the Fine Offset W1080.

I made a new circuit board and simplified everything this year to get 
reliable output from the arduino.

I now have that.

My station spits out data every second and monitors rain tips. This data is 
collected by a raspberry pi, which in turn spits out a data string every 
minute and creats a weewx.txt file for the FileParse driver.

My file looks like this.


rain=0.0
outTemp=60.855201
barometer=29.8096146482
outHumidity=84.443167
dewpoint=56.13
windSpeed=4.2271667
windDir=252
UV=0.0
radiation=0.2218873
extraTemp1=1.88
extraTemp2=1.58
soilTemp1=136.4
extraTemp3=1
inTemp=69.95

Don't worry too much about the contents as I'm only having a problem at the 
moment with rain calculations.

When it rains, the bucket tips and the rain value above will be 0.011 (for 
a single tip) or 0.022 for two tips, or 0.033 for 3 tips.

This is calculated every minute by my station and a new weewx file is read.


My problem is this.

Say for example, I have three weewx files over three minutes.


In file 1 I have 

rain=0.011


In file 2 I have 
rain = 0.022

In file 3 I have 

rain = 0.011


So, the total rain over the three minutes will be 0.044 inches or 1.1176mm


I have been having a problem with weewx double reading the fileparse file 
so I added a line in the fileparse driver to delete the weewx file once it 
has been read. This works a treat.


However, I'm still seeing weewx sometimes double reading the data.

I know it's only getting the three weewx files and it should sum up to 
0.044inches, but this evening it summed to 1.76 mm which is 2 more of 0.011 
inches than it should be.

I have the "poll interval" set to 60 seconds and the archive interval set 
to 60 seconds.


I have also watched the weewx file disappear once it's been read and I'm 
seeing no errors on syslog saying the weewx.file doesn't exist. In other 
words, weewx is being given 100% correct data, but still seems to be 
screwing up the rain value.

Any help would be appreciated.

Thank you


-- 
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/8db781e9-612f-4c69-80f6-c7bfe2c5b33a%40googlegroups.com.

Re: [weewx-user] Re: WeeWX Station Type.

[Steve Shuff]

Hi, thanks for your reply.  I assume that is done in the weewx.conf file ?

On Wed, 14 Aug 2019, 18:46 Michi Kaa,  wrote:

> I think simply changing to "Simulator" and a restart will do. But backup
> your database before and restore it, before you connect the real station
> again.
>
> Am Mittwoch, 14. August 2019 19:15:41 UTC+2 schrieb Steve Shuff:
>>
>> Hi All,
>>  I wish to change the station type from Vantage to Simulator, Can someone
>> explain how to do this please, I have moved house and setup my Raspberry Pi
>> but my station need collecting from my old house and I just want to
>> temporarily run Simulator to ensure everything is alright with the lat/long
>> etc changes I made to config file .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/250f958a-21ec-4895-b511-5dd0aa766cf9%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/250f958a-21ec-4895-b511-5dd0aa766cf9%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/CADNpUBFPHbYBo1cCKk99%2Bq2CxXWuXXve98noajD%3Dk1_arBNW5A%40mail.gmail.com.

[weewx-user] WeeWX Station Type.

[Steve Shuff]

Hi All,
 I wish to change the station type from Vantage to Simulator, Can someone 
explain how to do this please, I have moved house and setup my Raspberry Pi 
but my station need collecting from my old house and I just want to 
temporarily run Simulator to ensure everything is alright with the lat/long 
etc changes I made to config file .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/931157f0-0c2e-49dd-9deb-af64e9424068%40googlegroups.com.

[weewx-user] Python installation woes

[Steve London]

Trying to install weewx on Raspbian. Python has never (successfully) been 
installed on this rPi. Here's the errors. Suggestions ?

Thanks !

pi@raspberrypi:~ $ sudo apt-get install weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
weewx is already the newest version (3.9.2-1).
The following packages were automatically installed and are no longer 
required:
  libfile-copy-recursive-perl openbsd-inetd update-inetd
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 120 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up python-configobj (5.0.6-2) ...
  File "/usr/lib/python2.7/encodings/__init__.py", line 1
SyntaxError: Non-ASCII character '\xa4' in file 
/usr/lib/python2.7/encodings/__init__.py on line 1, but no encoding 
declared; see http://python.org/dev/peps/pep-0263/ for details
dpkg: error processing package python-configobj (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up python-usb (1.0.0-1) ...
  File "/usr/lib/python2.7/encodings/__init__.py", line 1
SyntaxError: Non-ASCII character '\xa4' in file 
/usr/lib/python2.7/encodings/__init__.py on line 1, but no encoding 
declared; see http://python.org/dev/peps/pep-0263/ for details
dpkg: error processing package python-usb (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up python-imaging (4.0.0-4) ...
  File "/usr/lib/python2.7/encodings/__init__.py", line 1
SyntaxError: Non-ASCII character '\xa4' in file 
/usr/lib/python2.7/encodings/__init__.py on line 1, but no encoding 
declared; see http://python.org/dev/peps/pep-0263/ for details
dpkg: error processing package python-imaging (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up python-cheetah (2.4.4-4) ...
  File "/usr/lib/python2.7/encodings/__init__.py", line 1
SyntaxError: Non-ASCII character '\xa4' in file 
/usr/lib/python2.7/encodings/__init__.py on line 1, but no encoding 
declared; see http://python.org/dev/peps/pep-0263/ for details
dpkg: error processing package python-cheetah (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of weewx:
 weewx depends on python-configobj (>= 4.5); however:
  Package python-configobj is not configured yet.
 weewx depends on python-cheetah (>= 2.0); however:
  Package python-cheetah is not configured yet.
 weewx depends on python-imaging (>= 1.1.6) | python-pil (>= 5.1.0) | 
python-pillow (>= 5.1.0); however:
  Package python-imaging is not configured yet.
  Version of python-pil:armhf on system is 4.0.0-4.
  Package python-pillow is not installed.
  Version of python-pillow on system, provided by python-pil:armhf, is 
.
 weewx depends on python-usb (>= 0.4); however:
  Package python-usb is not configured yet.

dpkg: error processing package weewx (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python-configobj
 python-usb
 python-imaging
 python-cheetah
 weewx

-- 
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/90edf5bb-baa8-4f24-8a71-c9eb91adfc07%40googlegroups.com.

Re: [weewx-user] Re: Second crash after 11 days

[Steve Meltz]

Gary..yes..I believe you are correct, but there is something kind of
nagging at me, so I am going to do a controlled test (ie writing down what
I do) rather than trying to remember the steps I go through.

On Thu, Jul 18, 2019, 11:40 AM gjr80  wrote:

> Hi Steve,
>
> Haven’t we been round this buoy before? I thought you had previously
> disabled all things SteelSeries and it had more or less no effect on the
> problem. I thought the issue/leak had been nailed down to the driver(can’t
> link to a post on this device but on 6 Feb Tom said):
>
> Well, that's pretty definitive: the problem is in the driver, or its
> underlying libraries.
> Can you check what version of pyserial you are using:
> python -c "import serial; print serial.VERSION"
> I get "3.4"
>
> -tk
>
> Disabling all things SteelSeries will certainly save some memory (all
> extensions will use some) but I don’t see it having any great effect on
> your system, you are still going to run out of memory albeit a little while
> (minutes, hours, day) later.
>
> Gary
>
> --
> 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/VehicK_KNso/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/44c48951-8b76-40e8-aa90-cf814edcc82a%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAH0o-amMX5KOs5wv9Kmb6O72RyTNAQx4dUieANrKERSXQx_K2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Steve Meltz]

Peter..yes, Weewx is running when I backup.  I have it scheduled to run on
an odd minute once/day.  Archiving runs on the even minute.

-- 
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/CAH0o-akSQPUid1NVx97PUskKyS0puj%2BVhDZ3VXoWRdE96i9iPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Steve Meltz]

Thanks Gary...as usual, your fix was spot on!

Steve

On Mon, May 27, 2019 at 11:19 PM gjr80  wrote:

> Steve,
>
> When I look at your gauges just now they are not working, the clue is in
> the scroller message - 'error: Not Found'. This means the gauges.js
> script cannot find gauge-data.txt. I suppose it is possible that when we
> uncommented the SteelSeries skin a few days ago to get your plots back that
> caused your web server gauges.js to be overwritten with the default
> gauges.js (or a version that is not up to date with your latest setup).
> Though if this were the case/cause I would have expected the gauges to stop
> straight away and I remember seeing them working properly after your plots
> came back. No matter, this is clearly a case of gauges.js not finding
> gauge-data.txt. I can see that gauge-data.txt is being updated on your
> web server every few seconds so rtgd is doing its job. The file is located
> in photokinetics.org/Weather/. To fix it, on your WeeWX machine, edit
> skins/SteelSeries/scripts/gauges.js and find the realTimeUrlWeewx setting
> at about line 74, it probably looks like:
>
> realTimeUrlWeewx : 'gauge-data.txt', // *** WeeWX Users: 
> Change to your location of the gauge data file **
>
>
> Try changing the setting to '../gauge-data.txt'. Save the file and the
> restart WeeWX. The next report cycle should seethe modified gauges.js
> uploaded to your server and hopefully the gauges will come on line.
>
> Gary
>
> On Tuesday, 28 May 2019 10:25:26 UTC+10, Steve2Q wrote:
>>
>> Gary...I was away for the weekend, so when I checked in using the Chrome
>> browser on my phone, the Steel Gauges were, and still are, working.
>> However, if I pull up the guages on my desktop or tablet, they are frozen
>> and "offline".  Please take a look at photokinetics.org/Weather and
>> click on the Steel Gauges button at the bottom and see if you observe the
>> same behavior. I tried both Chrome and Firefox on both devices. Thanks.
>>
>>
>> --
> 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/VehicK_KNso/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/4b1de92a-fc25-4050-b692-d9dfb54033b2%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/4b1de92a-fc25-4050-b692-d9dfb54033b2%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAH0o-anu2iS_WCtstwhAq%2BUFDNBPWN1PyWDWH0s-eDxCc0VbQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Attempting to switch to non-root user for rsync

[Steve Chiz]

Looks like the forecast.sdb database is generated by the the [forecast] 
report, and has the same issue with non-root /var writing. I created a 
/home/weewx/db folder, much like I did with for the PID earlier with 
home/weewx/run to get past the first error, and edited the wseewx.config 
accordingly. As I had mentioned previously I was writing the archive to 
mariadb, and was unaware that the forecast has its own database. For others 
who might be stuck, find it here: " SQLITE_ROOT = /" in the [Database 
types].

Finally running as non-root! And at the bottom of the log I was happy to 
see that my rsync worked straight away.

May  8 15:16:33 WeeWx1 weewx[1402]: rsyncupload: rsync'd 258 files 
(1,190,946 bytes) in 2.39 seconds


On Wednesday, May 8, 2019 at 7:59:55 AM UTC-4, Steve Chiz wrote:
>
> Well that added some confusion, but sort of helped as I figured out what 
> you meant. I can't run Step#3, as I had removed the rc script based on the 
> systemd wiki page "its almost certainly a bad idea to have both the rc 
> script and a weeex.service file installed." 
>
> That did prompt me to edit the weewx.service file and move the location- 
> pidfile=home/weewx/run instead of var/run. As you noted, var/run would be 
> difficult for non-root writes. Makes perfect sense to move it out of there. 
> The systemd wiki page says 'make sure the paths match', but offers no info 
> as to what they should look like, if not the default.  Maybe home/weewx/run 
> should be the default.
>
> The wiki also says to make sure that there are permissions to the weewx 
> database, but I'm using mariadb and those credentials did not change. Now 
> however, I see that there are other databases involved- that are not 
> mentioned. The weewx user has no permissions to forecast.sdb, for example, 
> which I find no reference to in either wiki page. Again, the read only 
> error makes perfect sense and must come up every time someone tries to move 
> from the root user, but I found no mention of it. Are there other internal 
> databases that weewx creates/uses that I need to be aware of? The error log 
> also reflects issues with items in usr/share/weewx/user and lack of write 
> access. 
>
> Am I the only one who has tried to hammer this out with such difficulty? 
> I'm no noob, but I'm feeling pretty ignorant after struggling with this for 
> so long. 
>
> On Tuesday, May 7, 2019 at 8:35:05 PM UTC-4, Thomas Keffer wrote:
>>
>> Rather than put the PID file in /var/run (which could have permission 
>> problems), put it somewhere else where your user has write permissions. See 
>> steps #3 and #4 in *Run as a non-root user 
>> <https://github.com/weewx/weewx/wiki/Run-as-a-non-root-user>*. In that 
>> example, /home/weewx/run is used as a writable directory for user 'weewx'.
>>
>> -tk
>>
>> On Tue, May 7, 2019 at 5:25 PM Steve Chiz  wrote:
>>
>>> I've tried a dozen things since then, all to no avail. I found an old 
>>> post from Tom regarding commenting out the username lines to run as root 
>>> again, and that is what I did to get the weewx.service to start. 
>>>
>>> Running the chown returned a file not found, so I assume one or more 
>>> hard reboots (shutdown -r) deleted that file. I removed the commenting on 
>>> the user name and this is the result. Oh, for a troubleshooting guide...
>>>
>>> I did not make any database owner changes as I use mariadb.
>>>
>>> May  7 20:18:47 WeeWx1 weewx[773]: engine: Locale is 'en_GB.UTF-8'
>>> May  7 20:18:47 WeeWx1 weewx[773]: engine: pid file is /var/run/weewx.pid
>>> May  7 20:18:47 WeeWx1 weewxd[773]: Traceback (most recent call last):
>>> May  7 20:18:47 WeeWx1 weewxd[773]:   File "/usr/bin/weewxd", line 64, 
>>> in 
>>> May  7 20:18:47 WeeWx1 weewxd[773]: weewx.engine.main(options, args)
>>> May  7 20:18:47 WeeWx1 weewxd[773]:   File 
>>> "/usr/share/weewx/weewx/engine.py", line 841, in main
>>> May  7 20:18:47 WeeWx1 weewxd[773]: 
>>> daemon.daemonize(pidfile=options.pidfile)
>>> May  7 20:18:47 WeeWx1 weewxd[773]:   File "/usr/share/weewx/daemon.py", 
>>> line 77, in daemonize
>>> May  7 20:18:47 WeeWx1 weewxd[773]: if pidfile: 
>>> file(pidfile,'w+').write("%s\n" % pid)
>>> May  7 20:18:47 WeeWx1 weewxd[773]: IOError: [Errno 13] Permission 
>>> denied: '/var/run/weewx.pid'
>>>
>>> I am changing permissions back to root/ftp and calling it a day. Thanks 
>>> for your help.
>>>
>>> On Tuesday, May 7, 2019 at 6:46:51 PM UTC-4, Leon Shaner wrote:
>>>>
>>>> Ste

Re: [weewx-user] Attempting to switch to non-root user for rsync

[Steve Chiz]

Well that added some confusion, but sort of helped as I figured out what 
you meant. I can't run Step#3, as I had removed the rc script based on the 
systemd wiki page "its almost certainly a bad idea to have both the rc 
script and a weeex.service file installed." 

That did prompt me to edit the weewx.service file and move the location- 
pidfile=home/weewx/run instead of var/run. As you noted, var/run would be 
difficult for non-root writes. Makes perfect sense to move it out of there. 
The systemd wiki page says 'make sure the paths match', but offers no info 
as to what they should look like, if not the default.  Maybe home/weewx/run 
should be the default.

The wiki also says to make sure that there are permissions to the weewx 
database, but I'm using mariadb and those credentials did not change. Now 
however, I see that there are other databases involved- that are not 
mentioned. The weewx user has no permissions to forecast.sdb, for example, 
which I find no reference to in either wiki page. Again, the read only 
error makes perfect sense and must come up every time someone tries to move 
from the root user, but I found no mention of it. Are there other internal 
databases that weewx creates/uses that I need to be aware of? The error log 
also reflects issues with items in usr/share/weewx/user and lack of write 
access. 

Am I the only one who has tried to hammer this out with such difficulty? 
I'm no noob, but I'm feeling pretty ignorant after struggling with this for 
so long. 

On Tuesday, May 7, 2019 at 8:35:05 PM UTC-4, Thomas Keffer wrote:
>
> Rather than put the PID file in /var/run (which could have permission 
> problems), put it somewhere else where your user has write permissions. See 
> steps #3 and #4 in *Run as a non-root user 
> <https://github.com/weewx/weewx/wiki/Run-as-a-non-root-user>*. In that 
> example, /home/weewx/run is used as a writable directory for user 'weewx'.
>
> -tk
>
> On Tue, May 7, 2019 at 5:25 PM Steve Chiz > 
> wrote:
>
>> I've tried a dozen things since then, all to no avail. I found an old 
>> post from Tom regarding commenting out the username lines to run as root 
>> again, and that is what I did to get the weewx.service to start. 
>>
>> Running the chown returned a file not found, so I assume one or more hard 
>> reboots (shutdown -r) deleted that file. I removed the commenting on the 
>> user name and this is the result. Oh, for a troubleshooting guide...
>>
>> I did not make any database owner changes as I use mariadb.
>>
>> May  7 20:18:47 WeeWx1 weewx[773]: engine: Locale is 'en_GB.UTF-8'
>> May  7 20:18:47 WeeWx1 weewx[773]: engine: pid file is /var/run/weewx.pid
>> May  7 20:18:47 WeeWx1 weewxd[773]: Traceback (most recent call last):
>> May  7 20:18:47 WeeWx1 weewxd[773]:   File "/usr/bin/weewxd", line 64, in 
>> 
>> May  7 20:18:47 WeeWx1 weewxd[773]: weewx.engine.main(options, args)
>> May  7 20:18:47 WeeWx1 weewxd[773]:   File 
>> "/usr/share/weewx/weewx/engine.py", line 841, in main
>> May  7 20:18:47 WeeWx1 weewxd[773]: 
>> daemon.daemonize(pidfile=options.pidfile)
>> May  7 20:18:47 WeeWx1 weewxd[773]:   File "/usr/share/weewx/daemon.py", 
>> line 77, in daemonize
>> May  7 20:18:47 WeeWx1 weewxd[773]: if pidfile: 
>> file(pidfile,'w+').write("%s\n" % pid)
>> May  7 20:18:47 WeeWx1 weewxd[773]: IOError: [Errno 13] Permission 
>> denied: '/var/run/weewx.pid'
>>
>> I am changing permissions back to root/ftp and calling it a day. Thanks 
>> for your help.
>>
>> On Tuesday, May 7, 2019 at 6:46:51 PM UTC-4, Leon Shaner wrote:
>>>
>>> Steve,
>>>
>>> Probably a leftover.
>>> I expect this should do it:
>>>
>>> $ sudo chown weewx /var/run/weewx.pid
>>>
>>> I would expect that file to be deleted on host reboot, except of course 
>>> it is pronounced reboot, but spelled:
>>>
>>> $ sudo shutdown -r now
>>>
>>> If you use actual "reboot" then it skips shutdown scripts, so it's a big 
>>> no-no.
>>>
>>> What about the other files, did you change their owner, too, such as for 
>>> the DB?
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On May 7, 2019, at 5:42 PM, Steve Chiz  wrote:
>>>
>>> Guess I spoke too soon. After a reboot, weewx won't start. IOError: 
>>> [Errno 13] Permission denied: '/var/run/weewx.pid'
>>>
>>> On Tuesday, May 7, 2019 at 4:37:44 PM UTC-4, Steve Chiz wrote:
>>>>
>>>> Basically, it was my lack of unders

Re: [weewx-user] Attempting to switch to non-root user for rsync

[Steve Chiz]

I've tried a dozen things since then, all to no avail. I found an old post 
from Tom regarding commenting out the username lines to run as root again, 
and that is what I did to get the weewx.service to start. 

Running the chown returned a file not found, so I assume one or more hard 
reboots (shutdown -r) deleted that file. I removed the commenting on the 
user name and this is the result. Oh, for a troubleshooting guide...

I did not make any database owner changes as I use mariadb.

May  7 20:18:47 WeeWx1 weewx[773]: engine: Locale is 'en_GB.UTF-8'
May  7 20:18:47 WeeWx1 weewx[773]: engine: pid file is /var/run/weewx.pid
May  7 20:18:47 WeeWx1 weewxd[773]: Traceback (most recent call last):
May  7 20:18:47 WeeWx1 weewxd[773]:   File "/usr/bin/weewxd", line 64, in 

May  7 20:18:47 WeeWx1 weewxd[773]: weewx.engine.main(options, args)
May  7 20:18:47 WeeWx1 weewxd[773]:   File 
"/usr/share/weewx/weewx/engine.py", line 841, in main
May  7 20:18:47 WeeWx1 weewxd[773]: 
daemon.daemonize(pidfile=options.pidfile)
May  7 20:18:47 WeeWx1 weewxd[773]:   File "/usr/share/weewx/daemon.py", 
line 77, in daemonize
May  7 20:18:47 WeeWx1 weewxd[773]: if pidfile: 
file(pidfile,'w+').write("%s\n" % pid)
May  7 20:18:47 WeeWx1 weewxd[773]: IOError: [Errno 13] Permission denied: 
'/var/run/weewx.pid'

I am changing permissions back to root/ftp and calling it a day. Thanks for 
your help.

On Tuesday, May 7, 2019 at 6:46:51 PM UTC-4, Leon Shaner wrote:
>
> Steve,
>
> Probably a leftover.
> I expect this should do it:
>
> $ sudo chown weewx /var/run/weewx.pid
>
> I would expect that file to be deleted on host reboot, except of course it 
> is pronounced reboot, but spelled:
>
> $ sudo shutdown -r now
>
> If you use actual "reboot" then it skips shutdown scripts, so it's a big 
> no-no.
>
> What about the other files, did you change their owner, too, such as for 
> the DB?
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 7, 2019, at 5:42 PM, Steve Chiz > 
> wrote:
>
> Guess I spoke too soon. After a reboot, weewx won't start. IOError: [Errno 
> 13] Permission denied: '/var/run/weewx.pid'
>
> On Tuesday, May 7, 2019 at 4:37:44 PM UTC-4, Steve Chiz wrote:
>>
>> Basically, it was my lack of understanding on how the .rules files work. 
>> I appreciate the explanation of the granular permissions as it helped me 
>> understand the 'why'. I am not worried about others plugging USB devices 
>> into the pi, so I went ahead and edited the 99-usb.rules and added my newly 
>> created weewx user to the plugdev group. I am successfully running weewx as 
>> non-root, thanks again!  WeeWx still complains that my key verification 
>> fails, but I can directly ssh successfully to my remote host as the weewx 
>> user without a password, so I'm close. 
>>
>> Oh, and thanks for updating the wiki. I had run the "lsusb", I just 
>> wasn't entirely sure what to do with the output. The edit makes it more 
>> clear.
>>
>> On Tuesday, May 7, 2019 at 11:28:35 AM UTC-4, Leon Shaner wrote:
>>>
>>> Steve,
>>> Hope it works!  =D
>>>
>>> I just updated the wiki.  That section now reads:
>>>
>>> First find the idVendor and idProduct of your weatherstation with lsusb 
>>> command 
>>> then add a rules file in /etc/udev/rules.d/ with this content:
>>>
>>> SUBSYSTEM=="usb", ATTR{idVendor}=="your_value", 
>>> ATTR{idProduct}=="your_value", ACTION=="add", GROUP="weewx", MODE="0664"
>>>
>>> Name the udev rules file something descriptive, such as an abbreviation 
>>> of your weatherstation model or just weewx.rules, a la 
>>> /etc/udev/rules.d/weewx.rules (extension must be .rules and filename 
>>> should be simple, no spaces or special characters other than '-' and/or '_' 
>>> and should not contain more than one period '.').
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On May 7, 2019, at 10:39 AM, Leon Shaner  wrote:
>>>
>>> Steve,
>>>
>>> In my first reply, I failed to answer your first question.
>>>
>>> Yes, if you use the first form with idVendor, idProduct explicitly 
>>> filled in, you can call the UDEV rules file anything you like, as long as 
>>> the extension is .rules and you place it in the /etc/udev/rules.d directory.
>>>
>>> I used a more generic /etc/udev/rules.d/99-usb.rules in my example, 
>>> because my example is very generic, not tied

Re: [weewx-user] Attempting to switch to non-root user for rsync

[Steve Chiz]

Guess I spoke too soon. After a reboot, weewx won't start. IOError: [Errno 
13] Permission denied: '/var/run/weewx.pid'

On Tuesday, May 7, 2019 at 4:37:44 PM UTC-4, Steve Chiz wrote:
>
> Basically, it was my lack of understanding on how the .rules files work. I 
> appreciate the explanation of the granular permissions as it helped me 
> understand the 'why'. I am not worried about others plugging USB devices 
> into the pi, so I went ahead and edited the 99-usb.rules and added my newly 
> created weewx user to the plugdev group. I am successfully running weewx as 
> non-root, thanks again!  WeeWx still complains that my key verification 
> fails, but I can directly ssh successfully to my remote host as the weewx 
> user without a password, so I'm close. 
>
> Oh, and thanks for updating the wiki. I had run the "lsusb", I just wasn't 
> entirely sure what to do with the output. The edit makes it more clear.
>
> On Tuesday, May 7, 2019 at 11:28:35 AM UTC-4, Leon Shaner wrote:
>>
>> Steve,
>> Hope it works!  =D
>>
>> I just updated the wiki.  That section now reads:
>>
>> First find the idVendor and idProduct of your weatherstation with lsusb 
>> command 
>> then add a rules file in /etc/udev/rules.d/ with this content:
>>
>> SUBSYSTEM=="usb", ATTR{idVendor}=="your_value", 
>> ATTR{idProduct}=="your_value", ACTION=="add", GROUP="weewx", MODE="0664"
>>
>> Name the udev rules file something descriptive, such as an abbreviation 
>> of your weatherstation model or just weewx.rules, a la 
>> /etc/udev/rules.d/weewx.rules (extension must be .rules and filename 
>> should be simple, no spaces or special characters other than '-' and/or '_' 
>> and should not contain more than one period '.').
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 7, 2019, at 10:39 AM, Leon Shaner  wrote:
>>
>> Steve,
>>
>> In my first reply, I failed to answer your first question.
>>
>> Yes, if you use the first form with idVendor, idProduct explicitly filled 
>> in, you can call the UDEV rules file anything you like, as long as the 
>> extension is .rules and you place it in the /etc/udev/rules.d directory.
>>
>> I used a more generic /etc/udev/rules.d/99-usb.rules in my example, 
>> because my example is very generic, not tied to weewx, but would work for 
>> weewx provided weewx user is in the plugdev group.
>>
>> The (optional) number prefixes on the UDEV .rules files establish an 
>> order of precedence with later rules overriding earlier rules.  Really it's 
>> ordered lexicographically, so files that start with letters, such as 
>> weewx.rules will be evaluated after (take precedence over) the files that 
>> do start with numbers.
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On May 7, 2019, at 10:31 AM, Leon Shaner  wrote:
>>
>> Hey, Steve,
>>
>> That first wiki looks pretty complete.
>> Did you in fact try the "lsusb" command to get the values you need for 
>> the first form of the udev rules?
>> Using the first form with the idVendor and idProduct for your weather 
>> station is preferred.
>>
>> As an alternative, and if it's just you with physical access to the host 
>> and USB devices, e.g. you aren't too worried about other people connecting 
>> USB devices and accessing them as non-root, you can also just do this:
>>
>> File:  /etc/udev/rules.d/99-usb.rules
>> Contents:
>> SUBSYSTEM=="usb", GROUP="plugdev", MODE="0660"
>>
>> Then be sure to put the wxuser and any other users in the "plugdev" group 
>> in /etc/group, a la:
>>
>> plugdev:x:46:steve,pi,weewx
>>
>> (Or whatever usernames you care to be allowed to access USB ports).
>> (Your GID may differ from 46)...
>>
>> Notice that for perms, above, I put 0660.  I can't think why "others" / 
>> "nobody" should even need to read the USB ports.  Anybody that needs to 
>> read(or write) USB ports should be in the "plugdev" group.
>>
>> You could of course put GROUP="weewx" in my example above, but then any 
>> user would need to be in the weewx port to use any USB device, even those 
>> unrelated to weewx.  The "plugdev" group is commonly used for other USB 
>> devices, such as auto-mounting removable media, so that is why I chose it 
>> in my example.  If you used my example and put GROUP=&q

Re: [weewx-user] Attempting to switch to non-root user for rsync

[Steve Chiz]

Basically, it was my lack of understanding on how the .rules files work. I 
appreciate the explanation of the granular permissions as it helped me 
understand the 'why'. I am not worried about others plugging USB devices 
into the pi, so I went ahead and edited the 99-usb.rules and added my newly 
created weewx user to the plugdev group. I am successfully running weewx as 
non-root, thanks again!  WeeWx still complains that my key verification 
fails, but I can directly ssh successfully to my remote host as the weewx 
user without a password, so I'm close. 

Oh, and thanks for updating the wiki. I had run the "lsusb", I just wasn't 
entirely sure what to do with the output. The edit makes it more clear.

On Tuesday, May 7, 2019 at 11:28:35 AM UTC-4, Leon Shaner wrote:
>
> Steve,
> Hope it works!  =D
>
> I just updated the wiki.  That section now reads:
>
> First find the idVendor and idProduct of your weatherstation with lsusb 
> command 
> then add a rules file in /etc/udev/rules.d/ with this content:
>
> SUBSYSTEM=="usb", ATTR{idVendor}=="your_value", 
> ATTR{idProduct}=="your_value", ACTION=="add", GROUP="weewx", MODE="0664"
>
> Name the udev rules file something descriptive, such as an abbreviation of 
> your weatherstation model or just weewx.rules, a la 
> /etc/udev/rules.d/weewx.rules (extension must be .rules and filename 
> should be simple, no spaces or special characters other than '-' and/or '_' 
> and should not contain more than one period '.').
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 7, 2019, at 10:39 AM, Leon Shaner > 
> wrote:
>
> Steve,
>
> In my first reply, I failed to answer your first question.
>
> Yes, if you use the first form with idVendor, idProduct explicitly filled 
> in, you can call the UDEV rules file anything you like, as long as the 
> extension is .rules and you place it in the /etc/udev/rules.d directory.
>
> I used a more generic /etc/udev/rules.d/99-usb.rules in my example, 
> because my example is very generic, not tied to weewx, but would work for 
> weewx provided weewx user is in the plugdev group.
>
> The (optional) number prefixes on the UDEV .rules files establish an order 
> of precedence with later rules overriding earlier rules.  Really it's 
> ordered lexicographically, so files that start with letters, such as 
> weewx.rules will be evaluated after (take precedence over) the files that 
> do start with numbers.
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 7, 2019, at 10:31 AM, Leon Shaner > 
> wrote:
>
> Hey, Steve,
>
> That first wiki looks pretty complete.
> Did you in fact try the "lsusb" command to get the values you need for the 
> first form of the udev rules?
> Using the first form with the idVendor and idProduct for your weather 
> station is preferred.
>
> As an alternative, and if it's just you with physical access to the host 
> and USB devices, e.g. you aren't too worried about other people connecting 
> USB devices and accessing them as non-root, you can also just do this:
>
> File:  /etc/udev/rules.d/99-usb.rules
> Contents:
> SUBSYSTEM=="usb", GROUP="plugdev", MODE="0660"
>
> Then be sure to put the wxuser and any other users in the "plugdev" group 
> in /etc/group, a la:
>
> plugdev:x:46:steve,pi,weewx
>
> (Or whatever usernames you care to be allowed to access USB ports).
> (Your GID may differ from 46)...
>
> Notice that for perms, above, I put 0660.  I can't think why "others" / 
> "nobody" should even need to read the USB ports.  Anybody that needs to 
> read(or write) USB ports should be in the "plugdev" group.
>
> You could of course put GROUP="weewx" in my example above, but then any 
> user would need to be in the weewx port to use any USB device, even those 
> unrelated to weewx.  The "plugdev" group is commonly used for other USB 
> devices, such as auto-mounting removable media, so that is why I chose it 
> in my example.  If you used my example and put GROUP="weewx" it would 
> likely break auto-mounting of removable media (maybe you don't care; maybe 
> you don't use the usbmount service, etc.).
>
> Note that changes in /etc/group take a log out / log in to take effect.
> Check group membership via "id -a" ...
>
> Of course the explicit method, per the wiki, using the idVendor and 
> idProduct values for your specific USB device avoids any conflict, because 
> then assigning group weewx would only ever happen to that one device that 
> exactly matches the idVendor a

Re: [weewx-user] Attempting to switch to non-root user for rsync

[Steve Chiz]

Hi Leon,

Terrific explanation! Thanks very much, and I'll give it a try.   

On Tuesday, May 7, 2019 at 10:39:56 AM UTC-4, Leon Shaner wrote:
>
> Steve,
>
> In my first reply, I failed to answer your first question.
>
> Yes, if you use the first form with idVendor, idProduct explicitly filled 
> in, you can call the UDEV rules file anything you like, as long as the 
> extension is .rules and you place it in the /etc/udev/rules.d directory.
>
> I used a more generic /etc/udev/rules.d/99-usb.rules in my example, 
> because my example is very generic, not tied to weewx, but would work for 
> weewx provided weewx user is in the plugdev group.
>
> The (optional) number prefixes on the UDEV .rules files establish an order 
> of precedence with later rules overriding earlier rules.  Really it's 
> ordered lexicographically, so files that start with letters, such as 
> weewx.rules will be evaluated after (take precedence over) the files that 
> do start with numbers.
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 7, 2019, at 10:31 AM, Leon Shaner > 
> wrote:
>
> Hey, Steve,
>
> That first wiki looks pretty complete.
> Did you in fact try the "lsusb" command to get the values you need for the 
> first form of the udev rules?
> Using the first form with the idVendor and idProduct for your weather 
> station is preferred.
>
> As an alternative, and if it's just you with physical access to the host 
> and USB devices, e.g. you aren't too worried about other people connecting 
> USB devices and accessing them as non-root, you can also just do this:
>
> File:  /etc/udev/rules.d/99-usb.rules
> Contents:
> SUBSYSTEM=="usb", GROUP="plugdev", MODE="0660"
>
> Then be sure to put the wxuser and any other users in the "plugdev" group 
> in /etc/group, a la:
>
> plugdev:x:46:steve,pi,weewx
>
> (Or whatever usernames you care to be allowed to access USB ports).
> (Your GID may differ from 46)...
>
> Notice that for perms, above, I put 0660.  I can't think why "others" / 
> "nobody" should even need to read the USB ports.  Anybody that needs to 
> read(or write) USB ports should be in the "plugdev" group.
>
> You could of course put GROUP="weewx" in my example above, but then any 
> user would need to be in the weewx port to use any USB device, even those 
> unrelated to weewx.  The "plugdev" group is commonly used for other USB 
> devices, such as auto-mounting removable media, so that is why I chose it 
> in my example.  If you used my example and put GROUP="weewx" it would 
> likely break auto-mounting of removable media (maybe you don't care; maybe 
> you don't use the usbmount service, etc.).
>
> Note that changes in /etc/group take a log out / log in to take effect.
> Check group membership via "id -a" ...
>
> Of course the explicit method, per the wiki, using the idVendor and 
> idProduct values for your specific USB device avoids any conflict, because 
> then assigning group weewx would only ever happen to that one device that 
> exactly matches the idVendor and idProduct values from "lsusb" output.
>
> Hope that helps!  =D
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 7, 2019, at 9:37 AM, Steve Chiz > 
> wrote:
>
> I've been trying to use the wiki to resolve this on my own, but can't seem 
> to sort it out. This page suggests I create a rules file, but no indication 
> on what that file should be named...  weewx.rules?  
> https://github.com/weewx/weewx/wiki/systemd 
>
> I hunted up an older page 
> https://github.com/weewx/weewx/wiki/Run-as-a-non-root-user that cites an 
> example for Vantage (name the file vpro.rules) but what about other 
> devices? In any event, the contents of the rules file is different than the 
> more recently edited page. Which should I use? 
>
> SUBSYSTEM=="usb", ATTR{idVendor}=="your_value", 
> ATTR{idProduct}=="your_value", ACTION=="add", GROUP="weewx", MODE="0664"
>  or 
> SUBSYSTEM=="usb", ATTRS{interface}=="CP2102 USB to UART Bridge Controller", 
> MODE: = "664", GROUP = "wxuser"
>
> I get that one page is about systemd specifically, which I am using, but both 
> address the need to run weewx as a non-root user. If someone could point me 
> to some documentation on how to switch from running weewx as root to a 
> non-root user, that would be great! I probably should have set it up that way 
> initially, regardless of rsync, as running as root always seems like a risky 
> ide