New Pi 4 running bullseye with weewx 4.6.0b7
the generated webpage plots does not display Wind Vector, the file
"daywindvec.png" is there in "/var/www/html/weewx" folder
when looking into "index.html" with editor, I see no link to the file
"daywindvec.png"
any suggestion to bring back the Wind
Well, this is interesting.
On a lark, I tried running your command after sudo su -. Viola, no error
message. Also, I got the list you indicated above.
I then exited from sudo su and proceeded with the regular weewx
installation instructions.
All is right in the World!
Thank you very
I re-flashed and tried your suggestion.
Here is the result:
-bash: /etc/apt/trusted.gpg.d/weewx.gpg: Permission denied
On Thursday, November 11, 2021 at 3:38:22 PM UTC-8 vince wrote:
> update - if you haven't reflashed your system yet and it's still hosed up,
> can you try one thing for me ?
Perhaps it is (was) a GitHub transient issue. When I checked just now all
wiki home page links I tried came up just fine, this included a mix of
short form links, full GitHub wiki URLs and external URLs as well as the
ones Vince cited.
Gary
On Saturday, 13 November 2021 at 07:07:10 UTC+10
Looks like anything using a magical link without specifying a path is doing
this. If you check the first 'posting to weewx-user' link which works fine
you'll see that one specifies a full path to the file rather than relying
on github's wiki functionality to figure it all out.
This one works
Seen this for some time, been hopping it would correct.
Link to my hardware page (i2C sensors) keeps going to the home page, I use
the the drop down to get to the pages.
Not all hardware links have this problem but some do.
Neville
On Friday, November 12, 2021 at 11:09:31 AM UTC+10
Bit of a punt but do you have the è (e grave - lowercase e with grave
accent) character anywhere in the Ftp skin.conf or the [StdReport] [[FTP]]
stanza in weewx.conf or in the name/path of any of the files being ftp’d?
That will likely be the source of the utf-8 error.
Gary
On Friday, 12
I don’t know. It’s possible both loggers have corrupt station memory. It’s
not as unlikely as you may think, corrupt station memory is frequently
caused by power supply interruptions. If you are not reading archive
records from the logger you would never know you have the problem; the
console
