Z-Wave AEOTEC USB Stick Error - where's my /dev/ttyACM0?

Configuration Z-Wave
1

I’m trying to get my zwave usb stick working but running into trouble for uncertain reasons. First of all, I see /dev/ttyAMA0 available but not /dev/ttyACM0 - it seems most everyone uses the second one so I’m curious if thats a problem.

I’m running a Raspberry Pi v4 w/usb 2 hub w/ AEOTEC USB stick. I followed the manual install on raspbian as documented here - https://www.home-assistant.io/docs/installation/raspberry-pi/

I suspect I don’t have enough info to troubleshoot. What should I do?

update, found this in the logs -

2019-09-18 06:14:18 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
2019-09-18 06:14:18 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/zwave/__init__.py", line 875, in _finalize_start
    network.set_poll_interval(polling_interval, False)
  File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/network.py", line 894, in set_poll_interval
    self.manager.setPollInterval(milliseconds, bIntervalBetweenPolls)
  File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/network.py", line 564, in manager
    raise ZWaveException(u"Manager not initialised")
openzwave.object.ZWaveException: 'Zwave Generic Exception : Manager not initialised'
type or paste code here

found this, wish me luck - https://raspberrypi.stackexchange.com/questions/47671/why-my-program-wont-communicate-through-ttyama0-on-raspbian-jessie

2

last log lines from the zwave controller -

2019-09-18 06:34:54.817 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-09-18 06:34:54.818 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-09-18 06:34:54.819 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-09-18 06:34:54.819 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-09-18 06:34:54.819 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-09-18 06:34:54.819 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-09-18 06:34:54.819 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-09-18 06:34:54.819 Detail,
2019-09-18 06:34:54.820 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-09-18 06:34:54.820 Detail, contrlr, Notification: DriverFailed
1 Like
3

/dev/ttyAMA0 is the RPi’s UART, it will never belong to an Aeotec Z-Stick plugged into a USB port.

The Aeotec will definitely be /dev/ttyACM0, or the preferred /dev/serial/by-id/usb-0658_0200-if00. I assume you’re aware of the Aeotec and RPi4 problem that requires the USB 2.0 hub, since you mentioned that specifically. Are you sure your hub is not the problem? People have been reporting compatible USB hubs here, are you using one of those? Try plugging it into a different port?

4

Referring to freshcoast post the alerts page which was introduced lately (in the previous release?).

5

What does dmesg tell you?

What does it tell you as you plug/unplug/replug the USB device?

6

Ah, I didn’t realize that only some (apparently random) set of usb hubs fix the problem.

I’ll also look into using dmesg. I had seen it referenced in some of the troubleshooting info but what I remember was in the form of ‘do this now you’ll see this’ and I wasn’t seeing what I expected. After a little more research its clear that I should see events related to the plugging and unplugging of the usb stick. I don’t think I was seeing that so I should start there.

7

…and everything is working if I just remove the power from my usb hub. Thanks!

1 Like