[weewx-user] Weewx 4.6.0b7 Wiind Vector plot

2021-11-12 Thread Mks Mk 
New Pi 4 running bullseye with weewx 4.6.0b7

the generated webpage plots does not display Wind Vector, the file 
"daywindvec.png" is there in "/var/www/html/weewx" folder
when looking into "index.html" with editor, I see no link to the file 
"daywindvec.png"

any suggestion to bring back the Wind Vector plot?

-- 
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/edbe83e2-83de-4c29-af47-585ce7ac0e00n%40googlegroups.com.

[weewx-user] Re: Difficulty installing on Debian

2021-11-12 Thread choc...@gmail.com 
Well, this is interesting.

On a lark, I tried running your command after sudo su -.  Viola, no error 
message.  Also,  I got the list you indicated above.

I then exited from sudo su and proceeded with the regular weewx 
installation instructions.  

All is right in the World!

Thank you very much, Vince.

On Friday, November 12, 2021 at 6:28:51 PM UTC-8 choc...@gmail.com wrote:

> I re-flashed and tried your suggestion.
>
> Here is the result:
> -bash: /etc/apt/trusted.gpg.d/weewx.gpg: Permission denied
>
>
>
> On Thursday, November 11, 2021 at 3:38:22 PM UTC-8 vince wrote:
>
>> update - if you haven't reflashed your system yet and it's still hosed 
>> up, can you try one thing for me ?
>>
>> wget -qO - https://weewx.com/keys.html | sudo gpg --dearmor > 
>> /etc/apt/trusted.gpg.d/weewx.gpg
>>
>> Then if you run 'sudo apt-key list' it should show:
>>
>> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d 
>> instead (see apt-key(8)).
>> /etc/apt/trusted.gpg
>> 
>> pub   rsa2048 2012-04-01 [SC]
>>   A0DA 38D0 D76E 8B5D 6388  7281 9165 938D 90FD DD2E
>> uid   [ unknown] Mike Thompson (Raspberry Pi Debian armhf 
>> ARMv6+VFP) 
>> sub   rsa2048 2012-04-01 [E]
>>
>> pub   rsa2048 2012-06-17 [SC]
>>   CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
>> uid   [ unknown] Raspberry Pi Archive Signing Key
>> sub   rsa2048 2012-06-17 [E]
>>
>> /etc/apt/trusted.gpg.d/weewx.gpg
>> 
>> pub   rsa2048 2014-11-15 [SC]
>>   EAC2 0711 8C0B D050 B835  9313 A0CB 255B 75BF 977C
>> uid   [ unknown] Thomas Keffer (Author of weewx) <
>> tke...@gmail.com>
>> sub   rsa2048 2014-11-15 [E]
>>
>> pub   dsa1024 2014-01-28 [SC]
>>   1E9F F20B 86EF 78AB 3B45  4944 ED44 4FCC F0E2 B09E
>> uid   [ unknown] Matthew Wall (weewx) <
>> mw...@users.sourceforge.net>
>> sub   elg1024 2014-01-28 [E]
>>
>> On Thursday, November 11, 2021 at 3:24:23 PM UTC-8 choc...@gmail.com 
>> wrote:
>>
>>> I will re-flash the image and try again.
>>>
>>> Thank you Vince.
>>>
>>> On Thursday, November 11, 2021 at 3:16:09 PM UTC-8 vince wrote:
>>>
 FWIW - I just tried another newly reflashed SD card and the commands 
 worked fine this time.   The only difference I can think of is perhaps 
 there's some kind of timing issue under the hood.   This time I did the 
 first command manually, then the second command manually.

 When I did them by cutting+pasting the two lines at once, that's when I 
 saw oddities occasionally.

 No explanation.

 On Thursday, November 11, 2021 at 3:03:34 PM UTC-8 vince wrote:

> You can force it with the --allow-unauthenticated flag if needed
>
> https://askubuntu.com/questions/732985/force-update-from-unsigned-repository
>
> There does seem to be some difference in debian11 re: apt-key (which 
> now shows as deprecated) but I didn't get too far trying to work it.
>
> "sudo apt-key list" should show you which keys you have imported 
> currently.  You should have two keys there, one from Matthew and one from 
> Tom, in addition to your normal os repo keys
>
> On Thursday, November 11, 2021 at 2:48:25 PM UTC-8 choc...@gmail.com 
> wrote:
>
>> Thank you for the reply.
>>
>> Same result.
>>
>> Here is an an additional error that I did not notice before:
>> The repository 'http://weewx.com/apt/python3 buster InRelease' is 
>> not signed.
>>
>>
>>
>>
>> On Thursday, November 11, 2021 at 2:28:07 PM UTC-8 vince wrote:
>>
>>> No, just try adding the key one more time than run apt-get update 
>>> again.
>>>
>>> Same thing happened to me this morning setting up a new pi.
>>>
>>> On Thursday, November 11, 2021 at 1:29:33 PM UTC-8 choc...@gmail.com 
>>> wrote:
>>>
 On a fresh installation of Raspbian Bullseye (11.1)

 Following the instructions at https://weewx.com/docs/debian.htm

 wget -qO - https://weewx.com/keys.html | sudo apt-key add -
 wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
 /etc/apt/sources.list.d/weewx.list

 sudo apt-get update yields the following:
 The following signatures couldn't be verified because the public 
 key is not available: NO_PUBKEY [long string of alphanumeric 
 characters]

 As a, probable, result 
 sudo apt-get install yields the following:
 Unable to locate package weewx

 What am I doing incorrectly?
 Should I revert to Buster?





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

[weewx-user] Re: Difficulty installing on Debian

2021-11-12 Thread choc...@gmail.com 
I re-flashed and tried your suggestion.

Here is the result:
-bash: /etc/apt/trusted.gpg.d/weewx.gpg: Permission denied



On Thursday, November 11, 2021 at 3:38:22 PM UTC-8 vince wrote:

> update - if you haven't reflashed your system yet and it's still hosed up, 
> can you try one thing for me ?
>
> wget -qO - https://weewx.com/keys.html | sudo gpg --dearmor > 
> /etc/apt/trusted.gpg.d/weewx.gpg
>
> Then if you run 'sudo apt-key list' it should show:
>
> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d 
> instead (see apt-key(8)).
> /etc/apt/trusted.gpg
> 
> pub   rsa2048 2012-04-01 [SC]
>   A0DA 38D0 D76E 8B5D 6388  7281 9165 938D 90FD DD2E
> uid   [ unknown] Mike Thompson (Raspberry Pi Debian armhf 
> ARMv6+VFP) 
> sub   rsa2048 2012-04-01 [E]
>
> pub   rsa2048 2012-06-17 [SC]
>   CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
> uid   [ unknown] Raspberry Pi Archive Signing Key
> sub   rsa2048 2012-06-17 [E]
>
> /etc/apt/trusted.gpg.d/weewx.gpg
> 
> pub   rsa2048 2014-11-15 [SC]
>   EAC2 0711 8C0B D050 B835  9313 A0CB 255B 75BF 977C
> uid   [ unknown] Thomas Keffer (Author of weewx)  >
> sub   rsa2048 2014-11-15 [E]
>
> pub   dsa1024 2014-01-28 [SC]
>   1E9F F20B 86EF 78AB 3B45  4944 ED44 4FCC F0E2 B09E
> uid   [ unknown] Matthew Wall (weewx)  >
> sub   elg1024 2014-01-28 [E]
>
> On Thursday, November 11, 2021 at 3:24:23 PM UTC-8 choc...@gmail.com 
> wrote:
>
>> I will re-flash the image and try again.
>>
>> Thank you Vince.
>>
>> On Thursday, November 11, 2021 at 3:16:09 PM UTC-8 vince wrote:
>>
>>> FWIW - I just tried another newly reflashed SD card and the commands 
>>> worked fine this time.   The only difference I can think of is perhaps 
>>> there's some kind of timing issue under the hood.   This time I did the 
>>> first command manually, then the second command manually.
>>>
>>> When I did them by cutting+pasting the two lines at once, that's when I 
>>> saw oddities occasionally.
>>>
>>> No explanation.
>>>
>>> On Thursday, November 11, 2021 at 3:03:34 PM UTC-8 vince wrote:
>>>
 You can force it with the --allow-unauthenticated flag if needed

 https://askubuntu.com/questions/732985/force-update-from-unsigned-repository

 There does seem to be some difference in debian11 re: apt-key (which 
 now shows as deprecated) but I didn't get too far trying to work it.

 "sudo apt-key list" should show you which keys you have imported 
 currently.  You should have two keys there, one from Matthew and one from 
 Tom, in addition to your normal os repo keys

 On Thursday, November 11, 2021 at 2:48:25 PM UTC-8 choc...@gmail.com 
 wrote:

> Thank you for the reply.
>
> Same result.
>
> Here is an an additional error that I did not notice before:
> The repository 'http://weewx.com/apt/python3 buster InRelease' is not 
> signed.
>
>
>
>
> On Thursday, November 11, 2021 at 2:28:07 PM UTC-8 vince wrote:
>
>> No, just try adding the key one more time than run apt-get update 
>> again.
>>
>> Same thing happened to me this morning setting up a new pi.
>>
>> On Thursday, November 11, 2021 at 1:29:33 PM UTC-8 choc...@gmail.com 
>> wrote:
>>
>>> On a fresh installation of Raspbian Bullseye (11.1)
>>>
>>> Following the instructions at https://weewx.com/docs/debian.htm
>>>
>>> wget -qO - https://weewx.com/keys.html | sudo apt-key add -
>>> wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
>>> /etc/apt/sources.list.d/weewx.list
>>>
>>> sudo apt-get update yields the following:
>>> The following signatures couldn't be verified because the public key 
>>> is not available: NO_PUBKEY [long string of alphanumeric characters]
>>>
>>> As a, probable, result 
>>> sudo apt-get install yields the following:
>>> Unable to locate package weewx
>>>
>>> What am I doing incorrectly?
>>> Should I revert to Buster?
>>>
>>>
>>>
>>>

-- 
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/d1f47c46-556b-42d4-93ae-ea984bfb3e14n%40googlegroups.com.

Re: [weewx-user] Re: Problem with the Wiki

2021-11-12 Thread gjr80 
Perhaps it is (was) a GitHub transient issue. When I checked just now all 
wiki home page links I tried came up just fine, this included a mix of 
short form links, full GitHub wiki URLs and external URLs as well as the 
ones Vince cited.

Gary

On Saturday, 13 November 2021 at 07:07:10 UTC+10 vince wrote:

> Looks like anything using a magical link without specifying a path is 
> doing this.  If you check the first 'posting to weewx-user' link which 
> works fine you'll see that one specifies a full path to the file rather 
> than relying on github's wiki functionality to figure it all out.
>
> This one works (absolute URL path):
>
> * [Posting to weewx-user](
> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user)
>
> This one doesn't (no full path specified)
>
> * [Frequently-asked questions (FAQ)](WeeWX-Frequently-Asked-Questions)
>
> So it can be fixed via putting the full path in there for all such links, 
> but it shouldn't ideally be necessary...
>
> On Friday, November 12, 2021 at 12:34:29 PM UTC-8 nevilled...@gmail.com 
> wrote:
>
>> Seen this for some time, been hopping it would correct. 
>> Link to my hardware page (i2C sensors) keeps going to the home page, I 
>> use the the drop down to get to the pages.
>> Not all hardware links have this problem but some do.
>>
>> Neville
>>
>> On Friday, November 12, 2021 at 11:09:31 AM UTC+10 tke...@gmail.com 
>> wrote:
>>
>>> It seems to be adding an extra 'wiki' to the URL. For example, instead of
>>>
>>> https://github.com/weewx/weewx/wiki/extensions
>>>
>>> it sends you to
>>>
>>> https://github.com/weewx/weewx/wiki/wiki/extensions
>>>
>>> On Thu, Nov 11, 2021 at 12:14 PM gjr80  wrote:
>>>
 Yes, I noticed last night the the ‘Troubleshooting Davis stations’ page 
 was behaving similarly. I did check the main page source and it appeared 
 fine, when I re-entered the link and saved the main page the link worked. 
 Though when I checked this morning the link is not working again and the 
 home page indicates it was last updated seven days ago. Sounds like a 
 GitHub issue, will look into it later today.

 In the meantime you can get to the pages you want by looking under the 
 dropdown on the top right side of the home page that lists all available 
 pages, not the easiest way to navigate but the links appear to still work.

 Gary

 On Friday, 12 November 2021 at 06:01:22 UTC+10 jonatha...@gmail.com 
 wrote:

> When I click on an entry in the wiki (URL: 
> https://github.com/weewx/weewx/wiki/) 
>  instead of getting the page 
> clicked for, I get the home Wiki page.
> For example
>
>- Open https://github.com/weewx/weewx/wiki/
>- Click on What you should know about paths 
>
>- Page produced is  https://github.com/weewx/weewx/wiki/
>- Page expected is 
>https://github.com/weewx/weewx/wiki/wiki/Understanding-paths
>
>
> When I type in by hand the expected page (
> https://github.com/weewx/weewx/wiki/wiki/Understanding-paths), 
>  the 
> expected page opens.
>
> -- 
>
> Sincerely Jonathan Ryshpan 
>
>   Those who have put out the eyes of the people
>   reproach them for their blindness. -- Milton
>
> -- 
 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/9ec40bf2-3393-4f97-a349-75a8daa491dbn%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/bd9f3aff-252b-4ed8-be50-157b1f0e8b98n%40googlegroups.com.

Re: [weewx-user] Re: Problem with the Wiki

2021-11-12 Thread vince 
Looks like anything using a magical link without specifying a path is doing 
this.  If you check the first 'posting to weewx-user' link which works fine 
you'll see that one specifies a full path to the file rather than relying 
on github's wiki functionality to figure it all out.

This one works (absolute URL path):

* [Posting to 
weewx-user](https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user)

This one doesn't (no full path specified)

* [Frequently-asked questions (FAQ)](WeeWX-Frequently-Asked-Questions)

So it can be fixed via putting the full path in there for all such links, 
but it shouldn't ideally be necessary...

On Friday, November 12, 2021 at 12:34:29 PM UTC-8 nevilled...@gmail.com 
wrote:

> Seen this for some time, been hopping it would correct. 
> Link to my hardware page (i2C sensors) keeps going to the home page, I use 
> the the drop down to get to the pages.
> Not all hardware links have this problem but some do.
>
> Neville
>
> On Friday, November 12, 2021 at 11:09:31 AM UTC+10 tke...@gmail.com wrote:
>
>> It seems to be adding an extra 'wiki' to the URL. For example, instead of
>>
>> https://github.com/weewx/weewx/wiki/extensions
>>
>> it sends you to
>>
>> https://github.com/weewx/weewx/wiki/wiki/extensions
>>
>> On Thu, Nov 11, 2021 at 12:14 PM gjr80  wrote:
>>
>>> Yes, I noticed last night the the ‘Troubleshooting Davis stations’ page 
>>> was behaving similarly. I did check the main page source and it appeared 
>>> fine, when I re-entered the link and saved the main page the link worked. 
>>> Though when I checked this morning the link is not working again and the 
>>> home page indicates it was last updated seven days ago. Sounds like a 
>>> GitHub issue, will look into it later today.
>>>
>>> In the meantime you can get to the pages you want by looking under the 
>>> dropdown on the top right side of the home page that lists all available 
>>> pages, not the easiest way to navigate but the links appear to still work.
>>>
>>> Gary
>>>
>>> On Friday, 12 November 2021 at 06:01:22 UTC+10 jonatha...@gmail.com 
>>> wrote:
>>>
 When I click on an entry in the wiki (URL: 
 https://github.com/weewx/weewx/wiki/) 
  instead of getting the page 
 clicked for, I get the home Wiki page.
 For example

- Open https://github.com/weewx/weewx/wiki/
- Click on What you should know about paths 

- Page produced is  https://github.com/weewx/weewx/wiki/
- Page expected is 
https://github.com/weewx/weewx/wiki/wiki/Understanding-paths


 When I type in by hand the expected page (
 https://github.com/weewx/weewx/wiki/wiki/Understanding-paths), 
  the 
 expected page opens.

 -- 

 Sincerely Jonathan Ryshpan 

Those who have put out the eyes of the people
reproach them for their blindness. -- Milton

 -- 
>>> 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/9ec40bf2-3393-4f97-a349-75a8daa491dbn%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/03f551e1-7c87-4fb7-8757-e08f09b4f00en%40googlegroups.com.

Re: [weewx-user] Re: Problem with the Wiki

2021-11-12 Thread Neville Davis 
Seen this for some time, been hopping it would correct. 
Link to my hardware page (i2C sensors) keeps going to the home page, I use 
the the drop down to get to the pages.
Not all hardware links have this problem but some do.

Neville

On Friday, November 12, 2021 at 11:09:31 AM UTC+10 tke...@gmail.com wrote:

> It seems to be adding an extra 'wiki' to the URL. For example, instead of
>
> https://github.com/weewx/weewx/wiki/extensions
>
> it sends you to
>
> https://github.com/weewx/weewx/wiki/wiki/extensions
>
> On Thu, Nov 11, 2021 at 12:14 PM gjr80  wrote:
>
>> Yes, I noticed last night the the ‘Troubleshooting Davis stations’ page 
>> was behaving similarly. I did check the main page source and it appeared 
>> fine, when I re-entered the link and saved the main page the link worked. 
>> Though when I checked this morning the link is not working again and the 
>> home page indicates it was last updated seven days ago. Sounds like a 
>> GitHub issue, will look into it later today.
>>
>> In the meantime you can get to the pages you want by looking under the 
>> dropdown on the top right side of the home page that lists all available 
>> pages, not the easiest way to navigate but the links appear to still work.
>>
>> Gary
>>
>> On Friday, 12 November 2021 at 06:01:22 UTC+10 jonatha...@gmail.com 
>> wrote:
>>
>>> When I click on an entry in the wiki (URL: 
>>> https://github.com/weewx/weewx/wiki/) 
>>>  instead of getting the page 
>>> clicked for, I get the home Wiki page.
>>> For example
>>>
>>>- Open https://github.com/weewx/weewx/wiki/
>>>- Click on What you should know about paths 
>>>
>>>- Page produced is  https://github.com/weewx/weewx/wiki/
>>>- Page expected is 
>>>https://github.com/weewx/weewx/wiki/wiki/Understanding-paths
>>>
>>>
>>> When I type in by hand the expected page (
>>> https://github.com/weewx/weewx/wiki/wiki/Understanding-paths), 
>>>  the 
>>> expected page opens.
>>>
>>> -- 
>>>
>>> Sincerely Jonathan Ryshpan 
>>>
>>> Those who have put out the eyes of the people
>>> reproach them for their blindness. -- Milton
>>>
>>> -- 
>> 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/9ec40bf2-3393-4f97-a349-75a8daa491dbn%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/8e2456fd-ecbb-4bc6-9a6f-5311a1391769n%40googlegroups.com.

[weewx-user] Re: problem with ftp anc post http error 403

2021-11-12 Thread gjr80 
Bit of a punt but do you have the è (e grave - lowercase e with grave 
accent) character anywhere in the Ftp skin.conf or the [StdReport] [[FTP]] 
stanza in weewx.conf or in the name/path of any of the files being ftp’d? 
That will likely be the source of the utf-8 error.

Gary

On Friday, 12 November 2021 at 07:08:53 UTC+10 scarz...@gmail.com wrote:

> Nov 11 22:03:10 raspberrypi weewx[5059] DEBUG user.sdr: lines=[]
> Nov 11 22:03:10 raspberrypi weewx[5059] INFO weewx.cheetahgenerator: 
> Generated 3 files for report ClientrawReport in 41.49 seconds
> Nov 11 22:03:10 raspberrypi weewx[5059] DEBUG weewx.reportengine: Running 
> report 'FTP'
> Nov 11 22:03:10 raspberrypi weewx[5059] DEBUG weewx.reportengine: Found 
> configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
> Nov 11 22:03:10 raspberrypi weewx[5059] DEBUG weeutil.ftpupload: 
> Attempting connection to ftp.sassarimeteo.altervista.org
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 'weewx.reportengine.FtpGenerator'
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    'utf-8' codec can't decode byte 0xe8 in position 104: invalid 
> continuation byte
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    Traceback (most recent call last):
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/home/weewx/bin/weewx/reportengine.py", line 196, in run
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    obj.start()
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/home/weewx/bin/weewx/reportengine.py", line 281, in start
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    self.run()
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/home/weewx/bin/weewx/reportengine.py", line 331, in run
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    n = ftp_data.run()
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/home/weewx/bin/weeutil/ftpupload.py", line 133, in run
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    ftp_server.connect(self.server, self.port)
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/usr/lib/python3.9/ftplib.py", line 160, in connect
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    self.welcome = self.getresp()
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/usr/lib/python3.9/ftplib.py", line 242, in getresp
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    resp = self.getmultiline()
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/usr/lib/python3.9/ftplib.py", line 228, in getmultiline
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    line = self.getline()
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/usr/lib/python3.9/ftplib.py", line 210, in getline
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    line = self.file.readline(self.maxline + 1)
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>  File "/usr/lib/python3.9/codecs.py", line 322, in decode
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    (result, consumed) = self._buffer_decode(data, self.errors, 
> final)
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe8 in position 
> 104: invalid continuation byte
> Nov 11 22:03:11 raspberrypi weewx[5059] ERROR weewx.reportengine:
>    Generator terminated
> Nov 11 22:03:11 raspberrypi weewx[5059] DEBUG weewx.reportengine: Report 
> 'RSYNC' not enabled. Skipping.
> Nov 11 22:03:13 raspberrypi weewx[5059] DEBUG user.sdr: lines=[]
> Nov 11 22:03:16 raspberrypi weewx[5059] DEBUG user.sdr: lines=[]
> ^C
> pi@raspberrypi:/home/weewx/public_html $ sudo tail -f /var/log/syslog
> Nov 11 22:04:09 raspberrypi weewx[5059] DEBUG user.sdr: lines=[]
> Nov 11 22:04:13 raspberrypi weewx[5059] DEBUG user.sdr: lines=['{"time" : 
> "2021-11-11 21:04:09", "model" : "Fineoffset-WHx080", "subtype" : 0, "id" : 
> 12, "battery_ok" : 1, "temperature_C" : 12.700, "humidity" : 97, 
> "wind_dir_deg" : 315, "wind_avg_km_h" : 0.000, "wind_max_km_h" : 0.000, 
> "rain_mm" : 3.600, "mic" : "CRC"}\n', '{"time" : "2021-11-11 21:04:09", 
> "model" : "Fineoffset-WHx080", "subtype" : 0, "id" : 12, "battery_ok" : 1, 
> "temperature_C" : 12.700, "humidity" : 97, "wind_dir_deg" : 315, 
> "wind_avg_km_h" : 0.000,

[weewx-user] Re: Generating same images over and over

2021-11-12 Thread gjr80 
I don’t know. It’s possible both loggers have corrupt station memory. It’s 
not as unlikely as you may think, corrupt station memory is frequently 
caused by power supply interruptions. If you are not reading archive 
records from the logger you would never know you have the problem; the 
console still works fine and any software that uses loop packets from the 
console will also work fine. WeeWX is one of the few PWS applications that 
use hardware archive records from the Davis logger/console and since the 
vantage driver default is to use hardware records WeeWX at times suffers 
the consequences of corrupt station memory.

One thing is certain; there is an issue with your logger. If the second 
console/logger is doing the same it has an issue too.

Gary

On Thursday, 11 November 2021 at 23:27:10 UTC+10 jens...@gmail.com wrote:

> No, different loggers as well
>
> torsdag den 11. november 2021 kl. 14.00.14 UTC+1 skrev gjr80:
>
>> Did you use the same logger in the different consoles? The memory is in 
>> the logger.
>>
>> Gary
>>
>> On Thursday, 11 November 2021 at 22:00:29 UTC+10 jens...@gmail.com wrote:
>>
>>> But then I don't get what the underlying problem is. Two diffrent 
>>> consoles, same problem?
>>>
>>> torsdag den 11. november 2021 kl. 12.13.09 UTC+1 skrev gjr80:
>>>
 Setting record_generation to hardware does not cure the corrupt station 
 memory, rather it mitigates the symptoms. The underlying problem is still 
 there, though it will now largely have no day to day effect on WeeWX 
 operation. However, you should be aware that while the corrupt station 
 memory remains you will no longer have the ability to backfill missing 
 archive records from your station should WeeWX go offline for some reason.

 Gary

 On Thursday, 11 November 2021 at 20:32:36 UTC+10 jens...@gmail.com 
 wrote:

>
> wee_device --clear-memory:
> ...
> raise weewx.WeeWxIOError("Unable to read hardware type")
> weewx.WeeWxIOError: Unable to read hardware type
>
> I don't understand why this happens. I even tried to use another 
> console, same problem.
>
> Then, as sugested option, I used:
>
> [StdArchive]
> ...
> record_generation = software
>
> - and this worked, thanks.
>
> torsdag den 11. november 2021 kl. 10.04.18 UTC+1 skrev gjr80:
>
>> No errors but what is missing is WeeWX is not obtaining any archive 
>> records from you console. You have all the symptoms of corrupt station 
>> memory. I suggest you refer to the Troubleshooting the Davis Vantage 
>> station 
>> 
>>  
>> wiki page and work through the steps in the Corrupt station memory 
>> 
>>  section.
>>
>> Gary
>> On Thursday, 11 November 2021 at 18:35:01 UTC+10 jens...@gmail.com 
>> wrote:
>>
>>> Debug = 1
>>> Apparently no errors?
>>> torsdag den 11. november 2021 kl. 07.47.56 UTC+1 skrev gjr80:
>>>
 Thanks but that log extract is not much use at all. We need to see 
 a log extract showing the WeeWX startup and processing at least a 
 couple of 
 report cycles. I suggest you go to the link in my first post next work 
 through the steps under ‘To get a good, useful log’ and post the 
 resulting 
 log.

 Gary
 On Thursday, 11 November 2021 at 16:04:44 UTC+10 jens...@gmail.com 
 wrote:

> Nov 11 07:00:17 jjk-F5RL weewx[10103]: cheetahgenerator: Generated 
> 3 files for report StandardReport in 0.07 seconds
> Nov 11 07:00:18 jjk-F5RL weewx[10103]: imagegenerator: Generated 
> 24 images for StandardReport in 1.69 seconds
> Nov 11 07:00:18 jjk-F5RL weewx[10103]: copygenerator: copied 14 
> files to /home/weewx/public_html
> Nov 11 07:00:20 jjk-F5RL weewx[10103]: ftpgenerator: ftp'd 41 
> files in 2.05 seconds
>
> Tried to stop and start weewx, delete all files from public_html - 
> no change.
>
> torsdag den 11. november 2021 kl. 06.33.16 UTC+1 skrev gjr80:
>
>> I suggest we start with the log 
>> , 
>> you don’t need an error in the log to diagnose a problem
>>
>> Gary
>>
>> On Thursday, 11 November 2021 at 15:19:03 UTC+10 
>> jens...@gmail.com wrote:
>>
>>> Suddenly, 11 days ago, weewx keeps generating same images over 
>>> and over. No error in syslog, wee_device says: weewx.WakeupError: 
>>> Unable to 
>>> wake up Vantage console.
>>> I tried to unplug the console, no change, even switched to 
>>>