Z-Wave Controller/Devices not available in Hass (SOLVED)

Configuration Z-Wave
1
  • Hass 0.48.0 fresh install on Rasp Pi 2 using All-In-One install using the Virtual Env
  • Aeotec Z-Stick Gen5
  • Following BRUH Video (https://youtu.be/ajklDCaOGwY)

I run OZWCP Web App (Getting started - Home Assistant). I can initialize the z-stick and turn the switch off/on

Back in Hass, when I add zwave to config.yaml and reboot, No z-wave controller or devices in States screen and no zwave domain on the Service screen

Block in configuration.yaml

#Z Wave Controller
zwave:
  usb_path: /dev/ttyACM0
  config_path: /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.3-py3.4-linux-armv6l.egg/config/

Dumb Questions:

  1. Does it matter were in config.yaml I put the above block?
  2. Two spaces is ok when indenting the params under zwave:?
  3. Do I set config_path to the “egg” directory or “egg/config”
  4. Do I need to …
sudo su -s /bin/bash homeassistant
source /srv/homeassistant/homeassistant_venv/bin/activate

…before I update config.yaml?

Any help would be greatly appreciated

1 Like
2

Follow-up…might not be related
After each restart…and I’ve been restarting a lot…I get the following in teh log

WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=18 from 2017-07-03 21:52:12.861072)
WARNING (MainThread) [homeassistant.setup] Setup of sensor is taking over 10 seconds.
WARNING (MainThread) [homeassistant.setup] Setup of tts is taking over 10 seconds.

If I put zwave: by itself or with some configuration, Hass will not start

3

Figured it out.

Executing sudo systemctl status home-assistant.service -l repeatedly, I could see what the hass process was doing on startup. It was building the zwave service.

Once all the make stuff completed (took about 35 minutes on my Rasp Pi B) then my zwave controller and devices appears on the States screen on Hass.

Patience is not only a virtue, it is required here

1 Like