RPi 2 Model B + Aeotec USB = Useless?

Installation
1

I’ve had no success with anything involving Raspberry Pi’s, Aeotech Gen 5 USB, and HASS.

Ultimately, on the attempts I get HASS to open without issue, I’m brought to the inability to properly configure ZWave.

Just curious what works right now? I very well may be the dumbest user on the planet, but I figured I’d see more users experiencing issues with the Hassbian image, but I really don’t, or they’re not vocal. The AIO issues as well, I see more experiencing problems in that realm but I ultimately still run into this Zwave issue. Nonetheless, I’d love to hear some success stories.

Any advice and/or direction would be great.

On the verge of just buying the Pi 3 and waiting for the next version the AIO.

If you’re interested, here’s a post I made a couple days ago with more detail:

2

Hello thats the zwave i use on my pi3 work perfect. did you put the correct patch? Note i think the path change base on your configuration…

zwave:
  usb_path: /dev/ttyACM0
3

Mine works perfectly as well and I am on a RPi3 with the AIO installer

### Aeotec ZWave Z-Stick Gen 5 ###
zwave:
  usb_path: /dev/ZStick
  config_path: /srv/hass/src/python-openzwave/openzwave/config
  polling_interval: 60000

There is a work-around for the issues with the AIO installer

4

What are you using the AIO on top of? Jessie Lite? Pixel?

Also, is the ZStick you have there, a reference you made? Or Might what I have, exactly what Jose wrote, not be correct any longer?

Thanks.

5

i did use this tutorial…

6

I am a hass newbie and setting up my Raspberry Pi 2b for the first time.

I am using an Aeotec USB Stick S2 Model DSA02203-ZWUS

I have configured as follows.

zwave:
  usb_path: /dev/ttyUSB1
  config_path: /srv/homeassistant/src/python-openzwave/openzwave/config
  polling_interval: 60000

Using the correct device
> pi@raspberrypi:/dev$ ls -l /dev/ttyUSB1

    crw-rw---- 1 root dialout 188, 1 Jan 21 19:35 /dev/ttyUSB1

But I just get invalid config when I visit the dashboard.

Am I missing something ?
I have used the z-stick on a PC to install firmware to Aeotec devices so I know it worked last time I used it.

Any ideas on how I can debug this?

My install was done using this image

https://home-assistant.io/getting-started/installation-raspberry-pi-image/

Then I decided to upgrade to full install using this page

Getting started - Home Assistant

So basically I ran the install command against the pi image

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

UPDATE: Found issue in the log. Need to work on that. I thought the “all in one install” included the open zwave component.

17-01-21 19:38:02 homeassistant.components.zwave: You are missing required dependency Python Open Z-Wave. Please follow instructions at: Z-Wave - Home Assistant

UPDATE: Nope, still have the same issue. I rebuilt the openzwave git project and the resulting package contained the same files that were installed with the “all in one install”. I tried changing the config to point to the new openzwave package but same result. Still says in the log that it can’t be found.

7

Maybe you have a defect device? Mine works perfectly also. On both RPI2 and 3.

8

Yea, I was thinking that also but not sure how to test. It works fine on my Windows machine when I use the Aeotech firmware upgrade tool. But perhaps it has other issues.

Which model zwave stick do you have that is working?

I am also considering buying the zwave daughter card but it’s pretty pricy and I wanted to play with hass before I pull the trigger on that.

9

I decided to start over with my install. Last time I used the hass image and then upgraded it with the all in one. I think this doesn’t work correctly. The documentation is very confusing because it seems out of date. A lot of the references are incorrect in terms of names of paths etc.

Anyway, I started with a raw raspbian image and then installed the all in one image. Had to do it twice because it fails if you don’t change your pi user password before you start. That’s not documented.

I have it running now and I have zwave configured with
zwave:
usb_path: /dev/ttyUSB0

The error message that zwave isn’t configured correctly is gone now. But I can’t tell if the zwave stuff is working. I thought there was supposed to be a zwave config panel but I don’t see it.

So I have a few questions about this setup.

  1. documentation says I can restart hass using

$ sudo systemctl stop [email protected]

But there is no such service installed so I have to boot the pi to make it restart. Is there a way to restart hass with the all in one install ?

  1. The All in one install says it installs the Open-Zwave Control Panel but I don’t see it in the UI. Do I have to do something to configure it ?
10

It’s not in the UI, the details of where to find are covered here.

11

Totally missed that! OZWCP just didn’t realize this was short for the Open Zwave Control Panel. I thought it was something else I wasn’t ready to setup yet like MQTT…Doh… Thanks for bearing with me.