If you have the updated version your ozw_log.txt will show version 1.5.xxxxxx
Yep it did not update to the developer version. I have UN-installed and re-installed again and it is still the same result. Is there any other steps I may be missing then?
Try uninstalling pyozwman and pyozwweb as well, then reinstall python-openzwave.
I tried un-installing them but it tells me the requirement is not installed.
I get the whole open source its done when its done aspect of it, but has anyone heard any rumblings on the next official update of Open Z wave which might support this device out of the box?
Guy’s I am back. Sometimes life gets in the way of hobbies. And as @gregg098 I understand open source it’s done when it’s done. And I know life gets in the way of the OZW guys. I really can appreciate that.
Look at how fast HA is growing, since HA has hitch it wagon to the OZW, are there any HA developers who could help out the OZW community?
Back to draining the swamp. I switch to HASS.IO and I know zero about it. Of course I did not know that much about Hassbain either.
There are two major fixes that need to work before I can put HA into production at the house.
First and the big one, I been waiting on is broadband. Right now I have is cell for internet and I am so far behind private IPs I can’t see the light of day. Major providers say our city is not dense enough to make it worth their while. There are lot’s of people just a big area. So the city took on the project of bring fiber to the home. So my city utility bill has water, sewer, trash, and gas on it. Now it will have a new one “internet”. My house may be turned on by Thanksgiving. 
Second is when this is fixed.
So, can I fix Hass.IO or do I just wait? Just had a thought, could Hass.IO have an options to use the beta OZW?
2 Likes
Sign me up for that. I bought the Lowes version of the Linear garage door opener when I saw it on sale earlier this year. It’s installed, just unplugged waiting for the next OZW release. I tried patching Hassbian and could never get it to work. For now I’m on Hass.io and would love to be able to just install the beta version.
By design, hass.io is very limited at this point. It isn’t something that can be easily modified. If there isn’t an installable module for something, then it isn’t possible. If you want or need something not on the menu, best to stick with some of the other install methods.
I was on Hassbain, just wanted to play with Hass.io
@chilicheech was working on a dockerfile. Again, new to Hass.io so what I am saying maybe easier said than done, if I understand right that dockerfile can be published in such a way as to be able to apply it.
Does this sound right or am I way off?
Today, in Hasbian, it is a simple one liner to install the developer version and be up and running. In Hass.io it would require time and development effort. That effort would be for naught once OZW was updated. ??? Wouldn’t peoples efforts be far better directed at something with a little wider appeal and something that didn’t"t have a simple alternative solution?
I think @chilicheech has a docker built, so that much is done. The magic for me is putting the dockerfile into the correct repository for hass.io.
More than likely it’s my fault, but since around version .44 I could not get the developer version to load and I did have it working on Hassbain before.
Setting aside the “simple alternative solution” for a second, how many devices does the barrier issue affect? I guess if it is just this one garage door opener, then I would agree. But doesn’t it affect door lock also?
To be honest, I am about to give up on GoControl and have started looking at the OpenGrage door project. I had a ESP8266 dev board laying around and did some basic hello world testing. Enough that I order the parts to build 2 of them. While I wait on the slow boat from China, My next test is to try and fire up the HA component.
I had the sonar pieces laying around, because I had an idea of using a PI3 to see if a car was in the garage. The OpenGarage kills two birds. The sonar tells if the door is open and if a car is present.
Well, don’t expect everything to be rosy with a docker image based on the development version. The development version changes rapidly. I have had to implement the dev version in a separate HA instance because some devices either no longer work or work differently. Have fun.
I hear you.
I hear you also …
That’s why I am dumping zwave if I can get the wifi open garage door. The biggest question I have now is it’s security. But that will be for another thread. 
All I was trying to get across is that a docker image is unnecessarily constraining in a situation that clearly calls out a need for customization.
Let’s see if I understood this huge thread. To get this to work, you would need to build a dev variant of openzwave. In addition, Docker doesn’t contain that version of openzwave.
As for me, I am running HASS on Synology. I tried quite a bit to build openzwave on it and failed. Looks like I am missing some usb-dev header. Anybody was able to build openzwave on Synology that I could pick his brain?
As far as I’m aware, you are correct. Waaay back up there towards the top of the thread I posted a solution but admittedly even I haven’t bothered with it since I had to re-create my Z-Wave network (after the HASS renaming and then again when my Z-Wave stick was reset by accident). I can confirm though it does work. Why it’s taking so long to get a solution into mainline I don’t know though 
I ran this twice after uninstalling python_openzwave, pyozwman, and pyozwweb (and removing the dirs from /home/pi/homeassistant/lib/python3.5/site-packages and after starting HA I’m still seeing
2017-12-21 02:03:45.220 Always, OpenZwave Version 1.4.2586 Starting Up
any ideas what I can try next?
Did you do that inside your virtualenv?
yes. I’ve done it twice now and both times get. 1.4.xxxx. do you happen to know how i can get python_openzwave to build from a local copy of open-zwave? Every time I try the dev flavor
dev : for python_openzwave developers. Look for openzwave sources in a local folder specified by the LOCAL_OPENZWAVE environment variable (defaults to 'openzwave').
I get an error saying openzwave not found even though I set LOCAL_OPENZWAVE to the path of my openzwave folder containing the source.
Re-remove the packages in your virtualenv: pyozwman, pyozwweb, python_openzwave and openzwave
Also check for a file libopenzwave.cpython-35m-arm-linux*.so and remove that file as well.
Then give
pip3 install 'python_openzwave==0.4.0.35' --install-option="--flavor=ozwdev" or
pip3 install python_openzwave --install-option="--flavor=ozwdev"
another shot.
It should take a bit to install due to compiling.