It is in the FAQ at https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-command-not-found-when-i-type-weewx-commands but perhaps buried a bit.
If you put everything into bin/user and remove your shebang lines all the python scripts should probably work ok. If you could rewrite your bash scripts into python that would probably help but I'm not 100% certain that is necessary. I don't really understand your skin enough to know for certain. You will need to pip3 install any additional modules into the venv as part of your instructions. You seem to use quite a few added modules in your python scripts. On Sunday, July 14, 2024 at 12:41:12 PM UTC-7 Karen K wrote: > Tom Keffer schrieb am Sonntag, 14. Juli 2024 um 21:24:24 UTC+2: > > On Sun, Jul 14, 2024 at 12:13 PM Karen K <[email protected]> wrote: > > I read a little bit through the pip installation guide > <https://weewx.com/docs/5.0/quickstarts/pip/>. There all calls of weectl > are preceded by "source ~/weewx-venv/bin/activate". Could it be, that for > installing extensions this is necessary, too? > > > Absolutely. Sourcing the "activate" file nominates the Python interpreter, > the Python runtime library, and the WeeWX code that is to be used. > > > So I will have to update all the installation instructions of my > extensions to reflect this requirement. > > Would it be an idea to mention that there > <https://weewx.com/docs/5.0/utilities/weectl-extension/>? > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2dbf776b-7b3b-446a-9f43-144de1f60374n%40googlegroups.com.
