Hassbian Zwave Problems - RPi

Installation
1

Having some issues getting Zwave to work on Hassbian for the first time.

Hardware: Raspberry Pi 2 Model B

Upon first boot I did in this order:

Changed password

Sudo apt-get update
Sudo apt-get upgrade

reboot

I then updated Hassbian via the documenation as I read the setuptools needs updating from 5.5.1 to 32.0.1 off the fresh install

I granted HomeAssistant access to USB via:
$ sudo usermod -a -G dialout homeassistant

reboot

I then followed the documentation to equip Zwave:

First installing cython, then upgrading cython to 0.24.1, then building the open zwave not as root.
As I stuck with the ‘make install’ option, I presume my config_path should be: /srv/hass/python-openzwave/openzwave/config
(I can paste these exact steps, but I followed the Hassbian install page as-is)

Currently there are a few things plugged into my Pi:
Ethernet
Canakit Wifi adapter I never seem to get working unless there’s a gui.
USB dongle for Keyboard/mouse device
Aeotec gen5 zwave USB

Upon running the command: ls /dev/ttyACM*, I’m told my device is: /dev/ttyACM0.

The only modifications to the configuration.yaml is the copy and pasted ‘zwave:’ portion.

I’ve tried both with and without the config_path. In the instance I tried the config_path, it was the one mentioned above.

I know changes to the config.yaml file take as the password applied to the front-end after altering the file.

Here is my config file:

Name of the location where Home Assistant is running

name: Home

Location required to calculate the time the sun rises and sets

latitude: **
longitude: **

Impacts weather/sunrise data (altitude above sea level in meters)

elevation: 381

metric for Metric, imperial for Imperial

unit_system: imperial

Pick yours from here: http://e

time_zone: /

Show links to resources in log and frontend

introduction:

Enables the frontend

frontend:

http:

Uncomment this to add a password (recommended!)

api_password: K***

Checks for available updates

updater:

Discover some devices automatically

discovery:

Allows you to issue voice commands from the frontend in enabled browsers

conversation:

Enables support for tracking state changes over time.

history:

View all events in a logbook

logbook:

Track the sun

sun:

Weather Prediction

sensor:
platform: yr

zwave:
usb_path: /dev/ttyACM0

Home Assistant Log via these commands:
$ sudo su -s /bin/bash homeassistant
$ cd /home/homeassistant/.homeassistant
$ nano homeassistant.log

Returns an empty log.

If I try and run: hass --script check_config
I get:
Testing configuration at /home/homeassistant/.homeassistant
Then nothing.

Someone mentioned needing colorlog, but I can’t figure out how to get that installed standalone and Googling turned up a few ways that didn’t work. If I’m correct, when I first ran the check_config routine, it stated it was installing colorlog, but I never saw anything from there.

I’ve watched the majority of Bruh Automation’s YT channel also.

I’ve had no luck with anything Zwave/Aeotec USB related and HASS.

Any assistance is greatly appreciated.

If anyone has any recent success stories related to the RPi 2 Model B and either the Hassbian image, the AIO on top of Jessie Lite, or the AIO on top of Pixel, I’d greatly appreciate the steps you took to get up and running.

If there are any additional logs or information I can pull and paste, I will see to it ASAP.

Edit:

The error would be helpful:

2

I’m having similar problems. Did you get past this?

3

I haven’t had too much time to dive back in unfortunately. The few different things I’ve tried have come up empty.

I plan to update this thread if/when I get some time to hack at this again; hopefully this weekend.

Here’s another thread I posted: RPi 2 Model B + Aeotec USB = Useless?

The comments haven’t been much help there either but I figured I’d live it here just in case.

4

I’ve gotten through this as of last night.

Not really sure how, as I’m about 98% sure I did everything the same as last time.

This time I installed Jessie Lite. Had no luck with adding an ssh.txt file to the /boot/ to enable ssh, so I hooked up a peripheral and enabled ssh via command line, from there I also changed the password at this time.

I then did three update commands:
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install -y pprompt Not 100% sure what this one does, if anyone does, please share.

From there I ran the AIO with this one command:
$ wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && chown pi:pi hass_rpi_installer.sh && bash hass_rpi_installer.sh

The installer took nearly 2 hours. Upon finishing HASS was up and running, registered my chromecast, roku, and GHome by first login, per usual. I then copy an pasted the simple zwave config:
zwave:
usb_path: /dev/ttyACM0

Rebooted and did not get the same error as I have in the past. I then removed my Aeotec USB and synced it with a GE switch and it actually worked. I was stoked. I promptly went to bed but I’m happy zwave is communicating as it should be!

Let me know if you have any questions, I rushed this reply.

5

Had the exact same problem, trying your solution now!

6

Good luck. I’ve had lots of fun tinkering with all of this since zwave has been working.

I learned the issue with the ssh.txt file is that the file has to be extensionless. With Windows I did this by removing the .txt when naming the file; I think to do this you might have to have file extensions enabled. With the extensionless file named ssh, I was able to get ssh to work on boot with Jessie Lite on a Diet Pi project I started last night.

Let me know if there’s anything else I can help with.

7

This approach worked for me as well. I was having the same issue.

Thanks!