@penright Ok yourâs looks compiled without error except for the ozwcp, which isnât a big deal.
Step 0: Stop homeassistant
Step 1: cd /srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/zwave
Step 2: sudo nano __init__.py
Step 3: Line 40 make it look like this:
Step 4: CTRL X to save and close that file
Step 5: cd /home/homeassistant/.homeassistant/deps
Step 6: Here either rm -Rf * or try to find anything openzwave related and delete it (easier to rm -Rf *)
Step 7: Start homeassistant
HA should start re-downloading anything you deleted and start using the openzwave libs you compiled.
First, I found REQUIREMENTS in between the "from ⌠" and âCONF_âŚâ
First time I restarted hass looks like zwave did not load. I restarted and dropped down the node in the zwave section and watched it probed and waited till all showed completed.
Few notes:
Looks like all the zwave devices lost their names
I now see an entity cover. and itâs state is open, but if I go into the dev {{ states.cover.unknown_id014f_unknown_type4744_id3530_barrier_state_label.state }} it shows open but does not change when I move the sensor. The ozw log shows it is communicating without error.
AppDaemon should not be affected, may be a separate issue.
Now that you have the cover showing up, you should be able to link it in the GUI providing youâve replaced the zwave component files
They go in your /srv/homeassistant//lib/python3.4/site-packages/homeassistant/components/cover directory or /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/cover using AIO.
As for naming the device, you can do that via the zwave config to name your device, or just manually edit the ozwcache_xxxxx.xml file in /home/homeassistant/.homeassistant/ directory or copy your zwcfg_xxxxx.xml on top of it.
For me it was â_/srv/homeassistant//lib/python3.4/site-packages/homeassistant/components/cove_râ directory. Now the GUI seems to work and the cover widget for the dashboard.
Default setup for the widget seems pretty bla, I wonder what customizing can be done? Oh well thatâs for another thread.
Yes, please make some kind of documentation. I am have the same issue and I am not very good at using Linux so a detailed guide would be amazing to have for rookies like myself.
Not sure I understand the pros and cons to different methods.
Is there a file that Name = Node#. That way if Node# changes, I change that and all my entities work. Every time I remove/added the garage door opener, it got a new node number. I am going to have two garage door openers.
Edit:
Just tried the zwcfg_xxx.xml. Restarted (hassctl restart) and the node name did not change.
Youâll still have to get the dev version of Python_OpenZwave compiled, but itâll still be much easier than manually copying files around in homeassistant
I gave up and just bought a zwave dry contact relay and tilt sensor.
both together were cheaper than the linear GDO and WAY easier to get it to work. it was 15 minutes versus 3 or 4 days of trying everything over and over again and it still not working.
it especially made more sense to go with the cheaper/easier alternative since i realized if i ever get another newer style GDO, HA and linear wonât work with the security features of the MyQ systems (which most of the readily accessible ones seem to be) without a connection to the internet and a MyQ gateway (even more $).
hopefully one day this will get fully integrated for those who need it.
thanks @firstof9 for all the help tho. i guess my linux skills need A LOT more work to figure it out!
