Mark, I didn't understand your sentence, "The pip install instructions said to use "sh ~/weewx-data/scripts/setup-daemon.sh". I couldn't run this because weewx-data is in the .env folder, not in root."
What is the ".env" folder? Is that where you put your virtual environment? This is normally called "weewx-venv", but calling it ".env" is OK. Just need to clarify what it is. Assuming it is your virtual environment then, yes, buried deep within, it contains a directory weewx_data. But note the underscore, instead of a hyphen: it's "weewx_data", not "weewx-data". This directory is used as the raw materials when creating a station. It is not intended to be used by the end user. Instead, commands such as "weectl create station" take its contents and massages them for your specific environment, then puts them in a final resting place. One of these contents is "setup-daemon.sh", which normally ends up in "~/weewx-data/scripts". If you run "setup-daemon.sh" directly out of the virtual environment I would not be surprised that you get unpredictable results. Anyway, to summarize, there are two key questions: 1. Is ".env" your virtual environment? 2. Did you run "weectl station create"? -tk On Mon, Jun 24, 2024 at 6:48 PM Mark Hahn <m...@hahnca.com> wrote: > > What are 'all' the commands you executed ? > Are you serious? I've been working on this for hours. > > > You should not need to 'change the location inside that script' if you > are following the instructions correctly. > I followed the pip install to the letter. See the commands I listed post > before last. > > > are you installing v5 pip on a clean no-weewx system ? > Read the thread. I took michael.k's suggestion. > > > are you upgrading a v4 setup to v5 pip ? > Read the thread. I said "I installed weewx long ago (10 yrs?). It is > version 4.10.2" > > > are you upgrading a v4 dpkg to a v5 pip ? > The subject of the thread is "want to upgrade to 5.0, don't know original > install method" > > > People have done hundreds (thousands?) of pip installations by now. > And none had any problems. > > On Monday, June 24, 2024 at 6:14:39 PM UTC-7 vince wrote: > >> Mark you're going to have to be much less concise please. What are >> 'all' the commands you executed ? What does the output look like end to >> end ? >> >> What exactly are you doing ? >> >> - are you installing v5 pip on a clean no-weewx system ? >> - or are you upgrading a v4 setup to v5 pip ? >> - or are you upgrading a v4 dpkg to a v5 pip ? >> >> You should not need to 'change the location inside that script' if you >> are following the instructions correctly. You have to be doing something >> different or missing a step or several. People have done hundreds >> (thousands?) of pip installations by now. >> >> Lets take a step back and please tell us where you're starting, what >> you've done step-by-step, and what each step's output looked like. >> >> >> On Monday, June 24, 2024 at 5:26:07 PM UTC-7 Mark Hahn wrote: >> >>> I did ... >>> # Create the virtual environment python3 -m venv ~/weewx-venv # >>> Activate the WeeWX virtual environment source ~/weewx-venv/bin/activate # >>> Install WeeWX into the virtual environment python3 -m pip install weewx >>> >>> On Monday, June 24, 2024 at 5:23:27 PM UTC-7 Mark Hahn wrote: >>> >>>> > Activate the venv first >>>> I followed the pip instructions carefully so I'm 99% sure I did "source >>>> ~/weewx-venv/bin/activate". >>>> >>>> On Monday, June 24, 2024 at 5:04:16 PM UTC-7 vince wrote: >>>> >>>>> You used pip. Activate the venv first. Always. >>>>> >>>>> On Monday, June 24, 2024 at 5:01:38 PM UTC-7 Mark Hahn wrote: >>>>> >>>>>> As suggested I did a separate install using pip. It was very quick. >>>>>> "weectl device --clear-memory" fixed my davis problem. >>>>>> >>>>>> I decided to run the new 5.0. I copied over the conf file. I didn't >>>>>> need to copy the db file. Weewxd works great. >>>>>> >>>>>> But now I want to run it as a daemon. The pip install instructions >>>>>> said to use "sh ~/weewx-data/scripts/setup-daemon.sh". I couldn't >>>>>> run this because weewx-data is in the .env folder, not in root. I went >>>>>> to >>>>>> the weewx-data in .env and ran /setup-daemon.sh. I had to change the >>>>>> location inside that script to also use weewx-data in .env. >>>>>> >>>>>> The daemon install gave no errors but when I run "systemctl start >>>>>> weewx" I get this error ... >>>>>> >>>>>> /etc/systemd/system/weewx.service:12: Executable "WEEWX_PYTHON" not >>>>>> found in path >>>>>> "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" >>>>>> weewx.service: Unit configuration has fatal error, unit will not be >>>>>> started. >>>>>> >>>>>> Can anyone tell me how to fix this? Meanwhile I'll run in not as a >>>>>> daemon but obviously I've got to fix this. >>>>>> On Monday, June 24, 2024 at 11:49:27 AM UTC-7 michael.k...@gmx.at >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> I'd recommend you to leave your old installation untouched, install >>>>>>> weewx5 the pip way in a venv together with your extensions, a copy of >>>>>>> your >>>>>>> database and config and see if it works out. When the new installation >>>>>>> works as desired, just switch. >>>>>>> Mark Hahn schrieb am Montag, 24. Juni 2024 um 20:10:20 UTC+2: >>>>>>> >>>>>>>> I should say that I want to upgrade to get commands like "weectl >>>>>>>> device --dump". Are there equivalent commands in 4.10.2? I need >>>>>>>> those >>>>>>>> commands to follow instructions in " Troubleshooting the Davis >>>>>>>> Vantage station" page of wiki. My other post here about my davis >>>>>>>> troubles >>>>>>>> is at https://groups.google.com/g/weewx-user/c/DMByZT6hyFM. >>>>>>>> >>>>>>>> On Monday, June 24, 2024 at 11:05:06 AM UTC-7 Mark Hahn wrote: >>>>>>>> >>>>>>>>> I installed weewx long ago (10 yrs?). It is version 4.10.2. I >>>>>>>>> don't have any idea how I installed it. The is nothing related to >>>>>>>>> weewx in >>>>>>>>> my /root directory. The is no weewx directory in /home. >>>>>>>>> >>>>>>>>> Any ideas on how I should upgrade to 5.0? Also, are there >>>>>>>>> breaking changes from 4.10.2 to 5.0? >>>>>>>>> >>>>>>>> -- > 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/6416d428-0cc2-47f4-9b56-ee12f6e62a7en%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/6416d428-0cc2-47f4-9b56-ee12f6e62a7en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECgvXV5taKy%3Dex9aLB39wO9%3DNbEBCvihEaLZgtNXM-xqQ%40mail.gmail.com.
