I did a fresh installation of HA on my RPi3. When I wanted to install Z-Wave as per this guide, it failed at step git checkout python3. It gives this error…
error: pathspec ‘python3’ did not match any file(s) known to git.
so I ignore it and continue on to PYTHON_EXEC=$(which python3) make build and sudo PYTHON_EXEC=$(which python3) make install.
When I restart my HA, I see this in the frontend.
In the log, it shows…
ERROR (MainThread) [homeassistant.setup] Error during setup of component zwave
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/homeassistant/setup.py", line 192, in _async_setup_component
None, component.setup, hass, processed_config)
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/zwave/__init__.py", line 253, in setup
CONF_CONFIG_PATH, default_zwave_config_path))
File "/usr/local/lib/python3.4/dist-packages/openzwave-0.4.0.31-py3.4.egg/openzwave/option.py", line 82, in __init__
libopenzwave.PyOptions.__init__(self, config_path=config_path, user_path=user_path, cmd_line=cmd_line)
File "src-lib/libopenzwave/libopenzwave.pyx", line 676, in libopenzwave.PyOptions.__init__ (src-lib/libopenzwave/libopenzwave.cpp:10136)
libopenzwave.LibZWaveException: "LibOpenZwave Generic Exception : Can't find config directory /usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config"
I browse to /usr/local/lib/python3.4/dist-packages/ and true enough, libopenzwave-0.3.1-py3.4-linux-armv7l.egg directory is missing.
It is not pre-installed in hassbian. If you installed hassbian, you should be able to SSH into the pi and there is a script to run to install open zwave. Please see here: https://home-assistant.io/docs/hassbian/customization/
Hassbian is the “image” install, where you image an SDcard and then just plug the PI in and it installs the OS and HA. You would then have to install Openzwave, Samba from a script. https://home-assistant.io/docs/hassbian/customization/
The AIO or all in one installer on the other hand makes you install Jessie OS onto your PI, and then use the all in one installer. That does install OpenZwave, but it forces you to install Jessie, first.
It is easy to get both installs confused, but the hassbian image is the easiest for people just starting out.
In this case it’s because you are using the user pi, but the git archive was likely downloaded using the homeassistant user account. You need to change user, and probably activate the virtual environment first.
But is it really? I started out never having touched a Pi in my life and if I ever had to do an new install, I would definitely go with AIO. Even with zero Pi and very little Linux experience I found the install to be pretty easy. This was pre-December 2016, so I’m not sure if that still holds true.
Hassbian installs seem to generate so many more issues in the forums and the HA subreddit.
I am happy with the product in general, but I am aware that it takes a great deal of attention and patience, sometimes… As a person who uses HA and reads the posts here, I appreciate the contribution of you and others who try to get everyone they help they need.
Thanks i think now i am using right account, but face a error: pathspec ‘python3’ did not match any file(s) known to git.
(homeassistant) homeassistant@hassbian:/srv/homeassistant/src $ cd python-openzwave
(homeassistant) homeassistant@hassbian:/srv/homeassistant/src/python-openzwave $ git checkout python3
error: pathspec 'python3' did not match any file(s) known to git.
(homeassistant) homeassistant@hassbian:/srv/homeassistant/src/python-openzwave $
Ok here is what Im doing using his suggestions. If you followed what he said without re-compiling openzwave, you probably had the same response as I did when running the last 2 commands. There were done very quickly which i am assuming did not re-compile. So here is what I did and am doing at the moment. I ran “make clean” without the quotes to clear the other build of openzwave and i am now running the commands in order. It is re-building openzwave, hopefully under the older version as I type this. I will have updates for you guys shortly
i think now i am using right account, but face a error: pathspec ‘python3’ did not match any file(s) known to git.