Re: [weewx-user] Error Uploading to WOW

[Tim Urberg]

I do believe I have the configuration right: 

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = true
station = f7fb9445-dd06-e911-9462-0003ff598847
# To guard against parsing errors, put your password in quotes:
password = XX


On Thursday, November 11, 2021 at 4:55:12 PM UTC-6 Glenn McKechnie wrote:

> Then again (cleans glasses) if I could read properly - mine is the pre
> 2016 variant and yours is the newer version.
>
> So. As you were.
>
> On 12/11/2021, Glenn McKechnie  wrote:
> > On 11/11/2021, Tim Urberg  wrote:
> >> Hello everyone, I'm having trouble uploading to WOW. I created an
> >> account
> >> got my username and created a password, but this keeps happening:
> >
> > The above suggests that you created the account recently, but the help
> > page suggests the siteid format you are using is pre 2016?
> > ( That's according to the section "Automatic Weather Stations" at
> > https://wow.metoffice.gov.uk/support/dataformats#automatic )
> >
> > Are you using the correct Site ID for your site?
> >
> > In my case it's a short string ( 941176001 ) , which is also in the
> > public address ...
> > https://bom-wow.metoffice.gov.uk/weather/view?siteID=941176001
> >
> > [[WOW]]
> > [...]
> > station = 941176001
> > [...]
> > --
> >
> >
> > Cheers
> > Glenn
> >
> > rorpi - read only raspberry pi & various weewx addons
> > https://github.com/glennmckechnie
> >
>
>
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

-- 
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/84f70005-f77f-4ace-b5ec-0226915c513cn%40googlegroups.com.

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

[Tom Keffer]

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+unsubscr...@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/CAPq0zEDokxdGm54ZfgqknwdsizoF5MDgarecQJi6%2Br4zYk1cdQ%40mail.gmail.com.

[weewx-user] Re: Difficulty installing on Debian

[vince]

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/7fb806c8-8705-4761-ac0e-90054f080c71n%40googlegroups.com.

[weewx-user] Re: Difficulty installing on Debian

[vince]

You shouldn't need to reflash - just force it (for now)

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/541add94-5c77-4b9b-9317-5f5902472c80n%40googlegroups.com.

[weewx-user] Re: Difficulty installing on Debian

[choc...@gmail.com]

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/5575398d-7c61-450d-b91c-ce7994c7de6fn%40googlegroups.com.

[weewx-user] Re: Difficulty installing on Debian

[vince]

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/4e10f124-b861-431b-a395-a3d4ad440ffen%40googlegroups.com.

[weewx-user] Re: Difficulty installing on Debian

[vince]

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/788f20d8-3d3b-4f72-8253-3ae11d2a65a4n%40googlegroups.com.

Re: [weewx-user] Error Uploading to WOW

[Glenn McKechnie]

Then again (cleans glasses) if I could read properly - mine is the pre
2016 variant and yours is the newer version.

So. As you were.

On 12/11/2021, Glenn McKechnie  wrote:
> On 11/11/2021, Tim Urberg  wrote:
>> Hello everyone, I'm having trouble uploading to WOW.  I created an
>> account
>> got my username and created a password, but this keeps happening:
>
> The above suggests that you created the account recently, but the help
> page suggests the siteid format you are using is pre 2016?
> ( That's according to the section "Automatic Weather Stations"  at
> https://wow.metoffice.gov.uk/support/dataformats#automatic  )
>
> Are you using the correct Site ID for your site?
>
> In my case it's a short string ( 941176001 ) , which is also in the
> public address ...
> https://bom-wow.metoffice.gov.uk/weather/view?siteID=941176001
>
> [[WOW]]
> [...]
>station = 941176001
> [...]
> --
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
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/CAAraAzgNatOMVVXExPYdb-%2BETu4h__93QYWdVSZ0W-sdhKpjxw%40mail.gmail.com.

[weewx-user] Re: Difficulty installing on Debian

[choc...@gmail.com]

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/3371d685-ba6f-4db9-89b6-e65eb2f47670n%40googlegroups.com.

Re: [weewx-user] Error Uploading to WOW

[Glenn McKechnie]

On 11/11/2021, Tim Urberg  wrote:
> Hello everyone, I'm having trouble uploading to WOW.  I created an account
> got my username and created a password, but this keeps happening:

The above suggests that you created the account recently, but the help
page suggests the siteid format you are using is pre 2016?
( That's according to the section "Automatic Weather Stations"  at
https://wow.metoffice.gov.uk/support/dataformats#automatic  )

Are you using the correct Site ID for your site?

In my case it's a short string ( 941176001 ) , which is also in the
public address ...
https://bom-wow.metoffice.gov.uk/weather/view?siteID=941176001

[[WOW]]
[...]
   station = 941176001
[...]
-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

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

[weewx-user] Re: Difficulty installing on Debian

[vince]

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/46092c25-c645-441b-bfd1-f04d137d6ef7n%40googlegroups.com.

[weewx-user] Re: Error Uploading to WOW

[Tim Urberg]

Here's 3 attempts at uploading.

Nov 11 15:10:17 weewx weewx[87598] DEBUG weewx.restx: WOW: url: 
https://wow.metoffice.gov.uk/automaticreading?action=updateraw=f7fb9445-dd06-e911-9462-0003ff598847=XXX=weewx-4.5.1=2021-11-11+21%3A10%3A00=29.457=38.7=75=8=225=17=248=31.5=0.00=0.510
Nov 11 15:10:20 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 1: HTTP Error 400: Bad Request
Nov 11 15:10:25 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 2: HTTP Error 400: Bad Request
Nov 11 15:10:31 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 3: HTTP Error 400: Bad Request
Nov 11 15:10:31 weewx weewx[87598] ERROR weewx.restx: WOW: Failed to 
publish record 2021-11-11 15:10:00 CST (1636665000): Failed upload after 3 
tries
Nov 11 15:15:17 weewx weewx[87598] DEBUG weewx.restx: WOW: url: 
https://wow.metoffice.gov.uk/automaticreading?action=updateraw=f7fb9445-dd06-e911-9462-0003ff598847=XXX=weewx-4.5.1=2021-11-11+21%3A15%3A00=29.461=38.5=75=8=225=16=248=31.3=0.00=0.510
Nov 11 15:15:17 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 1: HTTP Error 400: Bad Request
Nov 11 15:15:24 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 2: HTTP Error 400: Bad Request
Nov 11 15:15:29 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 3: HTTP Error 400: Bad Request
Nov 11 15:15:29 weewx weewx[87598] ERROR weewx.restx: WOW: Failed to 
publish record 2021-11-11 15:15:00 CST (1636665300): Failed upload after 3 
tries
Nov 11 15:20:17 weewx weewx[87598] DEBUG weewx.restx: WOW: url: 
https://wow.metoffice.gov.uk/automaticreading?action=updateraw=f7fb9445-dd06-e911-9462-0003ff598847=XXX=weewx-4.5.1=2021-11-11+21%3A20%3A00=29.463=38.4=75=8=202=21=225=31.2=0.00=0.510
Nov 11 15:20:26 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 1: HTTP Error 400: Bad Request
Nov 11 15:20:37 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 2: HTTP Error 400: Bad Request
ov 11 15:20:47 weewx weewx[87598] DEBUG weewx.restx: WOW: Failed upload 
attempt 3: HTTP Error 400: Bad Request
Nov 11 15:20:47 weewx weewx[87598] ERROR weewx.restx: WOW: Failed to 
publish record 2021-11-11 15:20:00 CST (1636665600): Failed upload after 3 
tries


On Thursday, November 11, 2021 at 3:33:06 PM UTC-6 Tim Urberg wrote:

> Here's the rest of the startup log: 
>
> Nov 11 15:06:43 weewx weewx[87583]:  * Starting weewx weather system weewx
> Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Initializing weewx 
> version 4.5.1
> Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Using Python 3.8.10 
> (default, Sep 28 2021, 16:10:42) #012[GCC 9.3.0]
> Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Platform 
> Linux-5.4.0-1045-raspi-aarch64-with-glibc2.29
> Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Locale is 'C.UTF-8'
> Nov 11 15:06:43 weewx weewx[87595] INFO __main__: PID file is 
> /var/run/weewx.pid
> Nov 11 15:06:43 weewx weewx[87598] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Nov 11 15:06:43 weewx weewx[87598] INFO __main__: Debug is 2
> Nov 11 15:06:43 weewx weewx[87598] DEBUG __main__: Initializing engine
> Nov 11 15:06:43 weewx weewx[87598] INFO weewx.engine: Loading station type 
> Vantage (weewx.drivers.vantage)
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Driver 
> version is 3.2.2
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Option 
> loop_request=1
> Nov 11 15:06:43 weewx weewx[87583]:...done.
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Opened up 
> serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Gentle 
> wake up of console successful
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Hardware 
> type is 16
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: ISS ID is 1
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Hardware 
> name: Vantage Pro2
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
> weewx.engine.StdTimeSynch
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
> weewx.engine.StdConvert
> Nov 11 15:06:43 weewx weewx[87598] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdConvert
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
> weewx.engine.StdCalibrate
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdCalibrate
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
> weewx.engine.StdQC
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdQC
> Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading 

[weewx-user] Re: Error Uploading to WOW

[Tim Urberg]

Here's the rest of the startup log: 

Nov 11 15:06:43 weewx weewx[87583]:  * Starting weewx weather system weewx
Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Initializing weewx 
version 4.5.1
Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Using Python 3.8.10 
(default, Sep 28 2021, 16:10:42) #012[GCC 9.3.0]
Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Platform 
Linux-5.4.0-1045-raspi-aarch64-with-glibc2.29
Nov 11 15:06:43 weewx weewx[87595] INFO __main__: Locale is 'C.UTF-8'
Nov 11 15:06:43 weewx weewx[87595] INFO __main__: PID file is 
/var/run/weewx.pid
Nov 11 15:06:43 weewx weewx[87598] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Nov 11 15:06:43 weewx weewx[87598] INFO __main__: Debug is 2
Nov 11 15:06:43 weewx weewx[87598] DEBUG __main__: Initializing engine
Nov 11 15:06:43 weewx weewx[87598] INFO weewx.engine: Loading station type 
Vantage (weewx.drivers.vantage)
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Driver 
version is 3.2.2
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Nov 11 15:06:43 weewx weewx[87583]:...done.
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Opened up 
serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Hardware 
type is 16
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: ISS ID is 1
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.drivers.vantage: Hardware 
name: Vantage Pro2
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Nov 11 15:06:43 weewx weewx[87598] INFO weewx.engine: StdConvert target 
unit is 0x1
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.wxservices: Calculations for 
LOOP packets: {'pressure': 'prefer_hardware', 'barometer': 
'prefer_hardware', 'altimeter': 'prefer_hardware', 'windchill': 
'prefer_hardware', 'heatindex': 'prefer_hardware', 'dewpoint': 
'prefer_hardware', 'inDewpoint': 'prefer_hardware', 'rainRate': 
'prefer_hardware', 'cloudbase': 'prefer_hardware', 'maxSolarRad': 
'prefer_hardware', 'humidex': 'prefer_hardware', 'appTemp': 
'prefer_hardware', 'ET': 'prefer_hardware', 'windrun': 'prefer_hardware', 
'windDir': 'software', 'windGustDir': 'software'}
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.wxservices: Calculations for 
archive records: {'pressure': 'prefer_hardware', 'barometer': 
'prefer_hardware', 'altimeter': 'prefer_hardware', 'windchill': 
'prefer_hardware', 'heatindex': 'prefer_hardware', 'dewpoint': 
'prefer_hardware', 'inDewpoint': 'prefer_hardware', 'rainRate': 
'prefer_hardware', 'cloudbase': 'prefer_hardware', 'maxSolarRad': 
'prefer_hardware', 'humidex': 'prefer_hardware', 'appTemp': 
'prefer_hardware', 'ET': 'prefer_hardware', 'windrun': 'prefer_hardware', 
'windDir': 'software', 'windGustDir': 'software'}
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.manager: Daily summary 
version is 4.0
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdDelta
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdDelta
Nov 11 15:06:43 weewx weewx[87598] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Nov 11 15:06:43 weewx weewx[87598] INFO weewx.engine: Archive will use data 
binding 

[weewx-user] Difficulty installing on Debian

[choc...@gmail.com]

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/69439e13-776e-4531-87f6-3fcb34d90429n%40googlegroups.com.

[weewx-user] Re: Error Uploading to WOW

[Tim Urberg]

https://wow.metoffice.gov.uk/automaticreading?action=updateraw=f7fb9445-dd06-e911-9462-0003ff598847=XXX=weewx-4.5.1=2021-11-11+21%3A10%3A00=29.457=38.7=75=8=225=17=248=31.5=0.00=0.510

Here's the URL:

On Wednesday, November 10, 2021 at 9:20:48 PM UTC-6 gjr80 wrote:

> Hi,
>
> Edit weewx.conf and set debug = 2. Save weewx.conf and restart WeeWX. You 
> should now see the full URL used to upload to any of the restful services 
> in the log. If you want any further help post a log extract from when you 
> restarted WeeWX through until a couple of report cycles have completed. 
> It’s import to capture the full WeeWX startup as well as the report cycles.
>
> Gary
> On Thursday, 11 November 2021 at 11:13:45 UTC+10 tim.u...@gmail.com wrote:
>
>> Hello everyone, I'm having trouble uploading to WOW.  I created an 
>> account got my username and created a password, but this keeps happening: 
>>
>> Nov 10 19:10:18 weewx weewx[3837] DEBUG weewx.restx: WOW: Failed upload 
>> attempt 1: HTTP Error 400: Bad Request
>> Nov 10 19:10:24 weewx weewx[3837] DEBUG weewx.restx: WOW: Failed upload 
>> attempt 2: HTTP Error 400: Bad Request
>> Nov 10 19:10:30 weewx weewx[3837] DEBUG weewx.restx: WOW: Failed upload 
>> attempt 3: HTTP Error 400: Bad Request
>> Nov 10 19:10:30 weewx weewx[3837] ERROR weewx.restx: WOW: Failed to 
>> publish record 2021-11-10 19:10:00 CST (1636593000): Failed upload after 3 
>> tries
>>
>> Not sure what would be causing a bad request, is there anyway to log the 
>> full response?
>>
>> Thanks!
>> Tim
>>
>

-- 
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/10dbcfce-5154-4830-ac2a-14665b59644dn%40googlegroups.com.

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

[Massimiliano Scarzella]

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, "wind_max_km_h" : 0.000, "rain_mm" : 3.600, "mic" 
: "CRC"}\n']
Nov 11 22:04:13 raspberrypi weewx[5059] DEBUG user.sdr: packet={'windGust': 
0.0, 'outBatteryStatus': 0, 'rain_total': 0.36, 'windSpeed': 0.0, 
'windDir': 315.0, 'outHumidity': 97.0, 'outTemp': 12.7, 'dateTime': 
1636664649, 'usUnits': 16}
Nov 11 22:04:13 raspberrypi weewx[5059] DEBUG user.sdr: packet={'windGust': 
0.0, 'outBatteryStatus': 0, 'rain_total': 0.36, 'windSpeed': 0.0, 
'windDir': 315.0, 'outHumidity': 97.0, 'outTemp': 12.7, 

Re: [weewx-user] WeeWx database differs from system log

[gjr80]

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

>
>
> Which did you intend? 5 or 30 minutes.
>
> I intend every 5 minutes, and am considering every minute.  Any advice?
>
> Yes, if you go down to a minute make sure you monitor your logs to ensure 
you are not overloading WeeWX. If your report cycle is taking longer than a 
minute to complete at best you will have some report cycles being skipped 
(will be noted in the log), at worst strange things may start happening.

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/e4ba598e-c503-4edb-bd59-050d67ff50bfn%40googlegroups.com.

[weewx-user] Re: Problem with the Wiki

[gjr80]

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+unsubscr...@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.

Re: [weewx-user] WeeWx database differs from system log

[Jonathan Ryshpan]

On Wed, 2021-11-10 at 12:23 -0800, Tom Keffer wrote:
> The times in the log are a month later than the times you are showing
> from the database. I'll bet if you looked later in the database, you
> would see that the records are arriving every 30 minutes.
You are correct; the database shows records arriving every 30 minutes.

> 
> Which did you intend? 5 or 30 minutes.
I intend every 5 minutes, and am considering every minute.  Any advice?

Thanks for your help.

-- 
Sincerely Jonathan Ryshpan 

 "Never try to teach a pig to sing.
 It wastes time and annoys the pig."

-- 
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/f19de3436d9b2a29e6576411a28d5a6d86ef3859.camel%40pacbell.net.

[weewx-user] Problem with the Wiki

[Jonathan Ryshpan]

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c1e336f98c1fa55b35a7cb04983e36c68c2694b1.camel%40pacbell.net.

[weewx-user] Re: No updates after upgrade to Bullseye

[vince]

Yes, you kinda have to install the required packages when you add things or 
use a different type of db.   You might want to write down your additional 
steps someplace for the next time you flatten the system since you're not 
running the no-extensions sqlite3 default setup.

The '*which log to look into*' question depends on what kind of message is 
being logged and what severity the message has.

My /etc/rsyslog.conf file has the following content:

*.*;auth,authpriv.none -/var/log/syslog
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages

So everything (*.* meaning all syslog 'facilities' and all severities) goes 
into /var/log/syslog, but only certain things go into /var/log/messages.

(tl;dr answer - just go with what they give you from the os and don't worry 
it)

It's possible to set up rsyslog to put weewx-specific things in its own 
file (it's in the wiki someplace) but I never do that.  I just grep for 
weewx in /var/log/syslog.

On Thursday, November 11, 2021 at 11:24:04 AM UTC-8 dan...@gmail.com wrote:

> > You didn't mention 'which' system log, but on a pi you generally want to 
> look in /var/log/syslog and not /var/log/messages
>
> Well, it seems some messages are going to messages, and others to 
> syslog--no, that isn't confusing at all.  "systemctl status weewx" showed 
> that the MySQL connector package wasn't installed ("apt install 
> python3-mysqldb").  Another restart and status check showed it was also 
> missing paho-mqtt ("apt install python3-paho-mqtt").  And with that, it's 
> now working.  Thanks for the push in the right direction.
>
> On Thursday, November 11, 2021 at 12:27:13 PM UTC-5 vince wrote:
>
>>
>> Restart it via 'systemctl start weewx' and then do a 'systemctl status 
>> weewx' and see what it thinks.   IYou might also try "journalctl -xe" to 
>> see what systemd thinks is going on.
>>
>> Try running it interactively:
>> python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf
>> (hit control-C to exit that)
>>
>> FWIW - I just installed weewx using that apt-get method on a bullseye pi 
>> and it runs fine for me here.
>>
>> [... editorial comment follows...]
>>
>> You didn't mention 'which' system log, but on a pi you generally want to 
>> look in /var/log/syslog and not /var/log/messages
>>
>> Lots of things are possible including your .zip files having old 
>> extensions that don't support python3.  You didn't mention 'which' 
>> extensions and versions of those.
>>
>> On Thursday, November 11, 2021 at 8:50:33 AM UTC-8 dan...@gmail.com 
>> wrote:
>>
>>> I've had WeeWx running happily along on a Raspberry Pi 3B for some 
>>> time.  Then I decided to upgrade that system to Bullseye.  And, well, I 
>>> apparently broke it.
>>>
>>> I first tried an in-place upgrade, rebooted, and it wasn't sending 
>>> updates--the last line in the log file indicated that it would send updates 
>>> to WeatherCloud, but then nothing was happening.  So, figuring that the OS 
>>> upgrade had gone south, I decided to reinstall from scratch.
>>>
>>> I downloaded weewx.conf from the Raspberry Pi, along with the .zip files 
>>> for the extensions I'd installed.  Then put a fresh image of RaspberryPiOS 
>>> onto the card, copied over those saved files, installed WeeWx, used 
>>> wee_extension to install the extensions, copied weewx.conf into 
>>> /etc/weewx/, and restarted weewx.  But sadly, no dice.  Here's what I get 
>>> in the system log when it tries to start:
>>>
>>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Initializing weewx 
>>> version 4.5.1
>>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Using Python 3.9.2 
>>> (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Platform 
>>> Linux-5.10.63-v7+-armv7l-with-glibc2.31
>>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Locale is 'en_US.UTF-8'
>>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Using configuration 
>>> file /etc/weewx/weewx.conf
>>> Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Debug is 1
>>> Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: Loading station 
>>> type Vantage (weewx.drivers.vantage)
>>> Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: StdConvert target 
>>> unit is 0x1
>>>
>>> As you see, debug is enabled, but that's the last entry as of almost 15 
>>> minutes ago.  Where should I be looking to sort this out?
>>>
>>>

-- 
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/025a9051-cd95-4cae-a609-4a8a038004dfn%40googlegroups.com.

[weewx-user] Re: No updates after upgrade to Bullseye

[dan...@gmail.com]

> You didn't mention 'which' system log, but on a pi you generally want to 
look in /var/log/syslog and not /var/log/messages

Well, it seems some messages are going to messages, and others to 
syslog--no, that isn't confusing at all.  "systemctl status weewx" showed 
that the MySQL connector package wasn't installed ("apt install 
python3-mysqldb").  Another restart and status check showed it was also 
missing paho-mqtt ("apt install python3-paho-mqtt").  And with that, it's 
now working.  Thanks for the push in the right direction.

On Thursday, November 11, 2021 at 12:27:13 PM UTC-5 vince wrote:

>
> Restart it via 'systemctl start weewx' and then do a 'systemctl status 
> weewx' and see what it thinks.   IYou might also try "journalctl -xe" to 
> see what systemd thinks is going on.
>
> Try running it interactively:
> python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf
> (hit control-C to exit that)
>
> FWIW - I just installed weewx using that apt-get method on a bullseye pi 
> and it runs fine for me here.
>
> [... editorial comment follows...]
>
> You didn't mention 'which' system log, but on a pi you generally want to 
> look in /var/log/syslog and not /var/log/messages
>
> Lots of things are possible including your .zip files having old 
> extensions that don't support python3.  You didn't mention 'which' 
> extensions and versions of those.
>
> On Thursday, November 11, 2021 at 8:50:33 AM UTC-8 dan...@gmail.com wrote:
>
>> I've had WeeWx running happily along on a Raspberry Pi 3B for some time.  
>> Then I decided to upgrade that system to Bullseye.  And, well, I apparently 
>> broke it.
>>
>> I first tried an in-place upgrade, rebooted, and it wasn't sending 
>> updates--the last line in the log file indicated that it would send updates 
>> to WeatherCloud, but then nothing was happening.  So, figuring that the OS 
>> upgrade had gone south, I decided to reinstall from scratch.
>>
>> I downloaded weewx.conf from the Raspberry Pi, along with the .zip files 
>> for the extensions I'd installed.  Then put a fresh image of RaspberryPiOS 
>> onto the card, copied over those saved files, installed WeeWx, used 
>> wee_extension to install the extensions, copied weewx.conf into 
>> /etc/weewx/, and restarted weewx.  But sadly, no dice.  Here's what I get 
>> in the system log when it tries to start:
>>
>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Initializing weewx 
>> version 4.5.1
>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Using Python 3.9.2 
>> (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Platform 
>> Linux-5.10.63-v7+-armv7l-with-glibc2.31
>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Locale is 'en_US.UTF-8'
>> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Using configuration file 
>> /etc/weewx/weewx.conf
>> Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Debug is 1
>> Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: Loading station type 
>> Vantage (weewx.drivers.vantage)
>> Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: StdConvert target 
>> unit is 0x1
>>
>> As you see, debug is enabled, but that's the last entry as of almost 15 
>> minutes ago.  Where should I be looking to sort this out?
>>
>>

-- 
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/2ff9aaff-7adf-49d9-b08d-80a06fbdf1f4n%40googlegroups.com.

[weewx-user] Re: No updates after upgrade to Bullseye

[vince]

Restart it via 'systemctl start weewx' and then do a 'systemctl status weewx' 
and see what it thinks.   IYou might also try "journalctl -xe" to see what 
systemd thinks is going on.

Try running it interactively:
python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf
(hit control-C to exit that)

FWIW - I just installed weewx using that apt-get method on a bullseye pi 
and it runs fine for me here.

[... editorial comment follows...]

You didn't mention 'which' system log, but on a pi you generally want to 
look in /var/log/syslog and not /var/log/messages

Lots of things are possible including your .zip files having old extensions 
that don't support python3.  You didn't mention 'which' extensions and 
versions of those.

On Thursday, November 11, 2021 at 8:50:33 AM UTC-8 dan...@gmail.com wrote:

> I've had WeeWx running happily along on a Raspberry Pi 3B for some time.  
> Then I decided to upgrade that system to Bullseye.  And, well, I apparently 
> broke it.
>
> I first tried an in-place upgrade, rebooted, and it wasn't sending 
> updates--the last line in the log file indicated that it would send updates 
> to WeatherCloud, but then nothing was happening.  So, figuring that the OS 
> upgrade had gone south, I decided to reinstall from scratch.
>
> I downloaded weewx.conf from the Raspberry Pi, along with the .zip files 
> for the extensions I'd installed.  Then put a fresh image of RaspberryPiOS 
> onto the card, copied over those saved files, installed WeeWx, used 
> wee_extension to install the extensions, copied weewx.conf into 
> /etc/weewx/, and restarted weewx.  But sadly, no dice.  Here's what I get 
> in the system log when it tries to start:
>
> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Initializing weewx 
> version 4.5.1
> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Using Python 3.9.2 
> (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Platform 
> Linux-5.10.63-v7+-armv7l-with-glibc2.31
> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Locale is 'en_US.UTF-8'
> Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: PID file is 
> /var/run/weewx.pid
> Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Debug is 1
> Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: Loading station type 
> Vantage (weewx.drivers.vantage)
> Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: StdConvert target 
> unit is 0x1
>
> As you see, debug is enabled, but that's the last entry as of almost 15 
> minutes ago.  Where should I be looking to sort this out?
>
>

-- 
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/cbbe3e21-547b-4b68-ad49-16105264029cn%40googlegroups.com.

[weewx-user] No updates after upgrade to Bullseye

[dan...@gmail.com]

I've had WeeWx running happily along on a Raspberry Pi 3B for some time.  
Then I decided to upgrade that system to Bullseye.  And, well, I apparently 
broke it.

I first tried an in-place upgrade, rebooted, and it wasn't sending 
updates--the last line in the log file indicated that it would send updates 
to WeatherCloud, but then nothing was happening.  So, figuring that the OS 
upgrade had gone south, I decided to reinstall from scratch.

I downloaded weewx.conf from the Raspberry Pi, along with the .zip files 
for the extensions I'd installed.  Then put a fresh image of RaspberryPiOS 
onto the card, copied over those saved files, installed WeeWx, used 
wee_extension to install the extensions, copied weewx.conf into 
/etc/weewx/, and restarted weewx.  But sadly, no dice.  Here's what I get 
in the system log when it tries to start:

Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Initializing weewx version 
4.5.1
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Using Python 3.9.2 
(default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Platform 
Linux-5.10.63-v7+-armv7l-with-glibc2.31
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: Locale is 'en_US.UTF-8'
Nov 11 11:36:56 wxbox weewx[3405] INFO __main__: PID file is 
/var/run/weewx.pid
Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Nov 11 11:36:57 wxbox weewx[3408] INFO __main__: Debug is 1
Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: Loading station type 
Vantage (weewx.drivers.vantage)
Nov 11 11:36:57 wxbox weewx[3408] INFO weewx.engine: StdConvert target unit 
is 0x1

As you see, debug is enabled, but that's the last entry as of almost 15 
minutes ago.  Where should I be looking to sort this out?

-- 
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/f18a94ca-0c7f-46ee-98cc-fa92f93cd5aen%40googlegroups.com.

Re: [weewx-user] Wind Missing from Database

[William Reinhardt]

That did it! I found I'm running the v4.0 schema, and the [[wx_binding] 
section of weewx.conf matches the new schema configuration. After doing a 
drop-daily and rebuild-daily, and waiting for the next archive intervals, 
it all came back.
Thanks very much for your assistance!

On Thursday, November 11, 2021 at 9:20:04 AM UTC-5 William Reinhardt wrote:

> Thanks for the info! I'll be sure the schema matches above. It's very 
> likely I'm trying to mix schemas. Will let you know what happens.
>
> On Wednesday, November 10, 2021 at 7:07:02 PM UTC-5 tke...@gmail.com 
> wrote:
>
>> How a database schema is specified changed in V4.0. The newer 
>> wview_extended schema uses the new way, the older wview schema uses the old 
>> way. My hunch is that you're mixing the new way and the old way. 
>>
>> Take a look in the [[wx_binding]] section of weewx.conf. You want either:
>>
>> # Old way, using wview schema
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.wxmanager.WXDaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview.schema
>>
>>
>> # New way, using wview_extended schema
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.manager.DaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview_extended.schema
>>
>> If you're using the older wview schema, make sure the manager is set to 
>> weewx.wxmanager.WXDaySummaryManager. Then, use wee_database to drop, then 
>> rebuild the daily summaries.
>>
>> -tk
>>
>>
>>
>>
>> On Wed, Nov 10, 2021 at 3:45 PM William Reinhardt  
>> wrote:
>>
>>> Hello all,
>>>
>>> Back in July, I successfully added a couple new observation types 
>>> ("appTemp" and "cloudbase") to my SQLite database by following these 
>>> instructions:
>>>
>>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>>
>>> Inexplicably, the "archive_day_wind" table was missing afterwards! The 
>>> other wind-related tables ("archive_day_windDir", "archive_day_windGust," 
>>> etc.) are still in the database, just the "wind" table is missing. I'll 
>>> post the Debug errors from the syslog at the end of this post. Let me know 
>>> if you need more. It also shows up on my weather station website at 
>>> www.woodvilleweather.com. In the "Weather Records Snapshot" section, 
>>> the Average and Highest Wind data show as $day.wind.avg, 
>>> $month.wind.avg, etc., with similar errors since July 2021 in the Reports 
>>> page. I verified the absence of the table using a SQLite database viewer to 
>>> open old database backups from before and after I added the observations in 
>>> July.
>>>
>>> My question is: how can I regain the wind table? Is there a wee_database 
>>> command to add this table? Add a new observation type and call it "wind"? 
>>> Copy-paste from a backup database and rebuild the daily data? My weather 
>>> station stores no data so I can't get it from there. It's been a busy 
>>> summer and I'm now just getting time to play with this and get my WEEWX box 
>>> working 100% again. Thanks for any ideas.
>>>
>>> -Bill
>>>
>>> *Debug info:*
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.max
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.maxtime
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.gustdir
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.avg
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.vecdir
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.vecavg
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $day.wind.rms
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $week.wind.max
>>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>>> Unrecognized: $week.wind.maxtime
>>> Nov 10 18:30:30 WX_WS1 

Re: [weewx-user] Wind Missing from Database

[William Reinhardt]

Thanks for the info! I'll be sure the schema matches above. It's very 
likely I'm trying to mix schemas. Will let you know what happens.

On Wednesday, November 10, 2021 at 7:07:02 PM UTC-5 tke...@gmail.com wrote:

> How a database schema is specified changed in V4.0. The newer 
> wview_extended schema uses the new way, the older wview schema uses the old 
> way. My hunch is that you're mixing the new way and the old way. 
>
> Take a look in the [[wx_binding]] section of weewx.conf. You want either:
>
> # Old way, using wview schema
> [DataBindings]
>
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.wxmanager.WXDaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview.schema
>
>
> # New way, using wview_extended schema
> [DataBindings]
>
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
>
> If you're using the older wview schema, make sure the manager is set to 
> weewx.wxmanager.WXDaySummaryManager. Then, use wee_database to drop, then 
> rebuild the daily summaries.
>
> -tk
>
>
>
>
> On Wed, Nov 10, 2021 at 3:45 PM William Reinhardt  
> wrote:
>
>> Hello all,
>>
>> Back in July, I successfully added a couple new observation types 
>> ("appTemp" and "cloudbase") to my SQLite database by following these 
>> instructions:
>>
>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>
>> Inexplicably, the "archive_day_wind" table was missing afterwards! The 
>> other wind-related tables ("archive_day_windDir", "archive_day_windGust," 
>> etc.) are still in the database, just the "wind" table is missing. I'll 
>> post the Debug errors from the syslog at the end of this post. Let me know 
>> if you need more. It also shows up on my weather station website at 
>> www.woodvilleweather.com. In the "Weather Records Snapshot" section, the 
>> Average and Highest Wind data show as $day.wind.avg, $month.wind.avg, 
>> etc., with similar errors since July 2021 in the Reports page. I verified 
>> the absence of the table using a SQLite database viewer to open old 
>> database backups from before and after I added the observations in July.
>>
>> My question is: how can I regain the wind table? Is there a wee_database 
>> command to add this table? Add a new observation type and call it "wind"? 
>> Copy-paste from a backup database and rebuild the daily data? My weather 
>> station stores no data so I can't get it from there. It's been a busy 
>> summer and I'm now just getting time to play with this and get my WEEWX box 
>> working 100% again. Thanks for any ideas.
>>
>> -Bill
>>
>> *Debug info:*
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.max
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.maxtime
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.gustdir
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.avg
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.vecdir
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.vecavg
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day.wind.rms
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $week.wind.max
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $week.wind.maxtime
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $week.wind.gustdir
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $week.wind.avg
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $week.wind.vecdir
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $week.wind.vecavg
>> Nov 10 18:30:30 WX_WS1 weewx[29868] DEBUG weewx.cheetahgenerator: 
>> 

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

[Jens-Jørgen Kjærgaard]

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 
>> another console, no change.
>> ?
>>
>

-- 
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/5af1a2a6-0485-4723-883d-17ccf5ded215n%40googlegroups.com.

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

[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 another 
> console, no change.
> ?
>


-- 
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/38370c31-d681-4268-aab2-bd467fbb70e0n%40googlegroups.com.

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

[Jens-Jørgen Kjærgaard]

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 another 
 console, no change.
 ?

>>>

-- 
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/072bcc96-2287-4b66-94b9-5b65218b4519n%40googlegroups.com.

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

[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 another 
>>> console, no change.
>>> ?
>>>
>>

-- 
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/18ea2966-da94-430b-9139-0b39bbe1c744n%40googlegroups.com.

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

[Jens-Jørgen Kjærgaard]

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 another 
>> console, no change.
>> ?
>>
>

-- 
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/6d7b6aa8-5ab8-46de-9f8b-3cb617699311n%40googlegroups.com.

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

[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 another 
> console, no change.
> ?
>


-- 
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/a11c9cba-6403-4ec7-a499-df19d323363bn%40googlegroups.com.

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

[Jens-Jørgen Kjærgaard]

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 another 
 console, no change.
 ?

>>>

-- 
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/38b66511-c4f2-4bd2-b296-b8833f884571n%40googlegroups.com.


mylog
Description: Binary data