if only it was that easy
worked when I updated my python venv from 3.4 to 3.5
also for what its worth - if anyone new to HA is reading this I used an automation with the MQTT payload as a trigger. The switch on the relay only sends âonâ payload to MQTT (whereas it will toggle the relay). So i had a challenge where the binary sensor i created for the switch would go on and stay on for a period of time (didnt pass the wife test). so I instead used this. when a switch is pressed âonâ is sent. I then turned the âonâ into a toggle to control the hue lights and my goodness is it quicker than wink + hue.
- alias: "Relay 1 Upper switch"
trigger:
platform: mqtt
topic: "Relay1/switches/upper"
payload: 'on'
action:
- service: light.toggle
entity_id: light.hue_light_group
Sorry for being dim, or rather not patient at this point to try and comb through everything. Can someone put together a quick summary/write up of the steps for a new hassbian user? Iâve been using HA from docker and with hass.io and I just moved over to hassbian and I would really like to give this a try but the information is kinda all over the place and Iâd rather not have to reflash
This finally worked for me! hass=65.6 python=3.6
cd /home/homeassistant/.homeassistant
sudo systemctl stop [email protected]
sudo su -s /bin/bash homeassistant
source /srv/homeassistant/bin/activate
cd /home/homeassistant/
git clone https://github.com/ryanwinter/open-zwave.git
chown -R homeassistant /home/homeassistant/open-zwave
pip3 install cython wheel six
pip3 install âPyDispatcher>=2.0.5â
pip3 install --upgrade cython==0.24.1
pip uninstall -y python_openzwave
sudo export LOCAL_OPENZWAVE=/home/homeassistant/open-zwave/
pip3 install python-openzwave --install-option="âflavor=dev"
exit
sudo nano /srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/zwave/init.py //update the requirements to 0.4.4
sudo systemctl start [email protected]
Now you can add your garage door using âadd node secureâ. Ensure you have removed it if not already before adding. You know itâs working if cover.xyz shows up under states.
Note: You will need to edit your init.py file after each upgrade. Before you start Hass after the upgrade, edit the init.py and update the requirements to 0.4.4, then you can start Hass safely without losing barrier support.
I will try this, not to get the garage door to open, but to get support for a HVAC z-wave adapter that requires command class âThermostat Setpoint V3â and âThermostat Fan Mode V3â:
Systemair / Villavent Z-Wave adapter
Support for this has been added in the dev-branch of open-zwave.
@baardpt The previous post by @ttaidapos is NOT using the dev branch of openzwave. It is using a patched copy of the current openzwave. Eliminate the git and export lines.
Thanks for pointing that out, I thought I would attempt to use this instead
git clone -b Dev https://github.com/OpenZWave/open-zwave.git
I have compiled it already and it runs on my Ubuntu, at least MinOZW runs. I tried to link it with domoticz just to test, but that failed. Now I wanted to try running hassbian with the open-zwave Dev branch⌠anyone tried that already?
You shouldnât need to clone anything locally. @firstof9 has posted a one-liner Linear NGDZ00-4 Garage Door
You will need to uninstall the current ozw etc.
This might work for some distroâs, but the current dev branch doesnt build on freebsd
You are on FreeBSD? Havenât used BSD of any flavor in quite a while.
Well Iâm actually running freenas, so not freebsd directly
anyone updated to 0.65.6 - my cover just disappeared. its not coming up as unknown though. Its showing up as a binary_sensor now as a node entity.
in the values:
EDIT - just ran through the process from @ttaidapos Linear NGDZ00-4 Garage Door
seems the HA upgrade put 0.4.3 back (saw that during the uninstall) so putting the dev version 0.4.4 seems required.
FYI did need a HEAL to show the cover again
I managed to install hassbian 0.65.6 with a local clone of the Dev branch of OpenZwave. Got it running now and the OZW log shows Iâm running OpenZwave Version 1.5.3101. It seems to be quite stable. I used the instructions from @ttaidapos above, except the git clone statement that I replaced with the dev branch of openzwave.
Now, that didnât solve my problem, I still cannot control my HVAC thermostat. HomeAssistant doesnât seem to set up things correctly, I get 3 entries for the HVAC in the GUI. Probably the output from the command class ThermostatSetpointCmd_CapabilitesGet is not recognized, being new in v3, it actually returns the min and max temperature range for the setpoint. Both min and max values returned are incorrect, but I think I will take this problem to the open-zwave forumâŚ
Your device may not yet have included support. Check the database. http://www.openzwave.net/device-database
If it isnât in the database, you should report it to the open-zwave forums.
No, itâs not present in the openzwave library, but I was hoping it would be supported as-is⌠but that doesnât seem to be the case. Iâve been in touch with someone who has made it work in OpenHAB, they have their own database and this device was added there. However, I cannot make mine work with OpenHabian. There could be a difference in firmware? Iâve looked at the code and OpenHab has not implemented support for version 3 of the command class thermostatsetpoint either.
If the correct command class is implemented in open-zwave, then you can usually fudge things with the manufacturer specific xml file for your device. If it has been made to work in OpenHAB get the xml file and add it to the appropriate location in HA. By working with the open-zwave folks, you should be able to get the xml file included in furure updates.
Yes, I started doing that. Iâve added the configuration parameters by editing the files in python-library, however, Open-Zwave doesnât actually read these parameters from the device. There are some read only parameters that gives system information, such as HVAC ID-number, number of days since last filter change etc., but the z-wave config panel just shows 0. In OpenHab, the correct parameters are shown⌠very tempting to drop Homeassistant now and see if the OpenHab team can help