Thanks again to @josh and @m00dawg as their info was invaluable. Same goes to AndrewL.
For those still struggling with the Linear GCZ004 and getting OZW to work with it, I’ll share how I finally got mine to work. Keep in mind that I’m a noob and have no clue what I’m talking about and whatever I say may in fact break your machine.
Since you’re still reading this, it’s safe to assume HA is not seeing your Linear as cover element. The key point is that even though you can open your garage door via OZWCP it does not necessarily mean OZW is set up properly so that HA can see it. m00dawg’s comment on this was quite helpful to me as it led me on the correct path.
So if you’ve read my previous posts, I pretty much screwed up the installs for OZW and OZWCP. It was a combination of being new to Linux and trying to follow directions randomly around the interwebs. Keep in mind, this worked for my set up, which is installing HA to virtualenv as detailed here. (I’m starting here bc I assume most people
have already installed OZW)
So now you’ve got a service account (hass), HA, and Python-OZW installed on virtualenv. Next is the install of OZWCP. So my f#ck up is following the instructions on this site without considering that what I did previously. Don’t make the same mistake I did. Here’s a modified version of what you should run if you went the virtualenv route like I did. First, open a 2nd terminal window (you’ll want the previous one where you’ve activated the virtualenv and as hass). In the 2nd terminal window:
Download, build and install libmicrohttpd (this part should still be fine, I never had to redo this part)
cd
wget ftp://ftp.gnu.org/gnu/libmicrohttpd/libmicrohttpd-0.9.19.tar.gz
tar zxvf libmicrohttpd-0.9.19.tar.gz
mv libmicrohttpd-0.9.19 libmicrohttpd
cd libmicrohttpd
./configure
make
make install
Now switch back to the 1st terminal window where you command line starts with (hass)$…
If you left off at the end of the building the virtualenv and installing Python-OZW, you should be in /srv/hass/src/python-openzwave. Go back up a level to /srv/hass/src
Download open-zwave-control-panel
cd
git clone GitHub - OpenZWave/open-zwave-control-panel: UNMAINTAINED - We are looking for someone to maintain ozwcp! The OpenZWave Control Panel (ozwcp for short) is an application built on the OpenZWave library that permits users to query, manage and monitor Z-Wave nodes and networks. It provides a web based user interface using AJAX principles.
cd open-zwave-control-panel
Now a tweak to modifying the Make file.
Open the Makefile and find the following lines:
OPENZWAVE := …/
LIBMICROHTTPD := -lmicrohttpd
Change it to:
OPENZWAVE := /srv/hass/src/python-openzwave/openzwave
LIBMICROHTTPD := /usr/local/lib/libmicrohttpd.a
We also need to uncomment the Linux lines and comment out the Mac lines in the Make file as follows since it is setup by default for Mac:
# for Linux uncomment out next three lines
LIBZWAVE := $(wildcard $(OPENZWAVE)/*.a)
LIBUSB := -ludev
LIBS := $(LIBZWAVE) $(GNUTLS) $(LIBMICROHTTPD) -pthread $(LIBUSB) -lresolv'
# for Mac OS X comment out above 2 lines and uncomment next 5 lines
#ARCH := -arch i386 -arch x86_64
#CFLAGS += $(ARCH)
#LIBZWAVE := $(wildcard $(OPENZWAVE)/cpp/lib/mac/*.a)
#LIBUSB := -framework IOKit -framework CoreFoundation
#LIBS := $(LIBZWAVE) $(GNUTLS) $(LIBMICROHTTPD) -pthread $(LIBUSB) $(ARCH) -lresolv`
At this point you should I’m going to PAUSE on building OZWCP bc we need to patch them per @Josh’s post from July 27th (please scroll up for his post and follow links for patching). If you’re Linux savvy this part is a breeze for you. If you’re like me, I had no clue how to patch the files. I believe I got the patch for OZWCP to work using curl and I kept getting errors for OZW and also didn’t know how to patch Python-OZW via that link. So from the Github pages modified the files manually, which was not too bad since OZW was modifying 2 files and creating 2 new files. OZWCP was just modifying the 1 file. For the OZW patch, since I had Python-OZW the file locations were from here /srv/hass/src/python-openzwave/openzwave/ on down. File path for OZWCP is /srv/hass/src/open-zwave-control-panel/
Now that the files are set, we go back to the terminal window with our virtualenv activated
cd -
cd python-openzwave
PYTHON_EXEC=`which python3` make uninstall
PYTHON_EXEC=`which python3` make build
PYTHON_EXEC=`which python3` make install
Ok, I’m not sure if it was all necessary but that’s how I finally got it to work…so don’t judge me! Next we’ll go back to building OZWCP that we never finished.
cd –
cd open-zwave-control-panel
make
Now if you want to do the symlink, then you’ll want to change the path as follows:
ln -sd /srv/hass/src/python-openzwave/openzwave/config
At this point, reread your node or remove/re-add in OZWCP, and save your xml’s. Then copy them to your .homeassistant folder and cross your fingers.
But beyond that, curious why the OZW folks aren’t pushing in the changes. I have a similar problem with the ‘radiotherm’ library. Not HA’s fault but it definitely impacts the project I think.
