"wee_device" not working after new install

[Christian Nimmervoll]

Hello,

I've run WEEWX on an existing Raspberry and installed a new one today.

Everything works so far on the new device again without problems.

Only one function doen't work...

wee_device works without problems on the old device but wee_device is not running on the new device.

I get the error message: "command not found".

In the weewx.conf the station_type is entered correctly:

station_type = Vantage

And the new Raspberry communicate also without errors with the Davis VP2 Console.

What can be the reason that the function: "wee_device" is not working?
Is there another important setting in the software?

Thanks for infos.
Chris

[Christian Nimmervoll]

For an example:

On the old Device I a get an answer when i type this:
wee_device --help
On the new install - i get only the erros message - not found...

[Leon Shaner]

Christian,

 What happens if you change to the /usr/share/weewx/bin dir an run it as:

$ ./wee_device --help

Or use the fully-qualified path?

$ /usr/share/weewx/bin/wee_device --help

By default the current path (.) is not in your PATH environment variable.

You may have changed that in user pi's "dot" files on the RPI where things are working (~/.bashrc, ~/.bash_profile, /etc/bash.bashrc, ~/.profile, /etc/profile, etc.).

It's better to leave the current path (.) out of your PATH for security reasons and always pretend ./ to the command or use the fully-qualified path to the exec/script.

You can "simulate" the "not found" using any command that doesn't exist.  For example,

$ oog

-bash: oog: command not found

Don't forget if you're running from pkgs, most weewx commands need to be prefaced with sudo.

Other than that, I would use "sudo apt list --installed" on each RPI and then diff the outputs to see what packages you are missing.  Seems unlikely that you are missing python, but that's wee_device is using:

 $ head wee_device

#!/usr/bin/python

If you don't have /usr/bin/python then that would explain a lot, but it would also be surprising to me that an RPI could function without it.  ;-)

Regards,

\Leon

--

Leon Shaner :: Dearborn, Michigan (iPad)

On Jul 7, 2019, at 9:37 AM, Christian Nimmervoll <christian....@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d5efbb2c-80fd-45ba-80c6-9c8e9eefba11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Christian Nimmervoll]

Great!

In your answer i found the solution.
I made a weewx installation via setup.py.
All is found in my case in /home/weewx....

So i changed the directory in the command line to /home/weewx/bin

and when i type:

wee_device --help

--> i get the error again.

but when i type:
./wee_device --help

--> it works! :)

so i'm no linux profi but the "point" make the different.

When i try this on my old raspberry, the "." isn't important.
It works everywhere...

Should i change the path?

Thanks a lot for yout tipp!
Chris